home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
oswapowr.txt
< prev
next >
Wrap
Text File
|
1997-02-04
|
3KB
|
91 lines
OSWAPOWR - POWERBUILDER 3.0 AND 4.0 WITH OS/2 2.11 AND OS/2 WARP
01/16/96
=======================================================================
PowerBuilder 3.0 and 4.0 with OS/2 2.11 and OS/2 Warp
=======================================================================
Please Read Entire Document for Full Explanation of Procedures
--------------------------------------------------------------
DESCRIPTION
* System locks up when connecting to WATCOM Database Server 3.2 or 4.0.
* Installation of PowerBuilder 3.0a fails after a drive is specified.
* Problems experienced when running PowerBuilder in a Dual Boot
environment.
* The following error message is received:
IM003: .Microsoft. .ODBC. Specified driver could
not be located when trying to connect to WATCOM 4.0
database in PowerBuilder 4.0.
* The following application error is received:
DB32W caused a GPF in module .unknown.
04ef:8e82db3w will close.
This error message appears because you might be using the wrong
WATCOM version.
RESOLUTION
Note: Make sure you have a backup of any file you intend to change.
These problems and issues are known to Powersoft, Inc., the
manufacturer of PowerBuilder.
The following information assumes you are using the default directory
names.
1. Run the WIN-OS/2 session in enhanced mode.
2. Edit the OS/2 AUTOEXEC.BAT file.
Change: SET TEMP=X:\OS2\MDOS\WINOS2\TEMP
To: SET TEMP=X:\OS2\TEMP
3. Go to the WINOS2 directory and delete the TEMP subdirectory.
4. Go to the OS2 directory; then type MD TEMP and press Enter to create
the TEMP subdirectory.
5. Restart the installation.
During installation, PowerBuilder updates the AUTOEXEC.BAT file of
the active operating system by adding \WSQL40\WIN and \PB4 to the
PATH statement.
6. Edit the AUTOEXEC.BAT file of the inactive operating system
AUTOEXEC.BAT, and add \WSQL40\WIN and \PB4 to the PATH statement.
Note: If you are using InfoMaker, add \IM4 to the PATH statement.
If Powersoft cannot find DB32W.EXE, WATCOM 4.0 English:
1. Edit the active AUTOEXEC.BAT file and add \WSQL40\WIN and \PB4 to
the PATH statement.
2. Go to the \WINDOWS or \OS2\MDOS\WINOS2 directory, depending on which
OS/2 version you are using.
3. Edit the ODBC.INI file.
Change: Start=DB32W -d -o512
To: Start=DBSTARTW -d -o512
This is for the WATCOM 4.0 database profiles.
______________________________________________________________________
IBM disclaims all warranties, whether express or implied, including
without limitation, warranties of fitness and merchantability with
respect to the information in this document. By furnishing this
document, IBM grants no licenses to any related patents or copyrights.
Copyright (c) 1994, 1995 IBM Corporation. Any trademarks and product
or brand names referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.