Kbase 17722: OS-COMMAND and UNC CONSIDERATIONS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
OS-COMMAND and UNC CONSIDERATIONS
UNC and the Progress OS-COMMAND statement might interfere in several
ways under NT 4.0 and not run properly because, among some other
reasons, UNC are not correctly implemented under a DOS session started
under win NT 4.0.
For Instance you are not able to start a DOS session where the working
directory is a UNC directory if you did not first use the informations
provided in this document. This means if Progress has a working
directory specified with UNC The OS-COMMAND called from there will not
have the progress working directory as current directory, but will
have the c:\windows directory as current directory.
Microsoft has recognized there are some issues here.
To have a proper idea of how they inted to use UNC under DOS please
check the Microsoft Technet: entry Q156276. This entry will explain as
well the informatiosn reported here.
To have a dos session started with a working directory specified by a
UNC under NT 4.0 you need to do the following:
1- install the service pack 3 at least
2- edit the registry and go in:
HKEY_CURRENT_USER\Software\Microsoft\Command Processor
3- there create a new entry:
name: "DisableUncCheck"
type: DWORD
value: 1
Once this is done you will be able to start your DOS session with a
working Directory specified accordingly to UNC
Regarding Progress Software products this means, if their working
directory IS specified with the UNC, that you will be able to use the
OS-COMMAND statement from there without any problems.
(sha 02/24/1998)
Progress Software Technical Support Note # 17722