Please help ... I've read up and attempted to patch the Evox M8 with the EVTool so that I can support my 250GB Maxtor Hard Drive, but I haven't seen any results. Also, I can't understand how to install everything to the F partition using Slayers v2.6. When I do install it to F instead of C, the system will only boot to the Xbox Dashboard instead of the Evox Dash. Everything works fine if I install to C (except for the Large HDD support only showing 120GB). I would like to install and boot from the F partition when the mod chip is enabled, and the C (orginal Xbox Dashboard) when the mod is disabled. (I think this is how it's supposed to work, anyway.) I would also like to support the full 250GB HDD. Thanks in advance! I'm pulling my hair out here. he he he EDIT: I forgot to mention, I have an Xecuter 3 chip with solderless adapter on a version 1.0 or 1.1 Xbox (can't recall which it was).
No you boot from C all the time. Just call your evox das evoxdash.xbe instead of xboxdash.xbe and everything will work fine. You dont need to patch the m8 BIOS it aleady has the hack to allow partition 7 all modern BIOSES do.
Icarbutt... Thanks for the reply, but can you please go into more detail? The reason I wanted to boot Evox from F is to keep my C partition exactly as it is with a normal retail HD, for Xbox Live purposes. Is this wrong? Should I install everything to the C drive? Why is there an option for "Stealth" mode to boot from the F partition? For the Large HDD, I tried normail M8 without a patch. The dashboard booted and worked fine, but only 128GB showed up on my F partition. If I don't need to patch it, how would I enable large HDD support? Note that the G partion shows 0 as well. Thanks again!
Okay ... I figured out that selecting the New/Large HDD in the Slayer's Auto-Installer only formats F to the non-LBA limit. However, now that I got my BIOS restored, I was able to format within the X3 build 1959 BIOS, which game me the full partition size of the hard drive. Now when I install apps/evox within Slayer's, the full F partition is 226GB or more. So, that problem is fixed. HOWEVER, I still have the boot problem. Within the 1959 BIOS, I enabled the "Dashboard Boot Drive" to be the F partition. I also changed the "Dashboard Boot Priority" to have "evoxdash.xbe" first, with "xboxdash.xbe" last in the order. I then opened Slayer's, and installed the Xbox Dashboard to C, and Evox/Apps to F. Booting while disabling the MOD will boot to the normal Dashboard, but enabling the X3 MOD will now take me back to the X3 build 1959 utility screen. Anyone know what I'm doing wrong??? Note that I have none of the 4 toggle switches on except "Flash Protect" when trying to boot (swithes 1 & 2 were used to flash 1959). Thanks again!!!
Okay... I suck, and figured out the problem. I had the "Autostart X3 Config Live" enabled .... so after disabling, everything works great!!!! Also had to figure out how to get back to the X3 Config .... holding white button on bootup.
icarbutt, you can install all of your hacked dashboards, and homebrew apps to F:. And you do have to modify the regular M8 bios with evtool. Once in evtool, set your boot order for the M8 bios to boot 2nd after the D drive and your in business, C next. With mod off it will boot from C and ignore F. You need the M8 plus bios for +137 gig HD's on xbox versions up to 1.5. You can also edit the M8 bios with evtool to recognize HD's over 137 gigs. I leave everything not microsoft original off of my C and E drives because I play xboxlive.
I have a box that boots evoxdash from F when modchip is enabled and boots msdash from C when chip is disabled. You need to flash a BIOS that supports Boot from F to do that. You were correct installing evox dash to F, then you need to flash a "Boot From F" BIOS to your X3. From Slayer2.6 flash BIOS menu, there are many BIOSs you can use to do that. I am using x2 4981_06 boot from F already patched. It is readily available from slayer 2.6 disc.
