I am an avid user of grub4dos and use it daily on many machines. Recently I
have noticed that something broke in grub4dos since version 2008-06-18 which
affected most IBM Thinkpad T Series laptops. The feature that broke is
where one can load a floppy image into ram and boot from there. This may
also affect hard drive images as well but I have not tested that yet.
I have tried to look at the source code changes between 2008-06-15 and
2008-06-18 and it looks like it has something to do with the A20 gate code
that has been worked on in that period. So until now, I am using the
2008-05-14 version as the latest version.
I am very willing to test any code that needs to be tested on the IBM
ThinkPad T Series - I have access to the following models:
T20, T23, T30, T42p, T43.
This is a problem that definetely needs to be looked into. I have
previously used syslinux with memdisk but all versions of them failed on IBM
Thinkpad laptops and the author, Peter Anvin could not find the problem. It
would help greatly if we could track this problem down so that it can be
fixed in both grub4dos and syslinux's memdisk program.
--
Best regards,
Quinn
_______________________________________________
Grub4dos-devel mailing list
Grub4do...@gna.org
https://mail.gna.org/listinfo/grub4dos-devel
Here is the result when trying to load a floppy memdrive and booting under
version 2008-11-11 on a Thinkpad T43:
----------------- Begin Clip -------------------------
Booting command-list
FAT12 BPB found with 0xEB (jmp) leading the boot sector.
probed C/H/S = 80/2/18, probed total sectors = 2880
int13/41(0),version=AA210001, int13/08(0),version=0, C/H/S=80/2/18,
int13/02
(0),
-------------- End clip ------------------------------
After that it hangs.
The same procedure works fine on a non-IBM machine. Here is the clip that
works:
-------------- Begin Clip ------------------
Booting command-list
FAT12 BPB found with 0xEB (jmp) leading the boot sector.
probed C/H/S = 80/2/18, probed total sectors = 2880
int13/41(0),version=AA210001, int13/08(0),version=0, C/H/S=80/2/18,
int13/02
(0),err=0, int13/41(0),version=AA210001, int31/08(0),version=0,
C/H/S=80/2/18
, int13/02(0),err=0,
--------------- End clip ------------------------
I also tried the Insert key upon bootup and only succeeded once in getting
it into debug mode. The next time I get success I will write the
information down.
I also quickly tested harddrive memdrives and they seem to work fine on all
machines.
2008/11/12 Quinn Plattel <qie...@gmail.com>
> Hi,
>
> I am an avid user of grub4dos and use it daily on many machines. Recently
> I have noticed that something broke in grub4dos since version 2008-06-18
> which affected most IBM Thinkpad T Series laptops. The feature that broke
> is where one can load a floppy image into ram and boot from there. This may
> also affect hard drive images as well but I have not tested that yet.
> I have tried to look at the source code changes between 2008-06-15 and
> 2008-06-18 and it looks like it has something to do with the A20 gate code
> that has been worked on in that period. So until now, I am using the
> 2008-05-14 version as the latest version.
>
> I am very willing to test any code that needs to be tested on the IBM
> ThinkPad T Series - I have access to the following models:
> T20, T23, T30, T42p, T43.
>
> This is a problem that definetely needs to be looked into. I have
> previously used syslinux with memdisk but all versions of them failed on IBM
> Thinkpad laptops and the author, Peter Anvin could not find the problem. It
> would help greatly if we could track this problem down so that it can be
> fixed in both grub4dos and syslinux's memdisk program.
>
> --
> Best regards,
> Quinn
>
--
Best regards/Med venlig hilsen,
Quinn Plattel
Several points. This mailing list is practically dead. Bean referred
me here for support:
http://www.boot-land.net/forums/index.php?showtopic=5384&view=getnewpost
How are you obtaining grub4dos? I see there is a new binary package
dated just yesterday (11 NOV), and there are several very recent commits
to the svn repository, if you build your own. Something in those recent
commits fixed the bug I reported at boot-land.net, so give it another
try if you haven't already. Before yesterday, the svn version of grub
was broken in a way that sounds a bit like your bug.
---AV & Spam Filtering by M+Guardian - Risk Free Email (TM)---