home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!newsgate.watson.ibm.com!news.ans.net!cmcl2!adm!lhc!dabl2
- From: dabl2@nlm.nih.gov (Don A.B. Lindbergh)
- Newsgroups: comp.os.os2.misc
- Subject: Re: PRN in VDM has a BUG !!!
- Message-ID: <1992Dec18.140620.3566@nlm.nih.gov>
- Date: 18 Dec 92 14:06:20 GMT
- References: <BzEzrK.6np@tct.com> <1992Dec17.224156.4529@midway.uchicago.edu>
- Distribution: usa
- Organization: National Library of Medicine
- Lines: 31
-
- In article <1992Dec17.224156.4529@midway.uchicago.edu> sip1@midway.uchicago.edu writes:
- >In article <BzEzrK.6np@tct.com> paul@tct.com (Paul Levin) writes:
- >>I am (still) running the GA release of 2.0. The only printer driver
- >>installed (or wanted, for that matter) is IBMNULL. It is set in raw mode.
- >>Try the following commands in a VDM
- >> echo "hello" > prn:
- >> -- this works, the "hello" is sent to the printer queue
- >> copy file prn:
- >> -- this does not work. The copy command completes
- >> with no complaints, but nothing goes to the printer
- >> queue. Replace prn: with lpt1: and everything
- >> works fine.
- >>Comments, fixes, etc. are welcome (especially from IBM).
-
- In DOS, I think 'prn' is a special name 'prn:' may not be. I use
- 'copy file prn' all the time.
-
- >
- >The same thing happens in DOS, I think, when you try to use COPY to
- >any non-disk device. Try:
- >
- >COPY /B file PRN:
- >
- >Does that do anything?
-
- As an aside:
- I've had to use this (except just 'prn' on Novell networks using CAPTURE
- where binary data in the 'print' job caused the CAPTURE to end......
-
- --Don Lindbergh
- dabl2@lhc.nlm.nih.gov
-