Installation Error !
"An I/O Operation has been aborted because of either a thread exit or an application request."
This error comes when I launch my package . Any idea ? related to package ?
This error comes when I launch my package . Any idea ? related to package ?
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
slb
16 years ago
Posted by:
anonymous_9363
16 years ago
try running Filemon and regmon toolsFolks, PLEASE, abandon FileMon and RegMon. ProcMon (from the same author) combines the two, adds spade-loads of functionality, not the least of which is the removal of the limit on the number of processes can be excluded.
Posted by:
AngelD
16 years ago
File and Regmon can still be vital as ProcMon requires SP4 on Win2000 and SP2 on XP.
Yes, there still exists environment with these versions due to old unsupported systems/applications.
Yes, there still exists environment with these versions due to old unsupported systems/applications.
Posted by:
anonymous_9363
16 years ago
ORIGINAL: AngelDReally? http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx says it "runs on" those OSs, not that it "requires" them. I'd expect SysInternals to be pretty hot on saying so if that were the case. The older versions are all still available in the usual 'net archives.
File and Regmon can still be vital as ProcMon requires SP4 on Win2000 and SP2 on XP.
there still exists environment with these versions due to old unsupported systems/applications.No offence, Kim, but only a fool would package and test on such a machine. Sure, keep a VM for regression testing but for day-to-day use...?
Posted by:
AngelD
16 years ago
Process Monitor uses minifilter driver thus requirement of the filter manager so there exist a OS version requirement. If I recall Mark also points that out in one of his video seesions.
I'm some time required to package on a windows 2000 client due to "customer policy" but I was more referring to analyze/troubleshoot with the tools rather then packaging on the oldies.
Cheers!
I'm some time required to package on a windows 2000 client due to "customer policy" but I was more referring to analyze/troubleshoot with the tools rather then packaging on the oldies.
Cheers!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
