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.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: thecow who wrote (20049)	5/27/2001 5:43:37 AM
From: mr.mark	Respond to of 110652

hey i suppose i keep it around so that i can have three operating systems at my disposal. i don't ask much of that w95 machine, and as for upgrading it, whatever time i do put towards that type of activity tends to be devoted to my main machine and w98se and w2k. i've been fiddling with it for the last several hours, trying various tweaks. i emailed za support, but i don't expect to hear from them until about tuesday. <g3> the blue screens are coming even with za off (i guess shutting it off at the 'control center' doesn't really close it all down... true vector still runs, or something?), but before i uninstall i think i'll continue to plink away. maybe za support will surprise and reply in a day. with the holiday weekend, i doubt it. thank you for your kind offer to help. inasmuch as i'm the one stupid enough to be still hanging on to w95, i'll try to troubleshoot it on my own a bit longer. :) mark

To: thecow who wrote (20049)	5/27/2001 6:53:56 AM
From: mr.mark	Read Replies (1) \| Respond to of 110652

tc well at least i got za to shut down completely (unchecked the 'load at startup' box on the configure panel), and that in turn did keep true vector from firing up. i made use of the instructions that you posted to e a couple of days ago... thanks. with za disabled, my blue screens have stopped and i am good to go again on the win95 machine. i was renaming vtdi.386 files and then looking at winsock2 and dun1.3 upgrades and crap like that. i felt sure that i had installed them a long time ago, but was hard-pressed to figure out how to confirm they were installed. then i found a cool reference page home.earthlink.net that lays out all the file sizes and version dates so as to confirm that i have winsock2 and dun1.3. anyway, at least i have the prob isolated to za and can keep it disabled while i track down possible causes. perhaps a simple uninstall and reinstall would do the trick, but i'd prefer to wait on the outside chance that the za support folks will provide me with a simple solution. dreaming, aren't i? <g3> hope your long weekend is going well :) mark