Welcome, Guest. Please login or register.

Author Topic: Minimig ITX / TF536 and attempting to use scsi.device on both  (Read 605 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Thomas


There is a big difference between multiple IDE expansions in an A2000 and the mainboard IDE of an A600 or A1200.

The former do Autoconfig which lets the OS assign a different memory address to each expansion. The latter just appears at a fixed memory address.

And that's your problem: both the Minimig and the TF mimic the onboard IDE at its fixed memory address. As the CPU is on the TF, it takes precedence and overlays the same address of the Minimig. You cannot use both at the same time.


Offline Thomas

Re: Minimig ITX / TF536 and attempting to use scsi.device on both
« Reply #1 on: November 26, 2025, 02:07:36 PM »

I am not a hardware expert but I believe in theory this should be possible. You would also have to make a 2nd.scsi.device which looks at the new address range. And you won't be able to boot from the TF IDE any more unless you hack a Kickstart ROM which contains both scsi.device drivers.

Offline Thomas

Re: Minimig ITX / TF536 and attempting to use scsi.device on both
« Reply #2 on: November 27, 2025, 01:09:52 PM »

No. The name "scsi.device" does say nothing about its function. The A4000T ROM has a scsi.device for IDE and another one for SCSI. There are many more expansions which use the name scsi.device for their drivers, but they are all for different hardwares. It is a convention that drivers which find the name scsi.device already in use rename themselves to 2nd.scsi.device, 3rd.scsi.device and so on. The same happens in the A4000T. If there are no IDE devices, the SCSI driver is called scsi.device. If there are no SCSI devices, the IDE driver is scsi.device. If both are present, IDE is scsi.device and SCSI is 2nd.scsi.device.