Share this post

Link to post

Share on other sites

furrycow 0

furrycow 0

Actually, just ive just run the program to check out what my array contains, and i have a few monitors installed on this machine, but theyre not connected, as in not plugged in, i dont have them with me either, but all their [1]Availability = 8, whereas my default one that i am using is [1]Availability = 3

EDIT:

Just read the actual link given by Pain at the beginning, and the answers in there!! Seeing as CompInfo.au3 uses the Win32_DesktopMonitor Class

The Win32_DesktopMonitor class defines the following properties.

Availability

Data type: uint16

Access type: Read-only

Availability and status of the device. Inherited from CIM_LogicalDevice.

Value Meaning

1

0x1

Other

2

0x2

Unknown

3

0x3

Running or Full Power

4

0x4

Warning

5

0x5

In Test

6

0x6

Not Applicable

7

0x7

Power Off

8

0x8

Off Line

9

0x9

Off Duty

10

0xA

Degraded

11

0xB

Not Installed

12

0xC

Install Error

13

0xD

Power Save - Unknown

The device is known to be in a power save mode, but its exact status is unknown.

14

0xE

Power Save - Low Power Mode

The device is in a power save state but still functioning, and may exhibit degraded performance.

15

0xF

Power Save - Standby

The device is not functioning, but could be brought to full power quickly.

Share this post

Link to post

Share on other sites

punisa 0

punisa 0

Actually, just ive just run the program to check out what my array contains, and i have a few monitors installed on this machine, but theyre not connected, as in not plugged in, i dont have them with me either, but all their [1]Availability = 8, whereas my default one that i am using is [1]Availability = 3

EDIT:

Just read the actual link given by Pain at the beginning, and the answers in there!! Seeing as CompInfo.au3 uses the Win32_DesktopMonitor Class

The Win32_DesktopMonitor class defines the following properties.

Availability

Data type: uint16

Access type: Read-only

Availability and status of the device. Inherited from CIM_LogicalDevice.

Value Meaning

1

0x1

Other

2

0x2

Unknown

3

0x3

Running or Full Power

4

0x4

Warning

5

0x5

In Test

6

0x6

Not Applicable

7

0x7

Power Off

8

0x8

Off Line

9

0x9

Off Duty

10

0xA

Degraded

11

0xB

Not Installed

12

0xC

Install Error

13

0xD

Power Save - Unknown

The device is known to be in a power save mode, but its exact status is unknown.

14

0xE

Power Save - Low Power Mode

The device is in a power save state but still functioning, and may exhibit degraded performance.

15

0xF

Power Save - Standby

The device is not functioning, but could be brought to full power quickly.

16

0x10

Power Cycle

17

0x11

Power Save - Warning

The device is in a warning state, though also in a power save mode.

Hey furrycow, thanks for taking interest. I'm sorry, but I admit that I don't actually understand what all this means.

You'll have to excuse my noobishnes

If it wouldn't be too much of a problem to point out some steps I should put in my script in order to make this work.

I'm not asking to make the wholle script for me, I love to get my hands dirty, but I'm really puzzled right now

Share this post

Link to post

Share on other sites

punisa 0

punisa 0

Yep, tried it on a couple of monitors. It makes no difference if the monitor is connected or not? Does anyone have a clue as to what could be done about it? Or should I just discard the idea as impossible? Many thanks, don't leave me now : ))

carpe diem

Share this post

Link to post

Share on other sites

furrycow 0

furrycow 0

Yep, tried it on a couple of monitors. It makes no difference if the monitor is connected or not? Does anyone have a clue as to what could be done about it? Or should I just discard the idea as impossible? Many thanks, don't leave me now : ))

It could be gathering the monitor status on startup? Have you tried restarting your comp with a monitor disconnected? if you build the .au3 to a .exe, put it in startup, so that it automatically runs when the comp starts windows, then when you hear that the array has been displayed, plug your monitor back in and see what it says? I've no idea if that will make difference or not, but worth a go, if youve nothing else to lead with :S.

Share this post

Link to post

Share on other sites

punisa 0

punisa 0

It could be gathering the monitor status on startup? Have you tried restarting your comp with a monitor disconnected? if you build the .au3 to a .exe, put it in startup, so that it automatically runs when the comp starts windows, then when you hear that the array has been displayed, plug your monitor back in and see what it says? I've no idea if that will make difference or not, but worth a go, if youve nothing else to lead with :S.

Probabbly the data is collected at start up, not in real time. I'll perform additional checks. This could work as a partial solution, although the ideal would be a small loop that would alert as soon as monitor looses contact.