Barry,

I apologize for my ignorance, but I don't recall
backing up my system.

I scanned through multiple pages under Directory of
C:\WINDOWS and find
HIMEM.SYS file in the list. Sorry, but this is where I
lost you, Barry.  At
the end of the Directory of files, I get a C:\WINDOWS>
prompt, but when I
type COPY HIMEM.SYS after that promp, ie.
C:\WINDOWS>COPY HIMEM.SYS, then
<enter> it says File cannot be copied onto itself
0 files(s) copied.  Then returns to the C:\WINDOWS>
prompt.  I know I'm not
doing something right but maybe you could be more
specific, remember I'm
not very bright at this.  Sorry.  I DO appreciate your
help though.  I do
have a Windows 95 CD-ROM Setup Boot disk and a Windows
95 Startup Disk, but
I have never had any problems like this to have to use
them, consequently I
don't know how to use them.

Larry

----------
From: Barry Aronson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: PCWorks: Startup Error Message
Date: Saturday, February 02, 2002 5:37 PM

At 16:01 2002-02-02 -0600, you wrote:
>Friends,
>
>I desperately need some help.  I am posting this on my
old laptop
>because I cannot get my primary Dell desktop computer
to bootup when
>turning it on this afternoon. Was working fine when I
shut it down
>last night. Here is the problem:
>
>When I turn the computer on (running Windows 95a) I
get to the
>Windows 95 logo window after which I keep getting the
message:
>
>    While initializing device IOS:
>    Error: An I/O subsystem driver failed to load.
>    Either a file in the .\iosubsys subdirectory is
corrupt, or the
>    the system is low on memory.
>
>I cannot even get it to startup in Safe Mode, but
somehow, which I
>have no idea what I did, I was able to get to some
BioFix screen and
>eventually, as only a novice idiot like me could do, I
kept franickly
>hitting keys until I am now to a black screen with a
lot of
>information with the last lines stating:
>
>     HIMEM.SYS is missing.
>     Make sure that the file is in your Windows
directory.
>
>     C:\>
>
>I have no clue what, if anything, I should type after
this prompt as
>I am a true novice and am totally lost here.  Please
help me!
>Thank you.
>
>Larry

Larry!  First of all DO NOT PANIC.  I take it from your
message that you
have not backed up your system at all?  Larry I will
chide you first then
attempt to help you.  Whether you be a novice
intermediate or advanced
power user, ALWAYS back up at least your system files.

Ok, determine if the himem.sys file exists.  type
cd\windows and hit
"enter" if you still have a window's directory, type in
dir /p and hit
"enter". Slowly look for himem.sys and if found then
type copy himem.sys
c:\windows <press enter>.  this will overwrite a
corrupted high memory
manager system file.

Then Reboot the computer, if the issue continues to
occur verify that the
config.sys is properly setup. The line himem.sys should
read:
DEVICE=C:\WINDOWS\HIMEM.SYS
or
DEVICE=C:\DOS\HIMEM.SYS

If none of this works at your c: prompt type in copy
con and press
enter.  Now type in one of the two lines above and this
should give you a
fresh config.sys file which is the legacy way to
configure devices in dos
or windows up through Win98SE.

Now if you have a recovery disk from Dell USE it,
instead of going through
all of the above. :)

Keep rebooting the computer cold and see if that does
anything.  Find out
if himem.sys EXISTS at all  first.

When this happens to you and you fix it Larry you will
no longer be a
novice.

I can not believe that you AT LEAST do not have a boot
floppy disk, or a
Windows startup disk

Contact me off list and I will show you what to do so
that if this ever
happens again you will be completely prepared for the
occurrence.  I am
sure there is nothing to worry about.

HTH,




Barry ~ [EMAIL PROTECTED]
============= PCWorks Mailing List =================
Don't see your post? Check our posting guidelines &
make sure you've followed proper posting procedures,
http://pcworkers.com/rules.htm
Contact list owner <[EMAIL PROTECTED]>
Unsubscribing and other changes: http://pcworkers.com
=====================================================

Reply via email to