Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error in setup WinME/ Win2Kpro dual boot"kmode_exception_not_handled"

Status
Not open for further replies.

sdjones

MIS
Oct 15, 2008
8
CA
Collective Brains,

I have a Dell dimension 4100 with Win ME pre-installed and I am trying to get an eval copy of win 2k pro on as a dual boot. I have a D: partition that I am trying to put the 2K on to, yet when I start I specify the installation drive as "D;\WINNT" and tick the "specify the installation folder" box. It then chugs away and goies to restart the machine. It comes up with the dual boot option to win 2k pro setup, but when it continues it blue screens with

"an exception error has occoured - 0x0000001e (0x80000003, 0x804a5b4f, 0x00000002, 0x0f5c8fb64)
kmode_exception_not_handled
address 804a5b4f base at 80400000 date stamp 384d4cfe - ntoskrnl.exe"

What the hell does that mean!!!

I can get ME up again, and I took off DirectCD in case that was effecting things.

PlEASE HELP.
 
I've had a few problems like that - solved only by having a system state registry back up to restore (forget about recovery disks, recovery console or repairing an installation).

Kmode is short for kernel mode I think. If you try the Microscoff website and search (try searching with the hex number) you'll probably find the BSD documented.

Don't hold out too much hope though, the helpful advice I got was something like "this could be caused by a hardware driver fault, or software..." Yeah, thanks a bunch!

The problems were caused by installing a flaky USB digital camera driver for me!

Once you've installed Win2K and then your apps be sure to use the backup to save your system state in case you need a restore (twice for me now!).

If you still have your apps installations intact when restoring then you should be able to run them after without re-installing your apps again.

Good luck.
Regards
John
 
JohnDee,

Cheers for replying, I was beginning to think that I was in a world of hurt of my own creating!!
I am still unsure if it is actually possible to dual boot with Windows ME and 2K Pro, since none of the docs I have read Official or otherwise have said it is an approved config. If anyone out there has actually installed 2K pro as a second boot option with Win ME please let me know!

As far as the (and I use the word with irony) "Knowledge base", as you said I found the enthrawling "windows 2000 Stop messages" document which gave me the same useful advice. It did mention using a kernel debugger, with the "/debug" switch, but to be honest I don't know much about debuggers, so if you could shine some light on what one I should install, where to get it etc, I would be grateful.

Cheers
 
I had a Win 2K dual boot w/ME on C and 2K on D, I have since gone back to 98SE on C as I didn't like ME. All OS have worked with no problem, W2K is by far the most stable.
 
I agree with MHughes regarding W2K being the most stable (of Win OSs, I hope he meant ! ) - despite the problems I've had (you should'a seen some of the other messes I've got into with Microscoff).

Just a thought, SDJones, you did install W2K on it's own partition didn't you, as specified?

Regards
John
 
Yep,

C: for the original win ME on my machine
D: for the win2k pro.

Both were way large enough for the install, FAT32.

 
One other thing - I understand that 128MB is the minimum RAM required for Win2K !!! I presume that's what you have?

Have you managed to install Win2K yet?

As a complete shot-in-the-dark I suspect that you might have a hardware driver conflict. Did you check the list of compatible hardware for Win2K?

Do you have the time / inclination / patience to strip your motherboard down to basics and see if it will install then?

Yeah, I stuck with FAT32 also because my dual boot Win98 can read that partition if I have another failure... I see no reason to go with NTFS unless I were on a large network and needed the extra security. If you have a stand-alone or are in a small office with trusted colleagues then I see no reason to change the file system.

Cheers
John
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top