China DOS Union

The machine is a notebook.
cpu: p-m, hard drive 40g, three partitions c: primary partition (9g); d,e: logical partitions (a bit over 10g each).
os: xp (home edition), file system is all fat32.
After downloading it and extracting it on the hard drive with winimage,
I booted from CD, and the installation went smoothly. When rebooting, there were two boot entries, xp and dos. But after entering dos, all I got was a black screen with only a blinking cursor.
My colleague's machine has the same problem too.
The machine's bios is a test version and has a bug, so it can't boot from floppy. Is it related to this?
I ask the moderator for guidance!!
Thanks!

This is a historical leftover issue concerning dual booting DOS and WinNT/2K/XP. Someone mentioned it before, but I had never been able to reproduce it on my own computer, so I was unable to fix it. This afternoon I tried for a long time in VMWare, and finally managed to reproduce the problem there. However, the cause of this problem is very special; you could say it is formed by a combination of bugs in WinNT/2K/XP, Bootpart, and other programs. I just now found a way to solve this problem, and it has passed testing on my VMWare machine. Please download the MS-DOS 7.10 installation disk again and try installing it once more. If this problem has been successfully solved or if there are still problems, please let me know, thank you!

http://newdos.yginfo.net/dosart32.htm

Thank you!
I'll download and install it again.
If there are any problems I'll tell you again.

It seems there is no problem on desktop test machines, but the chance of this problem appearing on notebooks is a bit higher.

After I downloaded it, the installation went smoothly, and after rebooting I could enter the dos system.
I really admire you, you are my model for learning.
Thank you!
But I still want to know the reason for it.
Which files did you modify?
If it's too troublesome, just roughly explain it!
thanks a lots！

That .PAK file was actually .ZIP all along before today's update, but during today's update, in order to keep some people from mistakenly thinking they needed to unpack it manually before installation, I changed the extension a bit with REN.

As for that problem, it should be possible to say that it is an issue with the boot record itself in WinNT/2K/XP or DOS. Although this update should already have greatly reduced the chance of this problem occurring, the specific reason why it happens is indeed not easy to explain clearly.

Thank you!
Let me ask bluntly, what kind of work do you do?