Francesco

Please vote: Vista/Win7/Win8 UAC support poll

   15 members have voted

  1. 1. How to make WPI support UAC?

    • Disable UAC before reboot and re-enable it after reboots
      9
    • Maintain UAC always on and remove the incompatible LoadDesktopBeforeInstall option
      3
    • I don't know, but I like turtles!
      3

Please sign in or register to vote in this poll.

37 posts in this topic

As title says. In case of the 2nd choice WPI will always launch with/after explorer.

Edited by Francesco
0

Share this post


Link to post
Share on other sites

If we can get WPI to disable\re-enable uac during install that would be super.

BTW Turtles are awesome!

0

Share this post


Link to post
Share on other sites

Hi, found an interesting reg file which turns off the UAC, may be it will be useful for You:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLUA"=dword:00000000

Using RegShot i traced tha to undo this change it is necessary to use this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLUA"=dword:00000001

But there is one disadvantage: to make this tweak work it is necessary to reboot

Edited by chymax3m
0

Share this post


Link to post
Share on other sites

Hi, found an interesting reg file which turns off the UAC, may be it will be useful for You:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLUA"=dword:00000000

Using RegShot i traced tha to undo this change it is necessary to use this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLUA"=dword:00000001

But there is one disadvantage: to make this tweak work it is necessary to reboot

I already figured out how to disable UAC and how to set a task on reboot but until people vote I'm not writing anything since both workarounds are extremely annoying.

0

Share this post


Link to post
Share on other sites

OK then. I think it would be better to make it optional.

0

Share this post


Link to post
Share on other sites

Will you guys add support for getosver=Win8?

Why do you guys use XP/Vista/Win7, would it not be better to use 5.1/6.0/6.1/6.2 etc? (future proof)

0

Share this post


Link to post
Share on other sites

I really don't want to support 8.

As for the Winver it is mainly because we have always done it that way and it is better for the "Less technically" inclined...

0

Share this post


Link to post
Share on other sites

Would not take much to add Win8 support, since it pretty much runs same as it does on Win7

Also if you use 6.1.x/6.2.x/etc. it would allot be better, because you could also add service pack specific install support. For instance the Microsoft Camera Codec Pack is only compatible with Vista sp2 and not meant for Windows 8, would be nice if we could add these conditions in WPI

Installed OR (WindowsBuild >= 6002) Windows Vista Service Pack 2 or higher is required to install the Microsoft Camera Codec Pack.

NOT (VersionNT > 601) This version of the Microsoft Camera Codec Pack is not compatible with Windows 8 or Windows Server 2012. You can get the codec pack through Windows Update on Windows 8. The codec pack is not available for Windows Server 2012.

0

Share this post


Link to post
Share on other sites

We already have a spver:

function getSPver()
{
position="wmi.js";
whatfunc="getSPver()";

if (szServicePackCache==NOT_FOUND) // this function is called often - get it once and cache the result
{
try
{
objWMIService=GetObject("winmgmts:\\\\" + "." + "\\root\\CIMV2");
colItems=objWMIService.ExecQuery("SELECT * FROM Win32_OperatingSystem", "WQL", wbemFlagReturnImmediately | wbemFlagForwardOnly);
enumItems=new Enumerator(colItems);
objItem=enumItems.item();

szServicePackCache=objItem.ServicePackMajorVersion;
}
catch(ex)
{
var sp="";

try
{
sp=WshShell.RegRead("HKLM\\Software\\Microsoft\\Windows NT\\CurrentVersion\\CSDVersion");
}
catch(ex)
{ ; }

if (sp != "")
{
szServicePackCache=sp.substr(sp.length-1,1);
}
}
}

return szServicePackCache;
}

As for the "5.1/6.0/6.1/6.2" IF You and francesco can just add it to the existing code fine. I am not going to tell the thousands and thousands out there that they have to change all of their osver to the 5.1/6.0/6.1/6.2. Only 5% or so of them will listen.

0

Share this post


Link to post
Share on other sites

Not change, if you can support both options would be nice

This MSI LaunchCondition:

Installed OR (WindowsBuild >= 6002) Windows Vista Service Pack 2 or higher is required to install the Microsoft Camera Codec Pack.

NOT (VersionNT > 601) This version of the Microsoft Camera Codec Pack is not compatible with Windows 8 or Windows Server 2012. You can get the codec pack through Windows Update on Windows 8. The codec pack is not available for Windows Server 2012.

In WPI could look like:

getOSver2()>="6.0.6002"&&getOSver2()<="6.1"

It would make WPI "future proof". You wont have to add a Win9/10/11 when/if another operating system comes out it will simply work, one would just have to increase the decimal point

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites

Not change, if you can support both options would be nice

This MSI LaunchCondition:

Installed OR (WindowsBuild >= 6002) Windows Vista Service Pack 2 or higher is required to install the Microsoft Camera Codec Pack.

NOT (VersionNT > 601) This version of the Microsoft Camera Codec Pack is not compatible with Windows 8 or Windows Server 2012. You can get the codec pack through Windows Update on Windows 8. The codec pack is not available for Windows Server 2012.

In WPI could look like:

getOSver2()>="6.0.6002"&&getOSver2()<"6.1"

It would make WPI "future proof". You wont have to add a Win9/10/11 when/if another operating system comes out it will simply work, one would just have to increase the decimal point

You can already read the windows version number from the registry (HKLM\Software\Microsoft\Windows NT\CurrentVersion\CurrentVersion) also you can't compare versions as strings there's a function for that.

0

Share this post


Link to post
Share on other sites

That's the workaround I been using

Edit: (Vista sp2 to Win7 ENU condition)

RegKeyValue("HKLM\Software\Microsoft\Windows NT\CurrentVersion\CurrentVersion")=="6.0"&&RegKeyValue("HKLM\Software\Microsoft\Windows NT\CurrentVersion\CurrentBuild")>="6002"&&getOSlang()=="ENU"||RegKeyValue("HKLM\Software\Microsoft\Windows NT\CurrentVersion\CurrentVersion")=="6.1"&&getOSlang()=="ENU"

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites

Rick & Francesco:

OK I will add support for 8 AND version #'s! BUT I need you guys to help add the code in so we can keep backwards compatability with the current getosver...

Rick I need the current style getosver info for win8.

0

Share this post


Link to post
Share on other sites

6.2.9200 is RTM, I think 6.2.9201 will be SP1, etc

Is that what you meant?

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.