Article ID: 92773 - Last Review: October 14, 2003 - Revision: 2.0 WFWG: Problems when Windows Express Version 3.0 Run as ShellThis article was previously published under Q92773
The following article contains information on the use of Windows for
Workgroups with third-party products or configurations that have not
been tested and are not supported by Microsoft.
If the steps or procedures described in this article do not function properly, contact the manufacturer of the third-party product for more information or use a supported configuration. SYMPTOMS
If you use hDC Windows Express 3.0 as the Windows shell with Microsoft
Windows for Workgroups, the following errors may occur:
CAUSE
Because of the differences between the shell logic used in Windows
Express and Windows for Workgroups, Windows Express loads itself as a
normal application without establishing a Windows shell. Because no
shell has been established, the only way to end the Windows session is
to restart (reboot) the computer.
WORKAROUND
To work around this problem, use Program Manager as the Windows shell
and do one of the following to run Windows Express:
MORE INFORMATION
When you use Windows Express version 3.0 as the Windows shell, it
expects to be started before all other Windows applications. However,
when you use this application with Windows for Workgroups, Windows
Express cannot be started first because Windows for Workgroups starts
two hidden applications (NETDDE.EXE and CLIPSRV.EXE) prior to loading
Windows Express.
This feature is by design. For additional information about Windows Express, contact hDC Computer Corporation. hDC Windows Express 3.0 is manufactured by hDC Computer Corporation, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability. | Article Translations
|

Back to the top
