Path: utzoo!attcan!lsuc!maccs!beame
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: wanted: printer redirector that works still under windows 3.0
Message-ID: <2692000E.28330@maccs.dcss.mcmaster.ca>
Date: 4 Jul 90 14:41:17 GMT
References: <9007021931.aa07944@louie.udel.edu>
Organization: McMaster University, Hamilton, Ontario, Canada.
Lines: 41

In article <9007021931.aa07944@louie.udel.edu> NEUMANN%AWIWUW11@WUW.WU-Wien.AC.AT (Gustaf Neumann) writes:
>Our setup:
>   several PCs hooked to an ethernet via packet drivers
>   + several unix machines as 'disk and print servers'
>
>Our problem:
>   PC-NFS and MD-DOS (Univ. of Maryland TCP/IP) work as a charm as long
>   MS Windows 3.0 is not involved. Both packages allow to assign the
>   printerports of the PCs (eg lpt1) to eg Unix's lpd spool queues.
>
>   Under Windows 3.0 the redirection of the printers ports is not
>   recognized anymore (we found no setup such one could print under eg.
>   MS-Word to lpt1). We can print to a file, switch to a dos window and
>   print the file from there using COPY SPOOLFILE LPTx, which is not
>   exactly what we want.
>
>Windows 3.0 allows to configure the printerports for several networks
>(IBM PC Lan, MS-Net, Bayan...). It has also a PrintManager that allows
>to inspect print queues in the network (we have the PrintManager
>deactivated). If a file is printed to say LPT1, Windows 3.0 comes up
>with a message like 'No printer connected to LPT1; please check your
>installation'. Under Windows 2.x printer redirection was slow
>(characterwise handshake?) but it worked.
>
>Any ideas? Fixes?? Patches????
>
>-------------------------------------------------------------------
>Gustaf Neumann		neumann@dec4.wu-wien.ac.at, neumann@awiwuw11.bitnet
>Vienna University of Economics and Business Administration
>Augasse 2-6,  A-1090 Vienna, Austria
>Tel: +43 (222) 347-541 x533 (9-18 CET) 	Fax 347-555

 BWNFS from Beame & Whiteside Software Ltd +1 (416) 648-6556 works correctly
with Windows 3.0 and allows full printer redirection. We are in the process
of writing a Network driver to provide mounting and unmounting capailities.
We have used the MSNET driver to mount drives, but the remote filesystem must
be in upper case. Our NFS takes about 55-60K of memory.

- Carl Beame
  Beame & Whiteside Software LTD.
  Beame@McMaster.CA