[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:	TeamLinks for Windows
Notice:	Kit and ECO locations: See replies to note 8.o note 8.
Moderator:	ORION::chayna.zko.dec.com::tamara::eppesAN

Created:	Mon Aug 28 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2238
Total number of notes:	9650

2216.0. "32-bit DLLs??" by ZPOVC::LAICHAN () Fri May 23 1997 07:01

    Hello there,
    
    From the various replies in this notes, the various DLLs from the
    TeamLinks 2.5 and 2.7 SDK are 16-bit versions. Do we have any new SDK
    versions that support the 32-bit versions of the DLLs such as the
    CFC.DLL, CONNECT.DLL?
    
    One of our customers who has both TeamLinks 2.5 and 2.7 with MAILworks
    1.3a server, is trying to doing some integration project using VB 5.0
    to call GETCONNECTINFO function (one of the requirement) in CONNECT.DLL 
    which will not work or supported with the current version of both 
    TeamLinks and SDK. The customer's plan is have the development 
    environment using Win 95 and target live environment on Windows 
    NT 4.0.
    
    Does it mean that the customer has to wait for TeamLinks V3.0 (Project
    Panther), the 32-bit client with the respective SDK which is planned
    for release this summer?
    
    Appreciate any info, pointers.
    
    Thanks.
    
    Regards,
    Lee

T.R	Title	User	Personal Name	Date	Lines
2216.1	We have some DLLs but they're not ready for release.	XANADU::cascobay.zko.dec.com::TAMARA::STJEAN	Bob St.Jean	`Fri May 23 1997 11:31`	23
	Lee, We have only some early baselevels of 32-bit DLLs. They are for TeamLinks V4.0, the 32-bit version, which has no official schedule yet but is planned for early next year. I have ported CONNECT.DLL to Win32. It's renamed to TLPWL32.DLL. However it is not quite ready for release yet. There is one very important function that this DLL does and that is maintain an in-memory password cache for all TeamLinks apps/components. That doesn't work yet due to differences in how shared memory works from Win16 to Win32. This isn't a big deal within a task or on Windows 95, because it can access the Windows Password Cache. Also, what are they planning to use this for on Windows NT? This platform does not support the Windows Password Cache like Windows 95 does. So there we really need the above to be fixed. We also have early test version of CFC32.DLL and the other CFC DLLs, but they too are not yet ready for release. Bob
2216.2	One developer's opinion	TAMARA::laceup.zko.dec.com::tamara::fitzell	It's not a bug it's functionally challenged !	`Fri May 23 1997 12:35`	8
	>> The customer's plan is have the development >> environment using Win 95 and target live environment on Windows >> NT 4.0. If you have any influence with them at all I would encourage them to do the developement on NT 4.0. Our experience especially with 16 bit apps is that WIN95 and NT4.0 don't always play the same. Mike
2216.3	clarifying project names and version numbers	ORION::chayna.zko.dec.com::tamara::eppes	Nina Eppes	`Wed May 28 1997 17:37`	11
	> Does it mean that the customer has to wait for TeamLinks V3.0 (Project > Panther), the 32-bit client with the respective SDK which is planned > for release this summer? TeamLinks V3.0 is "Cougar" and is 16-bit. "Panther" is the name for V4.0, the 32-bit version. Just FYI. - Nina