China DOS Union

I want to add both msdos7.1 and msdos6.22 to my win2000 boot selection menu. But after trying several times, I still didn't succeed.

In boot.ini, why do the /win95 /win95dos parameters seem completely useless? Adding them is the same as not adding them at all.
At first I thought that adding /win95dos would automatically rename the .dos file to .sys.
And that /win95 would rename winboot.sys and msdos.w40 back to io.sys and msdos.sys.
A lot of people online say they successfully used these two parameters to make ME and 98 dual boot, but I just don't believe it!!!!

If osloader is used, do msdos.sys and io.sys still need to be in fixed locations on the disk?

That claim was something I said before, but I never said to use it like this!

If you want to install an older version of DOS, I recommend adding a classic MS-DOS 3.3 and 7.10 dual boot; if you want to install a non-MS DOS, you'd be better off adding a ROM-DOS 7.10 or FreeDOS and MS-DOS 7.10 dual boot.

Also, if I change the dos6.22 files to the .dos extension and copy them to the win98 partition, then choose previous ms-dos from the 98 boot menu, the hard disk just keeps reading nonstop, and the screen shows it is preparing to load the old ms-dos, and it stays like that the whole time.
If I use the dos7.1 install disk and choose a 6.22 and 7.11 dual boot installation, the result is the same as above: the hard disk keeps reading and there is no response at all.
Could this be the reason: dos6.22's boot files must be at the very beginning of the root directory?
Is the reason people online succeeded with 98 and ME dual boot because their io.sys is not restricted like this?

Also, after I finish installing windows 97 under dos6.22, I can use NT's osloader to make dos62 and win97 dual boot, and I can also choose previous dos from win97's boot menu.
c:\bootsect.dos="dos 6.22" /win95dos
c:\bootsect.w40="win95" /win95 works very well
But when I tried moving dos6.22's io.sys to a different position in the root directory, NT's osloader could no longer boot dos6.22 properly.
But if I move win97's io.sys to a different position in the root directory, osloader can still boot win97 normally.
Also, if I delete win97's msdos.sys, it will boot directly into win97's dos7.0, and there is no longer any error message saying himem.sys and ifshlp.sys cannot be found. But if I delete it, then the next time I choose to boot dos6.22, osloader will no longer rename msdos.dos to msdos.sys, so dos6.22 can't boot, so I still have to keep an msdos.w40.
But installing 97 under dos6.22 works, while installing 98 does not. I remember I succeeded before. At that time I could even just copy the .dos files to the 98 partition and use the 98 boot menu to get dual boot.

dos622 requires a FAT16 partition, so when loading previous ms-dos the hard disk just keeps reading nonstop

to wengier:
Everything is fine now, thanks to bootpart!
Using NT's osloader for a dos7.1 and dos6.2 dual boot really is pretty good, everything works normally, haha.

I successfully made a 98 and 98 dual boot

Bump