This has stumped everyone...

Here's the situation:

I have 3 HD's running on a HPT370a built in controller and 2 optical running off the integrated IDE channels. The board is the Epox 4bda2+.

Installed 2k first and XP second to separate physical drives and CANNOT get XP to boot. I've reinstalled so many #@%*) times and no go. I've even installed each OS with the other HD's unplugged to no effect. What the __________?

Here's the boot.ini:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT= "Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS= "Microsoft Windows XP Home Edition" /fastdetect

1. With this config I get "config/systemd" errors.
2. I have tried fixmbr
3. I have done bootcfg /everything
4. I also replaced system hive
5. I have changed rdisk(), disk(), multi()= no effect

FACTS:
60gb drive<2k OS> and 120gb drive on IDE 0 (HPT370a)
60gb <XP OS> drive on IDE 1 (HPT370a)
CD-rom on IDE 2
DVD-rom on IDE 3

This has stumped everyone at experts-exchange.com

Any ideas?

 

Hi heydre and welcome to the Windows BBS.

Here's something to try that will help to further diagnose the problem:

Paste the following script into Notepad and save it as A:\boot.ini

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(2)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS= "Microsoft Windows XP Home Edition" /fastdetect

Then copy the NTDETECT.COM and NTLDR files from the root of the XP drive to this same floppy.

Leave the floppy in the drive bay and reboot. It should boot you to XP if all things are right with the boot.ini file. If it does, your MBR is the problem. This floppy boot method uses the floppies MBR instead of the hard drive MBR.

This presumes you have no drive overlay or Goback installed on this system. If so, wait for the option of floppy boot after the overlay loads. You probably don't have such or you would have mentioned it.

Post back your results of that test.
ps, Correct the unavoidable word wrap error that placed the S on the next line in the script above.

 

that narrows it down

Zeph,

Now that's a good method for narrowing it down. I put all the files on the floppy and it booted fine into XP. Should I assume that it's the MBR? If so, on which disk?

Let me know what this tells you now that I can boot off the floppy.

Heydre

 

Yes heydre, I think you can assume that you have a MBR problem.

That will be the MBR of the XP drive (drive2).

You'll need to boot to the recovery Console and run the FIXMBR command. You may say that you have done that already but perhaps you didn't do it correctly.

The beauty of the FIXMBR command (only available under Recovery Console) is that, unlike the old fdisk /mbr command, you can direct it. If you don't direct it, it will perform its work on the current boot (default) drive. In your case, that isn't going to be what you want. (Actually you can direct the old fdisk /mbr command but it's voodoo science and I'm not allowed to tell you how.)

In your case, you'll have to direct it to the XP drive. The command line would be:

fixmbr \Device\HardDisk2

I must warn you that it is absolutely necessary that you make certain that the drive being addressed is free from viral infection. Scan the drives fully comparing them to a current set of signatures and be sure your particular AV program checks for boot sector virus. You MUST do all this prior to running the fixmbr command or you'll be playing Russian roulette with your data.

Good luck.

http://www.microsoft.com/windowsxp/.../home/using/productdoc/en/bootcons_fixmbr.asp

 

I thought we had it

Zeph,

The mystery continues...and to think this whole %#^% thing started a month ago cause windowsupdate hosed my XP install. Anyways....

Did fixmbr on XP disk and rebooted. Unbelievable but still getting "config/systemd" error.

ALSO noticed another interesting detail that my power management features are disabled- relevant?

Let's do this,

Heydre

 

I think there may be a discrepency in the drive identifications. Obviously the drive is bootable if we use another MBR. You must determine that you are addressing the correct drive when running the FIXMBR command. Try viewing the files on the drive in question to asertain that it's the correct target.

Did you check for boot sector virus? These are real devious bugs and will give you fits if you don't know how they reinfect things.

 

I'll try again

Zeph,

I'll try it again. I am almost positive I fixmbr'd both disks (2k, and XP). But maybe I didn't soooooooooo I'll do it again.

Otherwise I thought boot sector viruses are erased when you reformat disks. That's been doen many times over. Otherwise I guess my only option is to scan for viruses?

Heydre

 

The fix

Just fixmbr'd both disks (HardDisk0, HardDisk2) listed as C2K) and EXP), respectively, in repair console. Same result: systemd error.

Guess I'll virus scan the mbr....

Heydre

 

Copy all the files from the boot disk to the root of the XP drive. Confirm any overwrites. Reboot.

 

;asdlkfj;asldkfjs

Zeph,

I appreciate you taking the time to help.

Just virus scanned the mbr....nada.

I'll copy over the files but this doesn't look good I take it....I hope you can still help me...


Heydre

 

As I expected

Are we s*it out of luck?

Copied over files and no dice....systemd


Heydre

 

Last thing, from the Recovery Console run, fixboot c:

 

And for laughs, place this file on Notepad and save it as a:\boot.ini to replace the previous version on the boot disk. Reboot with it in the bay.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT= "Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS= "Microsoft Windows XP Home Edition" /fastdetect

I've never understood if you can actually boot to 2k... Can you? Do you only get the error when you opt for XP?

 

OK OK OK

Zeph,

Did the fixboot...guess what????

Nada same s*it

You have NO idea how long this has been a problem. I'll try the new boot.ini and YES it will boot in 2k fine...always has.

Just a reminder did the no power management features have anything to do with it?

Heydre

 

Is this supposed to happen?

Zeph,

Check this out...

when I boot from XP floppy drives are:
C: XP OS
D: CD-rom
E: DVD-rom
F: 2k OS
G: Data HD

when I boot from 2k HD the drives are:
C:2K OS
D: CD-rom
E: DVD-rom
F: Data HD
G: XP OS

QUESTIONS:
Is it normal for the drives to switch letters like that?
Why isn't the XP drive F on 2k boot?
Am I grasping at straws?

Heydre

 

Hmmmmmmmmmmmmm

Zeph,

Get this.....copied your post to boot.ini file and it boots to EITHER OS. I can get into XP or 2k when I use the boot.ini from the floppy. That tells us something but what?

Heydre

 

heydre I think we have tracked it down to the final analysis.

Since the boot loader files on the A:\ drive are identical to those on the default drive, it is apparent that the NTLDR is having trouble reading the boot sector code of the XP drive (disk2) when it is based on the default drive, but can read it very well when based on the A:\ drive. That tells us that there is some issue between the drives that prevents the NTLDR from reading the other drive properly. System hardware configuration or outright incompatibility of hardware is generally the cause.

Several options present themselves now. You may choose to boot using the floppy and use the system as it exists with no further action needed.

Instead, you may choose to try reconfiguring the drives, moving them to different id channels, or perhaps both on the same channel, etc. This would also require reinstalling at least XP and perhaps 2k as well. This is time consuming experimental, cut and try frustration and I don't recommend it unless you are extremely bored.

You could also choose to use a third party boot manager program such as Boot Magic to see if it would overcome this hurdle. More than likely you will need to reinstall the OS's for this to work without risking loss of data.

All things considered, I would opt for booting with the floppy and hang around until times got better. It's not all that bad.

I'm sorry I can't take you any further with this but it appears we have hit the wall.

Obviously for peace of mind you will want to verify that the three bootloader files on the root of the default drive are indeed exact copies of the one on the A:\ drive. You could even copy them from the A:\ to the F: (2k drive) while booted to XP since they will be inactive then. You could also copy them in DOS but it requires juggling the attributes some.

I welcome your comments or perhaps any input from others.

Best regards.

 

the last hurrah....

Zeph,

You're quite a trooper for sticking it out for so long. I really do appreciate your expertise. I learned a lot.

I'll probably go with changing the XP drive to one of the regular IDE controllers and putting the two opticals on the same channel. Then just go from there.

The real bummer is the problem is so nebulous that I would have a hard time isolating the issue enough to warrant a hardware return of some sort. Grrrrrrrrrr.

I'll let you know how it turns out.

Heydre

 

I gotta ask what may be a dumb question but here goes,

heydre

Are you trying to have two HDs that both contain an Active Primary partiton visible to the system ?

Seing that you can boot from the Floppy and things seem to work leads me in that direction.

Booting from the HD and having two Primary Active partitions has always led to problems. One has to be hidden.

The Primary part is OK as long as it is not set as Active.

I ran into that when I switched a bootable Master to Slave and forgot to de-activate the Primary partition on it.

BillyBob

 

Try the 2 hard drives with Win2K (Primary) and Win XP (Secondary) on the same IDE controller.