Re: problems with running 32-bit tclsh on Windows x64

Hey Robert,
Do not copy files from the 32 to 64 bit folders, you can trust MS to
write their OS in such a way that this will cause problems.

The only workaround i can think of is to spwan a cmd.exe proccess and
ask it to run the 64bit application. I am not sure it will work but
it's worth a try.

Instead of running
ntbackup.exe
try to run
cmd.exe /c ntbackup.exe
or something like this.

good luck,
/NL

On Apr 4, 6:06 pm, rpre...@xxxxxxxxx wrote:
Hi!

On a MS Windows XP Pro. x64 (64-bit) Edition I installed ActiveState
ActiveTcl 8.4.14.0 (the 32-bit x86 distribution that is available as a
free download).

I noticed problems with invoking some system tools from the Tcl
scripts (which run in a 32-bit tclsh process). The problems are caused
by the way the WOW64 subsystem works in Windows x64. Namely,
the "%SystemRoot%\system32" directory is used for 64-bit DLLs and
EXEs, while
the "%SystemRoot%\SysWOW64" directory is used for 32-bit DLLs and
EXEs.
Some of the system files are present in both directories, i.e. they
have
64-bit and 32-bit versions, but some have only 64-bit version.

When executing 32-bit applications, the WOW64 subsystem makes files in
%SystemRoot%\system32 inaccessible to the application. The
application sees %SystemRoot%\sysWOW64 as %SystemRoot%\system32.

For example it is not possible to invoke ntbackup.exe from a Tcl
script as there is only 64-bit version of ntbackup.exe (in
%SystemRoot%\system32).

Is there a workaround for this problem besides copying the
inaccessible files from %SystemRoot%\system32 to another directory
that is accessible to 32-bit applications?

I hope some day the 64-bit binary distributions of the ActiveTcl
package will be available as a free download.

-- rpr. /Robert Premuz/


.

Relevant Pages

  • Re: What exactly Dll does
    ... difference between dlls and exes are that exes are entry points to applications, ... You can add references to each of them to use the types that are used in them. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Dll Hell
    ... :>ship with an installer is tame, and it puts usbcalls.dll and ... DLLs are created to share code between applications and to short used ...
    (comp.os.os2.apps)
  • Re: Deployment Question
    ... >> applications that use those core DLLs. ... >> .DLLs in the system folder and just share them between the two ... I would go ahead with the simple XCopy deployment. ...
    (microsoft.public.vstudio.general)
  • Re: binmod.exe, NK.bin files and other beginner questions
    ... If you can't get the EXEs ... my main concern is over the added executables and dlls ... having to rewrite the entire application (which consists of about a ...
    (microsoft.public.windowsce.embedded)
  • Re: Deployment Question
    ... > applications that use those core DLLs. ... Put the assemblies in the bin folders of their respective apps. ... I would go ahead with the simple XCopy deployment. ...
    (microsoft.public.vstudio.general)