Issue: Release ZuluSCSI firmware v2023.11.22 breaks implicit device typing #340
Comments
|
@ZigZagJoe thanks, as of last night I un-flagged the v2023.11.22 release as latest, and users should continue to use the previous v2023.10.31 until then. We expeect to have the problem resolved no later than Monday morning. |
This is a fix for issue: #340 The device type from a filename (e.g. NE5.img) and its implicit scsi vendor and model stings weren't being set after moving a lot off the SCSI settings code to ZuluSCSI_settings.cpp. This fix addresses the issue. Although more effort, it might make sense to move more of the SCSI device setup to ZuluSCSI_settings.cpp like image discovery. The current fix just plugs into ZuluSCSI.cpp `findHDDImages()`.
|
Thanks for the find @ZigZagJoe |
Yes, looks good. I just gave it a whirl and I see the expected device info strings for both CD-ROM and network device types. CD-Rom mounts, Dayna driver recognizes the network device and network functionality works too. |
Restore implicit device settings. This is a fix for issue: #340
|
This has been fixed with the v2023.11.27 release |
Issue:
All devices are getting initialized with info for fixed drives. Implicit device types - such as a file named NE0.bin is a network device - are only determined later. The drive info strings need to be updated with any drive type info found while scanning for images.
I specifically had this issue with network devices, seems likely the same applies to other image types (ie. CDs).
Replication:
This is only an issue with the 11-22 release - 10-31 is OK. Suspect is related to 7f4104c.
Screenshot before I added quirks=1 to the zuluscsi.ini
the zululog is from a build i was using to diagnose. Only change is to make setDefaultDriveInfo report what settings it is initializing with. Issue occurs with the official builds.
zululog.txt
zuluscsi.ini.txt
The text was updated successfully, but these errors were encountered: