Grub4dos error on certain systems
#1
Posted 23 April 2008 - 04:46 PM
#2
Posted 23 April 2008 - 05:25 PM
#3
Posted 23 April 2008 - 06:11 PM
Do you have both grldr.mbr and grldr at the root of the stick ?
Yes I do. The stick is formatted NTFS, if that helps.
#5
Posted 24 April 2008 - 07:23 AM
I wrote a small batch to this effect:
http://www.boot-land...?showtopic=2362
The batch is also used for the "install XP from USB":
http://www.msfn.org/...m-USB-f157.html
http://www.msfn.org/...SB-t111506.html
This approach has showed being compatible with a very large number of systems.
jaclaz
#6
Posted 24 April 2008 - 02:11 PM
As said elsewhere, the workaround should be using a "normal" MBR and change the invoked loader name in the bootsector.
I wrote a small batch to this effect:
http://www.boot-land...?showtopic=2362
The batch is also used for the "install XP from USB":
http://www.msfn.org/...m-USB-f157.html
http://www.msfn.org/...SB-t111506.html
This approach has showed being compatible with a very large number of systems.
jaclaz
I think I figured out the problem. What is happening is that the machines all treat the USB key as FD0 and all the other machines are newer and treat it as a hard drive. Is there a way to still get this whole thing to work?
#7
Posted 24 April 2008 - 03:49 PM
#8
Posted 24 April 2008 - 04:42 PM
I think I figured out the problem. What is happening is that the machines all treat the USB key as FD0 and all the other machines are newer and treat it as a hard drive. Is there a way to still get this whole thing to work?
I see.
I am afraid that there is no "one-size-fits-all" solution then.
You can try, with newish versions of grub4dos, what we attempted doing in this thread:
http://www.911cd.net...showtopic=18485
But cannot say if now we can get any further.
If you use/can use a FAT16 formatted volume, another possible try is the use of the makebootfat "double" or "triple" way MBR/bootsector.
See here for some details:
http://www.911cd.net...o...13784&st=44
http://www.911cd.net...o...0806&st=134
Another possible approach, provided that you are willing to "modify" the hard disk on those machines could be that of trying plop as a bootmanager, if it works on your hardware, it will provide it's own USB routines, that should detect the USB attached device correctly.
http://www.plop.at/e...mngrusblog.html
(WARNING! still experimental)
Whichever way you want to try, just drop a line here should you need some help.
Also, what size is the stick?
Are you sure it has been properly formatted (i.e. with "balanced" CHS/LBA data), see here:
http://www.911cd.net...o...21186&st=20
It is possible that older machines only have CHS support, and it is also possible that NTFS is not supported.
jaclaz
#9
Posted 24 April 2008 - 05:52 PM
I see.
I am afraid that there is no "one-size-fits-all" solution then.
You can try, with newish versions of grub4dos, what we attempted doing in this thread:
http://www.911cd.net...showtopic=18485
But cannot say if now we can get any further.
If you use/can use a FAT16 formatted volume, another possible try is the use of the makebootfat "double" or "triple" way MBR/bootsector.
See here for some details:
http://www.911cd.net...o...13784&st=44
http://www.911cd.net...o...0806&st=134
Another possible approach, provided that you are willing to "modify" the hard disk on those machines could be that of trying plop as a bootmanager, if it works on your hardware, it will provide it's own USB routines, that should detect the USB attached device correctly.
http://www.plop.at/e...mngrusblog.html
(WARNING! still experimental)
Whichever way you want to try, just drop a line here should you need some help.
Also, what size is the stick?
Are you sure it has been properly formatted (i.e. with "balanced" CHS/LBA data), see here:
http://www.911cd.net...o...21186&st=20
It is possible that older machines only have CHS support, and it is also possible that NTFS is not supported.
jaclaz
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users