Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Error Message starting Win98 (HP pavillion 6465)
35 views
Skip to first unread message
hu...@hotmail.com
Jan 20, 2012, 6:37:56 PM1/20/12
to
From hu...@hotmail.com
Has anyone seen the following error message? This is where it ends up
when I try
to start Win98 (hp pavillion 6465) in Normal mode or in Safe mode.
I never see it when I boot the DOS prompt.
"While initializing device IOS:
Error: An I/O subsystem driver failed to load.
Either a file in the .\iosubsys subdirectory is corrupt,
or the System is low on memory."
The first time I saw this msg I rebooted to the DOS prompt and looked
in
Windows\System directory. There was NO IOSUBSYS subdirectory in it!
Therefore the driver file did not load because it did not exist.
Let's check Memory. C:\> MEM => 260 MB ram(xms).
That's more than adequate for Win98.
In Windows\System I made an IOSUBSYS directory.
What I need is the file name the System is looking for.
The error message does not tell me.
Can anyone help?
Has anyone seen the following error message? This is where it ends up
when I try
to start Win98 (hp pavillion 6465) in Normal mode or in Safe mode.
I never see it when I boot the DOS prompt.
"While initializing device IOS:
Error: An I/O subsystem driver failed to load.
Either a file in the .\iosubsys subdirectory is corrupt,
or the System is low on memory."
The first time I saw this msg I rebooted to the DOS prompt and looked
in
Windows\System directory. There was NO IOSUBSYS subdirectory in it!
Therefore the driver file did not load because it did not exist.
Let's check Memory. C:\> MEM => 260 MB ram(xms).
That's more than adequate for Win98.
In Windows\System I made an IOSUBSYS directory.
What I need is the file name the System is looking for.
The error message does not tell me.
Can anyone help?
Sanity Clause
Jan 21, 2012, 2:07:16 AM1/21/12
to
<hu...@hotmail.com> wrote
> Has anyone seen the following error message? This is where it ends up
> when I try to start Win98 (hp pavillion 6465) in Normal mode or in Safe mode.
> "While initializing device IOS:
> Error: An I/O subsystem driver failed to load.
> Either a file in the .\iosubsys subdirectory is corrupt,
> or the System is low on memory."
> Error: An I/O subsystem driver failed to load.
> Either a file in the .\iosubsys subdirectory is corrupt,
> or the System is low on memory."
> What I need is the file name the System is looking for.
Not necessarily a missing file. Just something that it thinks was supposed
to load, but didn't.
(I'm no expert. I just did a quick Google search of the error message.)
Have you tried this: http://support.microsoft.com/kb/149962
Go down to #3 and start from there...
"If you receive the error message when you attempt to start the computer in
Safe Mode, follow the steps listed below to restore the registry:"
See if any of that helps.
98 Guy
Jan 21, 2012, 9:06:27 AM1/21/12
to
This was originally posted to alt.windows98. I'm cross-posting my
response to microsoft.public.win98.gen_discussion.
-------------------
hu...@hotmail.com wrote:
> Has anyone seen the following error message? This is where it ends
> up when I try to start Win98 (hp pavillion 6465) in Normal mode or
> in Safe mode.
> I never see it when I boot the DOS prompt.
>
> "While initializing device IOS:
> Error: An I/O subsystem driver failed to load.
> Either a file in the .\iosubsys subdirectory is corrupt,
> or the System is low on memory."
>
> The first time I saw this msg I rebooted to the DOS prompt and
> looked in Windows\System directory. There was NO IOSUBSYS
> subdirectory in it!
>
> Therefore the driver file did not load because it did not exist.
>
If the system is still using it's original hard drive, then it would be
a very old drive and quite likely near or at the end of it's useful
life, and you are seeing the result of read errors.
The first thing I would do is boot into DOS and run scandisk, and select
yes when asked to run a full surface scan. Scandisk might find your
missing iosubsys directory.
If you have any DOS-based drive tools (like unerase.exe which I think is
part of Norton Disk Doctor) or if you have ndd.exe then I would say try
those programs and see if they can bring back your iosubsys directory.
I have 63 files in my iosubsys directory. I think some of the more
important files are built by windows during original installation, so
it's not necessarily so easy to replace the files from other sources.
response to microsoft.public.win98.gen_discussion.
-------------------
hu...@hotmail.com wrote:
> Has anyone seen the following error message? This is where it ends
> up when I try to start Win98 (hp pavillion 6465) in Normal mode or
> in Safe mode.
> I never see it when I boot the DOS prompt.
>
> "While initializing device IOS:
> Error: An I/O subsystem driver failed to load.
> Either a file in the .\iosubsys subdirectory is corrupt,
> or the System is low on memory."
>
> The first time I saw this msg I rebooted to the DOS prompt and
> looked in Windows\System directory. There was NO IOSUBSYS
> subdirectory in it!
>
> Therefore the driver file did not load because it did not exist.
>
> In Windows\System I made an IOSUBSYS directory.
>
> What I need is the file name the System is looking for.
> The error message does not tell me.
> Can anyone help?
The obvious fact is that your iosubsys directory was deleted.
>
> What I need is the file name the System is looking for.
> The error message does not tell me.
> Can anyone help?
If the system is still using it's original hard drive, then it would be
a very old drive and quite likely near or at the end of it's useful
life, and you are seeing the result of read errors.
The first thing I would do is boot into DOS and run scandisk, and select
yes when asked to run a full surface scan. Scandisk might find your
missing iosubsys directory.
If you have any DOS-based drive tools (like unerase.exe which I think is
part of Norton Disk Doctor) or if you have ndd.exe then I would say try
those programs and see if they can bring back your iosubsys directory.
I have 63 files in my iosubsys directory. I think some of the more
important files are built by windows during original installation, so
it's not necessarily so easy to replace the files from other sources.
Axel Berger
Jan 21, 2012, 7:54:20 PM1/21/12
to
hu...@hotmail.com wrote:
> and looked in Windows\System directory.
> There was NO IOSUBSYS subdirectory in it!
Quite. It's in %windir%\system\
> and looked in Windows\System directory.
> There was NO IOSUBSYS subdirectory in it!
Axel
Ben Myers
Jan 22, 2012, 2:32:22 PM1/22/12
to
<hu...@hotmail.com> wrote in message news:f15a57ee-8bb6-4462...@s8g2000pbj.googlegroups.com...
Try using "Step by step confirmation" from the startup menu. Be sure to take
note of the last process loaded before the error occurs. You also might try
running scanreg from the DOS prompt to check for registry damage.
Ben
> From hu...@hotmail.com
> Has anyone seen the following error message? This is where it ends up
> when I try
> to start Win98 (hp pavillion 6465) in Normal mode or in Safe mode.
> I never see it when I boot the DOS prompt.
> "While initializing device IOS:
> Error: An I/O subsystem driver failed to load.
> Either a file in the .\iosubsys subdirectory is corrupt,
> or the System is low on memory."
<snip>
> Has anyone seen the following error message? This is where it ends up
> when I try
> to start Win98 (hp pavillion 6465) in Normal mode or in Safe mode.
> I never see it when I boot the DOS prompt.
> "While initializing device IOS:
> Error: An I/O subsystem driver failed to load.
> Either a file in the .\iosubsys subdirectory is corrupt,
> or the System is low on memory."
Try using "Step by step confirmation" from the startup menu. Be sure to take
note of the last process loaded before the error occurs. You also might try
running scanreg from the DOS prompt to check for registry damage.
Ben
hu...@hotmail.com
Jan 30, 2012, 4:40:34 PM1/30/12
to
On Jan 22, 11:32 am, "Ben Myers" <benjmy...@REMOVEmindspring.com>
wrote:
> <hu...@hotmail.com> wrote in messagenews:f15a57ee-8bb6-4462...@s8g2000pbj.googlegroups.com...
From hu...@hotmail.com
Let me elaborate:
At the Windows Startup Menu, in these choices:
1.Normal
2.Bootlog
3.Safe Mode
4.Step-by-step
After initial, if any, every one of them
give the Windows98 screen and then the error message.
The cursor blinks on an empty line just below the msg.
It produces no more output itself and takes no input from KB.
I can turn the machine off, or reboot with ctrl+alt+del.
MS-DOS is the only system in that works.
wrote:
> <hu...@hotmail.com> wrote in messagenews:f15a57ee-8bb6-4462...@s8g2000pbj.googlegroups.com...
Let me elaborate:
At the Windows Startup Menu, in these choices:
1.Normal
2.Bootlog
3.Safe Mode
4.Step-by-step
After initial, if any, every one of them
give the Windows98 screen and then the error message.
The cursor blinks on an empty line just below the msg.
It produces no more output itself and takes no input from KB.
I can turn the machine off, or reboot with ctrl+alt+del.
MS-DOS is the only system in that works.
98 Guy
Jan 30, 2012, 6:51:04 PM1/30/12
to
hu...@hotmail.com wrote:
> Let me elaborate:
>
> At the Windows Startup Menu, in these choices:
>
> 1.Normal
> 2.Bootlog
> 3.Safe Mode
> 4.Step-by-step
>
> After initial, if any, every one of them give the Windows98
> screen and then the error message. The cursor blinks on an
> empty line just below the msg. It produces no more output
> itself and takes no input from KB.
>
> I can turn the machine off, or reboot with ctrl+alt+del.
> MS-DOS is the only system in that works.
You admitted yourself in your first post that your
> Let me elaborate:
>
> At the Windows Startup Menu, in these choices:
>
> 1.Normal
> 2.Bootlog
> 3.Safe Mode
> 4.Step-by-step
>
> After initial, if any, every one of them give the Windows98
> screen and then the error message. The cursor blinks on an
> empty line just below the msg. It produces no more output
> itself and takes no input from KB.
>
> I can turn the machine off, or reboot with ctrl+alt+del.
> MS-DOS is the only system in that works.
Windows\System\IOSUBSYS is missing.
You won't be able to start windows without restoring that directory.
I told you to try to run an unerase program to try to recover that
directory. Did you?
Ben Myers
Feb 4, 2012, 2:31:55 AM2/4/12
to
<hu...@hotmail.com> wrote in message news:65a92b15-5ede-49af...@o4g2000pbc.googlegroups.com...
The idea behind "Step by step confirmation" is to take note of the last
process loaded before the error message occurs and use that information
to try to diagnose the problem. For example, if the last process loaded was
"vmouse.vxd", then the problem could be a defective or missing mouse
driver. Please note that "Load all Windows drivers" means that startup
is about to load the Windows registry.
Ben
On Jan 22, 11:32 am, "Ben Myers" <benjmy...@REMOVEmindspring.com>
wrote:
> <hu...@hotmail.com> wrote in messagenews:f15a57ee-8bb6-4462...@s8g2000pbj.googlegroups.com...
> > From hu...@hotmail.com
> > Has anyone seen the following error message? This is where it ends up
> > when I try
> > to start Win98 (hp pavillion 6465) in Normal mode or in Safe mode.
> > I never see it when I boot the DOS prompt.
> > "While initializing device IOS:
> > Error: An I/O subsystem driver failed to load.
> > Either a file in the .\iosubsys subdirectory is corrupt,
> > or the System is low on memory."
>
> <snip>
>
> Try using "Step by step confirmation" from the startup menu. Be sure to take
> note of the last process loaded before the error occurs. You also might try
> running scanreg from the DOS prompt to check for registry damage.
wrote:
> <hu...@hotmail.com> wrote in messagenews:f15a57ee-8bb6-4462...@s8g2000pbj.googlegroups.com...
> > From hu...@hotmail.com
> > Has anyone seen the following error message? This is where it ends up
> > when I try
> > to start Win98 (hp pavillion 6465) in Normal mode or in Safe mode.
> > I never see it when I boot the DOS prompt.
> > "While initializing device IOS:
> > Error: An I/O subsystem driver failed to load.
> > Either a file in the .\iosubsys subdirectory is corrupt,
> > or the System is low on memory."
>
> <snip>
>
> Try using "Step by step confirmation" from the startup menu. Be sure to take
> note of the last process loaded before the error occurs. You also might try
> running scanreg from the DOS prompt to check for registry damage.
>From hu...@hotmail.com
>Let me elaborate:
>At the Windows Startup Menu, in these choices:
>1.Normal
>2.Bootlog
>3.Safe Mode
>4.Step-by-step
>After initial, if any, every one of them
>give the Windows98 screen and then the error message.
<snip>
>Let me elaborate:
>At the Windows Startup Menu, in these choices:
>1.Normal
>2.Bootlog
>3.Safe Mode
>4.Step-by-step
>After initial, if any, every one of them
>give the Windows98 screen and then the error message.
The idea behind "Step by step confirmation" is to take note of the last
process loaded before the error message occurs and use that information
to try to diagnose the problem. For example, if the last process loaded was
"vmouse.vxd", then the problem could be a defective or missing mouse
driver. Please note that "Load all Windows drivers" means that startup
is about to load the Windows registry.
Ben
0 new messages