okay, so I've been racking my brain and I know it's been addressed before. However, I feel it warrants another post. Does anyone in them interwebs have any clue on how we could remap the XDK Launcher to look at the F drive on a larger HDD installed on either a debug or a dvt4? Right now I have an xbe to lead me to a soft mod dashboard that will see the F and G drives (me personally I only have an F drive additional). Point of what I would like to accomplish is lift the 8gb limit on the E drive so I can see all the builds on the XDK Launcher and totally eliminate the need for a hacked dashboard. Can we do it? I've dug through the debug xbe files in hex editing and thus far any adjustments cause the kit to crash the launcher on reboot and simply boot into the retail dash. Easily recovered but still a pain in the arse. Community at large, any thoughts?
I thought the XDK Launchers limit was 4gb. Either way it would be nice to adjust the size limit on the partition or make the F partition visible on the XDK Launcher.
iirc the paths are hardcoded in the xshell.xbe so you might be able to just hex edit it or something. Also XBE shortcuts are a thing.
Yeah I know I can use shortcuts but I'm trying to not have to. For science. But I've tried peeking into the code via hex editor and haven't figured it out yet.
iirc I changed it by just searching for e:// or something like that. Never got to test it tho cause xbox hdd died.
Hmm. It just seems like each time I changed something in hex editor it would cause the kit to boot only to retail dash and wouldn't run the XDK launcher until I restored the original xbe.
If you dont care that certain things, like saves, get messed up, just use HackDevkitBios. It's really a nasty hack though. You cant just modify the XBE and expect it to work, it breaks things (which modded Xboxes dont care about).
If you are using HackDevKit bios, then what I would do is create a shortcut XBE to the F drive's Dashboard, XBMC is what I use. Rename it to xshell.xbe, replace xshell (or rename the original). It'll take an extra second or two to boot, but then it boots to XBMC instead of xshell. Problem solved. I probably could come up with something at some point to keep the XDK Launcher, but hacking probably is breaking things somehow (Although I hacked it for 480p in the past). Again, though, HDevBios only, without it you wont be able to boot. As always, backup backup backup. And if you break something, boot the recovery disk or a game or anything to get past the dashboard, wont crash if it doesnt need to load
Right now I have a shortcut xbe that leads to UnleashX that has the F drive mapped from the launcher. It boots into the launcher first and then has the UnleashX as a bootable xbe. Then I have everything foldered up appropriately in the F drive. I prefer to keep the Launcher as the main booting option. But to be able to see all the beta builds under just the launcher without having to use soft/hard mod dashboards is my ultimate goal though. I could take the time and run shortcuts from every xbe I have on the F drive but I just can't see why we all can't figure out how to expand the E drive capacity easily. There are so many other things the community has cracked with legit debug kits.
Also when I messed something up I'd just ensure I could play a disc that gave me access to the hard drive and I'd just replace the original Xshell file.
@XboxSurgeon did you ever find a solution to this? I'm in a similar situation myself. I've got a 160GB(Not worried about losing 40GB due to bios limits) in my DVT-4 and ran a recovery. Still only see 4.37GB despite using the fdrive.dxt and formatting F in UnleashX...
Sadly no. I went to Broman The Barnarian for help a while back but he wasn’t sure either. I dove in as far as hex editing as well but no luck just crashed the Kit a lot.
Apparently you can format F in UnleashX and access it in neighborhood but I'll be damned if I can get it to work. You tried that yet?
I never got it to work unless running another bios or HackDevkit. You could take the same drive, have it appear in one of those, remove those hacks, and the partition would disappear. I think most people using the F drive will be using hackdevkit or similar.
