I just said that a second DOS session saw the NET USE changes, even though it was already open. Try my test yourself.
I have found that the NET USE commands are NOT environment commands. They affect the whole windows login session, and if the /persistent switch is used, they survive even a complete reboot. On the other hand, environment variable setting like PATH and such are session specific. Dennis McGrath ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Tuesday, October 13, 2009 4:35 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing to network printers LPT1-LPT9 in Rbasefor DOS vs Rbase for Windows Larry, 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. 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 4:51 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. >> Lo siento mucho, mi amigo, but I have to go with Dennis on this one. NET USE does not affect the local shell environment but rather the current Windows session. To test: 1. Open a command window. 2. Issue a NET USE printer command. 3. Issue NET USE without arguments to see that the USE is in effect. 4. Close the command window. 5. Open a new command window. 6. Issue NET USE again without arguments. You'll see that the NET USE from the first command window is still in effect, notwithstanding that the shell context from that window was destroyed when you closed it. -- Larry
