EvilMilt

It looks like the problem was that WB5 launched without it being config'd (or perhaps using the WB4 config). In any case, I had to install WB5 again. The first reboot, hung the system before I could unload WB. Re-booted and managed to unload WB, at which point the config screen popped and It's been running fine since (with yet another re-boot) to ensure it wouldnt still behave badly. Thanks for responding and setting me in the right

I was running WB4, as part of my OD purchase. I attempted to upgrade to WB5 but ran into a problem. With WB5 installed, cpu utilization runs at 100% immediately after starting up. It is difficult to do much of anything once WB5 loads but before ZoneAlarm completes loading. Prior to that, if I time it right I can either close WB5 or launch taskmgr. After having played with this for a reasonable amount of time, I have decided to remove WB5 untilI can hav