SI
SI
discoversearch

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 : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?


To: jlib who wrote (12787)10/1/2001 5:17:27 PM
From: Dan Duchardt  Respond to of 14778
 
Jimmy,

Dan, you don't want that DOS CDROM driver installed in your config.sys.

I sure hope you are right.. It's gone now. I did a complete reinstall on a wiped clean disk, and I did not do anything special to set up drivers for the CD and disk drives. My config.sys came up as a one liner:

DEVICE=C:\WINDOWS\setver.exe

I'm gradually getting things back together. It sure is a pain restoring software. Trying to bring stuff back in selectively from a full backup don't work so smoothly.

The thing that ultimately made me start from scratch was that some programs that used to open real fast were locking up my system, or slowing it to a crawl for a minute of two. There were also repeated periods of programs pausing while some unknown process was hogging the machine, letting nothing else run.. I could hardly move the cursor. One program that would barely start was defrag. Another was mIRC.. the chat program. As I was installing new copies of everything, I found that a new install of mIRC (new version) was taking forever to open, and that followed right after I did the install and update of McAfee antivirus s/w.. made me wonder. I uninstalled McAfee, and the thing now opens in a blink. The funny thing is I was almost sure I had some virus that McAfee had been unable to detect, and that turned out to be the thing acting like a virus. Anyone else have this trouble?? maybe I need to set it up differently so that it's not scanning every time open a program. I have no idea what the periodic process was, but there are numerous instances of an unnamed process in the task scheduler log. My guess it that was some McAfee thing too.

Dan