 |
 |
 |
 |
I wish to post the results and thank the many of you who offered help.
1) I was taught that the DOS copy command can send binary files to output
devices like printers using the /B command. The command is-- copy /B
filename lpt1:. I was assured this command works for Laserjet IV printers.
Unfortunately the result for HP InkJet printers is about 6 page feeds with &
without extended character set symbols AND the graphic page split over at
least 2 pages of paper with 6 black columns at the left margin. Bottom
line--try it if you crash & burn while printing to a LaserJet other wise go
to 2).
2) I was advised of a Print Manger replacement sold by Zenographics, Inc &
called SuperQueue (Superprint) available for Windows 3.1 & Windows 95. It
works! I've tried killing Windows several ways and SuperQueue can figure
out what it needs to print & finish the job. It batch prints as well as
spools. It gives some additional latitude in printer control. However, if
you print high quality prints from something like WordPerfect Presentations
please have alot of disk space free (many Meg as 1 spooled file hit 6+ meg
of spool file space) and 16 Meg of RAM memory or be prepared to wait.
3) Finally. Windows 3.1 has an exaspirating requirement for arcane precise
correctness in its path command i.e. path=c:\;c:\dos;c:\windows; (finish
path). For reasons totally unknown to me, my path command has gotten
changed twice this summer on different machines resulting in bizzare Windows
behavior. Examples-- CD ROM drive works but sound output disappears;
SuperQueue installed but Windows would not allow screen printing although
all other output to the printer was spooled with no problem; and finally
Windows had problems with its REGEDIT file and changes programs tried to
make on installation/reinstallation after operational failure. Symptoms--
overall Windows appeared to be working along with all DOS software except
Windows software installed to removable media would "just disappear" or
"fail to execute" with notice of lost path or bad installation. Apparent
reistallation resulted in the same error messages. Figuring this one out
cost PAIN I don't want you to have!!
If this is a virus--tell all of us. McAffee and Norton AntiVirus can't
find one.
Again, thanks for the help & post 3) somewhere in the event Windows seems
to go nuts.
Louis King
Email: kingl@pilot.msu.edu
|
|
|
|