similar to: Mkdiskimage exits with syntax (maybe drive letter problem?)

Hi there guys! I want to set up Puppy-Linux to run off a 2GB USB key-drive in native mode (I.e. not as a virtual machine, which I'm finding runs too slow on my system, under XP.) To test it out, I want to run off a 150GB USB HDD. Now this drive is NTFS formatted and way bigger than the 1GB file structure limit that I read about in the Syslinux documentation. There's only one

Dear All I have a problem with my Compaq EVO n410c laptop. I want to install Windows (Win98/WinXP) on it. But this laptop don't have any floppy/cdrom to boot from. I have try to use My USB Drive to boot, using syslinux. Here's my step 1. Format the USB Drive using "HP USB Disk Storage Format Tool" 2. Install syslinux (syslinux -f F:). F is my USB Drive 3. Using

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

Thanks Nazo, for that amazing long answer. The problem is, though, that you're talking to an _XP user_, so I can't: "Just use dd with if=/dev/sda" because that's Dutch to me. I even had trouble understanding what a "distro" was, till I looked it up. And I can't run "mkdiskimage", because it doesn't run under XP. Also, according to

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

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

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

Hi, I saw a post you made on a forum quite some time ago about booting linux off a USB drive with compatible bios via ISOlinux. I'm currently trying to do the same thing and keep running into problems with my initrd. This is probably caused by the fact that I don't really know what I'm doing! I was wondering if you found any useful info on the net you could point me in the

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

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

On 07/10/2014 12:18 PM, Geert Stappers wrote: >> >> 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. > > Yes, they are long. > There

Office Depot ran a deal with a Cruzer Micro 512MB (actually, around 488MiB) for about $20 after a rebate I may not see for months. I saw the ad yesterday and stopped by pretty well first thing this afternoon to snatch one up while they were still there since I've been having to make do with two 256MB drives to hold all the data I neded since one drive couldn't hold enough (though I must

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

Hallo, Mattias, Du meintest am 28.01.14: >> 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. > Probably not. But a left over backup GPT at the end of a "disk" (hard > disk, thumb drive, SSD, eMMC) now confuses some UEFI

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

I recently got a cheap PenDrive iVO which I'll be the first to admit is anything but perfect, but, a pretty decent player considering it's cost is that of the other players with half the memory. One of the things I was looking forward to was having a great bootable flashdrive with my favorite linux rescue image and a few other diagnostic/repair things. Unfortunately, since I tried to put

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