Emmitt, That is certainly something I understand.
My pervious method was for every DOS print job : 1. NET USE LPT1 /DELETE 2. NET USE LPT1 whatever 3. copy file to LPT1 At some point MS seemed to be dinking with their operating system and this method got extremely slow. That is why I went to using the PRINT command. It sends plain text to the printer without having to do all the intermediate steps. NET USE has gone back to being fast but there are some slight differences when using PRINT, so I'm staying there. BUT, if yours is not broke, don't change it (I'm preaching to the choir, I know!) Dennis ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Wednesday, October 14, 2009 9:14 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing to network printers LPT1-LPT9 inRbasefor DOS vs Rbase for Windows Dennis, We do what we do because it is the only way we have found over many years' experience to make it work reliably. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: Wednesday, October 14, 2009 9:51 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing to network printers LPT1-LPT9 inRbasefor DOS vs Rbase for Windows Emmit, Citrix is a whole other animal. Each session is a virtual machine so NET USE setting ARE Citrix session specific. But within the citrix session, IF you issue a NET USE it affect the whole session not just one command shell. I just tried my test under a citrix session and got the same resulets. 2l dos sessions saw the changes simultaneously. Dennis McGrath ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Tuesday, October 13, 2009 4:56 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing to network printers LPT1-LPT9 in Rbasefor DOS vs Rbase for Windows Allow me to revert to my original postulate: "The best approach is to set up your printer mappings in the batch file that starts R:BASE for DOS so you know they are in effect for the CMD.EXE session that is running R:BASE." What I can assure you is that over many years of experience in a Citrix/Windows Server/R:BASE for DOS/R:BASE for Windows environment, my statement above stands. Note the word "best." Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig Sent: Tuesday, October 13, 2009 5:49 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing to network printers LPT1-LPT9 in Rbasefor DOS vs Rbase for Windows << I don't dispute your steps below. However, if you have an R:BASE DOS session open throughout that entire process, I submit that it will not see any changes from the NET USE commands issued. >> I just did the following: 1. Started RBDos in a one window. 2. Opened another CMD window. 3. In the second window I issued NET USE to map LPT1 to a networked printer. 4. In the first window I CONNECTed and issues OUT LPT1; LIST; OUT SCREEN. My listing was produced on the network printer. Ten pages too, so I got the hairy eyeball from the network admin. I suppose this could vary according to operating system, but on this WinXP machine my NET USE in one command session is immediately available to my already-running R:Base for DOS session in another window. -- Larry
