Unusual OS Installation Failure - Need Advice

[Morceaux]

My new HP Omnibook XE2 DC Notebook is on the blink..

I imagine a preface is in order. Whenever I configure a new DOS/Windows computer I always partition the HD with FDISK (FAT32) then FORMAT. I created C:\D:\E:\F:\G: (3GB, 560MB, 5GB, 5GB, 6GB) - (system drive 3GB, dedicated virtual memory drive = 560MB). The Win98se source files were on E: - My usual technique is to boot from DOS floppy with minimal drivers on it. Then launch the Setup.exe in the WIN98 directory.

The last hundred times I did this with other computers the OS installs rather uneventfully and is followed by a dull hour or so of installing current drivers and tweaking settings for performance. Then I create a disk image follwed by installing the applications/programs.

This time was very different..

During the Win98se install, at about the time that Win98se installer looks at the hardware config, the notebook crashed - three times by the end of the install (all fatal exception errors accompanied by the dreaded blue-screen). I couldnt believe it, I've never seen anything like it so early in the progression of an OS install. I re-formatted and started from scratch a couple times, nothing made a difference, so I figured a rare instance of hardware failure, ran some tests and everything was fine - The notebook passed all of the Hardware diagnostics, including the RAM error tests. I then thought the BIOS was suspect, so I updated it to the latest version, released just a month ago. The CMOS is minimally configurable, like most portable CMOS's.
All of the most current drivers were then installed.

Now, mind you, I know a thing or two about computers, I could probably build a computer from raw silicon, hell, I might even be able to pull it off using silica in a pinch.. But I've never come across a problem like this. Usually the confilicts happen later in the game, when there is something to conflict with. Hence, my being suspect of hardware failure. BUT for the most part, the thing runs fine in Win98se 'Safe-Mode', which would be consistent of software being the culprit.

Here's what I've done so far:

- Set the CMOS to default settings (which were all reasonable)
- Clean-booted, defeating system.ini, win.ini, config.sys, autoexec.bat, startup folder files
- Run System File Checker
- Run Windows Registry Checker
- Checked for existence of a 'Winstart.bat' file - it does not exist.
- Did another Win98se install into a clean folder using what switches I could remember to keep the installer from looking for hardware.
- Troubleshot protected-mode driver problems, using msconfig's advanced settings.
- I even tried disabling EVERY device in the device manager.
- I ran the Automatic Skip Driver Agent (asd.exe)
- I checked for damaged VxDs by booting and using the 'step-by-step' function and not loading any file that had a .vxd extension.
- I checked my BOOTLOG.TXT file and confirmed I only had the usual failures (ndis2sup.vxd, SDVXD & VPD failing their initializations.
- And who couldnt resist disabling the PCI bus IRQ steering, just to see if it might help..

And guess what? I can proudly say that I now enjoy a well-balanced mix of not only garden-variety exceptions but also fatal exceptions -- all sprinkled generously with frequent windows protection failures at bootup and/or shutdown. Oh yes, I lest I forget to mention the good-ol "Invalid VxD Dynamic Link Call" - which makes a cameo appearance on occasion.

And I mean a lot of them, I can barely boot and launch a program without an exception and every other boot-up I have to hit the reset button because a protection error froze things.

With the evidence of a reasonably-stable system when in 'Safe-Mode', I have to think my problems are not hardware. Maybe a poorly-written CMOS/BIOS.. ?

Help!

======================================================================

Here are some of the more frequent error messages, I am sure most of you are quite familiar with them:


'Exception 0E has occured at 0028:C0059471 in VXD --- Called from 0028:C004B707 in VXD ---'

'A fatal exception 06 has occured at F000:0000494E'

'Invalid VXD dynamic link call from VWIN32(01) + 000714 ti device "0009", service 1'

'Your windows configuration is invalid, run windows setup program again to correct this problem'

'The size of system.dat is being misreported'

'While initializing device IOS: windows protection error'

'While initializing device CONFIGMG: windows protection error'

'The program has received an illegal operation and will be shut down'

'Explorer caused an exception C14EA650H in module MSVCRT.DLL'

'There was an internal error, you must restart your computer'


==> As my brand-new computer is currently useless to me, I will very much appreciate _any_ ideas on this, Thanks!!

 

[Alt255]

It sounds like you have taken almost every possible step to troubleshoot the system. (I admire your keen wit in the face of certain aggravation, it's the sign of a cool hand.)

I am hestitant to post this because it will sound quite trivial but, sometimes, it is the only way to retain our sanity and insure that we don't spend endless hours chasing wild geese: request an RMA from HP and send the machine back. Wipe your hands of that demon beast and start from scratch with a new machine.

Sometimes the problem with a new machine is so unlikely (eg. a "flaky" hard drive) that we unnecessarily bang our heads against an unmovable wall trying to understand something that doesn't require any thought at all.

Save yourself and your customers. Unless you have a particular need for a painful, possibly fruitless learning experience, write this one off as a lost cause, grit your teeth and take the road to a cost-effective solution.

We have all been there and none of us wanted to give up without a few kicks and screams. If you were here, I would pat your shoulder and offer my hand. <g>

Alt255@Vorpalcom.Intranets.com
​

 

[Mojanne]

I've just given up on a very similar problem, with an older Pentium 200MMX system. My customer could only boot into Win98 using the step by step confirmation option in the Start Menu as Safe Mode wouldn't work. Since nothing we did could resolve this problem the decision to fdisk, reformat &amp; reinstall Win98 was made. Froze on 1st reboot every time. Got in on step by step only to get fatal exception errors when hardware detection started. Went thru all the steps you listed as well as removed the modem and sound card. Then one by one, tried different hard drive, video card, new simms, new floppy, new cd-r. Fdisk/reformatted umpteen times. Exactly the same result every time. Ran virus checker, hard drive diagnostics - nothing found. Tried smaller partitions, larger partitions, FAT32 &amp; FAT16. Different Win98 CD's. Even tried installing Win95. Nothing worked, same result every time. I'm convinced it's hardware related, either the mobo or processor. Besides the power supply &amp; CPU fan, those are the only things I haven't swapped out. I've just put in over 12 (unpaid) hrs on this beast &amp; have had enough. I hate to give up but I've run out of patience. I wish I could RMA this thing.....

 

[edfair]

Spent 3 weeks trying to get FIC m/b + K6-2-300 then P200mmx to install W95,W95B, W95C,W98,W98SE with just about every one of the error messages.Would crash anywhere it wanted to. At the last went back to basic dos+31+95upg and replaced memory as a first item of parts swap. No more crashes. Loads any one of the versions now. I was frustrated by the 3 weeks but am now very aware of the ramifications of flaky memory.
I'm with Alt255, time for RMA.

Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[DavePL]

We had a similar problem. The error message was: &quot;while initializing device ios windows protection error. You must restart your computer.&quot; It worked fine for a year before crashing. Then it could only boot in command prompt mode. It would crash half way through installing Windows 98. The problem was fixed by adding a new DIMM module.

 

[butchrecon]

Well in most cases I would say that bad RAM is the culprit. But here a good portion of the errors are related to the CMOS. I agree with Alt255 get an RMA # and send it back for a new one. You will have more hair and happier days if you pass the problem off, ESPECIALLY if it is under warranty. I know this is not very good advice but the situation seems to point to sending it back. Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.


James Collins
Computer Hardware Engineer
A+, MCP

email: butchrecon@skyenet.net