copSSH on 64bit architecture - will not run a ADODB.Connect function.

2 posts / 0 new
Last post
Last seen: 12 years 6 months ago
Joined: 14.05.2009 - 18:11
copSSH on 64bit architecture - will not run a ADODB.Connect function.

The BASH environment and subseuent CMD environments appear to have attributes for x86 32 bit architecture only. 

I'm on Windows Server 2008 R2 in 64bit mode attempting to run a VBS script which uses ADODB.Connect to a MSSL 2008 database.  The VBS/WSH script runs but the call to ADODB.Connect gets a "module not found". Upon comparing the SET environment varables from the interactive logon and the same returned by a SET command issued within the copSSH environment, they are drastically different.  Specifically the PATH and all values that identify either a x86 or x64/i64 environment.


Has anyone been able to get copSSH shell to recognize and launch scripts that use 64bit function calls like the ADODB.Connect?

Is there an equivilent 32bit call that canbe used instead so that it will run within the copSSH environment?

Last seen: 3 days 4 hours ago
Joined: 01.05.2008 - 21:33
Copssh is based on Cygwin

Copssh is based on Cygwin which is a 32-bit environment. From Cygwin FAQ:

What versions of Windows are supported?


Cygwin can be expected to run on all modern 32 bit versions of Windows, except Windows CE and Windows 95/98/Me. This includes, as of the time of writing this, Windows NT4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, as well as the WOW64 32 bit environment on released 64 bit versions of Windows (XP/2003/Vista/2008/7/2008 R2). As far as we know no one is working on a native 64 bit version of Cygwin. Since Cygwin is a community-supported free software project, patches to provide support for other versions would be thoughtfully considered. Paid support contracts or enhancements are available through Red Hat. For information about getting a Red Hat support contract, see

Keep in mind that Cygwin can only do as much as the underlying OS supports. Because of this, Cygwin will behave differently, and exhibit different limitations, on the various versions of Windows.

Release news