Xref: utzoo comp.sys.ibm.pc.misc:9727 comp.sys.ibm.pc.hardware:8863 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!rutgers!mcnc!rti!mozart!vm.sas.com!sasddi From: SASDDI@vm.sas.com Newsgroups: comp.sys.ibm.pc.misc,comp.sys.ibm.pc.hardware Subject: Re: printing via the serial port Message-ID: <91141.093332SASDDI@vm.sas.com> Date: 21 May 91 13:33:32 GMT References: <91136.142619SASDDI@vm.sas.com> Organization: SAS Institute Inc. Lines: 46 Many thanks to the following people for their responses: Galen Hekhuis Chance C. Guerin Jonathan Miner Pietro P. Rizzi Joe Dorner James Birdsall Jui-hsiang Allan Yang Louis Davidson Rich Snow They all pointed out that the DOS manual describes using MODE COM1:baud,parity,bits,stop-bits,P and MODE LPT1=COM1 Unfortunately, it's not working. The printer is set for 1200 baud, even parity, and 2 stop-bits (not sure if it's 7 or 8 data bits). So that's what I set the COM1 port to, then I issue the second MODE command to redirect the printer, then I attempt to test it with ECHO hi > LPT1 Nothing. The printer stays quiet, and the system locks up until I hit CNTL-BREAK (that's if I added the P option; without it, after a few seconds, the system complains about the port (or words to that effect) and asks the ubiquitous question: Abort, Retry, Ignore?). I did of course try several variations, particularly of the number of data- and stop-bits. One extra variable: to connect the printer to the PC, I had to borrow a gender-mender from work. (The cable has two male plugs, as does the PC's serial port.) It's definitly NOT a null modem, as it's a ribbon cable with connectors on either end; no place to cross the send/receive lines. Any more suggestions from you net.gurus and/or hackers? :-) Thanks in advance. ------------------------------------------------------------------------= Dale D. Ingold SAS Institute Inc. snoddi@mvs.sas.com MVS Host Group SAS Campus Drive 919/677-8000 x7603 Cary, NC 27513-2414