Open GoogleCodeExporter opened 8 years ago
Forgot to mention that arch is x86_64
Original comment by olivier....@gmail.com
on 20 Aug 2011 at 8:31
Tested wiiBackupFusion 1.1 i386 on the same platform, same files, and it works.
Original comment by olivier....@gmail.com
on 29 Aug 2011 at 7:13
Hm strange :/
It's possible the libwbfs used is too old :/
I may try to find update of this crappy lib :)
Does all of your files are failing ?
Which software formatted your drive ?
Thank you.
Original comment by pasnox
on 31 Aug 2011 at 8:03
All my .wbfs files fail at 95%
My disk was formatted using wbfs command line a long time ago.
I used a separate qt extentiongui lib as I was unable to build qwbfsmanager
with the provided lib.
I'm using latest qt with latest gcc in x86_64 mode
Successful tests using wiibackupfusion were made using the i386 downloaded
binary
The qwbfsmanager-1.1 x86_64 I've built works perfectly with iso transfert to my
wbfs disk.
Original comment by olivier....@gmail.com
on 31 Aug 2011 at 11:59
Please answer these questions:
qwbfsmanager 1.1
iso -> wbfs partition is working fine ?
wbfs partition -> wbfs parttion is working fine ?
qwbfsmanager 1.2
iso file -> wbfs partition is working fine ?
wbfs partition -> wbfs partition is working fine ?
wbfs file -> wbfs partition is working fine ?
Thanks
Original comment by pasnox
on 31 Aug 2011 at 1:09
Please report architecture used too.
Original comment by pasnox
on 31 Aug 2011 at 1:10
Iso to wbfs works fine in both versions
Wbfs disk to wbfs disk works fine in both versions
Wbfs file to wbfs disk fails in V1.2.1 x86_64
Original comment by olivier....@gmail.com
on 31 Aug 2011 at 3:53
All my WBFS files fail to import in the same way. I can't convert them to iso,
as then the isos fail as well. I can't do any wbfs work in linux. I have to
switch into windows and use WBFS manager to get WBFS files onto my drive. It's
the only thing that I discovered that works.
Original comment by barcenas...@gmail.com
on 17 Oct 2011 at 2:55
ISOs have no problems though. Just anything having to do with wbfs. after a
fail I have to keep repairing my drive with WWT from WIMMS ISO TOOLS. As
everytime you try to import it, and fails, it leaves empty blocks assigned. i
don't want to corrupt my disk.
Original comment by barcenas...@gmail.com
on 17 Oct 2011 at 2:59
Sorry, I meant to say WBFS BACKUP MANAGER in my first comment. That was wwhat
worked for me to transfer WBFS files to the disk. I did not try WBFS MANAGER,
so I guess it could work for this purpose as well; but I don't think is support
wbfs file to disk.
Original comment by barcenas...@gmail.com
on 17 Oct 2011 at 3:04
It should be interesting to know which software formatted your hard drive ?
It could be nice to test using a usb key formated with QWBFS Manager and see if
the problem still appear?
Once you will say me which software formatted the partition i will try to
format a partitin using it and do some testing.
Thanks for the feedback !
Original comment by pasnox
on 17 Oct 2011 at 5:46
I used qwbfs manager. 1.2.1 even though it says 1.2.0
frank
Original comment by barcenas...@gmail.com
on 17 Oct 2011 at 6:19
Yeah know bug, anyway there is no real differences between them. it was just a
project file fix for mac os x.
Original comment by pasnox
on 17 Oct 2011 at 6:26
QWBFS has option to convert wbfs files to iso.
Could u try it and then try to import the iso ?
Does it's better ?
By the way as stated in the readme file, QWBFS Manager use some temporary
files, the size depend of the file it read, so assume 5GB left on the drive
where is located the system temp folder.
Original comment by pasnox
on 17 Oct 2011 at 8:22
No same problem when you try to import the ISO.
frank
Original comment by barcenas...@gmail.com
on 17 Oct 2011 at 8:48
Basically anything that comes from wbfs won't work. Even if you convert it to
an iso, unless you convert it to an ISO in windows with WBFS backup manager.
That did not give me an error. So basically you can't do anything in linux with
wbfs until the libs get updated.
Original comment by barcenas...@gmail.com
on 17 Oct 2011 at 10:25
Original issue reported on code.google.com by
olivier....@gmail.com
on 20 Aug 2011 at 8:31Attachments: