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

Boot order issue with hard drive disk image and CD image #225

Open
rwv opened this issue Aug 27, 2018 · 3 comments
Open

Boot order issue with hard drive disk image and CD image #225

rwv opened this issue Aug 27, 2018 · 3 comments
Labels

Comments

@rwv
Copy link

rwv commented Aug 27, 2018

I would like to boot freedos on hard disk image and use an iso file as a data drive. However, I encounter some strange behavior of the boot-order options. When both hard disk image and CD image are included. The hard drive boot entry will always be the last boot entry no matter the settings of boot order.
After more tests, it seems that if the CD image is include, the other two boot entry will be "disabled".

Order tables (with three entries both selected):

Description boot_order First Second Third
Hard Disk / CD / Floppy 0x132 CD Floppy hard disk
Hard Disk / Floppy / CD 0x312 Floppy (always fail) CD hard disk
Floppy / Hard Disk / CD 0x321 Floppy (always fail) CD hard disk
Floppy / CD / Hard Disk 0x231 Floppy (always fail) CD hard disk
CD / Hard Disk / Floppy 0x123 CD Floppy hard disk
CD / Floppy / CD 0x213 CD Floppy hard disk

disk image files (upload to mega.nz because file size exceeds GitHub limits)

@copy copy added the bug label Aug 27, 2018
@copy
Copy link
Owner

copy commented Aug 28, 2018

Indeed, configurations with both CD and HDD are haven't been tested much.

I don't really have the time or energy to fix this, so contributions are very welcome.

@markostamcar
Copy link

markostamcar commented Nov 10, 2018

Oh man, this bug really bums me out. It seems that using all 3 boot media types at the same time makes the boot fail completely.

I don't know much about coding an emulator but I did take a look at .js files and couldn't find anything like a bug in parsing boot media configuration etc... maybe it's a bug in the BIOS?

@rwv did you make any progress?
@copy what kind of bribe would tempt you to look into it - a beer, 6 beers, 24 beers? :D

@rwv
Copy link
Author

rwv commented Dec 17, 2018

@markostamcar nope, i haven't made any progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants