similar to: 2GB USBkey and mkdiskimage

I was trying to setup dsl (damn small linux) to boot off a usb drive. I found my BIOS wasn't booting from it when using a USB-HDD mode so I found a page for using SYSLINUX to set it up in USB-ZIP mode (http://syslinux.zytor.com/usbkey.php). I made a mistake and (doing exactly what the page warned against not doing) used the mkdiskimage command on the wrong drive (a 230Gb NTFS external

> > Both sticks show very unusual factors for heads and sectors > > which are hardly intentional. If BIOS gets confused like fdisk, > > then the failure to find files is quite plausible. > > > > ------------------------------------------------------------- > > > > Could you please exercise what is described for Linux in > >

I've been using a USB flash drive for quite a while now, and in my previous system it worked great, but, I find with my new motherboard now that I have upgraded I can't boot it. So I decided to try the trick mentioned in the README.usbkey file where you make a ZIP drive like image on the flash drive and set the BIOS to boot a USB ZIP drive instead. Unfortunately, it still doesn't

Hi, Ronald F. Guilmette wrote: > what exactly did we determine that GA-M55Plus-S3G is failing > to support? It appears to be related to the choice of CHS addressing with the FAT filesystem. This opens the door for misperceived factors of heads per cylinder and sectors per heads. My current suspicion is that the partition end did not expose the effective factors in its end CHS address, so

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

I'm playing with syslinux 3.0x to get PC to boot from USB key... In particular, I'm giving a look at the "ZIP geometry hack" to get some more BIOS boot working with USB... Some question: - if we have a usbkey with a single partition, can we change the geometry without requiring to reformat the partition? Or is a reformat unavoidable? - at the moment we can use the "ZIP

--- utils/mkdiskimage.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/mkdiskimage.in b/utils/mkdiskimage.in index 533193a..a95a077 100644 --- a/utils/mkdiskimage.in +++ b/utils/mkdiskimage.in @@ -218,7 +218,7 @@ $totalsize = $c*$h*$s; $tracks = $c*$h; # If -s is given, try to simply use truncate... -unless ($opt{'s'} && truncate(OUTPUT,

On 01/21/2014 11:13 AM, Thomas Schmitt wrote: > > My current theory is that vendors prefer to record > a cylinder aligned end CHS address over recording > an end CHS address which exploits the whole capacity. > This is used as an (inofficial ?) protocol to publish > the CHS factors H' and S'. > Indeed it is -- at least some BIOSes "deduce" the H/S to use

utils/mkdiskimage.in: With option -s: Avoid zeroizing the partition even if truncate() failed. --- utils/mkdiskimage_patched_01.in 2014-01-30 20:43:02.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:45:09.000000000 +0100 @@ -217,8 +217,11 @@ print OUTPUT "\x55\xaa"; $totalsize = $c*$h*$s; $tracks = $c*$h; -# If -s is given, try to simply use truncate... -unless

Hi, i too played with mkdiskimage in order to get more Linux examples. When i applied it to a real 2 GB stick with write speed 4 MB/s i had enough time to add some pacifier code to the big zeroizer loop. (-s does not prevent zeroizing on block device. Probably because truncate() fails.) My pacifier is combined with what Perl advised me when i tried "fsync(OUTPUT);". Of course this

utils/mkdiskimage.in: New option -S to sync zeroizing after each cylinder and to issue pacifier messages. --- utils/mkdiskimage_patched_03.in 2014-01-30 20:54:27.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:59:19.000000000 +0100 @@ -139,6 +139,7 @@ if ( $file eq '' || $c < 1 || $h < 1 || print STDERR " -4 use partition entry 4 (standard for

Hi, following is a series of patches derived from my proposed diff. Based on syslinux-6.03-pre1, but should also apply down to 4.xx. I hope to have imitated the changelog style sufficiently. Mine are a bit longer than usual with patches in the archive, i fear. Instructions for the future are welcome. Each intermediate state is tested for its designated purpose only. The final state after

Hi Maybe HPA or Murali could help me with this one, or anyone who got the following working. I spend numerous hours reading the list and googling without success. I'd like to create a bootable USB stick and CDROM that will do the following. I will have a menu, from which I could pick a specific dos image (not partition). The dos images could have up to 20Megs in size. The goal is to have

Hi, me: > > [mkdiskimage] -s does not prevent zeroizing on block device. Probably > > because truncate() fails. hpa: > Yes, we should probably fix that. The tool was originally designed for > images, not for hardware devices, and it doesn't make much sense to zero > the whole hardware device like that. Maybe for privacy reasons ? But indeed: -s should skip zeroizing,

Hi, this is the diff which i consider a halfways reasonable solution for the following problems with mkdiskimage: 1. Ignoring option -s if the target file is not suitable for truncate(). 2. Miscalculation of truncate() size by a factor of 512. 3. The storage capacity of device files can only be measured for Linux block devices. 4. Long time of silent work when slow devices (e.g. USB

I have had a problem with mkdiskimage for quite a while. It seems to always exit with the syntax messages. I'm not really familiar enough with Perl to figure out exactly what it's checking for there that it determines is incorrect, but, my guess would have to be that it doesn't like the letter. Eg, I think the last time it suceeded I was running it on sda, but, not I'm typically

On 07/11/2014 12:33 AM, Thomas Schmitt wrote: > Technical side note: > It turned out that the lseek(2) function of NetBSD does not work > with SEEK_END as expected from the manual. libburn had to resort > to a binary search with try-and-error to determine device sizes. > I did not check perl's sysseek() whether it suffers from the > lseek(2) shortcomming, but i would expect

Could i get an example to make a binary hard disk image with `mkdiskimage', populate it and install syslinux please? Preferably with a single FAT partition. On Wed, Jan 22, 2014 at 9:20 AM, Rich Mahn <rich at lat.com> wrote: > > > > Both sticks show very unusual factors for heads and sectors > > > which are hardly intentional. If BIOS gets confused like fdisk,

Hi, Dean Graff wrote: > Also, I am trying to use the syntax: > > mkdiskimage -z -F -4 binary.img 1000 > > To get that zip drive geometry for my images and increase the > portable ness of their boot ability. Will this work, to make the zip > drive geometry and then dd or cat this to the 'mass storage device' ? The copy program should not care what is in the image

Sorry for the delay, I should not send email on an holiday week-end. I'll try to answer all the questions by explaining what does work for me right now, and what I'd like to do. I have a script to create the a USB stick or an ISO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as