We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now


Installation problems

danw95 asked
Medium Priority
Last Modified: 2013-12-16
Hi all,

Can anyone give me some advice about reinstalling Win 95?

Having bought my daughter a 486/66 with Win 95 Version B (OEM) installed I thought
for once everything was working OK (after we tied up the bad sector on the 2nd hand drive).

And the Win 95 ran smooth as silk then for a few days - until we needed to Drivespace her Hard Drive.

This process went fine: just Win 95 itself died. The hard drive is about twice the size

Before the Windows 95 screen a warning message comes up:

ERROR, HIMEM.SYS has detected unreliable XMS memory at address 00690962, XMS driver not installed.

*****(this is an eight Mb machine). Does this mean we might have a bad RAM SIMM?

Anyway on booting up the Win 95 now we get endless error messages, mostly (after the usual Win 95 Cloudy sky screen:

We get the blue screen of death with cheery message:

*****A fatal OE has occurred at 0137:BFF9A3C0. The current application will be terminated.

The current application being nothing but Windows 95, or whatever is the initial program Win 95 defaults to after startup.

Sometimes a startup gets as far as the wallpaper but crashes with the above fatal OE message.

Sometimes we get the initial Win 95 menu: but "safe boot" certainly doesn't help.

I've tried doing another Scandisk, nothing seems wrong with the drive or its drivespacing.

We can reboot through the emergency boot disk and get into the Nether world of Win 95 DOS, but that is not much use, and as an old DOS man, it is has a rather "through the Looking Glass feel", and one worries what anything one does might do to the Win 95 installation.

Booting with the Emergency disk screams for "Sample.sys" that is not to be found apparently. And most importantly of all the system is now not controlling the CD drives.

Obviously a reinstallation is in order.

We have the Win 95 boot disks, however the vendor appears to have left out the DOS driver files for the CD drive, as attempting to do an install from the 3.5" floppy boot disk to the CD drive with the Win 95 renders the message:

Warning: this system may not be set up to use the CD ROM. Please contact the PC manufacturer if SETUP does not proceed automatically.

Well SETUP doesn't proceed of course, and the system screams out for "OEMCD001"

Is that the plug and play CD driver?

In the meantime I just realise I could most likely download the CD ROM
driver files from the Internet. Can someone assure me it is that simple, it's just a matter of getting the right files for the drive and entering them in the CONFIG.SYS and AUTOEXEC.BAT files?

Or is there another twist with Win 95?

I don't think the sound card is set up in DOS either. Setting up DOS games (in Win 95) kept reporting that. So I'd better enter the right lines of setup in the CONFIG.SYS AND A.B as well?

If anyone can confirm this I'd very much appreciate it.


Watch Question

Hi Daniel: I'll try and respond to your questions in the order given, although some are inter-related.

1. Yes there appears to be a bad chip somewhere in the 8Mb, I would recommend that you change it, and for ease of use, you might want to consider going to 16Mb minimum.

2. The blue screen and resultant fatal exceptions are no doubt coming from both the memory problem as well as the fact that upper memory cannot be accessed.

3. On the Dos Cd Rom drivers, click Start, Run and then type in "Sysedit" without the quotes. This will bring up your startup files, including autoexec.bat and config.sys. Starting with autoexec.bat look for the cd rom driver entry and write down the driver files. One should be Mscdex.exe and the other should look something like this:  D/smsoo1 (yours will differ but it's what comes after the D/ that counts). To confirm the driver, next click on the Config.sys file to bring it forward. You should see a line that looks like this:


Where MTMCDAI.SYS is the actual driver.

Close these windows and then use Find, Files and Folders and copy these files over to your startup disk:

Edit.com (should already be there)
Himem.sys (should already be there)
*******.SYS  (your cd rom driver)

Now your ready to recreate your dos cd rom drivers if you need to. Keep in mind that. once windows loads the first time, it uses protected mode drivers (if able) instead of real mode (dos) drivers. You should be able to open a dos prompt from within windows and still access the cd rom drive.

4. This is caused by the fact that windows disables real mode cd rom drivers and uses its own protected mode drivers. While you were in the autoexec.bat and config.sys files, you may have seen something like this:


The "rem" statement disables the dos drivers. You only need to backspace over the rem statement, save the file and restart your system to re-enable them.

5. These drivers should be on your system, but just disabled by Windows.

6. If your rebooting the system into MSDOS mode, yes, however if you have setup a Windows MSDOS window to operate the game, then the sounds should be fine.

Start with upgrading/repairing memory and I think we can get you where you need to be after that.
Best regards,

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts


Dennis was highly perceptive of the various questions, he just didn't get that Win 95 wasn't getting to the point where I COULD run sysedit - it crashes just after the welcome screen. But I did get Edit going and looked at the config.sys and autoexec.bat files using that.

Unfortunately my daughter's computer is at another address so it will be some days before I can find out if this has the answers.

From looking at the boot files, Win95 didn't rem out the CD drive references in the boot files, but the info that it can do that is useful. It seems the vendor just didn't install them.

But regardless, this was a well thought out answer, and may have the main keys to getting the system up and running. Confirmation of the hardware memory problem was particularly helpful.  

Sorry Daniel: I didn't realize that you couldn't get all the way into windows 95. To do so, Boot your system and as the message "Starting Windows 95" comes up, touch the F8 key and boot to safe mode. This will enable you to make your changes without windows 95 loading all of it's drivers.


Hi Dennis,
Ah "safe mode"
as I mentioned in the initial question this is what happened when I tried "safe mode":
>Sometimes we get the initial Win 95 menu: but "safe boot" >certainly doesn't help.
It tried to boot but eventually screamed out for a driver (regardles of it's being in Safe mode!) and carshed to a blue screen of death with the "Fatal OE exception error message", but the exact error is just from memory. That's the one error message I didn't get down.

This really seems to cry out for what we used to call the "Vudu solution" - reinstallation of O/S from scratch.

Unfortunately, unlike DOS, and reinstalling DOS/Win3.1 "scratch" with Win95 is not very familiar territory.

I've downloaded the DOS CD drivers from the CD ROM maker's site (Wearne's Peripherals) and so now I'll try to set them up in the "DOS" that the Win95 boot disk provides (or with them on the boot disk as you suggest) and hope for a successful reinstall.

These problems began after an otherwise successful drivespacing of a 300Mb drive. I know people warn all the time against Drivespace, but we're on a budget and I ran it with Dos 6 & 6.33 /Win 3.1 fine for four years.

The defective RAM will have to be addressed next week. There is no question of that I take it with that error message: "Error: Himem.sys has detected unreliable XMS memory at address 00690962. XMS driver not installed."

Anyway thankyou for your continuing interest in this Win 95 Newbie's problems.


Daniel, we were all newbies once!

Anyway, there's no way aorund that memory issue. And my reason for saying 16Mb was because even though MS says windows will work correctly with 8Mb (they fibbed), todays applications demand more upper memory area. Yopu haven't seen SLOW until you try running with 8Mb.

Anyway, if it will help, post the driver name *******.sys for your driver and I'll spell out just what you need for a procedure.

Best regards,
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.