Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

16-bit applications with 32-bit ODBC drivers on Windows 95

4 posts in ,  Windows NT Connectivity - ODBC Last posting was on 1998-01-10 08:22:03.0Z
Allan Taunt Posted on 1998-01-08 20:42:46.0Z
From: "Allan Taunt" <allant@gis.co.nz>
Subject: 16-bit applications with 32-bit ODBC drivers on Windows 95
Date: Fri, 9 Jan 1998 09:42:46 +1300
Lines: 34
X-Newsreader: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Message-ID: <E#DXxyGH9GA.62@forums.powersoft.com>
Newsgroups: sybase.public.connectivity.odbc,sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.connectivity.odbc:2628 sybase.public.sqlserver.nt:178
Article PK: 115585

I've come across a problem where I cannot connect a 16-bit application to
Sybase via 32-bit ODBC drivers. This problem only occurs under Windows 95
(Windows NT has no problem with this combination). Under Windows 95 I get
the following error message:

ct_connect():network packet layer:internal network library error:Attempt to
use invalid address handle.

Platform:
Sybase SQL Server 11.0.2.1 (running on NT4.0 SP3)
32-bit client software dated about 20-August-1996 (came with Sybase SQL
Server)
Intersolv 32-bit ODBC drivers 3.01
Network protocol TCP/IP
16-bit client application MSQUERY

Please don't tell me I have to run 16-bit client software - the above
combination should work (It does on NT 4.0, and it also works for MS SQL
Server).

Is there a patch to fix the above problem or is it fixed in Adaptive Server
11.5?

Any help appreciated,

Allan Taunt
________
Global Information Solutions
Christchurch
New Zealand.


BrunoMagal Posted on 1998-01-09 13:26:25.0Z
From: "BrunoMagal" <magal@sybase.com>
References: <E#DXxyGH9GA.62@forums.powersoft.com>
Subject: Re: 16-bit applications with 32-bit ODBC drivers on Windows 95
Date: Fri, 9 Jan 1998 14:26:25 +0100
Lines: 48
X-Newsreader: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Message-ID: <pVrlxmPH9GA.137@forums.powersoft.com>
Newsgroups: sybase.public.connectivity.odbc,sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.connectivity.odbc:2625 sybase.public.sqlserver.nt:177
Article PK: 115581

We currently do not support this configuration since Intersolv does not.
You have to use 16 bits and 32 bits soft. separately.

You can always try and email consult_odbc@intersolv.com to see if Intersolv
has any
suggestions.


Bruno Magal
Sybase Technical Engineer

Allan Taunt wrote in message ...
>I've come across a problem where I cannot connect a 16-bit application to
>Sybase via 32-bit ODBC drivers. This problem only occurs under Windows 95
>(Windows NT has no problem with this combination). Under Windows 95 I get
>the following error message:
>
>ct_connect():network packet layer:internal network library error:Attempt to
>use invalid address handle.
>
>Platform:
> Sybase SQL Server 11.0.2.1 (running on NT4.0 SP3)
> 32-bit client software dated about 20-August-1996 (came with Sybase SQL
>Server)
> Intersolv 32-bit ODBC drivers 3.01
> Network protocol TCP/IP
> 16-bit client application MSQUERY
>
>Please don't tell me I have to run 16-bit client software - the above
>combination should work (It does on NT 4.0, and it also works for MS SQL
>Server).
>
>Is there a patch to fix the above problem or is it fixed in Adaptive Server
>11.5?
>
>Any help appreciated,
>
>Allan Taunt
>________
>Global Information Solutions
>Christchurch
>New Zealand.
>
>
>
>


Randy Lynn Tusch Posted on 1998-01-09 20:41:59.0Z
From: "Randy Lynn Tusch" <drt@servtech.com>
References: <E#DXxyGH9GA.62@forums.powersoft.com>
Subject: Re: 16-bit applications with 32-bit ODBC drivers on Windows 95
Date: Fri, 9 Jan 1998 15:41:59 -0500
Lines: 28
Organization: Duke Energy
X-Newsreader: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Message-ID: <LfXc$XTH9GA.166@forums.powersoft.com>
Newsgroups: sybase.public.connectivity.odbc,sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.connectivity.odbc:2623 sybase.public.sqlserver.nt:176
Article PK: 115582

Although I don't think Intersolv employs this technique, it is possible to
piggy-back off the "General Thunking" technique Microsoft developed for this
purpose. Essentially, the 16 bit routines presented to the 16 bit ODBC
manager are converted to 32 bit address and instruction spaces, and then
routed to the appropriate 32 bit ODBC driver. This is how Thunking would be
applied in the arena of ODBC. I'm not sure if the Microsoft ODBC32GT.DLL
(or would that be ODBC16GT.DLL - you'll need to check) file could be used in
conjunction with Intersolv's 32 bit ODBC drivers, but it should be possible.
The files I referred to are part the ODBC 3.x.x specification, to the best
of my knowledge. You may want to contact Microsoft to see if this can be
done in your environment. Windows 95, behind the scenes, uses thunking
techniques to merge 16 bit functionality into its 32 bit environment. In
theory, it should work. (IBM accomplishes this thunking technique quite
successfully with their ODBC driver for their 32 bit CAE's. You can use 16
bit AND 32 bit ODBC apps. against the same drivers in a 32 bit environment.)
I haven't attempted this yet, but I will experiment with it, and I will post
a response here when I have drawn a conclusion.

Randy Lynn Tusch
Sr. LAN/WAN Engineer & Middleware Specialist
CCG

Allan Taunt wrote in message ...
>I've come across a problem where I cannot connect a 16-bit application to
>Sybase via 32-bit ODBC drivers. This problem only occurs under Windows 95
>(Windows NT has no problem with this combination).


Vitaly Lipovetsky Posted on 1998-01-10 08:22:03.0Z
From: "Vitaly Lipovetsky" <vit@fuib.com>
References: <E#DXxyGH9GA.62@forums.powersoft.com> <LfXc$XTH9GA.166@forums.powersoft.com>
Subject: Re: 16-bit applications with 32-bit ODBC drivers on Windows 95
Date: Sat, 10 Jan 1998 10:22:03 +0200
Lines: 31
X-Newsreader: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Message-ID: <34b72ed9.0@ifuib>
Newsgroups: sybase.public.connectivity.odbc,sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com!ifuib!172.17.3.101
Xref: forums-1-dub sybase.public.connectivity.odbc:2621 sybase.public.sqlserver.nt:175
Article PK: 115578


Randy Lynn Tusch wrote in message ...
>Although I don't think Intersolv employs this technique, it is possible to
>piggy-back off the "General Thunking" technique Microsoft developed for
this
>purpose. Essentially, the 16 bit routines presented to the 16 bit ODBC
>manager are converted to 32 bit address and instruction spaces, and then
>routed to the appropriate 32 bit ODBC driver. This is how Thunking would
be
>applied in the arena of ODBC. I'm not sure if the Microsoft ODBC32GT.DLL
>(or would that be ODBC16GT.DLL - you'll need to check) file could be used
in
>conjunction with Intersolv's 32 bit ODBC drivers, but it should be
possible.
>The files I referred to are part the ODBC 3.x.x specification, to the best
>of my knowledge. You may want to contact Microsoft to see if this can be
>done in your environment. Windows 95, behind the scenes, uses thunking
>techniques to merge 16 bit functionality into its 32 bit environment. In
>theory, it should work. (IBM accomplishes this thunking technique quite
>successfully with their ODBC driver for their 32 bit CAE's. You can use 16
>bit AND 32 bit ODBC apps. against the same drivers in a 32 bit
environment.)
>I haven't attempted this yet, but I will experiment with it, and I will
post
>a response here when I have drawn a conclusion.

We have tried to use thunk with Intersolve without success.