Hi!

Any idea why I get the "No Device Found" error when launching the WiFi Desk Accessory? I'm using version 1.4 but I have the same issue with 1.1. The error says SCSISelect Failed, and the debug logs go (and then it repeats):

handle_timer - idle, updating info handle_timer - idle, updating info handle_timer - idle, updating info handle_timer - idle, scanning scsi[-2]: SCSISellect failed handle_timer - checking for scan completion scsi[-2]: SCSISelect failed Click to expand...

I custom-installed DaynaPORT SCSI/Link. Networking otherwise works fine -- I can browse the web. I'm on a MacPlus, using a BLUESCSI with MacPack on it, System 7.1 (issue also happened on 7.5), and the only fields in my bluescsi.ini is WiFiSSID, WiFiPassword, and System=MacPlus.

Any suggestions would be appreciated!

Thanks kindly, and please let me know if more information is required from me as I am new to the community. :)

I've seen one or two people report a similar error but not sure what the common denominator is. Are you on the latest bluescsi firmware?

Pinging @jcs if he has any thoughts.

>> jenny said:

Hi! Any idea why I get the "No Device Found" error when launching the WiFi Desk Accessory? I'm using version 1.4 but I have the same issue with 1.1. The error says SCSISelect Failed, and the debug logs go (and then it repeats): I custom-installed DaynaPORT SCSI/Link. Networking otherwise works fine -- I can browse the web. I'm on a MacPlus, using a BLUESCSI with MacPack on it, System 7.1 (issue also happened on 7.5), and the only fields in my bluescsi.ini is WiFiSSID, WiFiPassword, and System=MacPlus. Any suggestions would be appreciated! Thanks kindly, and please let me know if more information is required from me as I am new to the community. Click to expand...

Nevermind... I just reread and you stated you got on to the web

>> eric said:

I've seen one or two people report a similar error but not sure what the common denominator is. Are you on the latest bluescsi firmware? Pinging @jcs if he has any thoughts. Click to expand...

Yep, on the latest firmware.

That looks like a bug in handling a device-not-found condition where it's still trying to a periodic scan and ends up doing SCSISelect(wifi_scsi_id) but wifi_scsi_id is -2 (WIFI_SCSI_ID_NONE).

But as for why it's not finding the device in the first place, I'm not sure. The logic is pretty simple: loop through each available SCSI id, get the SCSI bus, select that id, send a short SCSI inquiry command, if it succeeds, do it again with a longer Inquiry buffer to allow the full response to be sent, then check if the vendor is "Dayna" and product is "SCSI/Link".

More debugging could be added to that loop to see which part is failing I suppose.