Solved

0D error showed up during hardware detection

Posted on 1998-11-11
3
153 Views
Last Modified: 2013-12-16
I reinstalled win95, but during hardware detection error displayed, " 0D occurred at 117:000065BB amd 0D occurred at 117:000065Bf." I tried to install many times, but the same errors kept on appearing each time during hardware detection. I disable all hardware before setup but still not successful. Help
The thing is that win95 have no trouble using win3.1's himem.sys and win3.1 emm386.exe. I don't know if win95's himem.sys and emm386 cause the problem on a FAT16 system.
By the way, win95 is on CD, I have 486dx50, 340mb, 24ram.
0
Comment
Question by:visp
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 17

Expert Comment

by:mikecr
ID: 1759300
Try going into CMOS and disabling L2 onboard cache and L1 on chip cache and attempt your reinstall again. Or in CMOS choose setup defaults and load them and then reinstall Windows again without anything in your system like a sound card or modem.

Good Luck!
Mike
0
 

Author Comment

by:visp
ID: 1759301
The problem is that I can't get in cmos. I've used all different keys: DEL, ctrl-del, ctrl-esc ...you name it. I don't know how to get in cmos. My pc has a battery but it is permanently soldered onto the board, can't remove the battery. Shorting the jumpers doesn't work either. Help!
0
 

Accepted Solution

by:
mwyatt earned 0 total points
ID: 1759302
To get at the CMOS:
How many memory chips (SIMMs) are visible on the motherboard? If you have 24Mb RAM on a 486, you likely have three (8Mb each). With the PC off, try removing one or two of these SIMMs to reduce the available RAM to either 8- or 16Mb. This should cause the CMOS to register an invalid memory mismatch, or some similar error message, thereby allowing access to the CMOS. Also, try looking up the motherboard info on the internet.

As far as the 0D error, that too could be the result of flaky RAM. As you may already know, Win95 is more "demanding" of the memory and it could very well be the RAM is bad. You can reinstall with just 8Mb, then once Win95 is installed, reinsert the RAM (or better yet, get all new SIMMs).
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
Determining the an SCCM package name from the Package ID
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…

691 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