Microsoft KB Archive/102762: Difference between revisions
(stage2) |
m (1 revision imported: importing part 2) |
(No difference)
|
Latest revision as of 21:57, 16 July 2020
GetCommandLine() Under Win32s |
Q102762
The information in this article applies to:
- Microsoft Win32s versions 1.0, 1.1, 1.2, 1.3, 1.30a, 1.3c
SUMMARY
Under Win32s, GetCommandLine() includes the full drive/path of the executable, while under Windows NT GetCommandLine() does not include the full path.
MORE INFORMATION
When programs are run from the Program Manager or the File Manager on Windows 3.1, they are spawned using the full path. As a result, argv[0] will have the complete path. When a Win32s application is spawned by a 16-bit application, Windows detects that the application is a Win32s application. The full path is passed to Win32s regardless of whether or not WinExec() was invoked with the full path. As a result, 32-bit applications receive the full path.
When a Win32-based application is spawned from another Win32-based application, the 32-bit kernel passes the information as given by the parent process (that is, if a Win32-based application is started via CreateProcess() from another Win32-based application, argv[0] will contain the path that the spawning application passed in).
Additional query words: 1.00 1.10 1.20 cmdline
Keywords : kbOSWin32s
Issue type :
Technology : kbWin32sSearch kbWin32s100 kbWin32s110 kbWin32s120 kbWin32s130 kbWin32s130a kbWin32s130c
Last Reviewed: January 16, 2000 |