mobiusonline Posted April 28, 2009 Share Posted April 28, 2009 (edited) As you might have seen from my other posts, I am converting my CDShell over to Grub4Dos. I know it kind of figures, but I have a new issue I can not figure out.I am trying to get my BartPE to run.Here is the original command I had in my CDShellchain /bootsect.binIn Grub4Dos, I have tried using "chainloader /bootsect.bin", and it just comes up with the error in the screenshot.What am I doing wrong, and how can I make just work?M Edited April 28, 2009 by mobiusonline Link to comment Share on other sites More sharing options...
jaclaz Posted April 29, 2009 Share Posted April 29, 2009 (edited) As you might have seen from my other posts, I am converting my CDShell over to Grub4Dos. I know it kind of figures, but I have a new issue I can not figure out.I am trying to get my BartPE to run.Here is the original command I had in my CDShellchain /bootsect.binIn Grub4Dos, I have tried using "chainloader /bootsect.bin", and it just comes up with the error in the screenshot.What am I doing wrong, and how can I make just work?MWhat is "bootsect.bin"?Is it a "CD no-emulation bootsector"? (A 2048 bytes file)?Or is it a HD-like bootsector? (A 512 bytes file)?IN BOTH CASES, you do not use bootsectors to load a BartPE. Grub4dos has some advantages over other bootloaders, as it can completely bypass ANY bootsector. You directly chainload the OS loader. I.e. and this should have been clear enough on the Forums and docs I pointed you to, here are a couple examples:title some flavour of BartPEroot (cd)chainloader /I386/SETUPLDR.BINortitle some flavour of BartPE foundfind --set-root /I386/SETUPLDR.BINchainloader /I386/SETUPLDR.BINPlease take note that grub4dos is CaSe SeNsItIvE on CDFS filesystem!however check these:http://www.911cd.net/forums//index.php?showtopic=19124http://www.boot-land.net/forums/index.php?showtopic=7173http://www.911cd.net/forums//index.php?sho...18045&st=25jaclaz Edited April 29, 2009 by jaclaz Link to comment Share on other sites More sharing options...
m041633n Posted December 31, 2010 Share Posted December 31, 2010 Sorry for the interruption guys when i try to boot bartpe from grub4dos multiboot cd with these entries title XPEfind --set-root /I386/SETUPLDR.BINchainloader /I386/SETUPLDR.BINwell it boots up but i get these errors& finally i checked in the multiboot cd the file names are changed with 8 characterscan someone tell me how do i boot bartpe[xpe] without grub4dos's 8 character limit Link to comment Share on other sites More sharing options...
cdob Posted December 31, 2010 Share Posted December 31, 2010 can someone tell me how do i boot bartpe[xpe] without grub4dos's 8 character limitThere neither a 8 character limit at BartPE nor at grub4dos. How do you build the ISO image?Change your ISO creating tool settings to create long file names. Link to comment Share on other sites More sharing options...
m041633n Posted January 1, 2011 Share Posted January 1, 2011 can someone tell me how do i boot bartpe[xpe] without grub4dos's 8 character limitThere neither a 8 character limit at BartPE nor at grub4dos. How do you build the ISO image?Change your ISO creating tool settings to create long file names.Ya! there's an 8 character limit in GRUB4DOS iso andI tried grub4dos's bootable cd-rom method with mkisofsmkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_root& i don't know how to create an iso with long file names. If i create an iso with long file names with these settings will it boot? i've done it with diddy's grub4dos help fileCan someone tell me/help me in creating a grub4dos multiboot iso with long file name support (using MKISOFS same entry by modifying it to support long file names or some other help) Link to comment Share on other sites More sharing options...
cdob Posted January 1, 2011 Share Posted January 1, 2011 Can someone tell me/help me in creating a grub4dos multiboot iso with long file name support (using MKISOFS same entry by modifying it to support long file names Remember plain ISO9660 Level 1 allows 8.3 names only. Hence the current limitation.You have to allow long names to get long names.Bart himself use ISO-9660:1999 http://www.nu2.nu/pebuilder/#introTrymkisofs -iso-level 4 -r -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_rootFile case is used from readed files at hard disk. This assumes uppercase core boot file names at hard disk. PEBuilder uppercase reqiured files, if you build a ISO image.Or usemkisofs -iso-level 4 -force-uppercase -r -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_rootAll ISO9660 names are uppercased at CD. Link to comment Share on other sites More sharing options...
jaclaz Posted January 1, 2011 Share Posted January 1, 2011 (edited) I tried grub4dos's bootable cd-rom method with mkisofsmkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_root... taking the generic - actually Linux derived - example given on diddy's guide and assuming that it will be the "right" syntax for a PE 1.x .... The good news are that you are not the first one to do so:http://reboot.pro/9696/http://reboot.pro/9696/page__hl__mkisofs__st__26jaclaz Edited January 1, 2011 by jaclaz Link to comment Share on other sites More sharing options...
m041633n Posted January 4, 2011 Share Posted January 4, 2011 Can someone tell me/help me in creating a grub4dos multiboot iso with long file name support (using MKISOFS same entry by modifying it to support long file names Remember plain ISO9660 Level 1 allows 8.3 names only. Hence the current limitation.You have to allow long names to get long names.Bart himself use ISO-9660:1999 http://www.nu2.nu/pebuilder/#introTrymkisofs -iso-level 4 -r -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_rootFile case is used from readed files at hard disk. This assumes uppercase core boot file names at hard disk. PEBuilder uppercase reqiured files, if you build a ISO image.Or usemkisofs -iso-level 4 -force-uppercase -r -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_rootAll ISO9660 names are uppercased at CD.I tried your codemkisofs -iso-level 4 -r -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_rootbut its the same problem [8character limit] still persist Link to comment Share on other sites More sharing options...
cdob Posted January 4, 2011 Share Posted January 4, 2011 but its the same problem [8character limit] still persistWhich files are limited to 8characters still? Link to comment Share on other sites More sharing options...
m041633n Posted January 5, 2011 Share Posted January 5, 2011 but its the same problem [8character limit] still persistWhich files are limited to 8characters still?Everything inside the iso Can you tell me did you got loaded bartpe via grub4dos successfully ie:multiboot dvd/cd & can you show me a working image/screenshot Link to comment Share on other sites More sharing options...
cdob Posted January 5, 2011 Share Posted January 5, 2011 (edited) Everything inside the iso"Mkisofs -iso-level 4 -r" allows names up to 193 chars. There is no way this result 8.3 names at DVD.I doubt the new created ISO image is limited to 8.3 chars. Did you create a new ISO image?Can you tell me did you got loaded bartpe via grub4dos successfully ie:multiboot dvd/cd Yes, above command.can you show me a working image/screenshot No pictures, text only. You may trust my words or not, your choice.Don't you trust the author Bart himself? Why did Bart choose 'mkisofs -iso-level 4' as default for BartPE?Why does long names work at countless machines since 2003?Add verbose output "-v" and post the messages.How do you create the DVD? Do you edit the ISO image after? Edited January 5, 2011 by cdob Link to comment Share on other sites More sharing options...
m041633n Posted January 5, 2011 Share Posted January 5, 2011 Everything inside the iso"Mkisofs -iso-level 4 -r" allows names up to 193 chars. There is no way this result 8.3 names at DVD.I doubt the new created ISO image is limited to 8.3 chars. Did you create a new ISO image?Can you tell me did you got loaded bartpe via grub4dos successfully ie:multiboot dvd/cd Yes, above command.can you show me a working image/screenshot No pictures, text only. You may trust my words or not, your choice.Don't you trust the author Bart himself? Why did Bart choose 'mkisofs -iso-level 4' as default for BartPE?Why does long names work at countless machines since 2003?Add verbose output "-v" and post the messages.How do you create the DVD? Do you edit the ISO image after?Hey i tried your code:mkisofs -iso-level 4 -r -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_root to create the iso & it boots correctlyThis was my faultI've created a dummy/empty iso with this code & then updated the grldr.iso with bartpe and all my bootables using ultraiso checked it in vm it gave me the same problem.& then i changed the method like thismoved all my bootables including bartpe files to the iso_root directory & then created the iso & verified it in vm voila!! it worked including all my bootables i think updating the dummy/empty iso is my problem thank you verymuch cdob for sparing me your precious time in solving my problem Link to comment Share on other sites More sharing options...
jaclaz Posted January 5, 2011 Share Posted January 5, 2011 (edited) i think updating the dummy/empty iso is my problem Yes, NEVER edit a bootable .iso.If you are into experimenting, you can try the pesort approach and you can probably shave a few (several) seconds at boot time:http://www.911cd.net/forums//index.php?showtopic=6869OT I don't recall anyone publishing or testing a list for "normal" install, but maybe the same increase of speed can be achieved. jaclaz Edited January 5, 2011 by jaclaz Link to comment Share on other sites More sharing options...
cdob Posted January 5, 2011 Share Posted January 5, 2011 Do you edit the ISO image after?i think updating the dummy/empty iso is my problemMy crystal ball lost another life. Yes, editing ISO images may truncate names.Thanks for report.I don't recall anyone publishing or testing a list for "normal" installWhy a fixed list? This match selected "normal" install only.What about a dynamically created list? Link to comment Share on other sites More sharing options...
jaclaz Posted January 6, 2011 Share Posted January 6, 2011 I don't recall anyone publishing or testing a list for "normal" installWhy a fixed list? This match selected "normal" install only.What about a dynamically created list? I do like people proving me wrong , expecially when they are right. jaclaz Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now