ChrisR3tro wrote on 2026-11-02, 10:48:

TeleTubby666 wrote on 2026-11-02, 09:45:

For now I simply call it twice in AUTOEXEC.BAT, which works. But maybe CDBeQuiet could just retry once automatically when this error comes up?

CDBQ is designed to be called after MSCDEX is loaded, did you try that?

EDIT: I think, I never tested much with SHSUCDX. Can you tell me first, if your drive behaves normally with MSCDEX?

Sorry, I forgot to reply here. Yes, with MSCDEX, both drives spin down as intended.

TeleTubby666 wrote on Yesterday, 07:39:

Sorry, I forgot to reply here. Yes, with MSCDEX, both drives spin down as intended.

Ok, I tried it with SHSUCDX v1.09 now and can confirm, that CDBQ doesn't work with that, but I got another error (device not ready) and it does not resolve if I execute CDBQ a second time. It may or may not have to do with that unit attention condition, but it's possible. It would obviously make sense to not have CDBQ rely on MSCDEX or at least work with SHSUCDX, but I will have to make some time to check further into this. Thanks for pointing it out, though. For now, I put it on my todo list.

Regards
Chris

This haunted me, so I took some time today and with a little help of Claude, I actually fixed this + some other improvements.
This should work now with SHSUCDX. In my tests, the speed setting now even survived when CDBQ is loaded prior to MSCDEX or SHSUCDX. (but please don't do that)

Here's a new version: https://www.a20gate.net/dos-tools/cdbq/CDBQ140B.ZIP

If this also works for you, I'll make it a proper release. Anyone who wants to test this, please go ahead - much appreciated.

- Chris