I haven't modified any of the BIOSes - they all come with their standard dash locations, one of which is always C:\evoxdash.xbe. HeXEn, like ALL installation discs, assumes that one of the default dash locations in the BIOS is C:\evoxdash.xbe. It's the closest to a standard configuration that exists in the Xbox world. If you want to change it then that's fine, but lots of the features on HeXEn (like dash switching) simply won't work if the dash is somewhere else, so be prepared for a whole pile of changes - it's not as simple as just putting another BIOS on there.
HeXEn installs XBMC in E:\Apps\XBMC (or F:\Apps\XBMC). If you want it as your primary dash it puts a shortcut at C:\evoxdash.xbe. Again, that's the nearest there is to a standard installation for XBMC.
The BIOS IDs have nothing to do with flashing. They're used to identify the running BIOS.
X2.4981 doesn't support on-disk partition tables. You should really use Evox M8+, iND-BIOS.5003 or X2.5035 for maximum compatibility with large disks.
i could have sworn the x2.4981 file i downloaded from xbins has a different boot order than the one on that installation disc.
also, i am pretty sure the x2.5035 is changed also as the x2.5035 i got from xbins (which is as official download place you can get) the x2config.ini has this in there (June 7th 2005 1:37pm (untouched date))...
dash1Name = c:avalaunch.xbe
dash2Name = c:evoxdash.xbe
dash3Name = c:unleashx.xbe
dash4Name = c:xbmc.xbe
dash5Name = c:xboxdash.xbe
which i assume is what the x2.5035 bios defaults to if the x2config.ini is missing on E partition.
but like i was saying... as long as the disc boot and can flash any bios file i put on it to a v1.0-1.5 TSOP then the rest i won't have trouble with once i get FTP access to the XBox's hard drive through the boot disc.
also.... i guess main reason i avoid 'evoxdash.xbe' in my custom x2.4981 boot is that FTP wise it seems to require configuration of the FTP through PC prior to loading it as where as UnleashX (or Avalaunch) you can adjust FTP settings right from the screen in it's options.
p.s. i could go back to x2.5035 with the x2config.ini on E partition but i guess i preferred the quicker boot up of x2.4981 and it's more permanent with what it will load up where as if something happens with the hard drive and the x2config.ini etc gets messed up it could be a bit of a issue but i i guess the more i think about it... i might consider going back to x2.5035 since even if that where to happen and i lose my E:\XBMC\Default.xbe boot up it will still see my avalaunch.xbe/unleashx.xbe files on C by default that are hard coded into the BIOS if the x2config.ini is not available which if that happens i can simply FTP in and fix it and then XBMC will be good again.
but thanks for that BIOS ID thing
as far as the maximum compatibility... i thought with XB partitioner it cures any data corruption issues by making the cluster size bigger? , or are you saying x2.4981 ignores what XB Partitioner does to the partition with the large cluster sizes when i use hard drives over 250GB?
also large discs i assume you mean over around 250GB? (because i thought i remember reading somewhere that once you exceed 256GB is when cluster sizes need to be adjusted otherwise you will get data corruption after that point)
Edited by ThaCrip, 15 March 2012 - 02:23 PM.