home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!wupost!sdd.hp.com!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!glia!michael
- From: michael@glia.biostr.washington.edu (Michael)
- Newsgroups: bit.listserv.win3-l
- Subject: Re: print problem in procomm for windows
- Date: 3 Jan 93 06:19:41 GMT
- Organization: University of Washington
- Lines: 19
- Message-ID: <michael.726041981@glia>
- References: <01GT1Y8JY89C0001MV@CC.DENISON.EDU>
- NNTP-Posting-Host: glia.biostr.washington.edu
-
- In <01GT1Y8JY89C0001MV@CC.DENISON.EDU> Michael Gordon <GORDONM@DENISON.BITNET> writes:
- >Michael Stanley (michael@glia.biostr.washington.edu) writes:
- >>On the older ProComm 2.0 for DOS, I could use the dedicated print mode
- >>for vt100 emulation. This mode would temporarily "lock me out" while
- >>the remote system would access my printer.
- >>
- >>This doesn't seem to work properly now that I'm using ProComm for Windows.
- >>As soon as the remote system attempts to use my printer, I'm locked out
- >>totally. The printer prints garbage, and before even a minute is passed
- >>the carrier is lost and my connection is closed.
- >>
- >>Any idea what's going on or how I can fix this?
- > The maintenance release (1.01 available as maint1.exe from Datastorm
- >and at cica) allows better remote printing. At least, it fixed a somewhat
- >similar problem for me in vt100 emulation. Take a look.
-
- Datastorm sent me maint1.exe and I've already installed it. Any other ideas?
-
- Michael Stanley (michael@glia.biostr.washington.edu)
-