中国DOS联盟

Can GRUB call the boot and recovery CDs made by EZboot?
Thanks!

The function of starting the CDROM has been initially realized (but not completely realized); the function of starting the ISO file is still under development and cannot be used at present. You can read the English readme file to learn about these functions in detail.

The release of version 0.4.2 official version is postponed. The reason is that the current version is not stable enough and many places need to be improved and perfected. It has been decided to adopt the second plan, that is, to realize the booting of CDROM and ISO in 0.4.2, but the release of the official version is postponed (the release date is uncertain). Thanks to all friends who care about grub4dos.

The questions that have been answered above, I have nothing to add. Thanks to the questioner and the answerer.

May I ask:

I'm using an old version of GRUB (STAGE).
Just downloaded the new version of GRUB, and after installing it to the hard drive with BOOTLACE (BOOTLACE 0X80), it shows the MAXDOS GRUB (I installed it before), and this MAXDOS GRUB requires a password to enter the editing state, and I don't know the password.

How can I successfully install the new version of GRUB?
(After temporarily executing GRUB.EXE, everything is normal)

Last edited by GOTOmsdos on 2006-10-2 at 11:02 ]

It seems that both GRUB and IsoEmu have this problem:
Only recognize the .img or iso in the first partition and menu.lst or isoemu.ini!

I don't know whether this is a problem in software design or a problem in user usage.
Please ask the experts for advice!!!

The password should be in menu.lst! GRUB recognizes .img of all partitions, it must be a problem with the user's usage.

I can't find the executed menu.lst (none of the ones found are, BOOT\GRUB)
I don't know where the menu.lst of MAXDOS is

Check if there is anything in BOOT!

The directory of that MAXDOS is in BOOT, named MAXS (changing it to M still works).

There is no MENU.LST in BOOT, and MENU.LST is all in BOOT\GRUB. But just can't find the menu.lst of MAXDOS (the one actually executed, it's strange here!).

After changing the MAXS directory to M, using BOOTLACE.COM (having renamed the new version of the GRUB directory to GRUB and copied it to BOOT to become BOOT\GRUB, then in this directory, BOOTLACE 0X80) to install GRUB, the GRUB interface of MAXDOS still appears (this time there is no menu, only its command line, which is MAX:>)!

Last edited by GOTOmsdos on 2006-10-2 at 23:13 ]

Dear Master Budian and all experts: memtest86 memory test requires not to load any unnecessary drivers to run normally. Booting with a pure DOS floppy disk made with XP can use it normally, but after making it into a *.ima file, booting with grldr, it can only be emulated to mem (memtest86 runs extremely slowly, and needs to move some files from memory to other positions after running for a certain time), other forms of emulation have errors as soon as they run. Is my menu.lst file format incorrect? The content is as follows: Please correct!

color black/cyan yellow/cyan
timeout 60
default 0

title Boot from Virtual Floppy Disk
map --read-only (hd0,0)/boot/boot.ima (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)
map --floppies=1
boot

title Start Windows XP Profession
rootnoverify (hd0,0)
makeactive
chainloader +1

GOTOmsdos:

Installation is successful, but it doesn't mean you can use it smoothly. The reason is that your old menu.lst is still in effect, or you have an incorrect menu.lst. menu.lst is the configuration file of GRUB4DOS. If it's incorrect, you will have a bad experience. You can try to remove the commands incompatible with GRUB4DOS. If the GRUB you are using is not the original one but processed by others, it's best to consult its maker.

taojiang: Your commands are all correct. But you ignored one problem, that is, disk emulation without --mem requires that the emulated image file is stored continuously on the hard disk without fragments. If there are fragments, emulation is refused and an error exits. Disk emulation with --mem copies the entire emulated disk to memory, which occupies precious memory, but it doesn't require the original IMG file to be continuous.

－－－－－－－－－－－－－－－－－－－

Friends who love DOS, report a piece of good news: The latest GRUB4DOS starts to support all kinds and all versions of DOS. Everyone test it, and report problems here. I haven't been able to test other versions of DOS myself, but the mechanism to automatically detect and restore ROM BIOS interrupt vectors has been implemented. This mechanism is independent of the specific DOS version and is applicable to all versions of DOS. But this function has just been implemented, and maybe there are still problems. The automatic detection function can even allow device drivers and TSRs to run. But not all device drivers and TSRs are allowed. A poorly designed device driver or TSR may cause detection failure or even system crash, but it's believed that most device drivers and TSRs can pass.

You can download it here: http://grub4dos.jot.com/

GRUB is a great tool. Like the DOS system, no matter which partition it is placed in, it can start smoothly. It's really cool.

Thanks for the tip, hurry up and release a grub4dos tool that supports ISO files! I'm waiting to use it!

Take it one step at a time. The CDROM functionality has only been implemented recently, and there are still many problems in it. How can we rush to introduce new functions? CDROM and ISO files are closely related. If one is done well, it also helps the other. The function of ISO emulating CDROM will be considered at some point next year. The reason why the 0.4.2 official version was delayed is that basic issues like A20 still need to be refined, and this won't have a result until next year.

Thanks.

Brother Budian, you're here!

My current issue isn't with MENU.LST.
After renaming the MAXDOS directory, I installed the new version of GRUB4DOS, but I still get the MAX:> (GRUB prompt) from MAXDOS!

I don't know why it's still working!

I've tried multiple times, and it's always like this! I'm a bit desperate! (It's downloaded from www.grub4dos.jot.com!)

The boot\grub on my first partition has MENU.LST (but it's not being executed), and there's no MENU.LST in the grub directory


××××××××××××××××××××××××××
If you can't solve this problem, then no one can...

Last edited by GOTOmsdos on 2006-10-6 at 08:06 ]

GOTOmsdos
You just need to copy GRLDR from the GRUB directory to the root directory! Although you have successfully installed it now, you are still using the original GRLDR!