I have installed V.9 on our main computer which acts as server for our network.
We currently have two other PCs on our network that are set up to run PC+ v.8.0 on the network by accessing the server. We have one other that does not have PC+ but is on the network. We want to add that machine which means mapping a network drive. We are using XP Professional on all machines and from the Help menu I got instructions for mapping a drive. I haven't tried that yet but I'm not anticipating any difficulty. (Hope that's not being naive! )
Anyway, I haven't run across this in the PC+ manual: To add V.9 to the two machines already set up for V.8 do I need to run the new disk on each machine? What else is necessary? I have looked at the other subjects covered on this forum (Gen. Questions and Discussion) and while some have touched on networked machines, I haven't seen this mentioned.
Thanks in advance for any help on these two topics.
Ed
Ed Wallick wrote:I have installed V.9 on our main computer which acts as server for our network.
We currently have two other PCs on our network that are set up to run PC+ v.8.0 on the network by accessing the server. We have one other that does not have PC+ but is on the network. We want to add that machine which means mapping a network drive. We are using XP Professional on all machines and from the Help menu I got instructions for mapping a drive. I haven't tried that yet but I'm not anticipating any difficulty. (Hope that's not being naive! )
Anyway, I haven't run across this in the PC+ manual: To add V.9 to the two machines already set up for V.8 do I need to run the new disk on each machine? What else is necessary? I have looked at the other subjects covered on this forum (Gen. Questions and Discussion) and while some have touched on networked machines, I haven't seen this mentioned.
Thanks in advance for any help on these two topics.
Ed
If your disk does not show a NETSETUP.EXE module with a date of 9/16/2004, you need to get the new NETSETUP9.EXE module from the PC+ downloads page: http://www.powerchurch.com/support/downloads/
This fixes an issue found after the intiial release. Second, you should NOT run the disk in the client machines. Once you have the server drive mapped on the client machine, open the folder and run the NETSETUP9 program from there.
You don't have to do anything else on the clients, the clients will be mapped to the PC+ folder on the machine and they will run directly from that.
There is an issue when you install on the server, make sure you put the new version in an entirely separate folder on that machine. Sounds obvious, but you may not notice where the program defaults to and accidently overwrite the V8.0 files.
Many thanks, Neil. I made a test run on my laptop here at home on mapping a network drive, so that part should be okay when I go to the church to work on the network there. Our Ver.9 disk has the NETSETUP.EXE on it so I won't have to go to PC's website for that. So just running that on the client machines should take care of it once I confirm the mapped drive, right?
Seems easy enough - hmm, last time I said that ......
You WILL have to go to the website for the updated NETSETUP9.EXE, to be on the safe side.
The original version had a problem which was noticed the first week or so after full release, this newer version fixes that problem.
What you should do is:
1. Download the NETSETUP9.EXE file, hopefully with a broadband connection.
2. Install PC+ on your server machine.
3. Copy the NETSETUP9.EXE file to the server, then run it.
In working with the client machines, I had no trouble with the mapping a network drive. Then I ran the NETSETUP9.EXE on each machine. I entered a new User Name and Password for the additional machine on the server machine. On that machine all usernames and passwords work correctly.
However, on ANY of the client machines I can only get in using my System Administrator Password. If I try to use ANY other User Name and Password I get the following message:
"Program FRM_PCLOGIN.VALIDATE
LINE: 29
ERROR: 111
Cannot update the cursor PCUSERS, since it is read only."
If I click on the " X " in the upper right hand corner to exit from the Power Church screen I get: " Invalid file descriptor "
The NETSETUP9.EXE has a modified date of September 16, 2004. I understand that is the date that has the correct file on it.
Any clue as to what may be wrong? I had to temporarily disable the passwords and I don't want to leave it that way too long.
Incidentally, I had one other error message but I/m not sure what I was doing at the time. It was as follows:
Program PCSSETTINGS.SAVESETTING
LINE 128
ERROR: 111
Cannot update the cursor PCUINFO since it is read only
Permissions? Don't know about this unless you are speaking of what module each of the client machines have access to. Tell me what this means and I'll check on it.
)
