Windows XP Pro-64 Compatible?

[rraisley]

I just distributed an app, and selected to allow Windows XP and all Future OS's, but a customer now tells me it will not install under the new 64-bit XP. What setting would be required for that? The only ones left not checked at this time are WinNT3.5 (which I don't want to install with) and Windows 2003 Server (this is a PC app, not a server app).

How can I change the install to work under XP-64, without letting it open to anything?

[Eagle]

I have not had issues with installations to Windows XP x64 Os's

Windows XP x64 (IA64 version was dropped by MS around 18 months ago.)

WinXP x64 version has built in win32 app redirection at the kernel level
and by default will direct-redirect 'installers' to the WOW64
(psuedo system32 folder for 32bit apps) folder on system.

'All future Os's' does not have influence on XP x64(if XP all sp's is enabled)
in system requirements.

make sure Admin rights is selected as an install condition and check the
individual os conditions for every binary file included in your install, as this
could be the install issue.(during design, select file properties for all your files

I would recommend requesting a copy of the install log file from the client
(your post did not detail at what point or stage the install spits the dummy)

hth a little.

[rraisley]

'All future Os's' does not have influence on XP x64(if XP all sp's is enabled) in system requirements.
Where is XP x64 considered, then? I checked Windows XP (all SP and all Future SP) and All Future OSs. It wouldn't proceed.
make sure Admin rights is selected as an install condition and check the individual os conditions for every binary file included in your install, as this
could be the install issue.(during design, select file properties for all your files

Admin rights were selected. But you're saying that in addition to setting the Project Settings, I have to set all the files individually?? Anyhow, I don't /think/ that was the problem, because it wasn't that it wouldn't install correctly; it wouldn't install at all. The message stated that the system did not meet the requirements. And (unfortunately) I checked to NOT proceed if the requirements weren't met, because I've had a rash of people trying to install without admin privilages.
I would recommend requesting a copy of the install log file from the client (your post did not detail at what point or stage the install spits the dummy)
As I said above, the program stopped because I told it to, if the requirements weren't met. I made a new install, checked Windows Server 2003 (the only thing not checked, other that NT 3.51), and now Notify the user instead of stopping the install. The new setup did not notify the user, so apparently was happy with the requirements.

Is it possible XP x64 is closer to w2k3 Server than XP??

[rraisley]

And I confirmed that all files are set to Any OS. Only the System Requirements specified what Windows versions were allowed.

[Eagle]

Yes, XP x64 IS basically Server 2003 (sp1) under the hood.

Specific 64 bit Os detection I'm sure will find its way in to 'system requirements',

I tend to have exact replication of Os types throughout the design settings, file properties.

I am again not convinced that there are'nt a glitch or two in the os requiremts checks at runtime,
with regard to 'notification selection' option

[rraisley]

Yes, XP x64 IS basically Server 2003 (sp1) under the hood.
Well, now, THAT explains a lot! ;-)
Specific 64 bit Os detection I'm sure will find its way in to 'system requirements',
Probably so.
I am again not convinced that there are'nt a glitch or two in the os requiremts checks at runtime, with regard to 'notification selection' option
I don't think so. I specifically did /not/ check Server 2003 in the system requirements selection, as I hadn't done any testing and figured no one would use it on a server. I'm sure now /that/ was the problem, because I selected to not proceed if it didn't meet the requirements. I have now added Server 2003 (because /I/ have installed other, standard apps on a 2003 server myself, plus the decision was reinforced by your statement above that XP x64 is considered Server 2003). And just to play it safe, I'm now allowing the user to continue.

Anyhow, you've answered my question: For use with SUF7 system requirements, Windows XP x64 = Windows Server 2003. For now, at least. ;-)

[Eagle]

all good, yep Server Os's can run Applications just like Client Osss can, as you stated.

[Intrigued]

I thought I would append my question onto this thread, seems relevant.

My new employer asked if SF 7 does true Win XP / Vista 64-bit and all I could see is that it steps down to 32-bit. Is there 64-bit, full support for such coming soon? (We are about to change to InstallShield or some other one and we will be shipping A LOT of our product and I want SF 7 driving the show, as I could then get into using such and paid for it, for one ;)).

So, this for us is a time-sensitive issue.

TIA

[Brett]

Setup Factory 7.0 will run fine on the 64-bit OS (Vista and XP). The only real thing that we will be adding is the ability to turn the WOW64 redirection on or off. We will be adding that in the coming weeks/months. However, for now it is real easy to make a DLL that will call the functions or even use the DLL action built into Setup Factory to do that (see this post. (http://www.indigorose.com/forums/showthread.php?t=14532))

[Intrigued]

Okay, thanks Brett. I'll show him this message and hopefully this will swing the tide for him.

:yes