Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New installer fails on 32-bit OS due to x64-only constant #18

Open
GreenReaper opened this issue Jan 3, 2016 · 3 comments
Open

New installer fails on 32-bit OS due to x64-only constant #18

GreenReaper opened this issue Jan 3, 2016 · 3 comments

Comments

@GreenReaper
Copy link

When starting to install the 5.0 executable on 32-bit Windows Vista, I received the following error

Cannot expand "pf64" constant on this version of Windows.

This behaviour is documented. You probably want to use {pf} instead.

The actual program works fine when extracted with innounp.

@GreenReaper GreenReaper changed the title New installer won't install on 32-bit OS due to x64-only constant New installer fails on 32-bit OS due to x64-only constant Jan 3, 2016
@PranavMahesh1
Copy link

@GreenReaper Did you get this program working on 32-bit?

@GreenReaper
Copy link
Author

GreenReaper commented Jun 2, 2017

No; I took the raw drive which held the VM out and put it in a HP MicroServer Gen8 instead. Worked a treat!

@ShadowEO
Copy link

ShadowEO commented Mar 23, 2019

Same issue here, attempting to install the version for 5.2 (32-bit OS locked in by firmware, so I can't install a 64-bit OS and run Vbox6) gives the same error.

It appears that the reason is this line:
#define InstallDir "{pf64}\Topten Software\VBoxHeadlessTray"
should be
#define InstallDir "{pf}\Topten Software\VBoxHeadlessTray" as {pf} should (iirc, it's been a little bit since i've used inno) automatically resolve to the C:\Program Files directory on a 64-bit capable system anyway, or at least go to the (x86) folder, which will still be correct for installation for an application that mixes architecture support like this one.

That should fix the installer's 32-bit crashing, and really shouldn't cause any issues with the application otherwise..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants