I dont know if this will be of any interest to you guys. I have a lexar 1GB flash drive. I used the mkdiskimage script and then did syslinux as described in the readme.usbkey. (the script took a REALLY long time too) I booted into 3.7 knoppix. Copied all the directories onto the key. Then copied the contents of the /boot dir into the root dir. I renamed isolinux.cfg to syslinux.cfg I had some problems because syslinux did not like the minirt24.gz file. I booted to a windows box and unzipped the minirt24.gz into miniroot.img and *BLAMMO* it booted knoppix! Just like the cd... I did have to fuss with the bios boot order.. ScottP
Scott Pasnikowski wrote:> > I had some problems because syslinux did not like the minirt24.gz file. > I booted to a windows box and unzipped the minirt24.gz into miniroot.img >What do you mean "didn't like?" What was the failure like? The only thing that I can think of that would affect syslinux would be if you had mounted the filesystem as vfat, and it for whatever reason chose to mangle the filename (a filename like minirt24.gz should normally not be mangled, though.) -hpa
Scott Pasnikowski wrote:> I dont know if this will be of any interest to you guys. > > I have a lexar 1GB flash drive. > > I used the mkdiskimage script and then did > syslinux as described in the readme.usbkey. > (the script took a REALLY long time too) >Ah yes... the script was really designed to create disk images, so it writes the entire file with zeros to keep it from being a sparse file, and to make sure the file will compress well. It's probably not what you want for block devices. It should be a fairly easy hack to fix, I just need to implement it. -hpa