reinstalling WIN98SE after HD Format-big problems!!

[bonkonbill]

Hi all from a chap with a major problem in the UK! Hope someone can help. I recently formatted a 20gb Hard Drive on a computer, and am having problems reinstalling Win98SE. The machine previously had WIN98SE installed. Anyway, used FDISK and FORMAT as normal, leaving one Primary DOS partition, and then try to reinstall Windows-it then rums through the checks, but as soon as I click on the icon to continue install, I get the following message... "Invalid TrueType Font Detected An application used a Truetype Font that caused an error in Windows. Quit all applications and then restart Windows." Below this message is a "CLOSE" box, and if I click on this the computer returns to a black DOS screen, and this message appears..."Standard Mode:Bad Fault in MS-Dos Extender. Fault:000D Stack Dump:0000 0000 0070. Raw Frame Fault:EC=0000 IP=08F2 CS=036F FL=3002 SP=0070 SS=02C7". Quite frankly I haven't the faintest idea what all this is about...can anyone please help? K6-2/500 processor, 20GB HD, DVD, CDRW, 64 NVRAM. Also on startup the HDD says something about being SMART capable but this is disabled-does this need to be enabled, and if so how?

[YODA74]

This article discusses the following two error messages with stack dump:


Bad Fault in MS-DOS Extender
-and-
Standard Mode: Fault outside of MS-DOS Extender


Raw fault frame:
EC=0344 CS=031F IP=85E2 AX=001D BX=0005 CX=1800 DX=155F
SI=0178 DI=0178 BP=016E DS=027F ES=027F SS=027F SP=0166

MORE INFORMATION

Bad Fault in MS-DOS Extender
This error message occurs when the fault handler dispatcher in DOSX.EXE generates another cascaded fault while trying to handle a protected-mode exception. This error is usually caused by one of the following factors:

HIMEM.SYS is unable to control the A20 line.


DOS=HIGH is not functioning properly (related to HIMEM.SYS control).


The RAM, static RAM (SRAM), single in-line memory module (SIMM), or dynamic RAM (DRAM) chips are not functioning properly.


You are running DR DOS.


The third-party memory manager is not configured correctly.


The EMM386.EXE NOEMS x=A000-EFFF line is missing from the Config.sys file.


You have an old, out-of-date ROM BIOS.


Your CMOS settings are incorrect.


Your Windows files are old or corrupted. To test this, create a new directory on the hard drive, and install Windows in that directory.


Your disks are corrupted.


Your system is infected with the Form, Forms, Noint, or Yankee Doodle virus.


Standard Mode Fault Outside MS-DOS Extender
This error message occurs when the Kernel generates a processor exception during initialization (before it has installed its own exception handlers) or when the Kernel determines that it cannot handle an exception. The causes are the same as those for the "Fault in MS-DOS Extender" error.

Meaning of Stack Dump and Raw Fault Frame
The portion of the display labeled "Stack Dump:" should always be the same and does not carry much valuable information.

The portion of the display labeled "Raw Fault Frame"

EC=0344 CS=031F IP=85E2 AX=001D BX=0005 CX=1800 DX=155F
SI=0178 DI=0178 BP=016E DS=027F ES=027F SS=027F SP=0166

contains information generated by the 80286 or 80386 processor in response to the original fault. The meaning of these settings is as follows:

Setting Meaning
------- -------
EC=xxxx An exception code produced by the processor in response
to the original fault.

IP=xxxx The program counter of the faulting instruction (8086
register "IP").

CS=xxxx The code segment of the faulting instruction. If this is
"0053" or "005B", the (original) fault was in DOSX.EXE,
the "MS-DOS Extender."

FL=xxxx The flag's image at the time of the original fault.

SP=xxxx The stack pointer at the time of the original fault.

SS=xxxx The stack segment at the time of the original fault. If
this is "004B", the fault occurred on a stack belonging
to DOSX.EXE.


The CS and IP sections tell at what point in the faulting program that the original problem was detected.

For more information about A20 handlers, see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q72302
TITLE : Specifying A20 Handlers with HIMEM.SYS /M in MS-DOS
this will give you an idea of what you are looking at but I know does not solve your problem.


------------------
W/Me (memory eater)
Me Help (http://www.webtechgeek.com/center_Frame_win_me_tips.html)
BUDS TS. (http://www.geocities.com/~budallen/whatsnew.html)

[bassman]

I just went thru the exact same problem. Also had a "SUWIN" protection fault error. Turns out I had mistakenly set my BIOS softmenu for a 266 CPU when I have a 233.
All went perfect after correcting.

------------------
Please let us know if what we suggest helps. This helps us help you better.