DOpus v4.03 bug?
3 messages in this thread
I own Directory Opus v4.03 (Germany version). It's a great product
and worth every cent of the upgrade fee, yet I am experiencing minor
problems. Sometimes DOpus kind of 'locks up' – the only things still
reacting in any way are the pushbuttons (display 'clicked' alternate
image) and the path string field (gets activated). Unfortunately,
this is the only reaction to be gotten from DOpus. No menus, no
refreshs, no shutdown, no nothing. It does happen very seldom but is
annoying nevertheless. As is the fact that sometimes after having
launched an external program (via double click on an executable or,
for example, selecting an archive and clicking the 'Extract'
pushbutton) the shell window won't go away after the program has
finished with the effect that there is no way to get this intance of
DOpus working again (only help = reboot). Yet I may start another
instance of DOpus (on startup it tells me that DOpus is already
running – do I want to run another?). I even got a Guru (ok, since
2.x it is 'Software Error') 800000B when returning to DOpus after
having (successfully) run an install script for a program (DisKey
2.1) Is this a known bug? Is there a remedy? Despite this, I'd say
DOpus 4.x is just great, really!!!
// Chris coming in from Germany
\X/ on AutoPilot 1.051……….
It's really difficult to answer these questions, Chris, without your config
file and/or more information about when the lock-ups or lock-outs occur.
Can you provide more details, or a config file?
Martin (From Koeln)
Hi, Martin
Thought it was you, but was a bit puzzled when reading your user id
(75300,…). My setup is:
A2000C (PAL) / 1Meg ChipRAM / 4 Megs FastRAM (Masoboshi) / Evolution v3.0
SCSI host adaptor (MacroSystem) with 121 Meg Maxtor HD / CSA Mega Midget
Racer with 68030-33 and 68882-20 and 4 Megs of 32bit RAM / 4 Floppy drives
(2×3.5" internal, 1×3.5" and 1×5.25" external) / WB 2.04 / normal PAL
monitor.
The lockups occur mainly (not always, though) when running a program from
DOpus (double-click on directory entry, no arguments, click on 'OK'). The
program will run from DOpus's output window on workbench which does _not_
close automatically sometimes, thus locking up this instance of DOpus
until the next boot. The same happens (again, sometimes) when extracting
archives (I'm DL'ing heavily), which I usually do from AP:Download into
T:. DOpus's Output window will open (this time on the DOpus screen), the
archive will extract and then that window won't go away… When adding
files to an archive, the is a message after 'click mouse to close window'
or so – that has always worked. Maybe DOpus loses count when waiting for
the end of the delay time before closing the window down?
Nevertheless, I'll try to upload my config file to you (haven't done this
before so I don't know whether I'll succeed)…
Have a nice weekend!
// Chris coming in from Germany
\X/ on AutoPilot 1.051……….