System32 and SysWOW64

[NewsArchive]

Shrimp cocktail. Now settling back with a Glenlivet (in a proper snifter).

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

> That's nothing. My son had a Nintendo 64 around 1996/1997<g>.

LOL... soon this thread will disintegrate to punch cards and beer
--

Mark Riffey
http://www.rescuemarketing.com
Now featured on the Visa Business Network
If Guy Kawasaki, the staff of the Wall Street Journal,
Fast Company, US Bank, Marketing Profs & Business Week read it,
maybe you should too.

[NewsArchive]

He wanted a Nintendo really bad. He also wanted a game boy.

This was before his Mom agreed to allow video games into his life.

I suggested calling a cardboard box a Pretendo. He didn't like that,
so how about a Lame Boy? Didn't like that either.

Jeff Slarve
www.jssoftware.com
www.twitter.com/jslarve
I'll search help files & Google for you.

[NewsArchive]

Hi Graham,

>> ......... But you never "hard-code" the SysWOW64 part.........
>
> Ah, now that bit took a little while to sink in :-)
>
> So you actually script \System32 and the installer, working with
> your installer option setting and the current OS determines whether
> to 'redirect' to SysWOW64 or not.
>
> Presumably the install LOG files show the actual install paths
> rather than the scripted paths?

This can be somewhat confusing, but there is some kind of "emulator" in
Windows x64 that redirects 32-bit application calls to System32 to the
SysWOW64 folder transparently. So even if the Sytem32 folder is
"hard-coded" in a 32-bit app (like C:\Windows\System32), the emulator will
make sure that the SysWOW64 folder is used instead. But it is not valid to
hard-code things like C:\Windows\SysWOW64.

Both the 32- and 64-bit Windows applications always "talk" to the System32
folder. As a result, you'll always see System32 in the SetupBuilder install
LOG. The tricky thing is that the installer knows in what "bitness mode" it
is running. So based on this mode (x86 or x64), it can access the "real"
System32 folder (for 64-bit components) or the "emulated" System32 folder
(SysWOW64) for 32-bit apps. This technology allows us to install a 32-bit
and 64-bit application from the very same setup.exe.

Friedrich

[NewsArchive]

Hi Friedrich,

> Both the 32- and 64-bit Windows applications always "talk" to the System32
> folder. As a result, you'll always see System32 in the SetupBuilder
> install LOG. The tricky thing is that the installer knows in what
> "bitness mode" it is running. So based on this mode (x86 or x64), it can
> access the "real" System32 folder (for 64-bit components) or the
> "emulated" System32 folder (SysWOW64) for 32-bit apps. This technology
> allows us to install a 32-bit and 64-bit application from the very same
> setup.exe.

Ah OK got that, so basically it's 'just' down to a support issue ie knowing
where to look for the program components.

Graham

[NewsArchive]

> I suggested calling a cardboard box a Pretendo. He didn't like that,
> so how about a Lame Boy? Didn't like that either.


--

Mark Riffey
http://www.rescuemarketing.com
Now featured on the Visa Business Network
If Guy Kawasaki, the staff of the Wall Street Journal,
Fast Company, US Bank, Marketing Profs & Business Week read it,
maybe you should too.