Wode Jukebox

My understanding is that you can speed up writing by making it more risky that it will corrupt the drive in certain unknown instances. If you make assumptions about the type and structure of ntfs you are writing to (there have been many revisions over the years) you may be able to speed up writing by ignoring some checking and verifications. I would NEVER allow a non windows system to write to a NTFS formatted drive that wasn't backed up elsewhere. Here is a Wiki link that shows some of the many features that could be implemented on a NTFS drive. http://en.wikipedia.org/wiki/NTFS

Thanks for the link. And yes, I ALWAYS have backups

Ok, that's a fair assumption, but a write transfer rate of below 10 Mbit still seems extremely slow even for a non-optimized procedure.

There's probably room for improvements, but it's not that important. Do people in general experince much problems with wode & fat32? (compared to ntfs etc)

Fat32 has been faultless here since it first made it to usb loaders and works just as well with wode and backup managers I see no reason to use anything else.

No issues here when I use either FAT32 or NTFS with the WODE... but when I rip, it's always as ISO to a 16G USB key formatted as FAT32... then I rebuild the ISO using command line COPY /B to make back into full-fat ISO and then WiiBackupManager to transfer it back to the NTFS drive attached to the WODE (intentionally using the NTFS R/O firmware)... long winded but "rip once & keep backups" is my philosophy.

Ok, so you rip to a "split iso" using wode and a usb stick, but why use WBM to just copy the non-segmented iso to the ntfs drive? Am I missing something here?

Would it be useful to be able to copy from a fat32 drive to an ntfs drive using just the wode and the two drives?


Running wode (2.5A) on a brand new black wii (crappy crippled drive) + Toshiba 1.5GB, and ripping works like a charm (both wii & GC), albeit a bit slow due to ntfs...

I do it that way because to achieve what I want to achieve, it's the quickest method... my deliverables at the end: WBFS on the drive attached to the Wii & ISO on the backup drive...

So the step-by-step is this:

Rip ISO to FAT32 USB stick (20-25')
Join the segmented ISO onto the backup drive (5' ish)
Use WBM to transfer it to the drive on the WODE (3' ish)
Put the backup drive back where it lives
Put the Wii disc in the shelf with the others
Wipe the USB key

@hunnymonster: That all makes perfect sense. Overall it is quicker to complete it the way you have mentioned than to rip straight to NTFS via WODE, then copy to a backup HDD.

Early on I would do pretty much the same thing just for the time saving factor. Not as convenient but saves time... Now, it is MUCH quicker to simply use CleanRip via the HBC. As I have HBC 1.0.8 installed on IOS58 I can rip FULL ISO to NTFS in about 13min - 14min. It needs no other install other than the HBC so no worse / more risky than using WodeFlow.

So my steps are now:

1. RIP Game to NTFS Backup Drive (13min to 14min)
2. Use Wii Backup Manager to convert to WBFS straight to WODE HDD (5min - 10min)

Overall, about 25min tops. Quicker than you can rip a full ISO to FAT32 via WODE ripping feature.

CleanRip: viewtopic.php?f=13&t=2907

Ah well... that all comes down to the reason for the WODE vs softmodding... there's a helpful chap in the house that's still in primary school... if a dialogue box appears he clicks "OK" or "yes" before reading it... so to keep my life simple, no softmodding here at all

I can fully appreciate that.

Only soft mod I have is the HBC and in terms of Soft Modding that is the easiest and safest as far as I am concerned. I will not go beyond that...

Well, I did install a Wode Flow Channel via the HBC. Nothing more needed than HBC. I did that so my 7 year old only had to click the Channel and START - just like a Wii channel but she can select the games herself