Dual hard drive with DLC question

[Scrufdog]

According to FatXplorer it can create all the partitions and break the 32GB limit, then it apparently has you install a dashlaunch patch that bypasses the 32GB limit on the software side.

I think perhaps I'll buy the latest FatXplorer and mess it. $30 isnt bad.

 

[jsinger47]

It's just an unused USB port, not a leftover MU port.

Ah Thanks. I wasn't sure

In the case of a spelling error, I blame Tapatalk.

 

[Martin C]

According to FatXplorer it can create all the partitions and break the 32GB limit, then it apparently has you install a dashlaunch patch that bypasses the 32GB limit on the software side.

I think perhaps I'll buy the latest FatXplorer and mess it. $30 isnt bad.

I wasn't even aware this was possible. Every day's a School day!

Even more interesting:

On retail Xbox 360 consoles, you can only utilize the 16 KB to 32 GB size range. Anything higher will not be recognized by the console due to a size limitation.
On hacked (JTAG or RGH) Xbox 360 consoles, you can use the Console USB Patcher (a wizard in FATXplorer) to create a DashLaunch patch to enable larger USB sizes. The patch removes the size limitation and will allow you to use anywhere from 16 KB to 2 TB. It also removed the limitation of 2 USB ports. You can now use up to 5 USB ports for content storage.

 

[Scrufdog]

yeah. Thats what I read. I'll let you know within the next day or 2 how it goes with it.

 

[Scrufdog]

ok, so technically it works...

there are issues however.

I formatted a 1TB partition for Content.

You install the dashlaunch patch to a drive and it loads while it boots. Problem is you cant have the oversized drive hooked up when it boots. You have to wait for FSD3 to be finished, then plug the HDD in. With my 1TB Content, it took 3 minutes for it to be recognized, hard drive light flickering the whole time. I'm sure a smaller Content partition would load faster.

So this brings multiple problems.

1. You still need something plugged in first, to load the patch on every boot, before you can plug in your 'main' drive. Makes it pointless to have a drive installed internally.

2. A 3 minute lag time is uncalled for to wait to play a game.

....

So unless there is a way to make the kxam.patch a part of the NAND itself, I dont see this being useful.


Oh well, guess I'll work this DLC thing from another angle.

 

[gavin_darkglide]

There is always the other option, and that would be having a relay that would switch between drives based upon whether demon is enabled or disabled. should be able to hook this to the cr_en pad on the demon, or coolrunner for that matter, and split the sata and power lines between hdds, then all you need is a relay that would switch the power from one drive to the other.

 

[Scrufdog]

I already have a relay setup. It turns off the stock sata drive and turns on the 2tb glitch drive, and vice versa. Go.na try the sata splice thing. Of course the 2tb drive I have is a WD with a proprietary usb connector. I'm gonna hack the drive to access the sata data directly and wire it into the splice setup, leaving the relay to switch power as needed.

 

[Lisac1606]

I already have a relay setup. It turns off the stock sata drive and turns on the 2tb glitch drive, and vice versa. Go.na try the sata splice thing. Of course the 2tb drive I have is a WD with a proprietary usb connector. I'm gonna hack the drive to access the sata data directly and wire it into the splice setup, leaving the relay to switch power as needed.

Did you find any tutorials for hacking this WD Elements drive? I have a 1TB Elements SE drive which has a built in USB port directly onto the drive chasis (no seperate USB module that connects to SATA port as in older drives). Thanks

Sent from my MI 1S using Tapatalk 4

 

[gavin_darkglide]

It would be a nice If you could buy a sata split mod just for this....... An idea for the developers. shouldnt be too hard, split sata line into 2, and put the power on a relay hooked to the cr_en pad for the demon to change which drive is enabled for each nand. as for the phat models it would require a little more work, because the hdd is outside and not connected via a sata cable to the motherboard, so most the board would have to be in a custom hdd enclosure that held 2 hdds, and a new plastic piece that the hdd connects to with a pad for cr_en, and a pogo pin type setup, or what they use to connect the battery packs to the controllers, so you could still take off the dual hdd setup, and plug in your buddys hdd and still use it.

 

[Martin C]

ok, so technically it works...

there are issues however.

I formatted a 1TB partition for Content.

You install the dashlaunch patch to a drive and it loads while it boots. Problem is you cant have the oversized drive hooked up when it boots. You have to wait for FSD3 to be finished, then plug the HDD in. With my 1TB Content, it took 3 minutes for it to be recognized, hard drive light flickering the whole time. I'm sure a smaller Content partition would load faster.

So this brings multiple problems.

1. You still need something plugged in first, to load the patch on every boot, before you can plug in your 'main' drive. Makes it pointless to have a drive installed internally.

2. A 3 minute lag time is uncalled for to wait to play a game.

....

So unless there is a way to make the kxam.patch a part of the NAND itself, I dont see this being useful.


Oh well, guess I'll work this DLC thing from another angle.

You *could* try adding the file to Flash: in FSD 3. Of course, bear in mind this may have unexpected consequences so only do this if you're able to easily hook up a NAND-x / JR-P.

 

[Scrufdog]

Lisac - google western digital e71 e72

Martin - tried to copy to flash (Demon) last night, copy failed. So unless there is another way to either get the file there, using xebuild or something, or a way to apply the patch directly while building the NAND....

 

[Martin C]

How did it fail? What error? How big's the file?

 

[Scrufdog]

1kb.

Have advanced file manager checked, tried to copy, Operation Failed. Doesnt matter though, as dashlaunch only looks for kxam.patch on usb and hdd.

 

[Martin C]

what do you add to launch.ini to address it?

 

[Scrufdog]

its an automatic function in dashlaunch, it doesnt work in the way that 'normal' plugins work.

 

[Martin C]

I don't know what that means. How do you load it?

 

[Scrufdog]

All you do is place kxam.patch on a usb or hdd. Dashlaunch automatically searches for a kxam.patch file on usb and hdd upon boot. No configuration of dashlaunch is needed.

 

[Martin C]

In which case it should be loadable via flash.

You can try adding the patch to the same area as lhelper.xex in xebuild, then adding a line to load it in your _x.ini file (under [flashfs])

 

[BrockThunderjam]

I feel like I'm missing what you are trying to achieve here....Why do you need more than 32 GB for DLC on a RGH? You can put your XBLA titles anywhere on a FATX drive and FSD will show it. That should mean you would have the full 32 GB for maps etc. for all your games. I can't imagine you would have more than 32 GB worth of actual DLC (non XBLA titles) right? Or is that indeed what you need the space for?

 

[Martin C]

I feel like I'm missing what you are trying to achieve here....Why do you need more than 32 GB for DLC on a RGH? You can put your XBLA titles anywhere on a FATX drive and FSD will show it. That should mean you would have the full 32 GB for maps etc. for all your games. I can't imagine you would have more than 32 GB worth of actual DLC (non XBLA titles) right? Or is that indeed what you need the space for?

Many games now ship with HD texture packs and installed content. For example, BF3, GTA V and SC:B would take up approx 13gb of HDD/MU storage alone. It wouldn't take that much DLC to top the 32gb mark.