中国DOS联盟

Whether using MAP or MEMDISK to run the MHD.DISK file, this happens (picture) ~ Every time it reaches "STARTING MS-DOS" it stops ~ no matter how I press, there's no response ~ I changed several MHD.DISK files, still the same ~ but that MHD.DISK file works fine when put into the CD boot ~

Picture:


Last edited by mikoto on 2007-8-19 at 10:18 PM ]

Try the latest version of grub4dos? Download: http://download.gna.org/grub4dos/

Or try replacing it with a pure DOS boot disk IMG?

Or try the map method without --mem?

The information you provided is not enough. Especially the map command sequence is not provided.

It seems that the problem is with the IMG, and it hasn't reached MHDD yet.

But it can be certain that the MAP needs improvement. Suppose the size of an IMG file is 2048K, Grub4dos will definitely not read the CHS of the IMG, but look at the actual size of this IMG disk. This.IMG is very likely 4096 or larger, but the subsequent sectors are not used.

Originally posted by Buddy at 2007-8-20 09:04 AM:
Try using the latest version of grub4dos? Download: http://download.gna.org/grub4dos/

Or replace with a pure DOS bootable disk IMG and try again?

Or try the map method without --mem...

It's already the version from August 17
===============Dividing line (2007-08-19)================
First, let's talk about the directory
menu.lst
|－menu_1.lst (disk tools)
|－menu_2.lst (backup tools)
|－menu_3.lst (virus-killing tools)
|－Enter PE
|－Restart
|－Shut down

If I put MHDD.IMA above the MENU.LST directory ~ using MAP can run normally ~ no problem at all

But if I put MHDD.IMA above MENU_1.LST, this situation will occur ~ and it seems like it's dead (as shown in Figure 1) ~

MENU.LST to MENU_1.LST is pasted with CONFIGFILE ~

Why is this happening??? The same file is placed
There are two results when executed in two directories

(Figure 1):


==============Dividing line (2007-08-20)=================
Just tried again~ If it's on MENU.LST, MHDD.IMA can be run

But if it jumps from MENU.LST to MENU_1.LST, and then jumps back to MENU.LST, MHDD.IMA cannot be run anymore~
============Another dividing line=========
Tried methods:
title MHDD
map --mem (cd)/boot/grub/MHDD.IMA (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title mhdd
kernel (cd)/boot/grub/mem/memdisk.gz
initrd (cd)/boot/grub/MHDD.IMA

Last edited by mikoto on 2007-8-20 at 09:49 PM ]

Originally posted by uindex at 2007-8-20 03:50 PM:
But it can be affirmed that MAP needs to be improved. Suppose the size of an IMG file is 2048K, Grub4dos will definitely not read the CHS of the IMG and look at the actual size of this IMG disk. This.IMG is very likely to be 4096 or larger, but the subsequent sectors are not used.

MAP should be able to judge the value of chs and adopt it. If there is a problem, you can give a detailed report.

In addition, if the first sector of your image has no BPB or its partition table is wrong, then MAP will indeed ignore the value of chs, and at this time the length of the memory disk image cannot be adjusted automatically. But you can adjust it manually. The method is to replace map --mem with map --mem=-8192.

The meaning of map --mem=-8192 is to reserve at least 8192 sectors (that is, 4096K) for the memory disk.

If I put MHDD.IMA on the directory above MENU.LST ~ using MAP can run normally ~ no problem at all

Seeing this, I'm very happy. I want you to confirm if this is really the case? Did you succeed with map --mem? Or with memdisk? Or both? I need your exact answer.

If map --mem succeeded, I also want you to clearly point out one thing: Could map --mem before August 17 succeed? That is, did the August 17 version solve the previous死机 problem? Because someone else reported elsewhere that the August 17 map --mem all failed, while the August 12 version all succeeded. So, I want to know more accurate information. This is important because it determines whether to use the code before August 12 or the code from August 17 (this involves the A20 control code). If the August 17 code is better, we will use the August 17 code. Conversely, we will use the August 12 code.

Your other question (configfile) seems not particularly serious (from a developer's perspective). I suspect it's a hidden problem with the configfile command. Can you further test that whenever the configfile command is used, this problem occurs? For example, does using configfile to directly boot menu.lst itself also have this problem? After using configfile, enter the command line, and then execute a few random commands to see if there are other anomalies? Try to find out more anomalies.

My bootable CD started to be made on August 18th~ I haven't tried GRUB4DOS before August 17th~ I'll try the one released on August 12th tonight~

I successfully booted MHDD using map --mem (cd)/**/**/MHDD.IMA in the MENU.LST directory and it can run normally

P.S: How to use CONFIGFILE to start MENU.LST?? MENU.LST is the basic directory~ I don't know~ I'm just starting to learn GRUB.....

My IMG indeed has no BPB, so sorry about that.

Originally posted by Buddha](不点) at 2007-8-21 08:59 AM:

I am very happy to see this. I would like you to confirm whether this is really the case? Did you succeed with map --mem? Or with memdisk? Or both? I need your accurate reply...

I found that it turned out to be a problem with that FONTS file~ Just now I tried both August 17th and August 12th~
The one on August 12th can run normally~ But I also found a little problem~ That is, the GRUB on August 12th did not display Chinese correctly~
The one on August 12th did not run the line fontfile (cd)/boot/grub/fonts in MENU.LST

So I also deleted the FONTS file of August 17th~ MHDD can run normally~

P.S: Both map --mem and memdisk can run MHDD normally

The one on August 21st hasn't been tried yet

Last edited by mikoto on 2007-8-22 at 12:03 AM ]

I see, thank you for your hard work. It is suggested that you study the command line of grub4dos more, which is very beneficial for debugging your own menu.

Originally posted by Buddy Don't Click at 2007-8-22 09:39 AM:
I see, thank you for your hard work. It is suggested that you study more about the command line of grub4dos, which is very helpful for debugging your own menu.

But where exactly did I go wrong there??? Could it be the syntax of the command line???

Last edited by mikoto on 2007-8-22 at 10:39 PM ]

I guess it should be caused by some kind of error in the usage method.

It feels like it's the problem with the FONTS file.
Reasons:
1. The MHDD in the sub - menu can't run~No other files are found to be unable to run for the time being.
2. Tested versions 7 - 10, 8 - 12, 8 - 17, 8 - 21, 8 - 24, all are like this.
3. As long as the FONTS file is not used, there are no problems! Whether it is the Chinese version of GRUB or the English version of GRUB.

Using mkisofs to create an ISO won't have all sorts of strange errors. Just search for information online first.

Report not click: There is a netizen from Wuyou Boot who helped test~ He tested on a real machine~ The result is also the same screen corruption

Is it really the problem of the software for making ISO??!?!?

Last edited by mikoto on 2007-8-28 at 07:24 PM ]