Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Strategies & Market Trends : TA-Quotes Plus -- Ignore unavailable to you. Want to Upgrade?

To: Craig DeHaan who wrote (6690)	9/20/1998 1:35:00 PM
From: Gary Lyben	Read Replies (5) \| Respond to of 11149

To eliminate the virtual driver as a possibility, go to the windows\system directory, and rename the file named qpdriver.vxd to qpdriver.vxd.old On rebooting, windows will complain that the driver isn't found, ignore that message. And the machine will finish rebooting. If the hangs disappear, then it's the driver. The system programmers have found a deadlock condition in the driver that would cause the machine to hang, A new driver should be ready by the end of the week. Gary

To: Craig DeHaan who wrote (6690)	9/20/1998 2:15:00 PM
From: Dick Brown	Respond to of 11149

Yes it seems to help my situation also.. Good job.. I didn't even have QPV in my startup so I don't think it was ever initialized ( of course I don't know everything that goes on transparent to us)..So why it would pick on the scan routines beats me..But if I'm hang free for the next 2 weeks, lets say, I'll be very upset as QPV then would them be the only suspect for lockups that happen doing things totally unrelated to QP. Why would we enter any QPV code scanning?? Unless there are daemons that get triggered from time to time.. Dick.