tin wrote:I for my part never tried CE in a chain with another device, so it could be an issue in itself.
tin wrote:There might be a clash with the ACSI IDs. In your config you told your CE to react to 3 ACSI IDs, namely:
-act has SD card harddisk on ID 0 (e.g. "boot here first").
-mount raw USB sticks (atari formatted ones) and make them accessible on ID 4 (e.g. "boot here next if there's nothing bootable on SD card). Note that this is disabled by your currently chosen "Mount USB sticks as translated" option.
-boot the translated driver (CE_Dd, that translates USB sticks and Network drives for use in TOS) on ID 5 if no bootable sd card or raw usb stick were found
Assuming your external drive has ID 4, too, thats problematic - the IDs have to be exclusive.
This very well might not solve your boot issue - I for my part never tried CE in a chain with another device, so it could be an issue in itself.
Let us know if this changes anything.
Jookie wrote:tin wrote:I for my part never tried CE in a chain with another device, so it could be an issue in itself.
Chaining CE with some other ACSI device on ACSI bus might be problematic - there wasn't a clear specification on how to do that, so there might be some issue with that.
Chaining on SCSI bus might be better choice, but I guess only on real SCSI-2 buses like in TT and Falcon - some older ACSI-to-SCSI adaptors didn't have the correct signals timing and caused issues with CosmosEx device.
dblanch369 wrote:No, I set up ID 4 in the CE config, because I read somewhere that for the CE to read an external drive, it needed to be set to "Raw", that's why I set it that way. Are you saying I should turn ID 4 to "Off"?
dblanch369 wrote:Yikes, I was afraid of that. Can you think of anything I could try, Jookie?
dblanch369 wrote:but not the other way around (presumably this is what I need CE_DD to be running).
tin wrote:dblanch369 wrote:but not the other way around (presumably this is what I need CE_DD to be running).
CE_DD is not needed in order to have the SD card show up as an ACSI hard disk. That work is purely done by your hard disk driver - basicly the CE behaves as a harddisk for that use case, just like the Ultrasatan. You told CE "be an ultrasatan on ACSI ID 0" in your config.
CE_DD is only needed for translated drives (e.g. Mounts or Thumb Drives that are not TOS formatted) that need to be emulated ("translated") as tos devices.
That your CE "disappears" as soon as you chain it with the other hard drive is definitely unrelated to CE_DD being loaded or not.
dblanch369 wrote:And I want to thank everyone who helped and responded, and others who have shared their experiences on these forums, it helped immensely!
Users browsing this forum: No registered users and 8 guests