Almost transplanted NeXTSTEP

Disk command errors
Disk command errors

I forgot just how crap pci ide controllers and disks can be.

I installed using Qemu 0.9 and having it drive the disk directly.   Naturally, MS-DOS works fine.

Author: neozeed

I live in SE Asia, doing generic work, enjoying my life & family

9 thoughts on “Almost transplanted NeXTSTEP”

    1. There is, I haven’t tried it with later versions. The P4 I was transplanting this to doesn’t have a SCSI controller, and I don’t have any SCSI disks..

        1. I thought it was more so to load the ‘beta’ drivers, the Dual channel Intel PII chipset or something like that one.. . I’ve used it on a P4 board in the past, although obviously not a 40GB disk jumpered to support only ‘8GB’ .. I may have to see how tricky it is to try other drivers.

  1. I do things like this with VirtualBox, raw disk access works pretty well. I’m pretty sure I installed NeXTSTEP once like this – although I didn’t use a “real” disk, I installed it on a CF-Card that I accessed via raw disk access.

    Cheers,

    -F

  2. This reminds me of the strange behavior exhibited by modern versions of qemu. I installed NeXTSTEP 3.3 on qemu 2.7.0 and the same ‘interrupt timeout’ errors. In that case, it was that edge triggered interrupts weren’t being handled properly. It was fixed by applying the first half of this patch: https://patchwork.ozlabs.org/patch/208252/

    Maybe whatever Intel did in this i8xx chipset interrupt controller wasn’t standard?

    1. It could be a hint, that is for sure! I never thought my old p4 ‘white box’ was such a special thing as it installed NS without any issues, but obviously it was.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.