Jump to content



.06 Vs .67 On Small Hdds, The Xbpartitioner Bug, And Vga Bios Question

  • Please log in to reply
No replies to this topic

#1 johnney5


    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,054 posts
  • Location:East Coast
  • Interests:gold teetheses
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 02 May 2012 - 07:09 PM

I have a 120GB HDD in my Xbox at the moment, using X2 4981.06, and I'm wondering if it is possible to use X2 4981.67 with this hard drive since I plan to upgrade the HDD at some point. I have my Xecuter 2.2 Pro to work with, so I could keep both .06 and .67 on seperate banks, but I may eventually want to use VGA bios which, from what I understand, would occupy a minimum of 512kb (2 banks) and I have been thinking of having the chip set up like this:

Bank 1 (256kb) : Boot to UnleashX
Bank 2 (256kb) : Boot to XBMC
Bank 3 + 4 (512kb) : Boot to VGA enabled bios

^Not sure if it's even possible to use two 256kb bios and a 512kb with the Xecuter 2.2 Pro.

Also, I'm wondering if customized bios (as in modified used XBTool, KernelBasher, and/or LogoX2) can be VGA patched, flashed, and used successfully.

Last question; I've been reading into SATA to IDE adapters, and I've come across this thread: http://forums.xbox-s...howtopic=696416 which mentions a bug in XBParititioner where it locks up when "seeing" partitions larger than 1TB. The workaround mentioned by run088 was to use an older version of XBPartitioner, unevenly split two partitions so that you can see a change indicating it formatted correctly after subsequently using the newer XBPartitioner version to evenly split the F and G partitions.

I'm just wondering if this bug was ever fixed, and if not, I saw a post on XBMC4XBOX.org where Heimdall suggested to use either ldotsfan's utility disc or HeXEn to format a 1TB HDD: http://xbmc4xbox.org...p;t=1524#p29410 so I'm guessing that using one of those will accomplish what XBPartitioner does, minus the bug, correct?

Thanks very much.

P.S. I noticed someone post on XBMC4XBOX.org ( http://xbmc4xbox.org...p;t=1901#p22437 ) that they were having trouble with XBPartitioner - I'm thinking it's because of the bug in XBPartitioner, but I don't want to be like the blind leading the blind telling them to go through with the somewhat complicated XBPartitioner workaround if they can just use HeXEn or ldotsfan's Utility Disc to get the job done easily. I'll pass the info along if it's true.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users