|
| | | Forum Guru
 
Group: Forum Members
Last Login: 11/6/2008 11:08:25 AM
Posts: 67, Visits: 143 |
| | When I receive the 6.1a CD, I assume I will build a 6.1a netsetup in the traditional way. Do I then place that in my shared NETSETUP folder? I have added the 6.1a patch to it. Will that cause any kind of version conflict? Will Point try to "upgrade" itself when a 6.1a native build replaces the 6.1 build w/6.1a patch? |
| |
| | | 
Sepal
Group: Moderators
Last Login: Today @ 10:28:02 AM
Posts: 1,183, Visits: 9,260 |
| You can follow these instructions for the patch release. You will not need to do anything with the point 6.1a cd they are the same thing(except the netsetup "point admin" install corrected some possible data loss issues).
Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.  |
| |
| | | Forum Guru
Group: Forum Members
Last Login: 11/6/2008 11:08:25 AM
Posts: 67, Visits: 143 |
| except the netsetup "point admin" install corrected some possible data loss issues). That's precisely why I have to roll out the 6.1a netsetup. The 6.1 netsetup adds a "|" character to the end of the PNTDATA folder path every time, and removes "L\" from the end of the PNTTEMPL path about 50% of the time. Automatically updating to 6.1a is good, but it's not a solution if I still have to edit the winpoint.ini file after every installation. And please don't suggest that I fix YOUR mistakes with a login script. |
| |
| | | Forum Guru
Group: Forum Members
Last Login: 11/6/2008 11:08:25 AM
Posts: 67, Visits: 143 |
| | So back to my question: Can I just create netsetup with 6.1a and copy it into my current share? One of my 6.1 users was updated to 6.1a by the netsetup folder. This is a user who lost both her Primary data folder and her templates folder due to Netsetup damaging the winpoint.ini file. I had fixed both problems by editing winpoint.ini. After the upgrade to 6.1a both directives were damaged again, so again I fixed them. When she restarted Point it prompted her to install 6.1a AGAIN and AGAIN it damaged the winpoint.ini file. |
| |
| | |
Sepal
Group: Moderators
Last Login: Today @ 10:28:02 AM
Posts: 1,183, Visits: 9,260 |
| you can just copy the netsetupfolder yes. However I don't belive your | issue was addressed in the 6.1a installer.
Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post. |
| |
| | | Forum Guru
Group: Forum Members
Last Login: 11/6/2008 11:08:25 AM
Posts: 67, Visits: 143 |
| BetaFisch (6/13/2008)
you can just copy the netsetupfolder yes. However I don't belive your | issue was addressed in the 6.1a installer.Wonderful. So can you confirm that my issue is a "real" issue and not some local bug that is afflicting only me? The NETSETUP 6.1, when upgrading a non-netsetup 6.0 user, appends a "|" to the path to the PNTDATA folder every time. It also removes "L\" from the path to PNTTEMPL some of the time. When I added the 6.1 patch, NETSETUP again removes "L\" from the path to PNTTEMPL but seems to do it every time. I went with a NETSETUP folder to make my life easier. Can you PLEASE fix it? Or is it a lost cause until 7.0 next May? |
| |
|
|