From - Mon Oct 20 08:28:17 1997 From: narc@nauticom.net (Stan) Newsgroups: comp.os.ms-windows.setup.win95,comp.os.ms-windows.win95,comp.os.ms-windows.win95.setup,microsoft.public.win95,microsoft.public.win95.filediskmanagement,microsoft.public.win95.general.discussion,microsoft.public.win95.setup Subject: Re: MS-DOS Compatability Mode when adding hard drive... Date: Sun, 19 Oct 1997 13:43:05 GMT Organization: North American Resource Corp. Reply-To: narc@nauticom.net Message-ID: <344c0d8f.8006056@news.nauticom.net> References: <62c2fg$nug$1@news.monmouth.com> <3449ca97.1768532@news.demon.co.uk> X-Newsreader: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 93.net8.nauticom.net Lines: 39 Path: news.mitre.org!blanket.mitre.org!news.tufts.edu!usenet.logical.net!nntprelay.mathworks.com!news-peer-east.sprintlink.net!news-peer.sprintlink.net!news.sprintlink.net!Sprint!newsfeed.internetmci.com!198.190.226.3!pgh.nauticom.net!93.net8.nauticom.net Xref: news.mitre.org comp.os.ms-windows.setup.win95:62064 comp.os.ms-windows.win95.setup:129440 >On Sun, 19 Oct 1997 00:34:38 -0400, "Eric C. Dunn" > wrote: > >>I have a 2 GB Western Digital drive. I recently tried to add a 1 GB western >>Digital drive as a slave drive to the 2GB drive (just for extra space...) >>When i did, windows reported both drives as "running under MS-DOS > Eric - This is a simpel problem to fix - for any one of several reasons, WIN95 was unable to correctly set up the drives to run the full 32-bit ide mode, SO: Assuming that the HDD is able to run 32-bit, AND that you have no lines in AUTOEXEC or CONFIG that are FORCING WIN95 to run the drive in DOS compatibility mode... the best way I've found to solve the problem is to give WIN95 a chance to get a second look at your HDD setup: Backup SYSTEM.DAT and USER.DAT (hidden files in WINDOWS dir). Then run REGEDIT and go to HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VSD\IOS and delete the "NOIDE" entry that you (probably) will find there. Then REBOOT and go to DEVICE MANAGER and see if it's fixed.... BTW - This info is from the MS Knowledge base, Article #kbQ-151911 - I don't have the URL, but can send you the whole article if you want. ALSO - If you have NO IDEA what the above procedure is about, FIND SOMEONE who does and have them help you - you can cause unbelievable problems if you screw up the registry... Stan -