China DOS Union

You're right, don't be afraid of being scolded. This is the DOS forum, and generally, you won't be scolded for saying that Linux is not good or that GRUB is not good.

Is Linux good? In my opinion, it's both good and not so good.

Is GRUB (or grub for dos) good? Similarly, it's both good and not so good. Saying it's good is because it's very unique and it solves many problems. Saying it's not so good is because there are too many unsolved problems.

Recently, I'm working on developing support for the ext2 file system in the GRLDR boot code. Once developed successfully, it will be very convenient for Linux users.

Thank you for using grub for dos, and thank you for your encouragement.

Bu dian da xia, bu zhi dao cai yong loadlin yin dao liunx hou, zai zai liunx zhong yong grub4lin ke fou?

Wait, the original text is in Chinese. Let's translate it properly:

Master Budian, I wonder if after using loadlin to boot Linux, can we use grub4lin in Linux then?

loadlin can indeed boot Linux, based on the fact that Linux is not sensitive to the BIOS interrupt vector table. Linux only uses int80 to handle system calls, which is not conflicting with DOS/WINDOWS. int80 is not used by DOS/windows, and Linux does not use those interrupts used by DOS/Windows either. Therefore, the large number of interrupt vectors damaged under DOS do not affect Linux, and it can still run normally. This means that loadlin can boot Linux.

But if you want the Linux booted by LOADLIN to run grub4lin, then the problem arises. I don't mean that there will definitely be problems in practice, but that there are problems in theory. Because although Linux can run, the interrupt vector table has already been the one damaged by DOS, which will bring countless potential problems and is very easy to crash. Linux hardly uses that real-mode interrupt vector table, so Linux is okay, but after booting GRUB4LIN into GRUB, GRUB runs in real mode and naturally uses this interrupt vector table. Therefore, the error of this table will be serious, and its performance is roughly that it crashes frequently.

If someone can patch LOADLIN to restore important BIOS interrupt vectors before entering Linux, then this problem will be solved. In fact, GRUB.EXE does not have this problem because after GRUB.EXE runs, it has correctly restored those BIOS interrupt vectors. Therefore, the Linux booted by GRUB.EXE is flawless, and under such Linux, it is completely possible to run grub4lin to enter the GRUB environment. As for GRLDR, needless to say, it retains all the original BIOS interrupt vectors without any changes. Therefore, the Linux it boots is also perfect.

(Today the forum lost the post again, fortunately I saved it to a file in advance!)

Today's test: grub for dos can run under Dos70 (Windows 98 SE) and Drdos7.03, but cannot run under Dos80 (Windows Me), directly clearing the screen and crashing without information prompt. The hardware environment is (VIA) p4vmm266 motherboard, 512MB ram, 80G hard disk.

Master Budian, I used floppy disk emulation to boot Windows 2003, but after booting, there's no software drive. I wonder if the floppy disk emulation can be released?

Ladies and gentlemen, how about I provide a space for GRUB technology exchanges? Let's come here to exchange and discuss GRUB in the future! http://sysoft.zdwx.com/bbs

> Today's test: grub for dos on Dos70 (windows 98 se)
It runs normally under Dos7, as expected.
And it's unexpected that it can run under Drdos7.03! I don't know which version you used. The one I released should not run under DRDOS. But it may support all DOS versions in the future.
It cannot run under Dos80 (windows me), directly clear the screen and crash with no information prompt. The hardware environment is (VIA) p4vmm266 motherboard, 512MB ram, 80G hard drive.

This is also unexpected because grub.exe supports DOS8. How did you make your DOS8? Is it a genuine Microsoft product? Tell us the production process.
In short, it feels either you mixed up the DRDOS and DOS8 floppy disks, or you used another release.
> Using floppy disk emulation to boot windows2003, no software drive after booting, I don't know if the floppy disk emulation can be released?
Windows NT series is not as friendly as 98. It no longer provides compatible support for BIOS-based calls. This problem should be solved by the system designer or Microsoft.

Drdos and DOS80 are indeed not anti. DOS80 is made by using the dosme patch and can be a DOS80 booted from the hard disk. The Drdos 7.03 boot disk is attached later.

Some time ago, when using grldr, I found that grub is incompatible with non-standard DOS boot (such as DOS71). I estimate that this kind of boot disk causes the fault because it does not check 55AA, not because of Grub.

Today's tests:
1. Under Windows 2003, 2003 is on the fourth NTFS partition, the primary partition is FAT32, and Windows 2003 can be booted using floppy disk emulation.
2. Under Windows 2000, 2000 is on the first primary partition, which is an NTFS partition. A floppy disk formatted under Windows 2000 that has been verified to be able to boot the system is made into an image file using WinImage, and when booted with grldr emulation to try to start the system, it directly clears the screen and crashes.
A floppy disk formatted under Windows 2003, with boot.ini modified, is made into an image file using WinImage, and when booted with grldr emulation, it reports that the system file is not found.

Originally posted by GONGXP at 2005-6-29 12:00 AM:
Today's test:
1. Under Windows 2003, 2003 is on the fourth NTFS partition, the primary partition is FAT32, and using floppy disk emulation can start Windows 2003.
2. Under Windows 2000, 2000 is on the first primary partition, which is an NTFS partition, and adopts ...

The last one had a wrong partition correction

The new version of GRUB4DOS from Budian is very good.
I successfully used the enhanced NBGRUB in the new version to solve the multi-language Chinese boot menu in the mixed mode of disk-based and diskless.
Special thanks!

Why can't I find the CD-ROM after GRUBDISK on my PCM CD-ROM? I have put the disc in the drive. Please help everyone.

Originally posted by blue777 at 2005-3-24 11:00 AM:
Now I'm not making GrubDisk boot disks anymore :) You can also take a look at my latest made sysliux+grub dual-boot latest boot disk, I feel it's not bad. There is a download in the "Pandora's Box" directory at http://bootdisk.ys168.com

Can't open it... Boss, go unlock it.

When I first entered this topic, I felt it was pretty good.