search for: mkdiskimag

--- 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...

...d with various options, suitable and unsuitable file types of various sizes. ---------------------------------------------------------------- I will think about another patch for an option which zeroizes the whole device even if the partition size is given explicitely and matches a cylinder end. (mkdiskimage_05.patch only zeroizes a known incomplete cylinder after the partition end.) Although mkdiskimage should be suitable now for USB sticks on unix-like systems beyond Linux, i still have no clue about USB sticks at NT/2K/XP/DOS systems. There is hope that the sysseek() method of size determination w...

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; $track...

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 adv...

...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 hard-drive). I typed 'sudo ./mkdiskimage -4 /dev/sdb 243 64 32' instead of typing /dev/sdc (for my 250mb usb drive) and now all my data on my external drive is inaccessable from Linux and Windows. I haven't performed any other read,wri...

...n the failure to find files is quite plausible. > > > > ------------------------------------------------------------- > > > > Could you please exercise what is described for Linux in > > http://www.syslinux.org/doc/usbkey.txt > > and check whether > > mkdiskimage -4 /dev/sda 0 64 32 > > prepares a problematic stick for a normal installation of > > Clonezilla, which then boots ? > > > > I have to disagree., at least at this point. > I have to disagree with the disagree, at least so some extent. I find mkdiskimage to be an ex...

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 ||...

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

...f hardware. To ease the process, I want to automate image creation (floppy or harddisk), and use it with memdisk. I use the mkfloppyimg.sh script and it is working fine up until 8M in size, if I go higher than this, it doesn't work, and I can't boot the image. I did try to do the same with mkdiskimage without success, I probably miss something in the way to create the image. My question is simple, is there any recipe to create a +8M dos/freedos image I could use with syslinux. Many thanks.

Hi, I am trying for quite some time to create a bootable hd disk image with mkdiskimage (included in the syslinux distribution) and the combination isolinux/memdisk. It just won't work:-} I have done the following: [snip] # ./mkdiskimage -d -o disk 256 32 1 640 # losetup -o 640 /dev/loop3 disk # mount /dev/loop3 /mnt/3 # mount | grep loop3 /dev/loop3 on /mnt/3 type vfat (rw) :...

Hi, I'm trying to make a USB-ZIP bootable filesystem on my USBkey, which is 2GB. The problem is that "mkdiskimage -4 /dev/sda 0 64 32" fails due to the large size. The number of sectors is 4005888/(64*32) = 1956, which is more than the maximum 1024. Is there any way around this or is it just not possible to make this USBkey look like a Zip drive? Regards, Ole Jacob

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...

utils/mkdiskimage.in: Option -s caused freshly created image files to be too small by a factor of 512. --- utils/mkdiskimage_orig.in 2014-01-23 12:23:34.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:35:13.000000000 +0100 @@ -218,7 +218,7 @@ $totalsize = $c*$h*$s; $tracks = $c*$h; # If -s is given,...

utils/mkdiskimage.in: Replaced the partly linux-specific file size determination by a sysseek() experiment. --- utils/mkdiskimage_patched_02.in 2014-01-30 20:49:46.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:50:59.000000000 +0100 @@ -19,6 +19,7 @@ use bytes; use integer; use Fcntl; +use Fcntl qw(:see...

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...

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 sticks) get for...

...d values 175-9-63 instead of 21-254-63 But the same message also apply if I use the 1.4M freedos image itself. Probably something change, because in Murali document http://people.cs.uchicago.edu/~gmurali/gui/isodos.html he mention being able to do 10M image. The syslinux doc talk about mkdiskimage to create disk image. I try to use it without success. What I did is the following mkdiskimage /tmp/dexter1.img 2 255 63 (this create a 16M image) mount -o loop,offset=32256 /tmp/dexter1.img /mnt/loop ++ I copy my dos file in /mnt/loop I change my syslinux.cfg to be label 1Dexter-bios8217-b...

...gt; > Unclaimed space may remain after the end of the partition if the > partition size stems from option -M, or is computed from arguments > h and s because argument c is 0. > Especially on device files, such space might contain a backup GPT > which would be invalid after mkdiskimage but could lure partition > editors into restoring the outdated main GPT. > This change overwrites the space between partition end and image > file end by zeros, unless option -s is given. (-s shall prevent > zeroization in general.) I have concerns about this, especially in th...

...254-63 > > But the same message also apply if I use the 1.4M freedos image itself. > > > Probably something change, because in Murali document > http://people.cs.uchicago.edu/~gmurali/gui/isodos.html > he mention being able to do 10M image. > > The syslinux doc talk about mkdiskimage to create disk image. I try > to use it without success. What I did is the following > > mkdiskimage /tmp/dexter1.img 2 255 63 (this create a 16M image) > mount -o loop,offset=32256 /tmp/dexter1.img /mnt/loop > ++ I copy my dos file in /mnt/loop > I change my syslinux.cfg to b...

...rs 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 http://www.syslinux.org/doc/usbkey.txt and check whether mkdiskimage -4 /dev/sda 0 64 32 prepares a problematic stick for a normal installation of Clonezilla, which then boots ? This might involve the need to learn how to perform the advised mkdiskimage run on systems other than Linux. Such examples would be valuable for the wiki improvement. (What is a usual addr...