-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #551 is causing problems #24
Comments
Reference PR FujiNetWIFI/fujinet-firmware#551 |
Hi,
any news?
==
mozzwald ***@***.***) schrieb:
… Reference PR FujiNetWIFI/fujinet-firmware#551
<FujiNetWIFI/fujinet-firmware#551>
—
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZY3P3HUY6ODJ2TFBT64ZD3WXPORDANCNFSM6AAAAAAU36DP2E>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi, it would be great if there was an option to get an unmounted drive go offline again. See my suggestion on original post. |
Done in this commit. FujiNetWIFI/fujinet-firmware@07b666f |
Hi @tschak909, I am not sure if the "offline flag" function already is in the firmware dated 2023-03-18. |
While it is true that ejecting a disc does not take a drive offline this new behaviour is causing problems.
All ejected drives now reply to a drive status command which makes FujiNet occupy up to all drives on the serial bus.
So we can no longer for example copy a real disk using a real drive to an ATR on the FujiNet because we have more than one drive with the same drive ID active on the bus.
Beyond this all software that relies on the old behaviour (drives going offline) will eventually have to be rewritten.
I guess it would be more compatible if the $E9 command (unmount drive image) would work like before and only if maybe AUX2 MSB is set the drive does not go offline. So we have both: compatibility with exisiting software and the means to unmount an image without having the drive go offline. Plus of course we can again use other drives to copy data from.
XeAtari
The text was updated successfully, but these errors were encountered: