[beta] Party Buffalo Drive Explorer Options

[CLK Rebellion]

[This is a copy/paste from another board, so please excuse me if something doesn't make sense or out of context]

This app is pretty self explanatory -- created by me from ground-up, and has been in development for a while now. To use, connect your drive (if using a drive), press File>Open>Open Drive Selector>Select your drive. If you're not using a drive, load your file by going to File>Open>Open Dump.

Features so far...

• Backing up of drive
• Extracting files
• Reading files
• Reading backups/files that are a single FATX partition (such as the xlaunch.fdf file found in devkats)
• USB support added 1/13/2010

Future updates...

• Adding support for memory units
• Backing up security sector, josh sector -- Done.
• Writing to individual sectors/clusters
• Reading fromm individual sectors/clusters
• STFS implimentation (so you can see the game name/file name of an STFS package) -- Done.
• Maybe undeletion... -- Done.
• Anything else that people would want
• Package creation

One known issue I want to address is when extracting multiple files from a hard disk, it will throw an error about the handle not supporting asynchronous operations, etc. -- working on that.

Instead of keeping this closed-source, and having licensing and all that junk, I've decided I'll just make it open-source. I figured it would be too annoying for Cheater912 for me to ask him every time I need to update for him to obfuscate the executable, and then to have to create a licensing system would be annoying as hell.

Quick note if you peek at the source code...
The code in just about every single one of the forms is really messy. Please excuse that. Also, if you use the dev build, you're doing so at your own risk... I wrote a lot of the code in the writing quickly, and have barely tested any of it. So if you're using a hard drive, or anything else you don't want to get messed up on accident, please use enable beta mode by changing the bool at line 16 of the main form to true.

Screenshots:





Source:
http://clkxu5.com/drivexplore/src/fatx.zip

EXE (will auto-update):
http://clkxu5.com/drivexplore/Party%20Buff...%20Explorer.exe

If you want to donate, do so hurr (I'm not trying to be one of those guys who's like you donate or else I'll stop developing, I'm just sayin, it'd be cool if you did): https://www.paypal.com/cgi-bin/webscr?cmd=_...gif%3aNonHosted

This post has been edited by CLK Rebellion: Jan 14 2011, 01:33 AM

[hyperfire21]

just tried that but it wont detect on the xbox 360 as a memory unit.

also tried usb image tool and that didnt work also.

is there some security sector or something that didnt copy over?

This post has been edited by hyperfire21: Nov 17 2010, 06:21 AM

[EatonZ]

just tried that but it wont detect on the xbox 360 as a memory unit.

also tried usb image tool and that didnt work also.

is there some security sector or something that didnt copy over?

When you attempt to format the USB, what is the exact message you get on the dash?

[hyperfire21]

When you attempt to format the USB, what is the exact message you get on the dash?

I get something like Failed Data Loss Test.

One more thing I wanted to add is that i've formatted these drives through various software. I tried to set the 16gb drive to 7gb xbox storage through the dash and one time I was able to make it work. Not after that one time though...

[EatonZ]

I get something like Failed Data Loss Test.

One more thing I wanted to add is that i've formatted these drives through various software. I tried to set the 16gb drive to 7gb xbox storage through the dash and one time I was able to make it work. Not after that one time though...

I am pretty sure the device ID is the issue. I will have to verify how it is calculated and maybe I can get it to work.

[EatonZ]

I am pretty sure the device ID is the issue. I will have to verify how it is calculated and maybe I can get it to work.

Confirmed. The Device ID value in the data files is what locks it to the USB itself. Modifying it to match the ID of the new USB will make it work. Unfortunately, it seems to be calculated differently than hard-drives. Once I figure it out, formatting will be a possibility.

[hyperfire21]

Confirmed. The Device ID value in the data files is what locks it to the USB itself. Modifying it to match the ID of the new USB will make it work. Unfortunately, it seems to be calculated differently than hard-drives. Once I figure it out, formatting will be a possibility.

This is definately great news. What app will modify device ID of the flash drive properly?

[EatonZ]

This is definately great news. What app will modify device ID of the flash drive properly?

You can't modify it, it is in the firmware which is not writable by normal means.
Only option is to find it, but I am still unable to find out how it is generated for USBs.

However, through an IO function on the console, there is a way to get the ID. Expect a PM from me soon, we'll try getting one of them to work.