search for: diskcopy

...pressed --> 35KB gzip'd) and maybe Smart Boot Manager (gzip'd COM32 binary instead of normal COM32 binary?). I'm using both on a simple bootdisk, and all space savings are welcome. a workaround could ofcourse be to write each of them to a diskette, then read in the diskette (RAREAD, DISKCOPY, Linux dd, maybe RAWRITE), compress the imagefile, then load it using Memdisk which has (g)zip decompression support. other possibility would be to create an intermediate loader (let's call it 'ungzip') which would decompress the GZ and then let the decompressed binary ('kernel'...

...mdisk boot image). Expected behaviour: Drive A: --> see contents of 360KB boot imagefile Drive B: --> see contents of 1.44MB physical diskette - without diskswapping/pausing diskswapping normally only happens if drive not ready or driveletters are pointing to same diskdrive. (DISKCOPY A: B: on a single-floppydrive system for example) Replacing only MEMDISK by v3.09 works. Guess I should have been testing earlier in order to help release a flawless v3.10, but I disliked signing up for even more mailinglists. Bernd

Hi: Thank you very much for creating this very useful program. I downloaded the DOS version because there was a suggestion in th isolinux website. I was not able to detect the cd-rom on my pentium II computer with Award BIOS 4.51 v 1.10. I tried to set the IDE i/o address but I am not sure where to get the i/o address information. I used the i/o address in the Win98 device manager IDE

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If