While previous version of dopus5 (5.82) which done on SASC can runs without problems without s-s , our one just stuck when open dopus5.library. I.e. code think that opening of library happens fine, but then, seems libinit code of dopus5.library fail by some reasons.
To have it works the same as sasc version will be good because of that reasons:
5.82 works without startup-sequence on the same setup, while 5.90 not, and i currently didn't see why it should't.
some 68k users already report that they can't run it without s-s , so they try it and fail (so they use it like this in some conditions). There is no "error" , or anything like that, just "forever stuck and eat of memory" when it open dopus5.library.
testing stuff without s-s always was (and still) good, when user want faster check when nothing involved.
The good suggestion come from Xenic:
Before you start debugging the library I suggest you find what is missing in the startup-sequence that 68k Dopus5 needs. Start at the bottom of the startup-sequence and eliminate one thing at a time, rebooting in between and trying to start Dopus5. Dopus5 should start each time until you eliminate the thing that it needs. Then you'll know what to look for in the library,