Leaderboard

I've been affected by this irritating issue for a very long time (years). I suspect it was due to Logitech mouse or Gxx keyboard driver or add-on but in all case it has little to do with AutoIt as at least one other application (not build with AutoIt) had a similar issue. Chase drivers until you find the culprit is the best advice I can give you.

No problem - the code is good :-) Thanks Dizzy

FileDelete will return 0. I would search the term 'shared file in use' on google or such-like.

_Net_Share_FileEnum() may come in handy. edit: in conjunction with _Net_Share_FileGetInfo(), if you need specific details.

DllOpen just retrieves a handle to a Dll, in the same way that FileOpen can get a handle to a file. It's really only useful if you're going to call a specific .dll file multiple times. Are you maybe wondering about the parameters used with DllCall?

See help file: AutoItSetOption Opt("CaretCoordMode", 1) ;1=absolute, 0=relative, 2=client

  I'm rejigging the resource code so that it does all its updating in one go so it should be pretty much instant.

Just messing around with it, this is what it looks like might be on the right track.. You need pointers to the functions, and the array has to be a DLLStruct.. I was lazy and didnt' declare most variables though. And I can't test it.. Dim $DLL = DllOpen('nvapi.dll') $N = NvAPI_Initialize() ConsoleWrite("Return = " & $N & ", @error = " & @error & ", @extended = " & @extended & @CRLF) $R = NvAPI_EnumPhysicalGPUs() _ArrayDisplay($R) For $i = 0 To 100 NvAPI_GPU_GetUsages($R[0]) Sleep(1000) Next DllClose($DLL) Func NvAPI_QueryInterface($nInterface) $result = DllCall($DLL, "ptr:cdecl", 'nvapi_QueryInterface', 'int', $nInterface) If @error Then Return SetError(2,@error,0) If $result[0] = 0 Then Return SetError(3,0,0) Return $result[0] EndFunc Func NvAPI_Initialize() Static Local $pInitialize = 0 If $pInitialize = 0 Then $pInitialize = NvAPI_QueryInterface(0x0150E828) If $pInitialize = 0 Then Return SetError(@error,@extended,0) EndIf $result = DllCallAddress("int:cdecl", $pInitialize) If @error Then Return SetError(2,@error,False) Return $result[0] EndFunc Func NvAPI_EnumPhysicalGPUs() Static Local $pEnumPhysGPUs = 0 If $pEnumPhysGPUs = 0 Then $pEnumPhysGPUs = NvAPI_QueryInterface(0xE5AC921F) If $pEnumPhysGPUs = 0 Then Return SetError(@error, @extended, 0) EndIf $stGPUHandles = DllStructCreate("ptr gpuHandles[64];") $result = DllCallAddress("int:cdecl", $pEnumPhysGPUs, 'ptr', DllStructGetPtr($stGPUHandles), 'int*', 0) If @error Then Return SetError(2,@error,0) If $result[0] Then Return SetError(3,0,0) $nGPUCount = $result[2] Dim $result[$nGPUCount] For $i = 1 To $nGPUCount $result[$i - 1] = DllStructGetData($stGPUHandles, 1, $i) Next Return $result EndFunc Func NvAPI_GPU_GetUsages($vGPUHandle) Static Local $pGetUsages = 0 If $pGetUsages = 0 Then $pGetUsages = NvAPI_QueryInterface(0x189A1FDF) If $pGetUsages = 0 Then Return SetError(@error, @extended, 0) EndIf $stGPUUsages = DllStructCreate("uint gpuUsages[34];") DLLStructSetData($stGPUUsages, 1, BitOR(34 * 4, 0x10000), 1) $result = DllCallAddress("int:cdecl", $pGetUsages, 'ptr', $vGPUHandle, 'ptr', DllStructGetPtr($stGPUUsages)) If @error Then Return SetError(2,@error,0) If $result[0] Then Return SetError(3, 0, 0) Return DllStructGetData($stGPUUsages, 1, 4) ; 4 is equivalent to c's array[3] EndFunc *edit: Fixed parameters and parameter return check (non-zero is error).. AND indexing. Still not sure its entirely kosher though

Above shit is a good foundation for what you're trying to accomplish and I think that thread can expand our knowledge further about how to handle process and window with AutoIT. Or you might want to hire a freelancer

Unfortunately for you when a Mod asks you questions on this forum, you had best answer - you saw what happens when you do not. And then abusing the Mod in question via PM because you could not be bothered to answer the questions he asked and so got your thread locked is not the way to a happy life here. Take 3 days to think about how you might behave when and if you return. Continue as you are and we might well decide we can do without you. M23

Sharz, Sending PMs to an MVP asking for help with a thread that has been locked is not the way to have a happy stay here. Spend the next week reading those Forum rules and thinking about how to respect them in future. And in French so there is no problem understanding: Et en francais pour qu'il n'y ait aucun probleme de comprehension: L'envoi d'un PM demandant de l'aide avec un sujet qui a été verouillé n'est pas la bonne voie. Passe la semaine prochaine a relire ces regles et a penser comment les respecter dorenavant. M23