Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Sylvia Else <sylvia@not.at.this.address> |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: Aggh! Bloody Windows |
| Date | 2015-04-19 16:06 +1000 |
| Message-ID | <cpguviFisv5U1@mid.individual.net> (permalink) |
| References | <cpek93F12qmU1@mid.individual.net> <4fj5jadkhv1h9ec7itpht0dl92lk8em5ih@hive.bjoern.hoehrmann.de> |
On 19/04/2015 7:36 AM, Bjoern Hoehrmann wrote: > * Sylvia Else wrote in comp.misc: >> "The system cannot find the file specified." > > Sysinternals `filemon` or more recently the "Process Explorer" available > via Microsoft Technet allow you to log file operations and filter for a > failure to open a file, telling you which file was being looked for. Of > course, that does not improve the user experience, but helps to debug. > I did try that, but without success. The problem with it is the huge amount of raw data, coupled with an uncertainty about which piece of the system is actually encountering the error and what operation it was trying to perform on the file. Now that I know the offending file path, I could probably go back and figure out what filtering would have yielded the information, but at the moment I'm not sure what that would achieve. Sylvia.
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Aggh! Bloody Windows Sylvia Else <sylvia@not.at.this.address> - 2015-04-18 18:51 +1000
Re: Aggh! Bloody Windows Bob Eager <news0005@eager.cx> - 2015-04-18 09:13 +0000
Re: Aggh! Bloody Windows Sylvia Else <sylvia@not.at.this.address> - 2015-04-18 20:14 +1000
Re: Aggh! Bloody Windows Andy Burns <usenet.feb2014@adslpipe.co.uk> - 2015-04-18 11:22 +0100
Re: Aggh! Bloody Windows Bjoern Hoehrmann <bjoern@hoehrmann.de> - 2015-04-18 23:36 +0200
Re: Aggh! Bloody Windows Sylvia Else <sylvia@not.at.this.address> - 2015-04-19 16:06 +1000
Re: Aggh! Bloody Windows Shadow <Sh@dow.br> - 2015-04-19 10:12 -0300
csiph-web