I just tested this on my computer. I opened 2 sessions of RBASE for DOS. In each session I shelled out to dos A net use showed a printer mapped to lpt1
In one session I used the /delete for lpt1 In the other session I checked and the LPT1 was no longer defined. Dennis ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Tuesday, October 13, 2009 2:44 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing to network printers LPT1-LPT9 in Rbasefor DOS vs Rbase for Windows Au contraire, Dennis. When R:BASE for DOS starts on a Windows-based computer, it inherits the environment in place at that time. You can open another DOS session and change the environment, but the R:BASE for DOS session will not see the change, and this applies to printer mappings accomplished with NET USE. Trust me, we've been around this block many times, and I found that the only way to make it all work was: a) Share any locally-attached printer b) Do a NET USE of that or any other printer defined to Windows in the batch file that starts R:BASE for DOS 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: Tuesday, October 13, 2009 3:29 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing to network printers LPT1-LPT9 in Rbasefor DOS vs Rbase for Windows I think you are mistaken. Any NET USE affects the computer, not the session,, regardless of what makes the call. Dennis McGrath ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Tuesday, October 13, 2009 2:10 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing to network printers LPT1-LPT9 in Rbase for DOS vs Rbase for Windows Michael, When you do a ZIP NET USE when running R:BASE for DOS in a Windows environment, you are not changing the setup for the current session, but a child session which goes away as soon as ZIP returns control to R:BASE. 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. As for the port numbers other than LPT1, I cannot say. We have had far better results sticking with port 1, but I know of one location where we have a dot matrix printer and a Datamax printer attached to the same PC mapped to LPT1 and LPT2, and we print to both of them using the "COPY filename LPTx" approach. 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 Michael J. Sinclair Sent: Tuesday, October 13, 2009 2:57 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Printing to network printers LPT1-LPT9 in Rbase for DOS vs Rbase for Windows Hi All, What is the best way to print to a network printers in Rbase for DOS and Rbase for Windows? Do both versions recognize LPT1 through LPT9? I have been using the following code with reasonable success, but I do get a few jobs that just don't print.... ZIP NET USE LPTx /delete ZIP NET USE LPTx \\servername\printequename<file:///\\servername\printequename> OUTPUT LPTx WRITE 'whatever you want' OUTPUT SCREEN --or sometimes... OUTPUT LPTx COPY filename.txt LPTx OUTPUT SCREEN Adding a PAUSE FOR 2 after the ZIP NET USE COMMANDS seems to decrease the number of times that my print jobs "get lost". What is the best way to do this? Do both versions (DOS and Windows) running on Windows XP support LPT1-LPT9?? TIA! Mike
