![]() Trying to make a simple way to setup my project for users. So I strongly suggest you test using a VM (VBox/VMWare/QEMU) because this means we are using a 'known good' BIOS. Some BIOSes will look at the total capacity of the USB drive and if it is below a certain size it will boot it as a floppy device - but if above that size, it will boot it as a hard disk! ![]() That is why I strongly suggest that you always test with a virtual machine first - to eliminate any peculiar BIOS features/bugs. grub4dos 0.4.6a does not support booting from a USB floppy. Some BIOSes, if they see a single partition on a (small) USB drive will treat it as a floppy drive. Another issue with your Dell BIOS is that it may have the 'single partition' bug. The RMPrepUSB download includes grubinst.exe and the 'Install grub4dos' button will install the boot code for you. I use this with the LockDismount.exe tool which first dismounts the USb drive from Windows so that the grubinst tool can lock access to the USB drive and write to the MBR, etc. ![]() Know that I don't know enough at this point.Īs in the ReadMe files inside the grub4dos download docs folder, bootlace is for DOS and Linux (not Windows).įor Windows we have grubinst.exe which can be found in the grubutils pages. Rather complex process, so thought I'd see if someone might have a solution, or at least some direction on how to come up with a single solution? The zip file with all the kernels and ramdisk and support files is about 50M, and could just be unzipped to the resulting flashes? So, could be downloaded like that, then uncompressed, and burned to flash. The iso files are 67108864 in size being 64M, but with compression the files are 16320 or 16272. Was looking at create two ISO files that just had the FAT16 and FAT32 setup with the bootloader installed. If not, any ideals on how one would know which would require FAT16 and which FAT32? Wouldn't be hard to create two iso files with the FAT16 and FAT32, but don't want people to have to download both, and have to figure out which one works?ģ. Is there any program that can do what bootlace is with 64bit windows?Ģ. Don't know what causes the issue, or how one would know what flash would require FAT16 and which would need FAT32?Īll files copied to the partitions regardless of FAT16 or FAT32 are exactly the same? So, it must be something in the GRLDR.ġ. To the scandisk flashes this worked with the FAT16. So, created an iso that has the grldr installed and it can be copied to flash using dd in linux, or using rufus in windows. But windows seems to have no way to do it that I've found. ![]() Problem is that the bootlace programs no longer work under 64 bit windows, so copying the files from a zip file is no problem, but making the usb bootable is the issue. So, not clear on what could possible be the issue? PNY 120G flash, and it fails to boot if the partition is formatted with FAT16, but manually did the same process with it formatted to FAT32, and it then works just fine. Since using FAT16 worked fine on all these flashes, thought I had a solid solution.īUT hand another flash that I just tried it on. Using 4 scandisk USB drives 3 8G and 1 30G the process worked great, but required the partition to be formatted as FAT16 or it would get a message that the GRLDR was not found, but file was there. Trying to create a process to support booting my G4L project and thought I had a simple single solution that would work for linux and windows users.Ĭreated a 64M iso image that contained a partition that had the grub4dos setup as a regular usb boot loader, and also as an UEFI boot loader.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |