utmapp
Unable to run NeXTSTEP / OpenSTEP / Rhapsody (x86): drive access is lost
Hello,
I have working x86 images of floppy disks and CDROMs of NextSTEP and OpenSTEP (tested with other emulators).
I tried to boot the floppies: I get a read error at the very beginning. I load a working system image with UTM: I get a Kernel Panic because it can't access the HDD at some point during the startup.
Unless someone give me a hint about a setting that I missed, I think that there is an issue with those OS' drive access.
Here are the screenshots of the verbose modes, taken with UTM 3.04.
NeXTSTEP.log Rhapsody.log Logs attached. Yes, this is related to #2730 . The only difference with this issue report is that I've tried the next step (sorry): boot directly on the installed OS image.
I've seen the same problem (with CDROM access?) trying to boot Rhapsody DR2 under UTM version 3.2.4 (58).
As I understand it, you need to select IDE HDs, use the Primary/Secondary IDE driver (and install it twice). Where I think it gets hung up, though, is that it's very picky about using two masters but I don't see a way to set up IDE channels on the virtual drives (e.g. I can't assign which one is primary and which is secondary, unless that's just based on which shows first in the devices list...but then it still seems like it's installing both the HD and the CD-ROM as primary and secondary master drives, which freaks OpenStep/Rhapsody out).
Some of this MIGHT be solvable (at least for me) if we could either:
- More directly import VMWare machines instead of just the drives, so machine config information can come over, without us needing to use virtual device settings that aren't exposed in UTM. (it seems
- Ability to select a SCSI host adapter that OS/Rhap supports, to get around needing IDE at all. I see the (unsupported) SCSI adapter in the arguments tab of the UI, but I see no way to change an entry that's already there.
