Try Recuva or Yodot recovery.
......?????
[Wii] Xenoblade [NTSC-J]
|
Indeed. You've barely scratched the surface of the game, so go ahead and restart.
Your savefile was gone a long time ago. From the moment you delete it, it's actually still on your harddrive (that's why you can use recover software), but it's now marked as "rewritable". So anytime you write to the harddrive by downloading/unrarring something the file that you deleted will be overwritten by whatever you wrote to the harddrive. A word of advice. If something like this happens again, and you want to recover the file, turn off the computer immediately. Get a live CD/DVD/USB with a Linux distro and boot up with that. Use free recovery software that are available for Linux to hopefully recover your file(s). 10-23-2012, 08:35 AM
Kay. Thx. It's just funny how files from april this year are "in excellent condition" while the one i need from 2 days back is gone:D
10-24-2012, 12:01 PM
(08-24-2011, 02:12 AM)ebenholzjunge Wrote: sorry for my bad english. can not read English. must use google translate Hi Im having the exact same problem that you are having. Did anyone get back to you with a solution Thanks! 10-25-2012, 04:57 AM
(10-24-2012, 03:20 PM)DefenderX Wrote: What about redumping your game? Tried redumping but no luck. Thanks though. Im running it on an imac and the game was running fine with osx. I started using bootcamp to see if it would run a bit better in windows but now the same game file and dolphin version give me the operand 1 problem while in the wii start up screen. Oh well, i guess thats what happens when you try to game on a mac. Thanks 10-25-2012, 05:43 AM
That is not what happens when you try to game on a Mac. Something else is wrong. Idk what, but it definitely isn't a Mac issue.
Desktop:
OS: Windows 7 64 bit CPU: Intel Core i5 3570K @ 4.4 GHz GPU: EVGA NVIDIA GeForce GTX 550 Ti (Factory OC'ed) RAM: 16 GB @ 1600 MHz Dolphin Revision:3.0, 3.0-784, 3.5, latest 3.5 10-25-2012, 06:12 AM
This error code?
I remember, that "Lock Threads to Cores" can do something against this. 10-25-2012, 06:35 AM
Thanks but locking threads to cores didnt do it either. It seems so weird that its running in osx but not in windows.
|
« Next Oldest | Next Newest »
|