Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Keywords: appexist NT
If it cannot access the registry key it will fail.
Also if the key is locked by some other application it can fail.
The problem is that the HKEY_DYN_DATA section of the registry is quite tricky to access and most simpler performance monitors do not access it quite properly and lock other users out. If they lock us out, we can't see it, and AppExist fails.
He's using WB2000b.
The AppExist is testing the existence of an app on a mapped drive to a server. This same command returned immediately in 95. Why would it be taking so long on NT4?
The app does NOT exist, so the next line in his script is to Run the app.
Any ideas as to why NT would behave differently than 95?
There may be other ways to tell is the App exists or not. WinExist is probably one of the first contenders. I'm not sure if the new (NT Only) process extender might also be able to determine what is going on.
Here is a sample NT only script that uses our new "Process Extender"
It may be able to do the AppExist faster. Not sure, since AppExist works fast on all out machines here. Its worth a try.
AddExtender("wwprc44I.dll") filename=StrUpper("WinBatch Studio.exe") count=tCountProc() proclist=tlistproc() For x = 1 to count item=ItemExtract(x,proclist,@Tab) procname=ItemExtract(1,item,"|") if StrUpper(procname)==filename ; parse off process id procid=ItemExtract(2,item,"|") message("%Procname% exists","Process Id is %procid%") endif Next
Article ID: W13038
Filename: AppExist Not Working.txt
File Created: 2013:04:01:09:16:02
Last Updated: 2013:04:01:09:16:02