|
| | | Forum Newbie
Group: Forum Members
Last Login: 6/20/2008 9:25:42 PM
Posts: 2, Visits: 5 |
| | I installed 6.1 to our server and then to 2 clients. I downloaded the 6.1a patch and followed the instructions to install it. One client (Windows Server 2003) updated with no problem. 1 client (Vista SP1) keeps wanting to install the update every time you start the program. I tried updating the winpoint.ini with the new count from the sever but that didn't work. I tried also updating the version and build in the winpoint.ini but that didn't help either. I tried deleting the winpoint.ini and running the run.exe file to replace it. I tried unistalling the program and re-installing using run.exe from the netsetup folder but that didn't solve the problem either. Any one know how to fix this issue? Thanks. |
| |
| | | 
Supreme Being
Group: Forum Members
Last Login: 11/14/2008 11:40:23 AM
Posts: 78, Visits: 86 |
| On Vista, be sure that you are opening or deleting the correct winpoint.ini file, which will be in the users virtual directory.- Double-click Computer.
- Double-click Local Disk (C
 . - Double-click the Users folder.
- Double-click the folder that has the user name of the user that logged into Windows. From the Menu bar:
- In Standard View: select Tools > Folder Options.
- In Vista View: select Organize > Folder and Search Options
The Folder Options window appears.
- Click the View tab.
- Insert a check in the Show hidden files and folders box.
- Click OK.
- From Windows Explorer, double-click the Appdata folder.
- Double-click the Local folder.
- Double-click the Virtual Store folder.
- Double-click the Windows folder.
- The winpoint.ini file that Point will use is here.
jhgkhgk |
| |
| | | Forum Guru
Group: Forum Members
Last Login: 11/6/2008 11:08:25 AM
Posts: 67, Visits: 143 |
| | flynjets- The netsetup in 6.1 and 6.1a is unusable. I ran into exactly the same problem you have on the Vista machine, but for me it happened to an XP Pro user who just happened to be the Exec Assistant to the owner of the company. Also, every time I do a netsetup install for 6.1, a "|" is appended to the end of the path to the PNTDATA folder in winpoint.ini, which makes the Primary Data Folder unavailable. On some netsetup installs "L\" is removed from the end of the path to the PNTTEMPL folder in winpoint.ini, making the templates, cardex, etc, unavailable. I can fix the winpoint.ini file, but this is annoying. When netsetup deploys the 6.1a patch it once again breaks the winpoint.ini file, only this time it removes "L\" from the PNTTEMPL path *every* time. This behavior was not fixed in 6.1a. My 6.1a CD arrived this AM and that was one of the first things I tested. I built a brand-new 6.1a netsetup and tested it - and it added "|" to the end of the PNTDATA folder path. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 6/20/2008 9:25:42 PM
Posts: 2, Visits: 5 |
| Originalit (6/18/2008)
On Vista, be sure that you are opening or deleting the correct winpoint.ini file, which will be in the users virtual directory. - Double-click Computer.
- Double-click Local Disk (C.
- Double-click the Users folder.
- Double-click the folder that has the user name of the user that logged into Windows. From the Menu bar:
- In Standard View: select Tools > Folder Options.
- In Vista View: select Organize > Folder and Search Options
The Folder Options window appears.
- Click the View tab.
- Insert a check in the Show hidden files and folders box.
- Click OK.
- From Windows Explorer, double-click the Appdata folder.
- Double-click the Local folder.
- Double-click the Virtual Store folder.
- Double-click the Windows folder.
- The winpoint.ini file that Point will use is here.
I looked in that folder you mentioned and the winpoint.ini file is not there. I searched my computer to included hidden and no indexed files and there was only 1 winpoint.ini file. Anyone else with any ideas? |
| |
| | | Forum Guru
Group: Forum Members
Last Login: 11/6/2008 11:08:25 AM
Posts: 67, Visits: 143 |
| | I have seen Point 6.1 installed on several Vista PCs and I have never seen it put winpoint.ini anywhere other than c:\windows. |
| |
|
|