I'm still failing and I'm hoping it's just something real simple that I'm missing.
In the [Inactivity] section of my PWB.INI file I have:
InactivityTimer=True
InactivitySeconds=30 (this is just my test time, the real time will be at 300)
When the time expires my Inactivity.txt fires off like expected, but nothing happens. My account isn't logged off.

Here are my variables:
1 - these are public machines in our five libraries across campus (yes we are regestered PWB users, I'm just picking up this project from a previous employee)
2 - Staff & Students log in via traditional domain/LDAP info, so no worries there. It's not really a factor with PWB.
3 - We get visiting 'patrons' that want to view our digital libraries. For these, I simply have a local account built that fires off the PWB. (This was done utilize the setPWB.exe app. Everything works fine, but the user account isn't automatically logged out after 'X' amount of inactivity.
Bonus side question for multipoints

Something I noticed. For our normal domain/ldap users, I utilize an application called ActiveExit XP. This is a third party app that logs users off after a set amount of inactivity time. (It actually does a lot more than that.)
It is actually fired off from the registry when a user logs into a machine, from here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Works like a charm for everything.
Here's something I noticed. If I utilize the stand alone account that I have set up for PWB, but without the PWB shell set, then the log out application works fine. I can see it in the registry key above.
Now, when I enable the PWB shell for that stand alone account the registry key is erased or ignored, and my ActiveExit XP third party app no longer fires off after my set time.
So, is there a way to tell PWB not to manipulate my registry in this sense?
Sorry, about the overwhelming words

Thanks!
~shane