Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Iso fails that uses a 2.88 floppy image #614

Closed
mpheyse opened this issue Oct 12, 2015 · 3 comments
Closed

Iso fails that uses a 2.88 floppy image #614

mpheyse opened this issue Oct 12, 2015 · 3 comments

Comments

@mpheyse
Copy link

mpheyse commented Oct 12, 2015

Functional bootable ISO, that boots from a 2.88 floppy image (Dos 6.22) fails to load in Rufus.

"This image is either non-bootable, or uses a it uses a boot or compression method that is not supported by Rufus..."

2.88 Floppy images as bootable cds are not that uncommon.

@pbatard
Copy link
Owner

pbatard commented Oct 12, 2015

That's called an El Torito ISO, and these are tricky to support properly, because you need to analyse the AUTOEXEC.BAT and CONFIG.SYS from the image and figure out how to merge the content so that it actually boots from USB. For instance, you'll find that a lot of these images expect A: as the system drive, whereas C: will be used when booting from USB (because the drive is seen as a HDD by the BIOS and not a floppy - unfortunately, this is not something that can be changed programmatically once DOS is booting).

Oh, and for the record, what you are requesting is a duplicate of #63. I'm planning to look into it, but don't expect anything fast...

@pbatard pbatard closed this as completed Oct 12, 2015
@pbatard
Copy link
Owner

pbatard commented Oct 12, 2015

Oh, and I'll add that, for the time being, you might be interested in this FAQ entry, which details how you can handle El Torito content manually (which is a good way to ensure the DOS application you are trying to use will actually work).

@lock
Copy link

lock bot commented Apr 7, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@lock lock bot locked and limited conversation to collaborators Apr 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants