Problem with ZuluSCSI Daynaport emulation

[shirsch]

Since day one I've been able to get the ZuluSCSI Daynaport SCSI emulation working for a booted system by using Chooser to select and log to my netatalk server. However, it's never been willing to automatically reconnect to the server after reboot. I have to manually set it up every time, which gets old quickly. I recently acquired a real Daynaport SCSI link and discovered that it has no problem at all with persistent network volumes! This suggests there may be an issue with the ZuluSCSI emulation.

Has anyone else been seeing this issue and/or have any light to shed on the problem?

 

[campbellashe]

Make sure you don’t have the netatalk -no password setting. This prevents the saving of passwords on the client side…pulled my hair out for a while on this one.

 

[shirsch]

I'm not running with that option. When running over localtalk or via the actual Daynaport SCSI hardware it reconnects every time on a restart. The problem only occurs when networking over the ZuluSCSI Dyna API emulation. I'm thinking that the emulation is missing a subtlety somewhere.

 

[cheesestraws]

How long does it take your computer to boot? WiFi links take a lot longer to come up than Ethernet, and I wonder if the link just isn't ready yet when it tries to mount the drives...

 

[shirsch]

That was one of my first theories, but a programmer's button reboot behaves the same way.