Registry Problems? Or something else?

[Bahem]

I have several stations at my library that use PWB and get their configuration INIs from a shared folder on a central computer. I occasionally will get the following error message:

The INI file, \\casper\PWBini\PWB*.ini was not found, or unable to read configuration from Registry.

Please check to be sure \\Casper\pwbini\pwb*.ini exists, the Registry is set correctly or the correct INI was specified in the command line argument /INI=”…”

Casper is the central computer
PWBini is the shared folder
PWB*.ini is the configuration INI - the * represents the dept/branch where there station is located.

One of the more puzzling aspects of this error is that it will often only affect one of several stations in a particular dept. or branch.

The work around I have come up with is to delete all instances of the shortcut and/or command line on the affected station and recreate them. simple enough on its own. However, all the stations have DeepFreeze and are 'locked down' further with Group Policy in Active Directory. Therefore, to delete and recreate the shortcut, I need to Thaw the station(s) affected, move the user/station out of their Organizational Unit to free them from the GP, make the changes, test the changes, move them back into the proper OU, force a Group Policy Update, and then reFreeze the unit(s).

Is there a less cumbersome way to correct/prevent this problem?

For the record, all the stations are running Windows XP SP2, are on Pentium III 500Mhz machines with at least 128MB RAM. I am running version 2.09 of PWB.

Thanks in advance,

Mike - System Technician Waterloo Public Library, Waterloo Ontario Canada

[Scott]

It sounds like the server is not avialable when PWB starts. Please see the following thread.

http://teamsoftwaresolutions.com/phpBB2 ... .php?t=556

A better way may be to use the PWB startup script to copy the INI file locally when PWB starts. This will prevent the error when starting as when the server is not available PWB will use the current local INI file.

See the following thread.
http://teamsoftwaresolutions.com/phpBB2 ... .php?t=447

--Scott