中国DOS联盟

This is a normal phenomenon, and nothing will be damaged! Under MS-DOS 7.1, isn't it just entering the WIN command directly to enter Win98?!

After I installed DOS 7.1, the original dual-boot menu of Windows XP and Windows 98 became a dual-boot menu of Windows XP and DOS 7.1, and the original 98 boot menu is gone. Can DOS 7.1 be used to create a triple-boot menu of Windows XP, Windows 98, and DOS? How to create it?

It is probably not possible in boot.ini; it has never been implemented; we all have to put the others in the two - layer menu...

There is a way, but it's relatively troublesome. You need to use the /win95dos parameter.

The following is a quote from hunome on 2003-12-20 21:54:21:
There is a way, but it's more complicated. You need to use the /win95dos parameter.

Can you be more specific?

Using multi-boot is okay, such as easyboot

Using this "Daoshi" DOS, is it an improvement or a regression? I followed what was said to install version 7.10 or higher, and it all went wrong just like what was said. Originally, my Windows 98 was working fine. Oh, I have to reinstall the system again.

Check old posts, what Wengier said.

What was said before is that Win98 can be started directly with the WIN command under DOS.

The following is a quote from hai135 on 2003-12-24 11:12:29:
Is this "Daoshi" DOS an improvement or a regression? I followed the instructions to install a version above 7.10, and it all went wrong as the above said. Originally, my Windows 98 was working well. Hey, I have to reinstall the system again.

Why do you need to reinstall the system? Installing DOS doesn't affect the boot of Windows 98...

Open C:\BOOT.INI, find

C:\="Microsoft Windows 98" /win95
Add below it
C:\="Microsoft DOS" /win95dos
Then rename IO.SYS and MSDOS.SYS of DOS to IO.DOS and MSDOS.DOS

The following is a quote from wqxbc at 12:31:00 on December 28, 2003:
Open C:\BOOT.INI, find

C:\="Microsoft Windows 98"/win95
Add below it
C:\="Microsoft DOS"/win95dos
Then rename the DOS's IO.SYS and MSDOS.SYS to IO.DOS and MSDOS.DOS

It doesn't work. This method doesn't work for dual-booting MS-DOS 7.1 and Win98 (at that time I mentioned this method to solve the dual-boot of MS-DOS 7.1 and WinME, not MS-DOS 7.1 and Win98 dual-boot, because they are different)! And the compatibility of the old version of DOS is not good (such as not supporting long file names, large hard drives, etc.). Still use the method I mentioned before to solve the problem!

Virtual Floppy Disk
by lyh728
Updates:
Now supports 2.88M and 1.44M floppy disk image files
This is a virtual floppy disk system similar to pqmagic's vfloppy.sys that I implemented by referring to the source code of grub and the disassembled code of pqmagic's vfloppy.sys.
See the post written by brother vx_xsj, see the end.
Since there is pqmagic's vfloppy.sys, why do I need to modify it?
The main reason is that the boot program of pqmagic's vfloppy.sys is placed in the MBR and occupies the first 3 sectors of the disk. That is, when vfloppy.sys is installed, it needs to write data to the first 3 sectors starting from the MBR. In this case, if an error occurs, the system may not be bootable.
So is there any other boot program that can do similar work?
Lilo needs to be installed under Linux and cannot virtualize a floppy disk.
diskemu of nu2.nu is on the CD and does not support FAT, NTFS.
BootScriptor is also on the CD and does not support FAT, NTFS.
isolinux is also on the CD and does not support FAT, NTFS.
syslinux can support FAT16, FAT12, but does not support FAT32, NTFS.
grub supports the most formats. Some people are working in this direction, but it is not easy to use at present (referring to virtualizing a floppy disk on the hard disk), and it is most likely to achieve this goal in the near future.
............
So I integrated the source code of grub and the binary file of vfloppy.sys to make this thing.
Usage:
Suppose vfloppy is placed in c:\boot, and the C drive can be in FAT16, FAT32, NTFS partition format.
Run vfloppy -1 vloader.bin -2 vmemdsk.bin -i dos.img.
Add a line in c:\boot.ini: c:\boot\vloader.bin ="virtual floopy "
After restarting the system, select "virtual floopy" in the NT loader menu, and it will load the c:\boot\dos.img image and run it.
Features:
Safe, does not write code to the boot area, will not damage the system, no need to restore the MBR.
Convenient, can restart the system at any time and enter the DOS environment.
Very convenient to run other OS on systems without CD-ROM drives, without floppy disks, only with Windows NT, Windows 2k, Windows XP, Win2k3.
Supports 2.88M and 1.44M floppy disk image files.
Notes:
1. If the C: drive uses NTFS and disk compression is used, please ensure that the C:\Boot directory and its files below are not compressed.
2. Running install_vfloppy.bat only generates the corresponding boot files vloader.bin and virtual floppy vmemdsk.bin according to your hard disk situation, and will never rewrite the MBR.
3. vmemdsk.bin locates the disk image Dos.img (please make it yourself) directly through the disk sector where Dos.img is located, not through the file system, so it can easily support NTFS, FAT32, FAT. Even if Dos.img is deleted, as long as the data in the sector where it is located has not been overwritten, it may still be able to boot DOS, but after disk defragmentation, it may cause DOS to be unable to boot. Just run install_vfloppy.bat again.
4. Dos.img can be replaced with other bootable 1.44MB floppy disk images. Remember to run install_vfloppy.bat again after replacement.
5. Now supports 2.88M and 1.44M floppy disk image files.
6. The parameters of vfloppy.exe can be absolute paths, such as vfloppy -1 c:\ttt\vloader.bin -2 c:\kkk\vmemdsk.bin -i c:\img\dos.img
Testing:
Tested in the environment of Win2k3 English Standard Edition, supports NTFS, FAT32, FAT16 partitions.
The MS DOS7.10 boot disk made by DOS forum moderator Wengier

Virtual floppy disks are not the same as the triple-boot menu of WinXP, Win98, and DOS! Virtual floppy disks are a completely different matter.

But writing "Boot to DOS" in BOOT, it's a menu where both 98 and DOS are satisfied (there are differences, it seems that the DOS it boots is like the item on the right side of MEM, which is UMB, I forgot, it seems all are O) ——