#Opus problem-HELP!
9 messages in this thread
I've just purchased Directory Opus, and I'm having a problem printing from
it. Whenever I select a file and click on the PRINT gadget, I get the
normal print requester, but after clicking on THAT print gadget I get a
SOFTWARE FAILURE requestor that says "dopus_print" failed, and the error
number is 80000003. I am currently running 2.04 on a stock amiga 2000, with
3 MB ram, 2090a controller, 40MB rodime. The Opus print gadget is
configured to use the internal print command (*print), and the destination
is set to PRT:. I tried changing the destination to a print file
(testout), but with the same results. WP 4.2 and PRINTFILES seem to have
no problem printing. By the way, AREXX is running, and I'm set up for an
EpsonX printer. I would really appreciate it if anyone could help me, as
I've read everything in the manual concerning printing and I still don't
have a clue as to what is going on.
Marcus Mullins 🙁
Are you using DirOpus version 3.40? (version # is avail in the PROJECT
menu) If so, you've run across a known bug in that version. For the time
being, the workaround would be to: 1) go into the Print requestor and set
up the print parameters the way you want, but DON'T press print; 2) then
read the file as a text file (ie double click it) and use the Print gadget
available in the text reader. That will print it the way you want, sans
guru.
This is a bug that cropped up in version 3.40. Earlier versions were
supposedly ok. Innovatronics is aware of the bug, and is working on a fix.
I'll post here when it is available, or you can call them.
Sorry about the difficulty. Hope above helps you till the fix is done!
–jp–seattle–
Thanks! The only disadvantage to the work-around is that it doesn't spool,
but I can live with that… especially considering all the MANY other
things Opus does right. I've been a professional prgrammer for 12 years,
but I have never seen a program that can do SO MUCH. (Can you tell I'm
impressed? :-). Thanks for the help.
Marcus Mullins 🙂
I know that Innovatronics is well aware of the PRINT bug, and is working on
a solution. I have no idea if the solution will take the form of a patch,
upgrade, or whatever (or when it will arrive). We'll just have to wait and
see. It will certainly be posted here when it happens. TTFN
I have just discovered another problem, and maybe you can help me with this
as well. The HUNT and SEARCH functions have no affect when I click on
their gadgets. I looked at the configuration for each and they seem to be
internal functions. Any clues?
Thanks,
Marcus Mullins 🙂
HUNT and SEARCH require that you have hilighted the files/dirs that you
wish to process. To process an entire disk, for instance, you need to read
the directory of the disk, press ALL (to select all files/dirs) and then
say HUNT or SEARCH. You'll be asked for the pattern to HUNT for (ie. a
file name pattern) or to SEARCH for (ie. a text string inside a file) and
Opus will then look for them.
Make sense?
–jp–seattle–
John,
I too have an Opus problem. How do I get LZ to be the archive extractor of
choice?
RJ – via Whap!
Thanks. I was expecting a drive prompt for hunt, although search would
work better the way you described it.
Marcus Mullins 🙂
I think the idea of having to select what you want to HUNT for was to allow
you to manually narrow down the search params, if you had any idea of where
to start looking 🙂 Hey! If you want it to prompt for a drive, and then
automatically hunt the whole drive, just do it and replace the existing
HUNT button with your own command! That's the beauty of Opus, it's so
customizable. TTFN
–jp–seattle–