Jump to content

Crash at 99%


livret_a

Recommended Posts

Yeah I have the same bug. Maybe it's because of the overload of files recovered because mine was actually ALOT. In my C: drive that is. Please do fix this bug guys! :(

 

AppName: recuva.exe AppVer: 1.3.0.100 ModName: recuva.exe

ModVer: 1.3.0.100 Offset: 0004673a

 

Current Progress: 99%, 169488 files found

Link to comment
Share on other sites

Can you make sure you're using the latest version (1.03.100) and if you still have the same problem, post the error log here.

Thanks

MrRon

:)

 

That was a fast reply. And yes, latest version :)

 

It's supposed to be 1.03.100 coz I just got it from filehippo.com

 

To be honest, this bug has been around from the first beta that has ever been released. Only at that time I was too lazy to report a bug. Refer to my modified post above for the error log.

Link to comment
Share on other sites

Can you post the error log from Recuva (recuva.exe /debug)

:)

 

[2007-08-08 17:18:44] [ERROR] Exception: DriveNamesEnumerator.cpp(46) : The device is not ready.

 

[2007-08-08 17:18:44] [ERROR] Exception: DriveNamesEnumerator.cpp(46) : The device is not ready.

 

[2007-08-08 17:18:44] [ERROR] Exception: DriveNamesEnumerator.cpp(46) : The device is not ready.

 

[2007-08-08 17:18:44] [ERROR] Exception: DriveNamesEnumerator.cpp(46) : The device is not ready.

 

Additional Stuff:

 

<?xml version="1.0" encoding="UTF-16"?>

<DATABASE>

<EXE NAME="recuva.exe" FILTER="GRABMI_FILTER_PRIVACY">

<MATCHING_FILE NAME="recuva.exe" SIZE="505472" CHECKSUM="0xE9C47AF4" BIN_FILE_VERSION="1.3.0.100" BIN_PRODUCT_VERSION="1.3.0.100" PRODUCT_VERSION="1, 3, 0, 100" FILE_DESCRIPTION="Recuva" COMPANY_NAME="Piriform Ltd" PRODUCT_NAME="Recuva" FILE_VERSION="1, 3, 0, 100" ORIGINAL_FILENAME="recuva.exe" INTERNAL_NAME="Recuva" LEGAL_COPYRIGHT="Copyright 2006-2007 Piriform Ltd" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x7FE5F" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.3.0.100" UPTO_BIN_PRODUCT_VERSION="1.3.0.100" LINK_DATE="08/02/2007 11:36:29" UPTO_LINK_DATE="08/02/2007 11:36:29" VER_LANGUAGE="English (United States) [0x409]" />

<MATCHING_FILE NAME="uninst.exe" SIZE="69062" CHECKSUM="0x1CEA7103" BIN_FILE_VERSION="1.3.0.100" BIN_PRODUCT_VERSION="1.3.0.100" FILE_DESCRIPTION="Recuva Installer" COMPANY_NAME="Piriform Ltd" PRODUCT_NAME="Recuva" FILE_VERSION="1.03" LEGAL_COPYRIGHT="?2006-2007 Piriform Ltd" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x5B3F6" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.3.0.100" UPTO_BIN_PRODUCT_VERSION="1.3.0.100" LINK_DATE="07/14/2007 15:12:49" UPTO_LINK_DATE="07/14/2007 15:12:49" VER_LANGUAGE="Language Neutral [0x0]" />

</EXE>

<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">

<MATCHING_FILE NAME="kernel32.dll" SIZE="984576" CHECKSUM="0xF0B331F6" BIN_FILE_VERSION="5.1.2600.3119" BIN_PRODUCT_VERSION="5.1.2600.3119" PRODUCT_VERSION="5.1.2600.3119" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft? Windows? Operating System" FILE_VERSION="5.1.2600.3119 (xpsp_sp2_gdr.070416-1301)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="? Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF9293" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.3119" UPTO_BIN_PRODUCT_VERSION="5.1.2600.3119" LINK_DATE="04/16/2007 15:52:53" UPTO_LINK_DATE="04/16/2007 15:52:53" VER_LANGUAGE="English (United States) [0x409]" />

</EXE>

</DATABASE>

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.