China DOS Union

1. Adding emm386 noems will fail...

Oh, support!!!

grub4dos has annotated so many sites! Where to report it?

Originally posted by Budian at 2007-1-11 19:12:
In addition, if there is a problem with map --mem, you can also report it in detail. Don't just say it briefly, that's not useful. I can use map --mem on my real machine to boot the win98 virtual hard disk image, which is 37 M, far exceeding 2.88 M.

I'm sorry~ I'm really too busy


The same image could start with pre11, and the following is the screen information after startup

map --mem (hd0,0)/grub/20.img (fd0)
FAT16 BPB found with 0xEB (jmp) leading the boot sector.

probed C/H/S = 82/8/63, probed total sectors = 41265

floppies_orig=0, harddrives_orig=1, floppies_curr=1, harddrives_curr=1
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

Starting MS-DOS 7.1...


Microsoft(R) MS-DOS 7.1
(C)Copyright Microsoft Corp 1981-1999

A:\>

The same image cannot start with the official version (including the 2007-01-07 version), and the following is the screen information after startup

map --mem (hd0,0)/grub/20.img (fd0)
FAT16 BPB found with 0xEB (jmp) leading the boot sector.

probed C/H/S = 82/8/63, probed total sectors = 41265

floppies_orig=0, harddrives_orig=1, floppies_curr=1, harddrives_curr=1
map --hook
chainloader (fd0)+1
rootnoverify (fd0)


Invalid system disk
Replace the disk, and then press any key
_

Attach the original image

Version 0.4.2 official version map --mem method can start the 2.88 floppy disk image *.ima I made myself, but I haven't tried anything larger than 2.88 yet

The problem with emm386 noems has been resolved. Please download the grub.exe file that was just uploaded the other day for testing:

http://grub4dos.jot.com/

You can also go to the grub section of Eden to download the grub.rar file. After decompression, it is exactly the same as the above grub.exe:

http://grub.linuxeden.com/wakka.php?wakka=UploadFile


The problem reported by fastslz has not been resolved, but the cause of the problem has been initially identified as an error in hidden sectors. Before our grub4dos fixes the bug, fastslz can also have a workaround, that is, manually set the hidden sectors in the floppy disk image to 0.

Hidden sectors is a 4-byte integer, that is, DWORD, which is located at offset 1Ch of the floppy disk boot sector. In this image provided by fastslz, this value is 3F 00 00 00, which needs to be changed to 00 00 00 00, that is, only change 3F to 00.

This problem will be resolved as soon as possible. Please wait a few more days.

Budian: Why can't I access znpc.net/bbs? Where is the forum? (I am cchess_sb)

Question:
If there is menu.lst in the hard disk, after using grub.exe --config-file="#@r:\menu.lst" in the floppy disk, how to load the menu.lst in the hard disk?

My purpose is to load menu.lst in the directory where grub.exe is located.
Please tell me how to do it?

[ Last edited by cchessbd on 2007-1-18 at 11:46 AM ]

If you don't change 3F to 00 as Master said, it can boot. Also, it is explained that 20.img is obtained by creating a 20MB partition with PQ and then reading it with WinImage. Regardless of the FAT format and cluster size, 1Ch is always 3F. When using WinPM to view the partition boot sector of the hard disk, the 3rd partition also has 3F 00 00 00.

What a group of experts! Is there anyone taking apprentices?

Can the new version boot from a USB device? (My motherboard doesn't support it)

Originally posted by GOTOmsdos at 2007-1-19 13:21:
Can the new version boot from a USB device?
(My motherboard doesn't support it)

Your motherboard doesn't support it. What other methods are there to (first) boot from a USB device.
At most, it's indirect support.

For motherboards that do not support USB booting, it may be difficult to use with grub4dos. Even if you find a way to load USB support for DOS to make DOS recognize the USB flash drive, when you enter the grub environment with grub.exe, the driver for the USB flash drive no longer works, and thus the USB flash drive disappears.

It is recommended to flash the BIOS to obtain USB boot support.

Booting from a USB device and reading/writing to a USB device are different, right? My motherboard can't boot from a USB device, but it can read and write in the operating system. If GRUB has the function to drive USB and can read and write USB, and GRUB has an emulation function, since it can read and write USB, why can't it simulate the USB storage as a hard disk (or the first one)? (Moreover, the USB flash drive itself is emulating a floppy disk or hard disk.)

GRUB4DOS accesses disks through the BIOS. The same goes for accessing USB drives. If the BIOS doesn't support USB drives, GRUB4DOS can't access USB drives.

Of course, you can access USB drives in Windows, otherwise恐怕no one would still use Windows. This doesn't mean your BIOS supports USB drives, because Windows accesses USB drives without going through the BIOS.

DOS can access USB drives if it loads the USB drive driver. However, GRUB4DOS can't. Because no one has written a USB drive driver for GRUB4DOS, that's it.

I downloaded it, and this situation occurred when decompressing.