• Welcome to the Digiex Download Center, you are welcome to download anything you like here. No registration is required! Digiex offers direct download links with no captchas or wait times.
    The team do our best to ensure no content infringes copyrights and provide a DMCA Takedown request form to request the removal of content from Digiex.

    Notable sections: Pokemon Archives | Xbox Archives | Xbox 360 Archives

Party Buffalo Drive Explorer 2.0.1.0 Download Xbox 360 FATX Hard Drive & USB Explorer

InsaneNutter

InsaneNutter

Resident Nutter
Joined
Jun 1, 2007
Messages
11,864
Location
UK
Party Buffalo Drive Explorer 2.0.1.0 (Latest version) Download

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
  • Backing up security sector
  • STFS implimentation (so you can see the game name/file name of an STFS package
  • Undelition
partybuffalo1.jpg

Future updates...

  • Adding support for memory units
  • Writing to individual sectors/clusters
  • Reading form individual sectors/clusters
  • Anything else that people would want
  • Package creation

Authors Blog

Downloads:

Download Party Buffalo Drive Explorer 2.0.1.0

Download Party Buffalo Drive Explorer 2.0.1.0 Source Code
 

Attachments

Finally a proper drive explorer for 360 hdds. :)

Been using it for a while, found it when desperately searching for a XPort and Xplorer alternative.

But after poking around, I'm just missing a small feature: How can I check the size of individual folders? Can't even do it through ftp apparently...

Thanks for this awesome tool!
 
Haha, been using it since the 1st version appeared. It has improved since then. One excellent program for USB/HDD exploration.

But it seems CLK left the project. I haven't seen any updates since the 2.0.0.9 version. Still, it works great for its purpose, :)
 
Good stuff, I was unable to back up my Xbox 360's data to my computer using Xplorer 360 because I was getting a "Failed to read cluster chain map!" With Party Buffalo, it worked just fine...
 
I wish this worked for me but it just locks up when trying to open my drive (250GB Hitachi). Xplorer360 and USBXTAFGUI are able to open it OK but they can't seem to extract the files properly (I can sometimes manage to get it to work on individual files, but if I select a few folders to extract, it just locks up and they're both exceedingly slow).
 
doveman said:
I wish this worked for me but it just locks up when trying to open my drive (250GB Hitachi). Xplorer360 and USBXTAFGUI are able to open it OK but they can't seem to extract the files properly (I can sometimes manage to get it to work on individual files, but if I select a few folders to extract, it just locks up and they're both exceedingly slow).
Click to expand...
First safely remove the drive. Reconnect it to the computer and use xplorer 250 edition you can download that here.
The program locking up or freezing is normal.
 
Rick said:
First safely remove the drive. Reconnect it to the computer and use xplorer 250 edition you can download that.
The program locking up or freezing is normal.
Click to expand...

Thanks, I actually already had that and as I say, had problems extracting folders from the HDD with it. What I've done now is make an image of the HDD and open that and extract the files, which seems to be working better. It's a bit of a pain that it extracts the files to the temp folder first and then moves them to the selected location afterwards though.
 
I dunno why this is happening I tried Compatibility mode but

I have two drives hooked up via SATA channels 5, 6 in IDE Mode
Both formatted using hddhackr one is

BPVT - 320GB
LPVX - 320GB

I know the LPVX is not marked as supported But i did a job with this same drive a few months ago in windows 8.1 I made this post https://digiex.net/help-center/cons...-360-320gb-issue-windows-8-x64.html#post71976
The only thing that has changed is that I'm running Tech Preview Windows 10 but like I said its compatibility mode and so far everything is working even avast is up and working in 10 I guess 10 COULD be the issue? but I don't see how ANYWAYS the issue I'm getting is when trying to select either hard drives results in this error then if i click continue when i try to do anything to the drive even browse the one with files to copy it just crashes.
0BbzKbP.png

Code: 
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.


************** Exception Text **************
System.ArgumentException: Handle does not support synchronous operations. The parameters to the FileStream constructor may need to be changed to indicate that the handle was opened asynchronously (that is, it was opened explicitly for overlapped I/O).
at System.IO.FileStream.ReadCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)
at System.IO.BinaryReader.ReadBytes(Int32 count)
at CLKsFATXLib.Streams.Reader.ReadBytes(Int32 count)
at CLKsFATXLib.Streams.Reader.ReadUInt32()
at CLKsFATXLib.PartitionFunctions.FATSize()
at CLKsFATXLib.PartitionFunctions.DataOffset()
at CLKsFATXLib.Drive.get_Partitions()
at Party_Buffalo.Main.LoadDrive()
at System.Windows.Forms.MenuItem.OnClick(EventArgs e)
at System.Windows.Forms.Command.Invoke()
at System.Windows.Forms.Control.WmCommand(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)




************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
Party Buffalo
Assembly Version: 2.0.1.0
Win32 Version: 2.0.1.0
CodeBase: file:///C:/Users/Uh/Desktop/Party%20Buffalo.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8648 built by: QFE
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------


************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.


For example:


<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>


When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
Last edited:
hello i have tha same problem. someone can help me pleas?


s32ialx said:
I dunno why this is happening I tried Compatibility mode but

I have two drives hooked up via SATA channels 5, 6 in IDE Mode
Both formatted using hddhackr one is

BPVT - 320GB
LPVX - 320GB

I know the LPVX is not marked as supported But i did a job with this same drive a few months ago in windows 8.1 I made this post https://digiex.net/help-center/cons...-360-320gb-issue-windows-8-x64.html#post71976
The only thing that has changed is that I'm running Tech Preview Windows 10 but like I said its compatibility mode and so far everything is working even avast is up and working in 10 I guess 10 COULD be the issue? but I don't see how ANYWAYS the issue I'm getting is when trying to select either hard drives results in this error then if i click continue when i try to do anything to the drive even browse the one with files to copy it just crashes.
View attachment 14281

Code: 
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.


************** Exception Text **************
System.ArgumentException: Handle does not support synchronous operations. The parameters to the FileStream constructor may need to be changed to indicate that the handle was opened asynchronously (that is, it was opened explicitly for overlapped I/O).
at System.IO.FileStream.ReadCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)
at System.IO.BinaryReader.ReadBytes(Int32 count)
at CLKsFATXLib.Streams.Reader.ReadBytes(Int32 count)
at CLKsFATXLib.Streams.Reader.ReadUInt32()
at CLKsFATXLib.PartitionFunctions.FATSize()
at CLKsFATXLib.PartitionFunctions.DataOffset()
at CLKsFATXLib.Drive.get_Partitions()
at Party_Buffalo.Main.LoadDrive()
at System.Windows.Forms.MenuItem.OnClick(EventArgs e)
at System.Windows.Forms.Command.Invoke()
at System.Windows.Forms.Control.WmCommand(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)




************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
Party Buffalo
Assembly Version: 2.0.1.0
Win32 Version: 2.0.1.0
CodeBase: file:///C:/Users/Uh/Desktop/Party%20Buffalo.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8648 built by: QFE
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8645 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------


************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.


For example:


<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>


When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Click to expand...
 
Xbox 360 FATX Drive Explorers will not recognise my new 2TB 360 usb drive on a PC.

Hi all,

I'm not sure if I'm in the right place to ask this question on this thread but none of the Xbox 360 FATX Hard Drive & USB Explorers will recognise, mount or see my new 2TB 360 usb drive. I've tried using Xtaf, Party Buffalo and Horizon 2 but none of them see the drive.

I've got an original Hitachi 360 drive, a couple of HDDHACKED WD drives and a few USB flash drives that mount just fine on the PC.

I initially connected the 2TB Seagate Barracuda drive to the 360 via a SATA to USB caddy, which the 360 recognised just fine. I formatted it on the 360 using this caddy, copied data to it fine and I was happy until I connected it to the PC.
However, When I formatted the drive on the 360, it didn't give me the option of allocating the amount of space I wanted to use. I only gave me the format option and it used the full capacity of the drive.

When on the PC, the drive is there and mounted because I can see it there in Device Manager but, like I said, none of the FATX Explorers will see it even though they can see all the other FATX drives when connected to the PC.

Q1: Will it make a difference if I use the same caddy but connect it to the PC via SATA to eSATA?
I will try that tonight and see but I fail to see why that would make a difference.

Q2: Is it because the 360 may have an issue with Seagate drives?
Even though I've read a lot of articles indicating this to be true, I tend to doubt it because they have a dedicated Seagate external drive on the retail market here:
"http://www.seagate.com/au/en/consumer/upgrade/game-drive-xbox/"
Besides, the 360 doesn't appear to have any issues with my Seagate drive, what so ever.

Q3: Or is this just the nature of the new update that allows you to have up to 2TB external USB storage but won't let you see the drive on the PC?
This may be Microsoft just being the fascist bastards they have always been!

Any help of feedback will be greatly appreciated.

Cheers,
BELDAM.
 
From what you have said it would appear with larger drives the entire hard drive is been formatted. With usb memory sticks the usb drive was formatted as FAT32 and the 360 content was stored in a container on the FAT32 formatted drive.

Windows can read FAT32 with no issues, however if the drive has been formatted as FATX it could well be the tools to open these drives need updating, as large USB drives were simply not possible back when most of these tools were created.

On Windows you can search for diskmgmt.msc in the start menu and then open that (with admin rights), you should then be able to see what the drive is formatted as if it's something Windows can read:

file-system.jpg
 
You must log in or register to reply here.

About Digiex

Digiex is a technology and gaming forum, founded in 2004 by InsaneNutter and Nimrod. Digiex has served the internet community with breaking news, detailed guides, exclusive downloads and a popular discussion forum. A small, friendly community of like‑minded people has developed over the years. People are encouraged to register and participate in on‑going discussions.

Get Social

Top Bottom