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 : Computer Learning

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: PMS Witch who wrote (3516)5/11/1999 7:54:00 PM
From: wily  Read Replies (1) of 110631
 
Nope.

Now, here's yet another twist. Booted back to the original disk (that I had ramdrive on) only this time with my number 2 disk hooked up also. In this setup, I DO see the missing drive, but now, what used to be my D: drive is missing. This is really strange. Must be very wierd how Windows keeps track of these things.

I remember now what might have caused the problem: I edited config.sys from the Windows DOS console. When I was done I shut down and selected "restart in MS DOS mode". For some reason, it didn't like this and after thinking for a few seconds at the "restarting windows" screen, it went all the way back to the beginning of startup, where it tests memory, and did the entire boot process, which is not what usually happens when you restart to DOS. Then during the boot process it gave the error "FAT files don't match". So, I'm thinking I either shouldn't have edited the config.sys file from Windows, or shouldn't have restarted to DOS, or both.

w
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext