Hope someone can help... I'm trying to recover some data from a 70 gigabyte partition which a friend of mine performed an OS recovery operation on. I removed the hard drive and slaved it into my computer which I recently downloaded and installed Recuva on. I know the odds are long since much of the data may have already been overwritten by the OS recovery. But the Recuva wizard seems to find a fair amount of the missing files. I wanted to perform a deep scan and see if anything else shows up. But when I run the deep scan the process gradually drags to a crawl and eventually stops. Recuva then indicates that it is out of memory. I initially had 2 GB of RAM on a 3 GHz processor in my computer running Win XP Pro sp3. Recuva's deep scan terminated somewhere around 58% of the first stage. I upped the physical RAM to 4 GB of which Windows XP sees 3.5 GB. I also upped the virtual memory to 30 GB which is about 20% of the host system?s partition capacity. Recuva deep scan now makes it to about 80% of the first stage of the deep scan. But it still doesn't complete and still indicates that it is out of memory when it terminates prematurely. I don't know how to add any more memory to this system. Windows XP can't utilize more than 3.5 GB of physical RAM. And 30 GB of swap-memory/pagefile should be way more than enough. IDK? Maybe Recuva is simply not capable of effectively performing a deep scan on that large (70GB) of a partition. Does anyone out there have any other ideas? Would it help to run Recuva on a Win 7 host machine which could utilize quite a bit more than 3.5 GB of physical RAM? That would take some more work and expense on my part. But I?m willing to try it if it might work and if there are no simple options for making it work on my XP machine.
Something is seriously wrong if Recuva is allocating 3GB+ of RAM, to me this sounds like a memory leak.
Perhaps an older version of Recuva may perform better, apart from that try another recovery program.
Richard S.