6 replies to this topic

[LMichel]

Hello,

 

I've written a custom action to determine the screen format (4/3, 16/9, 16/10)

 

My custum action is part of the install execute sequence.

 

It seems that a wrong value for theses properties is returned : 1024x768 instead of 1366x768

 

Is it a bug ? Can this be fixed ?

 

Regards

[VBScab]

By definition, your custom action is acting outside the control of the Windows Installer engine so any bug will be in whatever it is your CA is calling (I'm guessing it's a WMI call?) Does the test work externally, i.e. outside of your MSI?

[LMichel]

By definition, your custom action is acting outside the control of the Windows Installer engine so any bug will be in whatever it is your CA is calling (I'm guessing it's a WMI call?) Does the test work externally, i.e. outside of your MSI?

 

ScreenX and ScreenY are properties that are set by Windows installer. My CA just read the value.

http://msdn.microsof...9(v=vs.85).aspx

[VBScab]

Well, saw my legs and call me "Shorty"!! You really do learn something every day!

In which sequence is your CA running?

[LMichel]

<sup>Well, saw my legs and call me "Shorty"!! You really do learn something every day!

In which sequence is your CA running?</sup>

 

^{Don't worry for your legs}

 

My CA is running into install execute (immediate execution)  just after AppSearch. I've tryed to move my CA at several places into the install execute with the same result.

 

It works fine Under Windows Xp but not Under Windows 7.

[LMichel]

An additional information this is Windows 7 - 64Bits

[VBScab]

>It works fine Under Windows Xp but not Under Windows 7.
I'd bet a fair amount that it is indeed the 64-bit vs 32-bit "gotcha". Personally, I'd abandon using those properties and use WMI in a script. That should work in any "bitness" :-)