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

BeOS issue #172

Closed
ArtiomWin opened this issue Aug 25, 2017 · 8 comments

Comments

Projects
None yet
3 participants
@ArtiomWin
Copy link

commented Aug 25, 2017

BeOS installation CDs for earlier versions don't see hard disk, for example, BeOS 4.5 gives: "Boot failure: The boot loader was unable to find a BeOS volume to boot from. If you are trying to boot from the CD-ROM and find that you are unable to do so, press space during the boot sequence to enter the boot menu and select "Boot from CD-ROM" as the boot volume.".

@claunia

This comment has been minimized.

Copy link
Contributor

commented Aug 26, 2017

@ArtiomWin are you using a .BIN/.CUE that correctly describe the 3 tracks present in the CD or the host drive?

What channel is the emulated CD-ROM connected to?

What motherboard are you using?

BeOS gives that error in a lot of real motherboards because of problems with the IDE controller and/or channel.

@ArtiomWin

This comment has been minimized.

Copy link
Author

commented Aug 27, 2017

Tested motherboard - ASUS P/I-P55T2P4
CD-ROM - ATAPI (PIO and DMA) - channel 0:1
Most of BeOS install images are in .mdf/.mds (I've downloaded the from BetaArchive) (BeOS 3.1 is .bin/.cue, BeOS 4.5 is .iso)

@OBattler

This comment has been minimized.

Copy link
Collaborator

commented Jan 16, 2018

Try the latest 86Box. Back in August, the PIIX IDE bus master for DMA was not working right (if at all) and there were other IDE bugs as well since fixed, and I suspect that might have been causing the problem.

@ArtiomWin

This comment has been minimized.

Copy link
Author

commented Jan 20, 2018

I've tried revision 1378. Still the same thing.
20180120_184036
20180120_184233
20180120_183315

@OBattler

This comment has been minimized.

Copy link
Collaborator

commented Jan 21, 2018

Please upload 86box.cfg, the NVR folder, and the hard disk and CD-ROM images you're using somewhere, so I can reproduce this bug and see what's going on.

@OBattler OBattler self-assigned this Jan 21, 2018

@ArtiomWin

This comment has been minimized.

Copy link
Author

commented Jan 21, 2018

Here's link to archive with config and disk images: https://mega.nz/#!FIsEzTTK!9inXte_Fg-Bm3Ma2_5dscHKirMWtiF8J9PGeiaJvYAs

@OBattler

This comment has been minimized.

Copy link
Collaborator

commented Jan 24, 2018

OK, I'm downloading this. Hopefully I can get this done today.

@OBattler

This comment has been minimized.

Copy link
Collaborator

commented Jan 24, 2018

I just look at this, and I can't see anything wrong on the emulator's side. I also heard that this issue tends to happen a lot on real hardware as well, so unfortunately, I have to close this with "can't fix".

@OBattler OBattler closed this Jan 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.