BlueSCSI and Atari ST ICD Hostadapter ... #167
Replies: 5 comments 15 replies
-
|
Hey Frank, I'm looking into this now with some hardware from BikerBob and hopefully I can figure out what is going on. There are some other strange issues with earlier era Sparcstations as well which might be caused by the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
It seems to only be specific ICD adapters oddly as I've tried the The Link II without issue and I have to retest but I believe my AdSCSI Pro adapter also worked. |
Beta Was this translation helpful? Give feedback.
-
|
The v2 BlueSCSI does have a backfeed jumper to put power from the berg connector onto the bus to power devices like the LINK2. |
Beta Was this translation helpful? Give feedback.
-
|
Yes "Back Feed" Jumper ... |
Beta Was this translation helpful? Give feedback.
-
|
I always used a BlueSCSI 25 D-Sub Module on the Atari and the ICD Avantage Host adapter and it has the problems described above but the BlueSCSI Desktop version works perfectly and without problems ... 25 D-Sub Version ... Desktop Version ... ... used the same SD card with both BlueSCSI Versions. |
Beta Was this translation helpful? Give feedback.
-
|
On a Atari TT with a real SCSI port the 25 D-Sub BlueSCSI works fine ... |
Beta Was this translation helpful? Give feedback.
-
|
Interesting! I don't have a DB-25 model yet but one is on it's way so I can test with it |
Beta Was this translation helpful? Give feedback.
-
|
So I started my barrage of testing and interestingly enough I found that BlueSCSI v2, ZuluSCSI RP2040 and ZuluSCSI 1.1+ all fail in the same way using the Tori MegaSTE adapter as built by BikerBob. The BlueSCSI XCVR v1 works perfectly without issue though. It's strange because in all the "failing" boards it would seem they all read the driver and load it just fine but when it gets to the TOS desktop then clicking on the C drive results in may be corrupt/damaged error. I also see no SCSI traffic at all on the lines so it's like the adapter isn't even doing anything when asked. I have external ICD clones to test as well plus 2 AdSCSI cards (earlier and later revs), plus the Link 2 so I will continue to post my findings. This is all done currently with HDDRIVER 12 but I will likely do the same tests with ICD drivers as well |
Beta Was this translation helpful? Give feedback.
-
|
There are some problems when operating the BlueSCSI v2 on the Atari TOS computer. On the Falcon I use a 25 D-Sub BlueSCSI v2 and with MiNT and the SCSILINK.XIF Driver, the WLAN only works without Dayna entries in the ini and with the help of the new BlueSCSI Accessory from Thorsten Otto -> https://github.com/th-otto/wifi_da/actions/runs/10098442601 On my MegaSTE ICD Avantage Hostadapter from tOri the BlueSCSI v2 Desktop works fine also with a LINK96/97 Hostadapter but the 25 D-Sub v2 BlueSCSI has problems. I use HDDriver 12 too ... |
Beta Was this translation helpful? Give feedback.
-
|
@franklukas can you re-run that firmware in the linked thread above? I'm sure the issue will be apparent - again the ini and the bluescsi toolbox api do the same thing so it is /likely/ data entry - which the debug firmware I built will show. If not we can investigate. |
Beta Was this translation helpful? Give feedback.
-
|
... it is about the 25 pin D-Sub v2 version use the SCSI drive section from the BlueSCSI with Atari SCSI ICD Hostadapter! The Wi-Fi fault is a problem with the Atari Daynaport Driver because when I use the original Dayna SCSILINK Hardware all is fine with the Atari use single TOS with STING or MiNT. Please describe exactly what I should do with which BlueSCSI adapter and which computer and which operating system? |
Beta Was this translation helpful? Give feedback.
-
If I'm reading it correctly that seems to be the same issue on the Atari as you had in the other thread on your mac? If so please just follow the same steps you did in the other thread with the Atari. |
Beta Was this translation helpful? Give feedback.
-
|
no !!! The Atari with MiNT and the SCSILINK.XIF driver freeze when I use the bluescsi.ini and the Wi-Fi entries in it. The SCSILINK.XIF works well with the original Dayna Hardware. Without the Wi-Fi entries in the ini and the use from the Wi-Fi DA from Thorsten Otto works. There seems to be an important difference between the Macintosh driver and the SCSILINK.XIF for Atari MiNT and the STING Single TOS driver ...? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry maybe something is being lost in translation but isn't this exactly the issue you had on the mac?
|
Beta Was this translation helpful? Give feedback.
-
|
Read ... |
Beta Was this translation helpful? Give feedback.
-
----------- bluescsi.ini ----
[SCSI]
System=Generic
EnableSCSI2=0 ; Off
EnableParity=1 ; On
Debug=1 ; On
--------------- or alternativ ---
[SCSI]
System=MegaSTE
MapLunsToIDs=1 ; On
EnableParity=0 ; Off
Debug=1 ; On
... with both ini files the BlueSCSI do not work with any ICD Atari ACSI/SCSI Hostadapter. Hard drives larger than 1GB, e.g. 9GB or 18GB hard drives, work on an ICD Host adapter. Parity is supported.
On the same Host adapter a ZULU works perfectly and without problems. The ZULU works without any config file (ini) only with the HD image on the SD card.
If the Atari Computer has a real SCSI Controller like a Falcon or Atari TT there are no problems ...
You can not use any ID or LUN ...
Beta Was this translation helpful? Give feedback.
All reactions