PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Face <[log in to unmask]>
Reply To:
PCBUILD - PC Hardware discussion List <[log in to unmask]>
Date:
Sun, 10 May 1998 21:53:07 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (65 lines)
This is a common problem with HD additions to the Windows 95 O/S. I do make
the assumption here that you are running this O/S. I went through this same
situation last December and I posted to the WD web page.
The problem is the Windows 95 Registry. I am by no means an expert on this
subject, and there is probably a way to set the proper keys to recognize
the new HD configuration. I don't know how to do this.
However, I can give a procedure that will work. First, backup your system
registry files. Then delete the registry files system.dat and user.dat in
the windows directory (and the dao backup files that Windows 95 keeps).
When you boot your system, Windows 95 will rebuild the registry based on
your current configuration. Sometimes this doesn't work. Then you have to
reinstall the Windows 95 system from scratch (which means you have to
install all your software applications!). But this does work.
>Hello all,
>
>        I need some advice after a new hard drive installation.  First of
>all, some details.  Originally had a WD 1.2GB drive as master and a
>little 80MB as slave for files only.  I bought a WD 3.2GB to replace
>the 1.2GB and used DriveCopy to copy all applications and everything
>else from one to the other.  After a successful copy, I then put
>back in my little 80MB as slave once again.  (I kept everything on
>the original 1.2GB and set it aside just in case I had problems.)
>
>        Here's my problem; somewhere in the middle of the whole process,
>something happened to cause my system to go to MS-DOS Compatibility
>Mode.  Windows Help says that...
>
>
>"Windows was unable to identify a real-mode driver or
>memory-resident program loaded in your Config.sys or Autoexec.bat
>file."
>
>
>        Now, I went to the Config.sys and REM'd out the only 2 lines in
>there, but it didn't do any good.  Below are my Config.sys and
>Autoexec.bat files.
>
>
>rem device=C:\VIDE-CDD.SYS /D:OEMCD001
>rem DEVICE=C:\DIAMOND\SANYO.SYS /D:DMSCD01
>
>and
>
>SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
>SET MIDI=SYNTH:1 MAP:E
>SET BLASTER=A220 I5 D1 H1 P330 T6
>@C:\PROGRA~1\NORTON~1\NAVBOOT.EXE /STARTUP
>PATH=%PATH%;C:\DIAMOND
>
>
>        See anything there that's causing the problem??  Any help would be
>appreciated!!  It's driving me nuts.  I probably just don't
>understand MS-DOS Compatibility Mode stuff well enough.
>
>
>Harold E. Schumacher, Jr.
>
>--
>**********Know Fear...
>                 Proverbs 9:10
>                        <><    **********
>Mailto:[log in to unmask]
>
>

ATOM RSS1 RSS2