Welcome, Guest. Please login or register.

Author Topic: WB 3.1 will not boot on A2000!?  (Read 4867 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Matt_H

Re: WB 3.1 will not boot on A2000!?
« on: September 01, 2017, 09:47:03 PM »
I'm using one of these card readers (I think it's the -50B) on an A2000 with a 2091 with no issues. Not really sure what the problem could be. I have LUNs disabled so only the PCMCIA slot works, which I use with a CF adapter. With LUNs enabled, the machine takes far, far longer to boot - longer than I have patience for ;) - since it polls each LUN at each SCSI address. My 2091 has 2MB of RAM installed and the system is also using a 2630 accelerator with 4MB. I don't remember my jumper settings on the card reader, but presumably I have termination enabled since it is the only SCSI device in the machine. I have nothing connected to the external SCSI port.

It sounds like you are able to boot from floppy and insert the CF drive afterwards to work on it in HDToolbox? Are there any filesystems installed in the RDB? Maybe the system is getting hung up on something there. SCSI reselection may be another flag worth investigating.

Are the v7 ROMs installed correctly (i.e., not accidentally swapped)? What revision DMAC chip is in your 2091? What revision SCSI chip?
 

Offline Matt_H

Re: WB 3.1 will not boot on A2000!?
« Reply #1 on: September 02, 2017, 12:55:35 AM »
I believe the 2091 controller itself is ID 7, so your device should have worked at ID 0. There are a number of hidden RDB flags having to do with identifying the last device on the chain so that the controller stops looking for others. (Sometimes HDToolbox with start up with a message "Drives have been added or removed from the system" which is an indication that it wants to update that flag.) I wonder if one of those flags was choking with ID 0.

My controller starts to boot instantly with LUNs disabled, but enabling them added a 20-30 second delay. That delay wasn't worth it to me since I don't need to sneakernet files to the machine. It's on the network so I just send things over that way.

For transferring from Windows drives you need fat95 on Aminet. I think you'll need to create a DOSDriver, too. GiggleDisk (also Aminet) can pull the geometry and do that for you.
 

Offline Matt_H

Re: WB 3.1 will not boot on A2000!?
« Reply #2 on: September 02, 2017, 07:46:14 PM »
Sneakernet is a joke networking term referring to transferring files by walking them from one machine (while wearing sneakers :) ) to another using removable media (floppy, CD, USB stick, etc.). No actual network hardware/software is involved.

(To explain my previous comment further, since my machine is on the network, I don't need to use any of the other card reader slots for transferring files back and forth and so I disabled LUNs.)