From: Jeremy on 3 Aug 2010 11:27 Hello, I am on Windows 7 64bit. I am using ActiveState's 8.6b3 install w/tls included. Here is a typical session: C:\Projects> tclsh86 % package require tls couldn't load library "C:/Development/Tools/Tcl/lib/teapot/package/ win32-ix86/lib/tls1.6/tls16.dll": invalid argument % I used dependency walked and found that three DLLs were missing: * GPSVC.DLL - found in C:\Windows\System32 * IESHIMS.DLL - found in C:\Program Files\Internet Explorer * SYSNTFY.DLL - found in C:\Windows\System32 So, for the fun of it I copied these files to "C:/Development/Tools/ Tcl/lib/teapot/package/win32-ix86/lib/tls1.6/" I continue to get the same problem, so I ran dependency walker again and see that the three files I copied into the tls directory are of CPU type x64 when all the rest of the dependencies are x86. Any thoughts on resolving this problem so I can use tls? Thanks, Jeremy
From: Jeff Hobbs on 3 Aug 2010 13:43 On Aug 3, 8:27 am, Jeremy <cp200...(a)gmail.com> wrote: > I am on Windows 7 64bit. I am using ActiveState's 8.6b3 install w/tls > included. Here is a typical session: > > C:\Projects> tclsh86 > % package require tls > couldn't load library "C:/Development/Tools/Tcl/lib/teapot/package/ > win32-ix86/lib/tls1.6/tls16.dll": invalid argument Works fine for me in 8.6 tkcon on 64-bit Windows Vista, using 32-bit AT 8.6b3: Main console display active (Tcl8.6b1.2 / Tk8.6b1.2) (System32) 49 % info loaded {{} Tk} {C:/Tcl-86/lib/tcl8.6/reg1.3/tclreg13.dll Registry} (System32) 49 % package require tls 1.6 (System32) 50 % info loaded {C:/Tcl-86/lib/teapot/package/win32-ix86/lib/tls1.6/tls16.dll Tls} {{} Tk} {C:/Tcl-86/lib/tcl8.6/reg1.3/tclreg13.dll Registry} > I used dependency walked and found that three DLLs were missing: > > * GPSVC.DLL - found in C:\Windows\System32 > * IESHIMS.DLL - found in C:\Program Files\Internet Explorer > * SYSNTFY.DLL - found in C:\Windows\System32 These are bogus optional DLLs that won't be used and don't prevent loading. In fact, the "invalid argument" error you see is not the one that indicates a missing DLL. Something else is wrong with your mix of tls and core, but I couldn't say what, given I have a similar setup. I'm not sure if Windows 7 could change the equation somehow. Jeff
From: Jeremy on 3 Aug 2010 15:01 Ok, I have not figured it all out yet, but I did get it to work. I found libeay32.dll and ssleay32.dll in C:\Windows\SysWOW64 If I move those to a bogus name, then do a package require tls, all works great. Move them back to their legit names and package require tls no longer works. Jeremy
|
Pages: 1 Prev: I GOT $2500 FROM PAYPAL.... Next: How to handle user input in multiple non modal windows? |