[GPU-Z Test Build] Support for multiple instances

[W1zzard]

This build should properly support multiple instances of GPU-Z without the dreaded "Can not delete driver" message.

This change required updates to our kernel mode driver, so I need testing on all possible OSes, 32 and 64 bit

 

[Kreij]

Windows 7 Ultimate x64

Ran 6 simultaneous instances, 3 for each core on my 4870x2.
No problems.

 

[Athlon2K15]

No Issues

 

[Kreij]

Launched two instances.
Second instance was started immediately after 1st, while the 1st instance's splash screen was still showing.
System locked up and required power-off reboot.

Currently not repeatable.

 

[W1zzard]

Launched two instances.
Second instance was started immediately after 1st, while the 1st instance's splash screen was still showing.
System locked up and required power-off reboot.

Currently not repeatable.

that's very possible and should have happened with previous versions too

 

[cadaveca]

that's very possible and should have happened with previous versions too

Yeah, I get this all the time if I open them to quickly one after the other....something to do with both accessing the same sensors or something, eh?

Because sometimes one instance will open with no data at all, if it doesn't freeze the system.

cpu-z also does this, since adding the "gpu tab".

 

[W1zzard]

Yeah, I get this all the time if I open them to quickly one after the other....something to do with both accessing the same sensors or something, eh?

Because sometimes one instance will open with no data at all, if it doesn't freeze the system.

cpu-z also does this, since adding the "gpu tab".

maybe i could put some kind of high-level "initialization lock" in the gpuz init process, where only one instance can own the lock at the same time

 

[wolf]

two isntances working flawlessly and detecting both intel onboard gfx and the mobility 5600

OS Win 7 64-bit Home Premium.

would you like testing of even more instances?

 

[cadaveca]

maybe i could put some kind of high-level "initialization lock" in the gpuz init process, where only one instance can own the lock at the same time

Yeah, that'd do it. Just wonder what happens if say, 15 instances at once are opened or something. Some "mad-clicker" is gonna cause an issue..

I guess what I mean is, what happens for successive instances...3rd instance should wait for 1st and 2nd...4th for all three...etc..

 

[W1zzard]

Yeah, that'd do it. Just wonder what happens if say, 15 instances at once are opened or something. Some "mad-clicker" is gonna cause an issue..

I guess what I mean is, what happens for successive instances...3rd instance should wait for 1st and 2nd...4th for all three...etc..

yes only one instance can own the initialization lock at one time

 

[ERazer]

window home server 32bit no issue

7 home premium 64bit no issue

7 enterprise 64 bit no issue

 

[Kreij]

yes only one instance can own the initialization lock at one time

I think that having instances wait in some kind of queue would be problematic.

It would be easier to check for the initialization lock and have any other starting instances terminate (with a user message to wait to start GPU-Z) if they are locked out.

 

[scaminatrix]

XP Pro x86 works fine, 4 instances