DOpus 5.91 and 5.92 crash on A3000

[Overmann]

Hello there,

I am running a pretty stock A3000 with OS 3.1.4 (3.1.4 roms) and I'm having problems getting DOpus 5.91 and 5.92 to run. I have tried running it on both my A3000 and using winUAE with more or less the same results. When I launch the progress bar pops up and drags along until I get a message saying "cannot draw screen" or something to that effect. I click continue and it goes on util it starts DOpus and draws the first lister on screen. It then crashes and I get a 8000 0004 error.

In WinUAE I tried setting the FPU to 68882 instead of 68881, and that made it possible to launch the program and begin using it but then I would suddenly get a message saying that "Unable to validate DH1" (which is the partition with DOpus on it). Strange? I'm stumped, but that honestly doesn't take much. Any ideas?

[daxb]

Does it work with V5.82?

[Overmann]

Originally Posted by daxb

Does it work with V5.82?

I have tried with 5.5 now and that appears to work without issue. I'll spend some time updating to 5.82 and check with that version as well.

[jPV]

I've been using 5.82 daily for 20 years now (mostly under MorphOS nowadays), and it's been very stable. Even though the open source versions have added couple nice features, they've been too unstable for real use in my experience. And are more demanding for real 68k machines.

[Overmann]

Originally Posted by jPV

I've been using 5.82 daily for 20 years now (mostly under MorphOS nowadays), and it's been very stable. Even though the open source versions have added couple nice features, they've been too unstable for real use in my experience. And are more demanding for real 68k machines.

I just updated to 5.8 and allthough I installed specifically NOT to start on boot it has now replaced my workbench, and I am unable to change it back. Running the install-script and changing the startup option does nothing. Do you know how I can go about it?

On a positive note, it is running like a champ :P But if I try to quit DOPUS I just get a gray backdrop. I am not returned to workbench.

[jPV]

Originally Posted by Overmann

I just updated to 5.8 and allthough I installed specifically NOT to start on boot it has now replaced my workbench, and I am unable to change it back. Running the install-script and changing the startup option does nothing. Do you know how I can go about it?

Weird it went that way, but in any case I'd recommend to run it as WB replacement to get most of it

If you want to disable it temporarily and use the old WB occasionally, boot with the shift key pressed.

When installed as the WB replacement, DOpus installs its own C:LoadWB command, and backups the original as C:LoadWB_old. So, to revert from the replacement installation back to the original WB, rename C:LoadWB to C:LoadDB, for example, and then rename C:LoadWB_old to C:LoadWB.

[Overmann]

Originally Posted by jPV

Weird it went that way, but in any case I'd recommend to run it as WB replacement to get most of it

If you want to disable it temporarily and use the old WB occasionally, boot with the shift key pressed.

When installed as the WB replacement, DOpus installs its own C:LoadWB command, and backups the original as C:LoadWB_old. So, to revert from the replacement installation back to the original WB, rename C:LoadWB to C:LoadDB, for example, and then rename C:LoadWB_old to C:LoadWB.

Thank you!
Holding shift only gives me the gray screen the "Workbench screen" white toolbar at the top is there but everything else is gray. Just like when I attempt to quit DOpus after it has launched.
I actually don't have a LoadWB_old, just a LoadWB and a LoadDB. Renaming so that LoadDB becomes LoadWB does nothing..

EDIT: I copied LoadWB from a DH0: backup that I had. Strange stuff.

[daxb]

Originally Posted by Overmann

EDIT: I copied LoadWB from a DH0: backup that I had. Strange stuff.

Does it mean it works now as expected (WB loads instead of DOpus)?

Strange that the install script doesn't worked for you. The only difference between DOpus WB-Replacement and WB is the LoadWB <-> LoadDB command launched by startup-sequence. Maybe you can try to reproduce it with the installer and check if the LoadWB/LoadDB change is correct or not. If it is still buggy it should be reported to OS 3.1.4 development team. Could be an Installer issue.

[jPV]

Originally Posted by Overmann

Thank you!
Holding shift only gives me the gray screen the "Workbench screen" white toolbar at the top is there but everything else is gray. Just like when I attempt to quit DOpus after it has launched.

Yea, it's because it tries to execute the "LoadWB_old" which you didn't seem to have as supposed.

And about quitting the WB replacement DOpus, if you have Scripts -> Shutdown defined to launch LoadWB_old then it would load WB in that case too. I don't remember if it should be a default setting there or not.. but it's possible to get it work that way too.

I actually don't have a LoadWB_old, just a LoadWB and a LoadDB. Renaming so that LoadDB becomes LoadWB does nothing..

Were they same file, did you happen to check if they were same size?

EDIT: I copied LoadWB from a DH0: backup that I had. Strange stuff.

Yea.. for some reason installation didn't happen as it should. Were you using official installer? Or did you happen to use the installer script from the newer open source versions? Maybe before using the original ones?

But anyway.. there's DOpus5:C/LoadDB within the DOpus installation.. and it is supposed to be copied as C:LoadWB and the original should be backupped as C:LoadWB_old (the shift key booting finds it then, and system can also be restored cleanly). So normally there shouldn't be LoadDB in C: at all. But of course people could do this different ways manually... or was the installer script in the open source archives buggy regarding this?

[alienkidmj12]

the first issue is easily solved, but the second is not. it used to work before i installed 3.14, but now crashes. actually it worked fine on my old 3.9 env. now i dont have a file manager to use, anyone suggest an alternative ?

[daxb]

What is the problem? What works and what not?