by Stephen Mille » Mon, 19 Jan 1998 04:00:00
Since Sybase uses the shell variable SYBASE to determine where to find the
Open Client dlls, what do you do if you have to run both apps on the same
machine? In other words one app is a 16-bit app that needs the 16-bit Open
Client dlls, and another app expects the 32 bit dlls. Do I have to comingle
the dlls in the /bin directory?
by jsr » Wed, 21 Jan 1998 04:00:00
Yes,
You can install both the 16 and 32 bit drivers in the same directory
(/sybase/dll is the default). Both 16 and 32 bit applications work without
problems in this environment.
by Graeme Alliso » Fri, 23 Jan 1998 04:00:00
Installing both sets of drivers has caused clients problems in the past due to
transport protocol errors..... A real problem to get to the bottom of.
> You can install both the 16 and 32 bit drivers in the same directory
> (/sybase/dll is the default). Both 16 and 32 bit applications work without
> problems in this environment.
> >Since Sybase uses the shell variable SYBASE to determine where to find the
> >Open Client dlls, what do you do if you have to run both apps on the same
> >machine? In other words one app is a 16-bit app that needs the 16-bit Open
> >Client dlls, and another app expects the 32 bit dlls. Do I have to
> comingle
> >the dlls in the /bin directory?
by Richard Scranto » Fri, 23 Jan 1998 04:00:00
One of our guys ran into this recently on a new ASE install, with
new PB5 clients and some old 16-bit PB4 stuff. We saw all kinds of
troubles when the both the 16-bit and 32-bit client software was
installed on a PC with NT 4.0. The problem:
The 16-bit and 32-bit clients were trying to use
different character encodings.
In our case, the 32-bit was set for iso_1 while the 16-bit was
trying to use roman-8 (mixed HP Unix and Wintel NT environment).
We addressed it by making sure that all servers involved had
both character sets installed. It was easier than trying to
reconfigure the several hundred client systems.
If this is helpful to others, I would like to hear. Thanks.
> Installing both sets of drivers has caused clients problems in the past due to
> transport protocol errors..... A real problem to get to the bottom of.
> > Yes,
> > You can install both the 16 and 32 bit drivers in the same directory
> > (/sybase/dll is the default). Both 16 and 32 bit applications work without
> > problems in this environment.
> > >Since Sybase uses the shell variable SYBASE to determine where to find the
> > >Open Client dlls, what do you do if you have to run both apps on the same
> > >machine? In other words one app is a 16-bit app that needs the 16-bit Open
> > >Client dlls, and another app expects the 32 bit dlls. Do I have to
> > comingle
> > >the dlls in the /bin directory?
by DQ Nin » Sun, 25 Jan 1998 04:00:00
How can you run 16 bit software on NT any way? I thought that NT
is a true 32 bit OS, and it won't run any 16 bit software.
--
by r l re » Tue, 27 Jan 1998 04:00:00
It has "ntvdm" - the NT Virtual Dos Machine, which does a fair-to-decentQuote:>How can you run 16 bit software on NT any way? I thought that NT
>is a true 32 bit OS, and it won't run any 16 bit software.
Cosidering the attitude of far too many vendors, who write to the lowest
common denominator, it has to - waiting for folks to get 32 bit
versions running is excruciating.
--
microtonal resources and what not at: http://www.panix.com/~ro/
"The most incomprehensible fact is the fact that we comprehend at all."
-Abraham Joshua Heschel
1. 16 bit and 32 bit open client
We have currrently installed 16 bit powerbuilder applications running on
windows 95 workstations and using Sybase 10 databases on HP unix servers.
We want to install
32 bit mode software and run both 16 and 32 bit applications. Has anyone
accomplished this and is there available documentation ? Thanks for the
help !
--
Ed Marzuki
Valero Energy Corp.
San Antonio, Tx.
2. How do i add a container to mdb
4. Hot to get MAx and MIN value in a database
5. Open client 16 to 32-bit - expensive upgrade?
7. Opening 16 bit Access 2.0 tables from 32 bit VB code
9. Upgrading 16 bit client to 32 bit??
10. corruption of 16 bit db when used by both 16 and 32 bit apps
11. 16 and 32 bit client config ???
12. Using 32 and 16 bit clients on one machine
13. Installing 16 and 32 bit clients