We've been running PWB for quite some time here at our library. During that time, we've generally kept the various .ini files on a server with no problems whatsoever. However, over the last couple of days I've been attempting to configure a standalone Windows XP PC with an .ini. stored on the local PC, but not in the PWB install directory, and am running into problems.
Incidentally, this is what the PWB v2.0 configuration file says regarding handling this scenario:
Alternate INI
…\PWB.exe /INI=”Other.ini” or PWB /INI”=C:\PWB\Other.INI”
Starts PWB with INI specified in the /INI= argument.
The path must be in quotes, with no space between the = and “.
I assumed the quote after the /INI but before the = was a typo, so I transposed these in my first attempt to get this working. This failed, so I switched them back and this, too, failed.
Here's what's happening:
A desktop shortcut has been configured to run PWB with the following information in the "Start In" field:
"C:\Program Files\TeamSoftware Solutions\Public Web Browser v2\" /INI="D:\pwb\test.ini" ... where D:\ is a 100 MB partition of the main hard disk. If you run this in the current state OR with the = and " transposed as I mentioned earlier, the browser starts but does not recognize the .ini. If you delete the original .ini, leaving the one in D:\PWB as the only version of the file, when I next run PWB it runs through an install check in order to create a new .ini in the default PWB install directory and again does not recognize the .ini on the D:\ drive. My guess is that while running PWB with this method the shortcut isn't properly relaying the ini info to the browser, but I'm not sure where I'm going wrong. Any suggestions on how to remedy this?
Thanks much.
Joseph Stude
Plymouth District Library
PWB 2.08 .ini woes
Moderators: Tyler, Scott, PWB v2 Moderator
-
Joseph Stude
- Participant
- Posts: 16
- Joined: Wed May 17, 2006 7:28 am
Minutes later, I solved my own issue. 
When creating a shortcut for PWB, I didn't create a new one, but instead attempted to modify the original. The problem with this is that the "target" field is greyed out in with the original shortcut, and PWB doesn't recognize the command switch info when it's entered into the "Start in" field, only target. The solution was to create a new shortcut from scratch and set it up as desired. Everything now works beautifully.
P.S. Yeah, the " and = transposed in the Configuration .rtf WAS a typo.
When creating a shortcut for PWB, I didn't create a new one, but instead attempted to modify the original. The problem with this is that the "target" field is greyed out in with the original shortcut, and PWB doesn't recognize the command switch info when it's entered into the "Start in" field, only target. The solution was to create a new shortcut from scratch and set it up as desired. Everything now works beautifully. P.S. Yeah, the " and = transposed in the Configuration .rtf WAS a typo.