[Solved]Compatibility Check?

[Hybrid]

Hey, so I made an installer and few labels which tell ur OS Version and Bit.. using @OSArch & @OSVersion

What I want to do is, if the OS Version is XP, controls get deactivated and a MsgBox appear saying that the XP Users aren't compatible

Edited December 30, 2012 by Hybrid

[guinness]

Look at MsgBox, GUICtrlSetState and If statements in the help file. You can also search _Toggle_EnableDisable in the Forum/Wiki.

[Hybrid]

Look at MsgBox, GUICtrlSetState and If statements in the help file.

I know this part. I have few experience in AutoIt

I just don't know how to make the program find if the OS is XP.

In visual basic were easier.

I'm looking for something like this: [this is in vb] If Label1.Text = "Win XP" Then

; block all GUI Controls

[Hybrid]

nvm. Got an ideea

[Hybrid]

Done. I need an XP user to test it ._.

[Melba23]

Hybrid,

Have you looked at the @OSVersion macro? All you need then is a If structure:

If @OSVersion = "WIN_XP" Then
    MsgBox(0, "OS", "XP")
Else
    MsgBox(0, "OS", "Not XP")
EndIf

M23

[Hybrid]

Hybrid,

Have you looked at the @OSVersion macro? All you need then is a If structure:

If @OSVersion = "WIN_XP" Then
MsgBox(0, "OS", "XP")
Else
MsgBox(0, "OS", "Not XP")
EndIf

M23

Ah.

I did it in other way >.>

Func _Check()
If $Label8= "WIN_XP" Then
MsgBox(0, "Error", "Your OS is XP." & @CRLF & "Your System is not compatible with this tool!")
Else
MsgBox(0, "", "Compatibility Test Passed~", 3)
EndIf
EndFunc

and Label8 ish:

$Label8 = GUICtrlCreateLabel("Label3", 160, 32, 36, 17, -1, $WS_EX_STATICEDGE)
GuiCtrlSetData(-1, @OSVersion)

Guess both versions work :3

Edited December 30, 2012 by Hybrid

[Melba23]

Hybrid,

Guess both versions work :3

Are you sure? What value do you get in the $Label8 variable? You will find it is the ControlID of the label, not the content.

If you do want the content, then you need to use GUICtrlRead($Label8).

M23

[Hybrid]

Hybrid,

Are you sure? What value do you get in the $Label8 variable? You will find it is the ControlID of the label, not the content.

If you do want the content, then you need to use GUICtrlRead($Label8).

M23

Look at the pic on the first post.

That's the content of label8

Anyway, used ur method :c

[Melba23]

Hybrid,

You create the label here:

$Label8 = GUICtrlCreateLabel("Label3", 160, 32, 36, 17, -1, $WS_EX_STATICEDGE)
GuiCtrlSetData(-1, @OSVersion)

and the variable $Label8 contains the ControlID of the label which you can use later to address it.

When you later use this

If $Label8= "WIN_XP" Then

how do you expect the ControlID of the label to read "WIN_XP"?

What I was explaining above was that you need to do:

If GUICtrlRead($Label8) = "WIN_XP" Then

in order to read the content of the label.

But as you say, using the @OSVersion macro directly is much quicker and more elegant.

M23

[Hybrid]

Hybrid,

You create the label here:

$Label8 = GUICtrlCreateLabel("Label3", 160, 32, 36, 17, -1, $WS_EX_STATICEDGE)
GuiCtrlSetData(-1, @OSVersion)

and the variable $Label8 contains the ControlID of the label which you can use later to address it.

When you later use this

If $Label8= "WIN_XP" Then

how do you expect the ControlID of the label to read "WIN_XP"?

What I was explaining above was that you need to do:

If GUICtrlRead($Label8) = "WIN_XP" Then

in order to read the content of the label.

But as you say, using the @OSVersion macro directly is much quicker and more elegant.

M23

Yeah, you're right.

i was just tired and hungry.

Coded 6-7hours today w/o eating ._.

Anyway, thanks

[Melba23]

Hybrid,

Glad you understand - now go and eat something.

M23

[guinness]

Hybrid,

I know it can be addictive when coding, but taking regular breaks will really help. For example the other day I had a momentary lapse of judgement and couldn't work out why this (just a small example, not the actual code which was a little longer in lines) was failing >>

For $i = 1 To 2
    ConsoleWrite('>> First loop: ' & @CRLF)
    For $i = 1 To 10
        ConsoleWrite('>> Second loop: ' & @CRLF)
    Next
Next

The output should be

>> First loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> First loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop:

and not

>> First loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop: 
>> Second loop:

Did you spot the mistake?

For $i = 1 To 2
    ConsoleWrite('>> First loop: ' & @CRLF)
    For $j = 1 To 10 ; << Was using $i instead of $j or another For loop variable name.
        ConsoleWrite('>> Second loop: ' & @CRLF)
    Next
Next

Edited December 30, 2012 by guinness

[KaFu]

I always use this WinAPIEx internal function to determine the OS. Comparing to a number is always easier imho than comparing to a string.

Global Const $__iWINVER = __WINVER() ; WinAPIEx internal function

If $__iWINVER > 0x0600 Then ; Vista+
    ConsoleWrite($__iWINVER & @tab & "Vista+ OS detected" & @crlf)
Else ; XP or older
    ConsoleWrite($__iWINVER & @tab & "XP or older OS detected" & @crlf)
EndIf

Func __WINVER() ; Minimum supported client: Windows 2000 Professional
    Local $tOSVI = DllStructCreate('dword;dword;dword;dword;dword;wchar[128]')
    DllStructSetData($tOSVI, 1, DllStructGetSize($tOSVI))
    Local $Ret = DllCall('kernel32.dll', 'int', 'GetVersionExW', 'ptr', DllStructGetPtr($tOSVI))
    If (@error) Or (Not $Ret[0]) Then
        Return SetError(1, 0, 0)
    EndIf
    Return BitOR(BitShift(DllStructGetData($tOSVI, 2), -8), DllStructGetData($tOSVI, 3))
EndFunc   ;==>__WINVER

[GordonFreeman]

A curiosity. Why not run on XP?

Select
Case @OSVersion = "WIN_XP"
MsgBox(0, "", "Your system is Windows XP and it will pick up a virus"
Case @OSVersion = "WIN_VISTA"
MsgBox(0, "", "Your system is Windows Vista and it will crash"
EndSelect

;Select is also good to this

Edited December 31, 2012 by GordonFreeman

[guinness]

Not only are your MsgBox comments ludicrous, but using a Select statement is not the most efficient approach.

[GordonFreeman]

Not only are your MsgBox comments ludicrous, but using a Select statement is not the most efficient approach.

I used only two. It's something useful for the 9 possible returns (@ OSVersion). And I already used Windows XP too, and of course the ways to make it good (DeepFreeze, A good firewall, A good anti-virus, disable autoruns, a large configuration).

Now guinness give me a kiss, please!

[Xandy]

Coded 6-7hours today w/o eating ._.

Welcome to Programmer club. Edited December 31, 2012 by Xandy