finding the .ini file

jfrasier · Post by **jfrasier** » Wed Dec 19, 2007 2:42 pm

We use the libonline reservation software and within that software we create the menu for the various applications. For the Internet we use the pwb.exe that is found on the local hard drive but then use an .ini file that is stored on another shared computer. 95% of the time this has worked fine for years.

At one library sometimes the public computers get an error that they can't find the .ini file so PWB can't start. We have tried checking port settings, network settings, replaced the cable, tried different ports and today replaced the NIC in that computer and we are still having the problem.

Can you think of some other things to try? We did put a different computer there for a day and it seemed fine.

Baffled,
Jane

jfrasier · Post by **jfrasier** » Wed Dec 19, 2007 2:43 pm

The other interesting tidbit. The shared computer where the .ini files are stored is the print release station for the public computers and the patrons are able to print to it just fine. It seems to be just trying to find the .ini file that we are having problems.

Post by **Scott** » Wed Dec 19, 2007 3:45 pm

Is it only when the computer logs on that PWB can not find the INI file, and/or does it work after restarting PWB?

--Scott

jfrasier · Post by **jfrasier** » Wed Dec 19, 2007 3:51 pm

The computer autologs on and the reservation software logon box appears. The patron logons on to the reservation software and a menu appears with Internet, Word, etc. When they choose Internet, that is when they get the error that the .ini file cannot be found, so PWB doesn't start. Here is the path used: c:\program files\teamsoftware solutions\Public web browser v2\pwb.exe /ini="\\lkrelease154\PubComputer\pwb.ini". Lkrelease154 is also used for printing using the LPTOne software.

Users are still able to direct print jobs to that computer so they can 'see' that computer to send the print jobs. So baffling.

Thanks.

Post by **Scott** » Thu Dec 20, 2007 5:19 pm

I wonder if the spaces in the PWB command line are causing a problem. Try changing the command line to the following.

c:\progra~1\teamso~1\public~1\PWB.exe /ini=\\lkrelease154\PubComputer\pwb.ini

Notice there are no quotes in this command line since there are no spaces.

What version of PWB are you using?

--Scott

jfrasier · Post by **jfrasier** » Thu Dec 20, 2007 5:50 pm

Thanks for the idea, Scott and maybe we will try that. However we have used that other path on all of our public computers with slight variation on the .ini part for months/years without this problem.

We are using 2.093

jfrasier · Post by **jfrasier** » Fri Dec 21, 2007 12:25 pm

It looks like maybe it is a DNS/Active Directory snafu. The entries for the computer name were deleted from DNS and AD and then the computer was returned to the WORKGROUP and then rejoined the Domain. We ran flushdns and registerdns and now it appears to be working.

I think we often forget that we need to do that when we swap computers around and rename them. etc.

Thanks for your help and Happy Holidays.

Jane