Hi,
I looked at what would involve to make memtest86+ build a multiboot
binary, and it's too much work I'm afraid. The 16-bit/realmode
initialisation (which would not be included in multiboot image) is
intermangled with cpu [gli]dt stuff in a way that makes it hard to
split.
So I've tried to look at the bug pointed by Marc instead. Which we
cannot fix without more information about the affected hardware (Marc
said on IRC that computer isn't accessible to him anymore).
I improved the warning (in GRUB 2) so that if the same situation is found
again, it'll print more useful information about addresses and offsets.
I'm not sure if it makes sense to leave this bug open. There's a bug in
GRUB [1], but we don't have enough information to fix it (I know, we did
before; this is my fault). There's also the wishlist request that memtest86+
supports multiboot, but seeing that it's so hard to make progress on that,
and given the confusing (and personally disturbing) track record of this
bug, I'd recommend closing it.
Anyone objects?
[1] That we know of, in GRUB Legacy (where it won't be fixed), and maybe
in GRUB 2 as well.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
