PRB: SYS2070 Issued When Running PWB.EXE for the First Time (61572)
The information in this article applies to:
- Microsoft Programmer's Workbench for OS/2 1.0
- Microsoft Programmer's Workbench for OS/2 1.1
This article was previously published under Q61572 SYMPTOMS
When running the Programmer's WorkBench (PWB) for the first time, the
following OS/2 system error may be issued:
Session Title:
PWBED.EXE
SYS2070: The system could not demand load the
application's segment. MSHELP HELPSHRINK is in error.
For additional detailed information also see message SYS0127
CAUSE
This problem is usually caused as a result of the Setup program not
being able to copy its version of MSHELP.DLL over the old version of
MSHELP.DLL. If another process (most likely a detached session of
QH.EXE) was accessing this file during the execution of Setup, the
Setup program will issue a message similar to the following:
ERROR: Could not create file C:\OS2\DLL\mshelp.dll
ERROR: File copy failed: A:\the PWB\mshelp.dll to C:\OS2\dll\mshelp.dll
RESOLUTION
To solve this problem, take the following steps:
- Disable QH as a keyboard monitor:
- Press ALT+Q (to invoke QH).
- Press O (for the Options menu).
- Press T (to terminate the monitor).
- Copy the up-to-date version of MSHELP.DLL from the distribution
disk:
- Insert the Setup/Compiler 1 disk into drive A.
- Change the default drive A.
- Run Setup with the /copy option by typing the following:
- Press ENTER
- Press ENTER again (unless the setup files are in a drive other
than A).
- At the prompt asking for the name of the file to copy, type
MSHELP.DLL and press ENTER.
- At the prompt asking for the name of the directory to which to
copy this file, type the directory in which the old MSHELP.DLL
is located (most likely C:\OS2\DLL).
- Setup should then ask for the Programmer's WorkBench/Utilities
for OS/2 disk to be inserted into the setup drive.
- When Setup is finished copying the file, press ENTER at the
next prompt.
The PWB should now start up correctly.
NOTE: SQL Server's Setup program also installs its own version of
MSHELP.DLL onto the system. The SQL Server Setup places its copy of
this DLL into a directory called \SQL\DLL. If this directory is in the
LIBPATH before the directory into which the latest MSHELP.DLL was
placed, this same problem can arise.
Modification Type: | Major | Last Reviewed: | 9/30/2003 |
---|
Keywords: | kb16bitonly KB61572 |
---|
|