Solved

Win95 OSR2 won't start Attn: Dew Associates

Posted on 1997-09-26
23
217 Views
Last Modified: 2013-12-16
I went through the steps you told me.  During setup I kept all the files that were newer than the ones Win95 was going to install.  When Windows starts up I get the message:

A device file that is specified in the SYSTEM.INI file is damaged.
It may be needed to run Windows.

You may need to run the Windows Setup program again.
If the file is included in another software package, you may need to reinstall the software that uses that file.
C:\WINDOWS\system\nwlink.vxd

I get the same message with the files:
vnetsup.vxd
vredir.vxd
vnetbios.vxd

then I get 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 system is low in memory.

HELP!
0
Comment
Question by:lieffm
  • 12
  • 11
23 Comments
 
LVL 25

Accepted Solution

by:
dew_associates earned 50 total points
ID: 1750812
Lieffm: Not a problem! You apparently have now or at one time had plus installed on your system. Plus installs some calls in your *ini* files but doesn't load the actual file. The following article addresses this problem and how to correct it.
========================
SYMPTOMS
========
When you start your computer after installing Microsoft Plus!, or reinstalling Windows without Plus, you may receive various error messages indicating that certain Novell NetWare files cannot be loaded. These error messages may include:
 
 - Cannot find a device necessary to run Windows.
 - Unable to load the dynamic link library Nwnp32.dll.
 - The system cannot find the file specified.
 - Some or all of the following feature is not available: NetWare.
   Various files that cannot be loaded are listed. This list of files
   may include all or most of the following files:
 
 - Vnetsup.Vxd
 - Nwlink.vxd
 - Nwredir.vxd
 - Nscl.vxd
 - Vredir.vxd
 - Nwnp32.dll
 - Ndis.vxd
 - Ndis2sup.vxd
 - Vnetbios.vxd
 
CAUSE
=====
This problem can occur if you do not have the Windows 95 CD-ROM, or you do not enter the correct path to it, when Microsoft Plus! Setup prompts you for it. When this occurs, the virtual device drivers (VxDs) may be registered even though the files are not copied.
 
RESOLUTION
==========
Go to the Network Icon in Control Panel and then add and then remove the Microsoft Client for NetWare Networks to resolve
this problem. To do so, follow these steps:
 
1. In Control Panel, double-click the Network icon.
 
2. Click Add, click Client, and then click Add.
 
3. In the Manufacturers box, click Microsoft. In the Network Clients box, click Client For NetWare Networks, and then click OK.
 
4. Click OK.
 
5. Restart your computer.
 
6. In Control Panel, double-click the Network icon.
 
7. Click Client For NetWare Networks, and then click Remove.
 
8. Click OK.
 
9. Restart your computer.
 
The above steps should resolve the problem. If the error messages persist, remove all the components in Network properties, and then reinstall them.

To do so, follow these steps:
 
1. In Control Panel, double-click the Network icon.
 
2. Note the installed components so you can reinstall them.
 
3. If necessary, note items such as Dial-Up Networking phone numbers and TCP/IP settings.
 
4. Remove all the components by clicking each component and clicking Remove.
 
5. Restart your computer.
 
6. Reinstall the network components. If you add a network adapter, the NetWare client will be added by default. You can remove the client if there is no NetWare network.
 
Reboot your system!  If the IOS issue is still there, then follow this if you load Smartdrive!
-----------------------------------------
SYMPTOMS
========
 
when you restart Windows 95 after installing a program or making a
configuration change to your computer, you may receive one of the
following error messages:
 
 - Windows initializing device IOS: Windows protection error. IOS failed
   to Initialize, Please restart
 
 - While initializing IOS: Windows protection error. You need to restart
   your computer.
 
After the error message is displayed, you may not be able to start Windows
95 normally. However, you should be able to start Windows 95 in Safe mode.
 
RESOLUTION
==========
 
It may also be possible to start Windows 95 normally after using the
following procedure:
 
1. Boot Windows 95 in Safe mode or to a command prompt.
 
2. Perform one of the following two steps:
 
    - Edit the Config.sys and Autoexec.bat files and remove or disable
      any references to Smartdrv.exe.
 
    - Rename Smartdrv.exe to another name.
 
Please post your results, I'll check in off and on several times a day!
0
 

Author Comment

by:lieffm
ID: 1750813
That sounds ok except I can't start Windows to get into the Control Panel.  Even in Safe Mode I still get the IOS message.  Can I access the control panel from the command prompt?

Mike

0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750814
Mike: Reboot the system, and as the "starting windows 95" message comes up, start windows in MSDOS prompt only.
Use the dos edit function and edit your autoexec.bat and config.sys files and "rem" out everything except the statements for your cd rom drive. Then reboot the system. If need be, you should be able to use the windows 95 startup disk for this.
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750815
BTW: if you feel uncomfortable as to what to change in either config.sys or autoexec.bat, open them but make sure they are at the drive root  "C:\" and write them down and post here and I'll change for you.
0
 

Author Comment

by:lieffm
ID: 1750816
Here are the only lines that AREN'T rem'd out:

AUTOEXEC.BAT:
c:\windows\commandmscdex.exe /d:mtmide01 /m:10

CONFIG.SYS
lastdrive=m
device=c:\mtm\mtmcdai.sys /d:mtmide01

Booting in Safe Mode, I still get the IOS error.

Here are my original files:

AUTOEXEC.BAT
C:\PROGRA~1\MCAFEE\VIRUSS~2\SCANPM.EXE C:\
@IF ERRORLEVEL 1 PAUSE
SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\QEMM;C:\PROGRA~1\NORTON~1;C:\NC
rem SET BLASTER=A220 I5 D1 H5 P330 T4
rem ---------------------- MTM ATAPI CD-ROM ----------------------
rem C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MTMIDE01 /M:10
rem ---------------------- MTM ATAPI CD-ROM ----------------------
rem - By Windows Setup - C:\MOUSE\mouse.exe

CONFIG.SYS
rem DEVICE=C:\QEMM\QEMM386.SYS RAM
rem SET BLASTER=A220 I5 D1 H5 P330 T4
rem DEVICE=C:\WINDOWS\HIMEM.SYS
rem DEVICE=C:\WINDOWS\EMM386.EXE
DOS=HIGH,UMB
rem DEVICE=C:\CDPRO\VIDE-CDD.SYS /D:MSCD001
rem ---------------------- MTM ATAPI CD-ROM ---------------------
rem LASTDRIVE=M
rem DEVICE=C:\MTM\MTMCDAI.SYS /D:MTMIDE01
rem ---------------------- MTM ATAPI CD-ROM ---------------------
DEVICEHIGH=C:\WINDOWS\COMMAND\DRVSPACE.SYS /MOVE

0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750817
Mike: Here are the changes to make. I see some problems here, but it will take a few trys to find the one with the problem! Save your original config.sys and autoexec.bat to a floppy. Make the following changes to the one on the "C" drive.
=====================
AUTOEXEC.BAT
=====================
REM C:\PROGRA~1\MCAFEE\VIRUSS~2\SCANPM.EXE C:\
REM @IF ERRORLEVEL 1 PAUSE
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\
SET BLASTER=A220 I5 D1 H5 P330 T4
rem ---------------------- MTM ATAPI CD-ROM ----------------------
C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MTMIDE01 /M:10
rem ---------------------- MTM ATAPI CD-ROM ----------------------
rem - By Windows Setup - C:\MOUSE\mouse.exe

CONFIG.SYS
rem DEVICE=C:\QEMM\QEMM386.SYS RAM
SET BLASTER=A220 I5 D1 H5 P330 T4
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
DOS=HIGH,UMB
rem DEVICE=C:\CDPRO\VIDE-CDD.SYS /D:MSCD001
rem ---------------------- MTM ATAPI CD-ROM ---------------------
LASTDRIVE=Z
DEVICE=C:\MTM\MTMCDAI.SYS /D:MTMIDE01
rem ---------------------- MTM ATAPI CD-ROM ---------------------
rem DEVICEHIGH=C:\WINDOWS\COMMAND\DRVSPACE.SYS /MOVE


Post what happens after these changes and after a reboot!
0
 

Author Comment

by:lieffm
ID: 1750818
I made the changes, and when I boot in Safe Mode I still get the IOS error message.  In normal mode I still get the file error messages first.
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750819
Mike: It appears that there is a corrupted system file that Windows hasn't been able to resolve. Rather than post notes back and forth trying to sort out which one it is we will do it all at one time. Part of the problem is the QEMM Memory Manager and MacAfee, but if you have kept the config.sys and autoexec.bat as I gave them to you, follow this procedure to resolve bad files.

1. Reboot your system and when you see the "starting windows 95" message, touch F8 and boot the system to MSDOS prompt only.

2. Verify that you have access to your CD Rom drive. If you do, then go on to the next step. If not, check your config.sys and autoexec.bat files to make sure that they are setting up the CD Rom drive correctly, then go on.

3. From the dos prompt, change directories to C:\WINDOWS
and rename smartdrv.exe to smartdrv.xxx. From the C:\Windows directory the syntax would be:

    REN smartdrv.exe smartdrv.xxx

4. Insert your windows 95 cd rom into the drive and at the dos prompt type: (assuming that your cd rom drive is drive "D", if it's something else, then change the "D" to your drive letter)

D:\setup /df

As windows starts the setup process it will ask you if you want the typical install or the custom, choose custom. As you move through the setup procedure and are asked which components you want to install, choose all that you need in each area. In the networking area just choose the defaults. You may have to update your Internet Explorer, but I'm more concerned with getting you to a solid Windows installation.

When the install is complete, check everything to make sure it works properly. When we have a good setup, I'll help you clean up the autoexec.bat and config.sys.

Let me know, I'll be here!

0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750820
If you get any errors during the boot into the final install, write them down and post them here!
0
 

Author Comment

by:lieffm
ID: 1750821
When I run Win95 setup off of the cd it tries to start Windows and I get the whole routine with the file and IOS errors.  Before this endeavour I copied the OSR2 setup files onto my hard drive and when I ran setup from there it started to go through the setup but it told me that I have a version of Windows installed that can't be upgraded by this version of setup, and to get the Windows 95 Upgrade.
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750822
Mike: Let's make sure I understand you correctly. You say that when you run the win95 setup it tries to start windows and you get the whole...., are you telling me that setup doesn't run and that it goes right to a windows startup? Be a little more specific here, as I don't want to use a push install if there's a problem that I'm not aware of (like there being a copy of the windows cr rom on your hard drive)  :-)

Let me know so we can resolve this thing for you
0
IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 

Author Comment

by:lieffm
ID: 1750823
Yes, when I run setup from the cdrom it doesn't go into the setup at all, it runs the Symantec Setup for Windows and then tries to start Windows and gives me the original problems.  When I run setup from the hard drive it goes into the setup but tells me that I aleady have an OS in place that can't be upgraded using OSR2.  Another weird thing is that I can access my cdrom (e:) but I can't view any dirs.
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750824
Mike, I must admit I have not clue how or why Symantec is starting anything. In any event, lets trim your config.sys and autoexec.bat down to the bare minimums to reload your system. The reload procedure will follow the autoexec.bat and config.sys changes. Note: Make sure just the lines shown for each file are there and do not use any "rem" statements.

AUTOEXEC.BAT
=====================
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\
C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MTMIDE01 /M:10


CONFIG.SYS
=====================
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
DOS=HIGH,UMB
LASTDRIVE=Z
DEVICE=C:\MTM\MTMCDAI.SYS /D:MTMIDE01


1. Make the above file changes and save them.

2. Restart your system and as the "Starting Windows 95" message appears, touch the F8 key and boot the system to MSDOS prompt only.

3. Insert the Windows 95 CD Rom disk into the CD Rom drive and verify that your CD Rom is accessible. If it is, proceed as follows:

4. At the dos prompt, type:

     D:\SETUP /df  (and touch enter)

5. As you move through the setup, choose "Custom" instead of a typical install and choose the items you want as above.

Post your results as soon as you can Mike, I will check in on and off all evening!

0
 

Author Comment

by:lieffm
ID: 1750825
Now when I cd to E:\WIN95_R2 and type SETUP or SETUP /DF it says Bad Command or Filename.  

When I run setup off of of the C drive it still tells me to get the Windows 95 Upgrade.

If I don't get this to work soon I will just have to get my computer up-and-running again.  Can I run setup for Win96 (from files on my C drive) to restore it?

I may wait until next weekend and rename my WINDOWS directory, install Win95 OSR2, and reinstall some of the affected software or try to copy files back to WINDOWS.

What about the files autoexec.dos and config.dos?
0
 

Author Comment

by:lieffm
ID: 1750826
For now I have gone back to Win96 with no problems.  Is there a better way to install Win95 OSR2 e.g. rename my current WINDOWS directory and install to a new one?  What programs will be affected if I do this?

I appreciate your attentiveness through all of this!
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750827
Mike, you can do a fresh install, especially into a new directory, but you will have to reinstall your other programs as well as your new install has no info on them. If your going to go that far, save off your important files ans data and do a format and install clean.

There's is something wrong with the way setup is running, and before you go any further, I want you to check that OSR2 disk and determine if there is a **setup** file on it. You shouldn't have to dig down into any directories, it should be right on top.

By the way, when you type the command line to do the install, you did not follow the directions given. Your words, "Now when I cd to E:\WIN95_R2 and type SETUP or SETUP /DF it says Bad Command or Filename".

You do not have to change drives or drive letters eg: "cd\win95_r2". All you need to do is "verify that you have access to your cd rom drive while in "DOS MODE" then type

   E:\SETUP /df  

That's it, no change directories or anything else!

What do you mean by "For now I have gone back to Win96 with no problems. Is there a better way to install Win95 OSR2 "?

0
 

Author Comment

by:lieffm
ID: 1750828
I setup Win96 again last night to get my computer up-and-running for the week.  On my cd OSR2 is in a directory called WIN95_R2, so I ran setup out of that directory.  There is a SETUP file in it.
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750829
Mike: We need to clarify some things.

1. The CD Rom disk that you have for OSR2, is it a legitimate version of OSR2 or a bandit version, or have you copied something to a hard drive?

2. Next, refresh me, are we loading OSR2 over a retail version?
0
 

Author Comment

by:lieffm
ID: 1750830
It is a bandit version of OSR2, and Win96 is not a retail version as it was installed when I bought my computer and I don't have the original cd.  Would this affect the install?
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750831
Sorry there guy, but that's the whole problem in a nutshell. Where would you like to go from here?
0
 

Author Comment

by:lieffm
ID: 1750832
What exactly is the problem?  And where can I go from here?  I'll give you a little history.  I got this computer a year ago from an acquaintance in St. Catharines.  He told me that he put Windows 96 on it, an enhanced version of Windows 95.  4 months later I installed a modem and my computer started locking up on a daily basis.  I tried updating drivers, checking my interrupt settings, replacing the modem, but nothing worked.  He wasn't much help.  Just recently I realized that I might be running a beta/early version of Windows96 (it's v4.10.999) and I wanted to install an earlier release of Windows 95 to see if the lockups ceased, but it hasn't been as easy as I thought.  I know I should be running a retail version of Windows, and I am hoping that Windows 97/98 is released this year so that I can upgrade and be done with Windows 96 forever.  
0
 

Author Comment

by:lieffm
ID: 1750833
One more thing, if we can continue this discussion after I grade your answer, I will give you the points that you've earned and we can let this discussion wind down.
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1750834
Mike: Of course we can continue the discussion. If you like, you can email me at dwaldron@tapnet.net.
As for your acquaintances comments, there's no such animal as Windows 96. Mike, I'm a certified Windows 95 and NT tech, and there has never been a WIN96. The version you have is a preconfigured OEM retail version of Windows 95. Companies like compaq, Dell etc. have special editions of windows 95 just for their equiment. Dell and Packard Bell are infamous for this, and when you change a major component for which a driver or inf file has not been included, your shot in the foot.

Windows 98 will not be released before March 25 1998 according to the release sheet given to the tech training areas, and we're not scheduled for training until after the holidays, if that tells you anything. On the other hand, I understand that legit copies of OSR2 can be purchased with hardware items, and if you need more info about that email me. Simply put, Windows 95 was released over 2 years ago and everyone (except microsoft) is still sorting it out. (there's already over 300 fixes) not counting versions (there are 4). Do you really want to install something that is far from bug free? I guess you don't remember what the fall of 1995 was like.
Send me some mail and we'll discuss the issue further.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Storage devices are generally used to save the data or sometime transfer the data from one computer system to another system. However, sometimes user accidentally erased their important data from the Storage devices. Users have to know how data reco…
The use of stolen credentials is a hot commodity this year allowing threat actors to move laterally within the network in order to avoid breach detection.
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now