Print

[joeblow420]

ohh huh? this is the 1st time anyone mentioned a special bios for f/g support.. bloke said x2.4981.06 would be fine, i had mentioned imusing the krayzie softmod via memory card for mechassault.. i have a xbox version 1.0, and had a 320 gig hdd..
so, now ur saying i need to use the one that ends in 67..? does the size matter..? can i use a 256 bios.. i seen on another thread it needs a 1mb.. but someone else said it was ok to use  a 256.. is that true..?

   this makes me very nervous.. i mean getting a little conflicting feed back, just because i cant afford to make a mistake.. i dont want to lose data, and dont want to toast my xbox.. im not in a country that i would be able to get another one..
  so, once i install the new C dash, and reformat E, i will need to power off,or also after i flash the xbox, does the xboxneed to be rebooted before i do anything else.. or i can just do all at once.. just flash, install new C, and reformat E.. since there is a file manager, i can just copy my E to another place on f/g, so then i can just copy everything back on overwith out even rebooting..?

[Bomb Bloke]

QUOTE(joeblow420 @ Jan 11 2011, 08:54 AM)

ohh huh? this is the 1st time anyone mentioned a special bios for f/g support..

That would be because this is the first time you mentioned already having an upgraded HDD in your system. All you were asking about was what was required to install a new drive, not what was required to maintain compatibility with your previous drive mods.

The .06/.67 stuff refers to how the BIOS expects the drive to be formatted. 6 refers to F, 7 refers to G... Hence .06 means "F only" and .67 means "F and G".

However, XBPartitioner writes "custom" partition tables, allowing you to ignore the partition layout the BIOS "expects".

Odds are your current mod already supports these custom partitions, but that doesn't mean you're USING custom partitions. Odds are you're using a .67 setup, by the sounds of things.

[steveo1978]

QUOTE(Bomb Bloke @ Jan 10 2011, 09:03 PM)

That would be because this is the first time you mentioned already having an upgraded HDD in your system. All you were asking about was what was required to install a new drive, not what was required to maintain compatibility with your previous drive mods.

Your mind reading powers acting up again?  

[Bomb Bloke]

Yes, they tend to cut out at the worst possible times.  

[steveo1978]

no InD-Bios should b 1MB they should all be 256KB. Whats the version numbers on those?


Ok I just checked. The actually Ind-bios download would be over 1MB but thats because its more then just 1 bios in there and the newest version is the 5003 so just download that and flash the 5003.67 to your xbox. You can use the configurator app later to change bios settings later and not have to reflash the tsop.

[Bomb Bloke]

Sometimes people repack BIOSes to match their TSOP size (by creating a single file containing multiple copies of the same BIOS). Some flashing programs don't automatically do this (though I don't know of any that don't), and flashing a BIOS of the wrong size means the console won't boot from the TSOP ever again (the machine would need a modchip installed instead).

[steveo1978]

If you use evox to flash the tsop or the flash utility on AID it will resize the bios for you so dont worry about that. Just do not get a bios bigger then 256KB and try and flash it to a 256KB tsop thats where most problems come from. Ind-Bios will work on any motherboard from a version 1.0 to a 1.5. If you are that nervous over doing this then you are probably better off just sticking with the softmod.

[Bomb Bloke]

QUOTE(joeblow420 @ Jan 14 2011, 01:33 AM)

can i just pop evox, and rename it to evoxdash.xbe into C drive before I flash.. then it will just load up the evox on the reboot, or is it pretty pointless to do that.. just use the AID to flash, and reboot if i have to, and install C "dashboard" right, not a Cdrive, im not reformatting just going to install a dash to C, correct.. and then wtf will happen to my MS dash that was on there... deleted, still there.. can I delete it if it IS still there, so i have more drive space...

I wouldn't mess with the C partition too much at the moment. Depending on your current softmod, things may go pear-shaped if you do that prior to flashing.

The MS dash is the first thing an unmodded/softmodded console attempts to load - it fires up from "c:\xboxdash.xbe". A softmod is literally a modified version of the MS dash, when it loads it tweaks the copy of the BIOS stored in RAM in order to get rid of some security features, then it loads some other dashboard file (the location of which depends on the softmod). Some softmods can use some additional trickery to allow users to load the MS dash "normally" while still maintaining the benefits of their softmod.

Once flashed, you can wipe out the MS dash completely if you like. I'd recommend wiping the C partition, if only to get rid of the softmod on there. You could then install a clean copy of the MS dash if you wanted (AID should be able to do this for you), and then throw on another dash as well (a flashed console will typically try to boot from "c:\evoxdash.xbe" first, then, if it can't find that, "c:\xboxdash.xbe").

QUOTE(joeblow420 @ Jan 14 2011, 01:33 AM)

can i ask "in theory" say one of my solder points was not made, what happens if u try to flash.. nothing, because the connection is not there..?

The flashing software will tell you the TSOP isn't writeable and nothing will happen. So long as the solder joins don't magically break while the flash is in progress (and it only takes about a minute, if that), nothing can go wrong there.

[Bomb Bloke]

QUOTE(joeblow420 @ Jan 15 2011, 03:38 AM)

and why would anyone want to adjust their bios anyways...?

Personally I use it to set a custom dashboard location and to alter the appearance of the flubber sequence displayed when the console boots. Long story short, the options are there if you want 'em.

QUOTE(joeblow420 @ Jan 15 2011, 03:38 AM)

thought maybe after reformatting C drive i would be able to get write permissions to my data folders.. so thats a no go.. i did kinda assume that would be the case anyway..

What data folders?

The console doesn't have much in the way of file/folder permissions, you might also need to elaborate on how you're trying to access them.

[steveo1978]

The config app should have been included in the zip file the bios was in. you just run it then copy the file to the C: drive and when you boot the xbox it will look for that config file and boot what ever options are in there.

[joeblow420]

ohh, no it wasnt in any zip.. not even sure where i got it from.. i had xbox files backed up for years now.. it was just in a bunch of other unzipped folders with various bios in it.. i will check binz for the zip though. thx steveo !
any thoughts on the other situation with my data folders in E drive..?

[joeblow420]

hey fellas, i just wanted to update with a few threads that seem a little similar to issues im having with my Edrive's udata/tdata folders..
http://forums.xbox-s...howtopic=664143

this guyswouldnt boot up after building a new hdd, well he couldnt get access to C anyway.. im worried if I reformat my E drive, and delete all the data folders in those 2 directories WILL THE XBOX BOOT AT ALL ?
I mean doesnt it require some data to be in them folders for it to work at all?

this thread
http://forums.xbox-s...howtopic=487270
is a guy having the exact same issues as i was, but there was no replies for any kind of suggestions..

and THIS thread is the one that has me a little worried..
http://forums.xbox-s...howtopic=560054
I did use the AID disc just to delete some things off of E just to see if maybe once memory was so low it wont allow anymore data to be written to those folders, and no.. thats not it.. still can not copy, or create anything in the root of either of those directories..
and in that thread the guy completely went back to stock config, but was having XBL issues not working.. im sure there is a data folder that needs to be in udata and tdata for it right? could that be the same issue, just a different situation

i have been a bit of a bugger and im sorry for that, and really appreciate all the advice thus far, but this really or COULD make the xbox not work at all..since it seems it has to already have some data on those directories, if I completely reformat, im very sure all folders and files will be re=copied, but i am NOT sure about the udata/tdata folders, and all the data within them...
I also removed the NEWEST created folders in those directories.. in case there was something corrupted, but still cant use any game/app unless it had a previous dir.. =/

[Bomb Bloke]

Rename the folders to something else (eg Udata_old and Tdata_old) and create new versions. If this works then you can start transferring your save games over to the new copies.

[joeblow420]

well for anyone who is interested to know.. i fixed it completely..
I was just out of frustration using my notebook to FTP inside to the UDATA folder trying to rename it under every dash i had.. nothing was working,couldnt rename any folders inside it, or the udata folder itself..
THEN magically when i booted into evox.. it allowed me to rename it.. couldnt believe it.. so when i loaded xbmc got an error, tried booting a game it worked ! looked in the e folder, and there was a NEW UDATA folder..
was stilling having some write issues though, and for what ever reason only in Evox could i rename it./. but i still couldnt get any new games or apps to work..but that was enough info to know, after renaming the folder that it would at least make a new one, and there was some amount of write available... I did try to load a saved game from San Andreas, which it copied to the folder no problem, but it still wont boot up.
So just figured eff it, and wiped the E drive totally, and ftp'd another one i had on back with all the data from the old one.. so now it at least booted the 18 gig coin ops emu i had gotten, which would never load.. tested many other things that werent being allowed to create Udata folders, and all seem to be working well.. so a BIG BIG thank u for ur help, and im sorry for being so reluctant to so what we all knew would be the best way to get it done, but i have never deleted the data folders before on a xbox, and with the write errors i didnt know if they would even come back after it was deleted.. if it wasnt for experimenting around with different dashes tryin to see if i could get any write permissions i wouldnt of had the guts to just delete everything on E.. i would of just waited till i got a new HDD, but not exactly when that would be.. anyways, I have seen this issue talked about on some boards, and NO one had fixed it.. or at least ever told anyone how they had fixed it..
So it seems like AID was a KEY piece of software to get this problem resolved, so thx again u guys for point me in that direction.. still havent been able to get any of the other "bootables" to load, the slayers, or the NEWHD discs.. but as u had told me, AID is all anyone needs =)
 I had been out of the scene for a few years, and never done a hard mod, or even considered it until now, out of shear desperation to find a way to format a HDD without a PC.. damn omg, it was so easy, i wish i had started doing this from the start ! softmodding if really the fastest, and simplest way for someone who just wants a basic emu, or media streamer box.. but to really get the max from it, a hardmod is surly the best way to go !
AGAIN THANK U GUY FOR ALL THE ADVICE ! hope if anyone else has an issue about their xbox not able to boot apps or games that have never been played.. that they will be able to find this helpful..

now a question about bios.. im just wondering as per my xbox's situation what other bios are compatible, and what various reasons/features would be of any interest..?

[joeblow420]

QUOTE

UnleashX may fail to mount the volume it's on if the case of the ind-bios.cfg
DASH string isn't exactly right. If you edit ind-bios.cfg by hand make sure the
case is like so: "\Device\Harddisk0\Partition6\".
Case of the dash path and file name doesn't seem to matter, just the device and
partition part. This issue may also affect MXM and/or other dashboards.

here is my cfg.

DEFAULTXBE=\Device\CDrom0\default.xbe
DASH1=\Device\Harddisk0\Partition2\evoxdash.xbe
DASH2=\Device\Harddisk0\Partition6\avalaunch.xbe
DASH3=\Device\Harddisk0\Partition2\nexgen.xbe

I have all dashboards in Apps folder on E drive.. Ava, seems to be the only one working.. evox, unleashX, MXM, and AnodX do not work.. IF i put evox on my C drive, and rename is evoxdash it will work.. but i can run any of them just as an app...Im not sure what the read men thing up there is saying, they were all working fine before, even after flashing the tsop.. so only thing i can think of it either the reformatting, which i doubt, or putting the bios in C messed something up.. I have sense tried to use the Krayzie mech assault softmod to get them to function as before, but they just will not.. any suggestions on what im could be doing wrong... do they need to be names evoxdash, or default.xbe.. i want to use GAME2DASH as my #1 C dash, and just like to be able to use the others as apps.. shit guys im sorry, im sure this is something simple here, but i just dont understand hardmods, and their protocols.. =/