[syslinux] Large Floppy Images

[Egan Ford]

Thanks, already tried it, I still get:

Non-System disk or disk error
Replace and press any key when ready

> -----Original Message-----
> From: syslinux-bounces at zytor.com 
> [mailto:syslinux-bounces at zytor.com] On Behalf Of ganapathy 
> murali krishnan
> Sent: Thursday, February 17, 2005 2:23 PM
> To: egan at sense.net
> Cc: syslinux at zytor.com
> Subject: Re: [syslinux] Large Floppy Images
> 
> 
> I use a 10MB floppy image with ISOLinux. If you have a working 2.88MB 
> bootable image, and just want to enlarge it look at the 
> "{new,}mkfloppyimg.sh" script in 
> http://people.cs.uchicago.edu/~gmurali/gui/downloads.html. Also don't 
> forget to tell memdisk about the non-standard geometry.
> 
> - Murali
> 
> Egan Ford wrote:
> 
> >I am still unable to build and boot large floppy images.
> >
> >1.44, 2.88, and any size HD images work great.  No problem.  
> However I have
> >BIOSes with problems booting HD images and would like to get 
> large floppy
> >working.
> >
> >I have tried every script and method I could find with PC 
> DOC 7 and MS DOS
> >6.22.  I have spent too much time analyzing boot sectors.
> >
> >So a few questions:
> >
> >1.  Who has actually see it work?
> >2.  How did you make the image?  Assume nothing, the more 
> detail the better.
> >3.  Can you provide a URL to a large floppy image?  I cannot 
> tell if I have
> >a BIOS problem or an image creation problem.  I'd just like 
> to see one boot.
> >An ideal image would be blank with COMMAND.COM only.
> >
> >Thanks.
> >
> >
> >_______________________________________________
> >SYSLINUX mailing list
> >Submissions to SYSLINUX at zytor.com
> >Unsubscribe or set options at:
> >http://www.zytor.com/mailman/listinfo/syslinux
> >Please do not send private replies to mailing list traffic.
> >
> >
> >  
> >
> 
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>