06301422.txt 30-Jun-00


Subject: Win9x Peer-to-Peer Printing
From: omegadec@iafrica.com (Omega Decisions)

I have a system that up till now was running on a single
  Win9x pc.
The pc has 2 lpt ports.  LPT1: has a HP LJ1100 for reporting
  and LPT2: a dot matrix for invoicing, statements, etc.
  The app uses SET PRINTER TO commands to send output to the
  relevant printer.
This has been fine until a second pc was networked and the
  dot martix printer moved to the new PC.   I thought it
  would be no problem to capture the Laser to LPT2: and the
  dot matrix to LPT3: on each machine.   However, you cannot
  capture a local printer which is the case on both PC's.
My app resides on one of the pc's and the configuration
  files are shared.
I have had to resort to the following:
PC #1 - Has two LPT ports 1 & 2
  LPT1:   -   mapped to dot matrix on PC #2
  LPT2:   -   local  (HP LJ1100)
PC #2 - Only has a LPT1 port
  LPT1:   -   local (dot matrix)
  LPT2:   -   mapped to laser on PC #1
The app is now set to send reports to LPT2: and doc's to
  LPT1:
This only works because PC #1 has two LPT port's and the
  LJ1100 could be switched from LPT1 to LPT2.
Would there be an alternate solution if each PC only had 1
  LPT port ?
or
Would you have to have multiple config files ( one for each
  PC ) to reverse the SET PRINTER TO commands for one of the
  PC's ?
Comments or suggestions will be appreciated.

Thanks
Mark Parsons


Subject: Re: Win9x Peer-to-Peer Printing
From: Uwe Heyer <uweheyer@my-deja.com>

Hi Mark,

when you have only 2 Printers and only one LPT port on each
  computer
you can do this one:
net use LPT2: \\OneShare\Printer
net use LPT3: \\SecondShare\Printer
on all computers
this will work because LPT1: (physical Output) is not
  redirected.
Because Clipper can't print higher than LPT3: port (MS
  Network) you need another trick when you have more
  printers.
Print in a file and then "copy /b" this file to the UNC
so you could have hundred of printers in your network and
  all are reachable from your application and this without
  NET USE.

Mabe there is a 3Party that will map shared printers ?

Ahoj
-Uwe


Subject: Re: Win9x Peer-to-Peer Printing
From: "Phil McGuinness" <heyphil@sherlock.com.au>

You can capture in the properties of the printer your LPT
  ports.  When you do this you have to make sure to actually
  select it though.
That is your printer maybe \\server\hp and when you capture
  LPT2 to path \\server\hp windows creates the capture but
  it is now on the list of available output methods.
To select it open the combo box on the bottom of the list
  will be LPT2\\server\hp.   Have been using this methof ofr
  years and it works fine.
Without using NET USE this will work.
Also you can use LPT4 it works fine.

Phil McGuinness

Subject: Re: Win9x Peer-to-Peer Printing
From: Uwe Heyer <uweheyer@my-deja.com>

Hi Phil,

today I'm using NT/W2K only. Here you can't select a printer
  port above LPT3 with Clipper (or better said, I don't know
  any trick). In the MSDN I read that NT would support up to
  LPT9 but some old DOS application could fail when a port
  higher than LPT3 is selected.
On W95 or DOS with Novell Netware Client there wasn't a
  problem, NT with NWC I have never tried.
Do you know how to select LPT4 on NT (Clipper 5.2e) ?

Ahoj
-Uwe


Subject: Re: Win9x Peer-to-Peer Printing
From: "Stephen Quinn" <squinn@brutecom.com.au>

Uwe

> Do you know how to select LPT4 on NT (Clipper 5.2e) ?
You can't.
It's a limitation of command.com that does this.

HTH
Steve Quinn


Subject: Re: Win9x Peer-to-Peer Printing
From: frank paulsen <frank.paulsen@gmx.net>

it's a limitation of Windows Networking. Netware Client
  allows LPT1-LPT8.

frobnicate foo


Subject: Re: Win9x Peer-to-Peer Printing
From: "Stephen Quinn" <squinn@brutecom.com.au>

Frank

Sorry it's command.com under NT4 where  the limitation is.
If you could use CMD.EXE with 16bit programs you could use
  LPT1-9
Its very easy to test this.
Start a DOS session with CMD.EXE
set some printers with 'net use'
Try and print to them
eg
CMD.EXE
net use LPT4 \\XYZ\Printer1
COPY ATEXTFILE TO LPT4
It'll print  the file
// Run  Command DOS shell
Command.com
COPY ATEXTFILE TO LPT4
It'll fail to print
// Exit DOS shell
exit
net use LPT4 /D
// Exit CMD shell
exit
All 16bit DOS programs use command.com under NT, the OS
  detects which type of exe it is and spawns the shell.
You have no control over this.
To test this try renaming/copying CMD.EXE to Command.com
  (save a copy first) and run a Clipper program from within
  a CMD shell, you'll see errors about not being able to
  understand the .PIF file.

HTH
Steve Quinn


Subject: Re: Win9x Peer-to-Peer Printing
From: frank paulsen <frank.paulsen@gmx.net>

sorry, but you are wrong. i checked the following clipper-
  program:
=== print4.prg ===
procedure main()
set printer to lpt4
set print on
? "hello world"
set print off
set printer to
return
===
C:\>net use lpt4 \\nwserver\laser
C:\>print4
on NT Server 4.0, Servicepack 6a, Netware Client, and it
  works.
the problem is Windows Networking, because Windows

  Networking does not emulate LPT>3 for 16bit applikations.
  Netware Client does, and so command.com uses LPT1-9.
  command.com does not know anything about devices under NT.
>
All 16bit DOS programs use command.com under NT, the OS
  detects which type of exe it is and spawns the shell.
You have no control over this.
<
command.com is definitely _not_ the problem, the problem is
  the lousy Windows Networking Client.

frobnicate foo


Subject: Re: Win9x Peer-to-Peer Printing
From: "Stephen Quinn" <squinn@brutecom.com.au>

Frank

I did the test on my machine without a network.
The printer I pointed to is attached to the same machine.

HTH
Steve Quinn


Subject: Re: Win9x Peer-to-Peer Printing
From: Uwe Heyer <uweheyer@my-deja.com>

Hi Steve,

that's the answer I hoped I wouldn't hear, but anyway your
  answer sounds to be real.

Thanks

Ahoj
-Uwe