Harkonenn Posted November 16, 2007 Share Posted November 16, 2007 After initiating a scan on C:\ I get the following error immediately: ---------------------------DrWatson Fatal Error---------------------------Dr. Watson was unable to attach to the process. It is possible that process exited before Dr. Watson could attach to it.Windows returned error code = -2147024891Access is denied. Is this a bug or am I doing something wrong? ============================== Sony VAIO VGN-A190, 1.7GHz 2GB RAM 120GB HD Windows XP SP2 Link to comment Share on other sites More sharing options...
CTskifreak Posted November 17, 2007 Share Posted November 17, 2007 That comes from Norton Anti-Virus. When ever I get that, it means I didn't let Norton fully load before I did anything on Windows. If you wait for the icon to turn Green, then you can do what you want to. Try that...see if Recuva works again AJ Link to comment Share on other sites More sharing options...
Harkonenn Posted November 17, 2007 Author Share Posted November 17, 2007 Thanks for the input. However, I'm not using Norton AV. The only restrictive app that I have running is ZoneAlarm Pro. But, I've already tried shutting it down and running Recuva - this didn't work either. Link to comment Share on other sites More sharing options...
CTskifreak Posted November 17, 2007 Share Posted November 17, 2007 I assumed...a little Google and bam -- hope this helps! AJ Link to comment Share on other sites More sharing options...
Harkonenn Posted November 18, 2007 Author Share Posted November 18, 2007 Well, Dr. Watson wasn't even logging the error. Ugh. So, I disabled Dr. Watson, ran Recuva again and got this: ---------------------------recuva.exe - Application Error---------------------------The instruction at "0x00449f2a" referenced memory at "0x00e70637". The memory could not be "read". I'm not sure what to do next, but thanks. Link to comment Share on other sites More sharing options...
CTskifreak Posted November 18, 2007 Share Posted November 18, 2007 Redownload it...just to see if that does anything. AJ Link to comment Share on other sites More sharing options...
Harkonenn Posted November 19, 2007 Author Share Posted November 19, 2007 OK, I just redownloaded it, uninstalled the previous copy and reinstalled the new d/l. Unfortunately, I'm getting the same error. It's not looking good for me... Link to comment Share on other sites More sharing options...
Guest MrRon Posted November 21, 2007 Share Posted November 21, 2007 Can you run Recuva in debug mode and either post the log here or PM for an email address to send it to. http://forum.piriform.com/index.php?showtopic=11523 Thanks MrRon Link to comment Share on other sites More sharing options...
Harkonenn Posted November 21, 2007 Author Share Posted November 21, 2007 I really have to apologize for this continuing frustration. I ran Recuva in debug mode as you said, but there was no log file created! From what I read about running in debug mode, the log file is supposed to be created as soon as the app is started, and in the same dir as the exe. There are only 2 files in c:\program files\recuva - recuva.exe and uninst.exe It was indeed running in debug mode, as indicated by the [debug] after the version number. Link to comment Share on other sites More sharing options...
Guest MrRon Posted November 21, 2007 Share Posted November 21, 2007 Try putting the recuva.exe on a different drive and see if that works in debug mode. MrRon Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now