Quantcast
Channel: VBForums - Visual Basic 6 and Earlier
Viewing all articles
Browse latest Browse all 21090

Develop, Deploy 32 bit applications to 64 bit Windows?

$
0
0
I create my self-contained programs and their NSIS install packages to
prevent their interfering with or being interfered with any other
applications on the user's PC.
http://www.indra.com/~anderci
They are reg-free and do nothing with the Windows Registry except record
links to their Executable file and their Uninstall File.

My applications create files and subfolders of their Install Folder as
needed without special (administrator) privileges.

I accomplish this by including all of the reference files and their manifest
files in the Install folder.

This works well on 32 bit Windows when the Install Folder is in the
C:\Users\Public\... folder structure e.g.:
C:\Users\Public\Clark_Anderson\QueryMgr .

For 64 bit Windows it is indicated that 32 bit applications belong in the
C:\Program Files (x86)\... folder structure and their shared components
belong in the C:\Program Files (x86)\Common Files\... folder structure.
There is also mention of the C:\Windows\Syswow64\... folder structure.

I have tweaked my NSIS install files to try the C:\Program Files (x86)\...
folder structure, if 64-bit. I hope they have the freedom to create files
and subfolders.

My quandary is where do I install my 32 bit applications to function on a 64
bit Windows system and give them the freedom to create their subfolders and
files as required?

Is there a method, other than the standardized location, for them to operate
in 32-bit compatibility mode?

Does WOW64 come with all Windows 7 installations? Or must it be downloaded
and installed?

Is it a matter if obtaining and including Wow64.dll (and possibly
Wow64Win.dll, Wow64Cpu.dll and Ntdll.dll) with manifest files in the install
for 64 bit Windows PCs?
re: http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

Viewing all articles
Browse latest Browse all 21090

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>