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
