TeamSoftware Solutions

done!

Scott,

We've been using PWB for years but this renewal is the first time we're attempting to use the autoregistration feature. We've set up the .ini file exactly as indicated on the code update procedure we received, including defining our own registration password, but with a week to go before ...

Scott,

After much wailing and gnashing of teeth, we've isolated it to problems with our (offsite) aquabrowser site only on this particular hardware profile. Something with the way the site is drawn using a particular Flash object is sending one of the two cpu cores skyrocketing to 100% cpu ...

One more edit - we've managed to get it to lock up when in IE itself now.

We've isolated this to the PAC hardware. For some strange reason, doing a search for 'houses' works fine on my own work computer but when following the steps I originally posted it locks up every time on the PAC. We've exhausted every possibility we can think of, including making sure Java and Flash ...

We're in the middle of deploying new catalog PCs which will use Aquabrowser (www.aquabrowser.com) for catalog searches. The browser uses a standard search form with a Flash-based "context" tree that comes up on the left side of the screen after you've entered search text. So you can test this, our ...

What ever ended up coming of this? We're experiencing this problem intermittently now on our catalog machines.

We're running IE 6 with all security and other updates on Windows XP SP2. The only plugin we're using with this current setup is PWBDisableWindowsGUI (we actually pared this down from three different plugins we were using in the last configuration). Given the problems we're having, if this plugin ...

The only software we run besides PWB is a program called DeepFreeze, which basically restores the computer to the condition it was last frozen in every time it's rebooted. When we still had a lot of machines on Windows 98 we ran PWB and Deepfreeze in tandem for years w/o any problems, so I have a ...

Update: We updated to 2.10.2 yesterday and were fairly excited expecting our crash problems to cease, but an hour after opening this morning we discovered three of the kiosks crashed to desktop again. This time, the faulting module is no longer flash, but instead is "unknown". At this point we're ...

We've recently done a new deployment using 2.10.1. These machines are being used as email kiosks with links to popular email providers on a homepage. The decision was also made to leave the address bar intact, meaning patrons can browse anywhere they want during their 10-minute session. Therein lies ...

We actually had the inactivity timer enabled with a time of 20 seconds in the last incarnation of the kiosk setup we were using, but we found that this caused patrons to have to constantly maintain "artificial" activity (wiggling the mouse back and forth, scrolling the screen, whatever) just to keep ...

I don't necessarily have an issue with the functionality of the activity timer as much as that I'm having difficulty devising a problem-free implementation for our email kiosks here at the library.

Here's the scenario: we have PWB 2.10.1 running in kiosk mode, dedicated to providing either email ...

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 ...

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 ...