China DOS Union

Tested booting the second primary partition of the third hard disk (XP system, FAT32), set it as active, and hid the first primary partition.

BIOS was set to boot from the third hard disk, but it displayed "NTLDR IS MISSING"
But all system files were good.

Then, tried SYS this partition: transferred the DOS system, booted again, and could boot to the DOS drop-down (which is this partition),
Explanation: Can boot to a non-first hard disk and non-first primary partition.

So, does that mean NT systems don't work?

[ Last edited by GOTOmsdos on 2006-8-14 at 15:31 ]

Strange, according to reason, if the boot from the third hard disk is set in the BIOS, (hd0) and (hd2) should be swapped, that is, the third hard disk in grub should be (hd0).

Since ntldr and boot.ini can only be placed in (hd0) (placing them on other hard disks will cause them to not be found), so manually swap the disk numbers of the two disks in grub, and then boot.

map (hd0) (hd2)
map (hd2) (hd0)
map --hook
chainloader (hd0,0)/ntldr
boot

Note that before this, change the following in boot.ini:

multi(0)disk(0)rdisk(2)partition(1)\WINDOWS

to

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

chainloader (hd0,0)/ntldr

You have (hd0,0) here, but I want it to be (hd0,1)!)
Brother fujianabc, haha! You are off-topic!

Tried modifying BOOT.INI, but it didn't work; the same error still occurs.

After installing with the installation CD in DOS using %cdrom%\i386\winnt.exe, when restarting, delete the temporary files and then modify BOOT.INI to see if the installation program can detect rdisk(?) partition(?)

Originally posted by GOTOmsdos at 2006-8-14 03:58 PM:
chainloader (hd0,0)/ntldr

You have (hd0,0) here, I want it to be (hd0,1)!
Brother fujianabc haha! You are off-topic!

Whether it is ntldr or boot.ini, they must be placed on hd0. If it is hd2, use the grub map command to swap the disk numbers.
It doesn't matter much whether it is (hd2,0) or (hd2,1).

Replace the original
multi(0)disk(0)rdisk(2)partition(2)\WINDOWS
with
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
instead.

It has been modified like this, but it doesn't work.

Boot ntldr using GRUB's chainloader, not the disk's own boot sector.

chainloader (hd2,1)/ntldr
boot

Or

chainloader (hd0,1)/ntldr
boot

Is it impossible to boot into an NT system on a non-first primary partition of a non-first hard disk?
This is negative. I once installed NT on the last active primary partition, as shown in the following figure:
GOTOmsdos brother, an old revolutionary has encountered a new problem, right?

What's wrong? I can't upload attachments with the .jpg extension. The attachment size that can be uploaded has changed from the original 1024KB to 300KB. Is it the same for you?

Originally posted by fastslz at 2006-8-14 05:02 PM:
What's wrong?
I can't upload attachments with.jpg extension.
The attachment size that can be uploaded has changed from the original 1024KB to 300KB. Is it the same for you?

Using png or gif, bmp is too large.

Both PNG and GIF have been tried, but they can be uploaded but not displayed. Maybe I should delete them. Now the prompt is: The attached file cannot be saved to the server. It may be that the space is full. Please upload the attachment to the China DOS Union File Upload System or contact the administrator.

[ Last edited by fastslz on 2006-8-14 at 17:50 ]

chainloader (hd2,1)/ntldr
boot
or
chainloader (hd0,1)/ntldr
boot

Tried, no good.
GRUB prompt:
insupported parameter

Now, the problem is: He just can't find NTLDR, but it's just there. Booting into DOS is fine..

Oh, right, the version of NTLDR also matters. For example, if you install 2003 first and then XP, when starting 2003, there will be this prompt, including ntdetect.com and bootfont.bin