knob,
Yep that works. I stumbled on to the same conclusion. Apparently, ProComm maintains it's own idea of the
default printer. And as you said, you must use File|
Print Setup at least once to 'register' the default printer with the ProComm application. If not, the fetch returns
an empty...
Knob,
Thanks for the tip !
Although pw5.prm is not in human readable form, it does
contain a string of text that looks very suspicious.
My approach will be to rename the file and launch ProComm.
Hopefully, I won't spend all day getting the settings
back to normal.
Please let me know if you...
I'm using Win2000 on a Dell with ProComm 4.8.
The problem seems to be the cmd -
fetch print device S0
It returns a bogus default printer. Yes, the printer
was defined at one time, but it has been deleted.
All other Windows apps seem to be using the printer
set as default in the printers...
Is it possible to obtain the return value from an
external process spawned using the Aspect run command ?
I'm developing an Aspect script on Win2000 Professional
that calls a Perl script to do some work. I'd like the
Aspect script to have visibility to the exit status of my
Perl code.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.