Post by: Ubergeek on November 15, 2003, 06:57:00 AM
| CODE |
Xecuter Proudly Presents: X2 4979 Date: 15 November 2003 Well folks it's been a long time in the making but we finally cracked it. As most of you know the new v1.4 and v1.5 Xbox had a new FOCUS video encoder (FS454) which replaced the old Conexant version (CX25871) and video output could no longer be generated. Evox implemented their old hacks to the new 5101 kernel and that all worked fine, however Xecuter doesn't patch the MS kernel, we use source code to develop our advanced patches and hacks, but without the source code for the Focus encoder we were pretty much stuffed. After many weeks of hardcore low level hacking we have successfully developed the Focus source code from scratch and are pleased to announce a fully working X2 bios with Focus support embedded for your enjoyment. Now you can use all the extra features you've all come to expect from Xecuter :) Another couple of features include the skipping of the MS Dash clock check which has been requested many times. This enables you to boot from DVD correctly when setting up a new hard disk without any problems or errors. This gets rid of Error 16 problems. We have also implemented the LBA48 concept originally discovered by OzPaul. Coded in C we used the same principals to get LBA48 working efficiently without using any of his GPL code (We should add the sources given to us a couple of months ago were beta and used with OzPaulb's permission). For those that are interested we didn't use OzPaulb's partitioning system (read partition from hdd block 0) or the highcode/lowcode system. This hack is now embedded into our X2 source so you can use two versions of our bios. One for LBA48 6 and one for LBA 48 6+7 (LBA48 6 is one large F partition - recommened for new HD installs, and LBA48 6+7 is for those who want to extend your current F drive to its larger size without losing any data). For those who dont know you were previousley limited to a 137GB drive - now you can have up to 2 TB :) (2199023255040 bytes) or 2000 Gb for the *ahem* uninformed. The hack is still entirley credited to OzPaulb. We've also added a "fix" section in this nfo that solves many crashing problems that some of you maybe experiencing with your games / apps - check it out. X2 4979 will most likely be the last bios in the X2 series, as well as the X2.3 hardware design (with new power adapter). We thank you all for your generous support over the last 2 years and we will be seeing you soon with the feature packed X3 hardware and software. HAVE A GREAT CHRISTMAS - SEE YOU IN 2004 !!!! Features Summary ============= Universal Bootloader - Works on ALL models (v1.0 to v1.5) Boot All Originals Boot All Unsigned Code Boot All Backups Boot Debug XBE's Macrovision Protection Disabled No Patch Hack No Reset On Eject Hard Drive Swap Hack LBA48 Hack* Embedded In Game Reset (IGR) - (LT+RT+BACK+START) or (LT+RT+BACK+BLACK) - Use IGR after pausing the game for best results Disable IGR - Copy x2_IGR_disabled file to E: partition Customized Error Screens ** No DVD Rom Hack *** No AV Cable Hack Media Flag Auto-Patcher Embedded XBE Capability - We can add any XBE into the bios to boot on-the-fly Dashboard Boot sequence Hack - 1. evoXdash.xbe - 2. avadash.xbe - 3. mxmdash.xbe - 4. xboxdash.xbe Change colors / boot sequences / fan speeds / Animation Patches / E-F Boot **** Conexant / Focus Video Support Clock Check Skipped / Error 16 Fix * Thanks to OzPaulb ** Thanks to Superfr0 *** Thanks to Santmat **** Use XBTool - Thanks to Nghtshd See http://teamxecuter.com/modules.php?name=NSN_Encyclopedias for more bios info See http://home.alltel.net/nghtshd/xbtool.html for Xbtool info and download Changelog ======== Changes 4978.03 - 4979 - Added Focus Video Encoder Support - Embedded OzPaulb's LBA48 Hack - Added MS Dash clock check skip - Removed embedded FTP (was simply a proof of concept anyway) - Resized and optimized back to 256k - Clean up of code and some general bug fixes - 4979.06 = LBA48 6 - 4979.67 = LBA48 6+7 Changes 4978.2-4978.3: - Fixed IGR function which made 4978.2 hang on game startup - Tested on pro & lite with evoX and a couple of games - Maybe drink less coffee next time before releasing :-p Changes 4978-4978.2: - Squeezed to 512k with FTP server still functional (this is done by implementing heavy compression algorithms) - no functional changes Changes 4978 Bug Fix - Fixed 1MB incompatibility problem with X2.x Lite Changes 4977-4978: - Added FTP server, IP: 192.168.10.123, Mask: 255.255.0.0, login/password: x3/x3 - FTP server starts up if you keep the 'A' button pressed on bootup, otherwise the dashes are run - Dashboard sequence changed to: evoXdash.xbe, avadash.xbe, mxmdash.xbe, xboxdash.xbe Changes 4976.02-4977: - Permanent No Reset On Eject - Finally got around to adding this - HATED to have it reset in xbox media player :-) Changes 4976-4976.02: - Unfortunately the 4976 hangs if people have a "debug" xbox and the default dash is set to launcher (xbsetcfg /l), this release fixes this problem Changes 4975-4976: - Disable IGR Feature - Removed No AV Cable Check (for Lan whores etc - Requested Feature) - Superfr0 Nice Error Screens (Credits to Superfr0 - should have added this as default a long time ago) Changes 4974-4975: - Auto Patcher for new media flag on new games - no need for patching ! - No DVD Drive Check - no longer throws Error 11 (Credits to SantMat) Changes 4973-4974: - ROM is now compatible to v1.0 and v1.1 Xboxes in one 256K image Changes 4972-4973: - Fixed "Non-Boot" Problem (tested on Silent Hill 2) - Fixed "only needed one trigger for reset" bug - Added S-Type IGR Reset (LT+RT+BA+BL) Notes ==== You should be made aware of some issues that we discovered and has probably had some of you tearing your hair out. If you have games like GTA, GTA Vice City and Fifa 2004 etc and they are crashing during the game then you will find they operate and AUTOSAVE check which uses your system clock. Now if your system clock is corrupt then it will crash a number of titles which use AUTOSAVE. One clock we found corrupt had a date/time setting of 15/11/8097. The second the clock was fixed in the MS Dash all the games that crashed worked just fine with no problems whatsoever. You should also be aware that some apps especially FlashX v1.2 are also crashing - this is down to the EVOX IGR. You should disable all EVOX IGR and this will get things moving nicely. If you have any questions / bug reports / success reports please post in this thread: http://teamxecuter.com/modules.php?name=Forums&file=viewtopic&p=29655 Disclaimer ======= This piece of software will most likely destroy your XBOX if you don't now what you are doing! We will not be held responsible for any damage or screw ups. For those that keep asking about FRAG (led Flashing Red And Green) means you flashed your shit wrong or installed your mod wrong. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ[XeCuT0R]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Thanks to #xbins, #xboxhacker and xbox-scene.com for their ³ ³ support Special thanks to Team Avalaunch and Worldxbox.co.uk ³ ³ We should also mention maxconsole.com and xbins.org ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ -=- Cracking is fun. We enjoy it and we know you enjoy using the shit we make so let's keep the scene fun as there have been too many idiot elements recently. If you don't like us that's fine, but it won't stop us doing something that we enjoy. This is a problem for some and we feel very sorry for these people. -/- Xecuter - Rocking the box since 2002 -- |
Post by: MN-Mod-Man on November 15, 2003, 07:09:00 AM
Keep up the Good work Guys...Happy Holidays. 
Post by: Be Absentminded on November 15, 2003, 07:18:00 AM
-Jameson
Post by: sulfur on November 15, 2003, 07:36:00 AM
Post by: XBoxgeek on November 15, 2003, 07:44:00 AM
Xboxgeek
Post by: feflicker on November 15, 2003, 07:48:00 AM
Maybe we can get this updated
http://forums.xbox-s...ST&f=38&t=43437
Post by: Heet on November 15, 2003, 07:50:00 AM
Post by: feflicker on November 15, 2003, 08:09:00 AM
UPDATED: New hash for 4979.06 after the "repack" was released.
ROM = "X2 4979.06",0x56be0f0146d1a69c0f1e6fa9a9558394
ROM = "X2 4979.67",0xf85d1d778ee80a3a9b5f57e4dedd13d3
Post by: ...ReLLiK on November 15, 2003, 08:14:00 AM
Post by: Ubergeek on November 15, 2003, 08:15:00 AM
| QUOTE (dacke @ Nov 15 2003, 05:10 PM) |
| Just wanna confirme that 4979 will work in my v1.4 with 256k before I flash it. |
read the post again
Post by: Illsley on November 15, 2003, 08:37:00 AM
Great work guys!
One question though, I have a 120 gb hd now and Im not going to upgrade to a larger.. Does it matter which bios i use, 4979.06 or 4979.67?
Because I dont use lba48, im not affected right?
Thanks.
Post by: X2Gamer on November 15, 2003, 08:38:00 AM
Post by: SNICK! on November 15, 2003, 08:49:00 AM
i want to see if anyone has any probs before i flash my chip with it
cheerz
oh and ps great work Uber geek you rock!
Post by: Ubergeek on November 15, 2003, 08:55:00 AM
Post by: sulfur on November 15, 2003, 09:04:00 AM
| QUOTE (Ed_209 @ Nov 15 2003, 01:41 PM) |
| For those who dont know you were previousley limited to a 137GB drive - now you can have up to 2 TB  (2199023255040 bytes) or 2000 Gb for the *ahem* uninformed. |
umm how do we know that xbox = 2 TB? if maxium hdd = 320gig?
Post by: Rob3121 on November 15, 2003, 09:34:00 AM
Post by: bi786 on November 15, 2003, 09:46:00 AM
.
Post by: sulfur on November 15, 2003, 09:55:00 AM
(2199023255040 bytes) or 2000 Gb for the *ahem* uninformed.read before posting.
Post by: bi786 on November 15, 2003, 10:00:00 AM
. Thanks
Post by: DynaMight on November 15, 2003, 10:17:00 AM
Keep up the good work.
Post by: ZildjianKX on November 15, 2003, 10:56:00 AM
| QUOTE |
| X2 4979 will most likely be the last bios in the X2 series, as well as the X2.3 hardware design (with new power adapter). We thank you all for your generous support over the last 2 years and we will be seeing you soon with the feature packed X3 hardware and software. |
So the X3 BIOS will be backwards compatible with the X2 chips, except for special hardware features, right?
Thanks for the release BTW.
Post by: heinrich on November 15, 2003, 10:58:00 AM
| QUOTE |
| anyword when Xbtool will support X2 4979 need to change my boot sequence to boot from F: does 4979 also support ftp or is it only 4978.03? thx |
When its done.
from the dront page:
What's new/fixed (Changes 4978.03 - 4979):
- Added Focus Video Encoder Support (xbox v1.4/v1.5)
- Embedded OzPaulb's LBA48 Hack
- Added MS Dash clock check skip
- Removed embedded FTP (was simply a proof of concept anyway)
- Resized and optimized back to 256k
- Clean up of code and some general bug fixes
- 4979.06 = LBA48 6
- 4979.67 = LBA48 6+7
Post by: feflicker on November 15, 2003, 11:00:00 AM
BTW, for those that do not know, if you have a hard drive > 120GB, and have not yet installed an LBA48 bios to read the remaining space on your F: partition, then you need to install 4979.67 (F and G drives), and then format paritiont 7 to be your new G:.
If you already have a big F: with LBA48 bios, then use 4979.06.
If it is a new mod job, use 4979.06.
===============================================
Whatever you do, do not install 4979.06 on a drive > 120 GB with an F: partition that is not currently setup for LBA48. Your partition table will be corrupted... This is not an X2 bios problem, but an LBA48 (inherent) problem
===============================================
Post by: heinrich on November 15, 2003, 11:02:00 AM
Post by: tyson on November 15, 2003, 11:29:00 AM
Post by: nonzero on November 15, 2003, 11:35:00 AM
Post by: heinrich on November 15, 2003, 11:35:00 AM
| QUOTE (tyson @ Nov 15 2003, 03:29 PM) |
| OK my box currently has 120 gig drive with a matrix chip,my question is currently im booting off my c drive with evox,so does this bios boot off the C drive or the F drive or does it . matter |
the C drive by default. Check the nfo for the .xbe order.
Post by: heinrich on November 15, 2003, 11:37:00 AM
Post by: -Natas- on November 15, 2003, 11:47:00 AM
Post by: feflicker on November 15, 2003, 11:58:00 AM
| QUOTE |
| 4979.67_256k.bin |
Ecct, That should have worked if you currently have an F:, but not using LBA48 and wanted to add a part7 as G: to claim your unused space.
What bios/config are you using that does work?
Post by: heinrich on November 15, 2003, 12:01:00 PM
(already had a 160gig with a G drive)
Post by: bi786 on November 15, 2003, 12:04:00 PM
Post by: heinrich on November 15, 2003, 12:10:00 PM
| QUOTE (nonzero @ Nov 15 2003, 03:35 PM) |
| Is there a BFM version of this BIOS out for us PBL users? |
the latest xbtool doesnt create one (at least not without any extra work), so just wait for a new version.
Post by: moggisan on November 15, 2003, 12:16:00 PM
Post by: shadow3000 on November 15, 2003, 12:31:00 PM
hey when will xbtool support these bios!?
Post by: heinrich on November 15, 2003, 12:45:00 PM
| QUOTE (moggisan @ Nov 15 2003, 04:16 PM) |
| alright what's with the clock skip, what purpose does that have? |
1.Xbox turns on
2. several checks are done for hardware, incuding RAM, HD, and DVD-DRIVE, just to test if they are present
3.Xbox checks SYSTEM TIME ->TIME NOT FOUND -> Xbox tries to launch dash off of hard drive -> DASH NOT FOUND-> ERROR 16 - DASH ERROR
Now, instead of error 16, the bios boots default.xbe from the dvd drive.
Post by: LEDHaywire on November 15, 2003, 12:46:00 PM
Post by: NghtShd on November 15, 2003, 01:54:00 PM
| QUOTE (heinrich @ Nov 15 2003, 04:10 PM) | ||
the latest xbtool doesnt create one (at least not without any extra work), so just wait for a new version. |
I haven't tested it a lot, but I was able to create one. It booted up to the dash and ran the couple of games I tried. IGR was fine, too. Look in the usual.
Post by: heinrich on November 15, 2003, 02:05:00 PM
| QUOTE (NghtShd @ Nov 15 2003, 05:54 PM) | ||||
I haven't tested it a lot, but I was able to create one. It booted up to the dash and ran the couple of games I tried. IGR was fine, too. Look in the usual. |
Thanks NghtShd
Post by: feflicker on November 15, 2003, 02:10:00 PM
| QUOTE |
| new bios on my chip(4979) which one should I use (.06 or .67) so I dont loose access to everything on my f drive. and should I turn the lba48 option on in xbtool b4 I flash it. |
The LBA48 option is always on in 4979. You should have to pick the correct one to load. .67 has part-6 (F) and part-7 (G), .06 just has part6 (F).
| QUOTE |
| I used a bios titled, 512kbigf.bin i dont know the offical name of the bios |
See if Bioscheck or Evox will report which bios it is... If I were you I would dump xbox hdd to a PC, reformat the drive using 4979 Bios and then put all the data back. That way you are safe to use all the new bioses from here out... Who knows what the other bios is doing (especially since you don't even know which release it is)
======================================
The clock fix makes X2 Bios, hands down, the best bios out there. {This was the only thing that EvoX Bios had over X2...}
Post by: heinrich on November 15, 2003, 02:11:00 PM
Post by: Ecct on November 15, 2003, 02:47:00 PM
---
After falshing it with 4979.06 I cannot see any data on the F: Drive.
Flashing back to 4977 LB48 works OK.
that worked for me too
Post by: LESTAT on November 15, 2003, 02:50:00 PM
i looked thru the read me file and i dont see any info about .67
i think .06 is bunk. try .67
Post by: feflicker on November 15, 2003, 03:02:00 PM
| QUOTE |
| have you guys tried using the 4979.67 ? i looked thru the read me file and i dont see any info about .67 i think .06 is bunk. try .67 |
They are from the same release, one is for a large part-6, the other for both part-6 and part-7.
I am using 4979.06 without issue, albeit I don't have a > 120GB drive
Post by: heinrich on November 15, 2003, 03:08:00 PM
| QUOTE (LESTAT @ Nov 15 2003, 06:50 PM) |
| have you guys tried using the 4979.67 ? i looked thru the read me file and i dont see any info about .67 i think .06 is bunk. try .67 |
| QUOTE |
| Changes 4978.03 - 4979 - Added Focus Video Encoder Support - Embedded OzPaulb's LBA48 Hack - Added MS Dash clock check skip - Removed embedded FTP (was simply a proof of concept anyway) - Resized and optimized back to 256k - Clean up of code and some general bug fixes - 4979.06 = LBA48 6 - 4979.67 = LBA48 6+7 |
Post by: LESTAT on November 15, 2003, 03:17:00 PM
also someone said it CAN be opened with xbtool.
i use XBtool_1.0.11 and it says unsupported kernel when using the debug open to load it.
so what version of xbtool is being used.
just a quick note about .06
i havent tested with all games but so far it refuses to boot crimson skies.
the others if tried work fine.
.67 WILL boot crimson skies.
dont know why but it does.
is there any other tool besides xbtool that will open this and or others and has more features than xbtool i like xbtool but there aint much you cna do with it. just real simply stuff.
Post by: tester123 on November 15, 2003, 03:40:00 PM
| QUOTE (iceCube @ Nov 15 2003, 07:26 PM) |
| Hey boyZ can anyone type here ROM string for EBOX.ini for this bioS ;o))) |
For 4979.06_256k (big 6 patition) ROM = "X2 4979.06_256k",0x50fe679cbf3882aba9f7bd3d812b7f51
For 4979.67_256k (big 6 and 7 partition) ROM = "X2 4979.67_256k",0xf85d1d778ee80a3a9b5f57e4dedd13d3
Post by: NghtShd on November 15, 2003, 04:03:00 PM
| QUOTE |
| also someone said it CAN be opened with xbtool. i use XBtool_1.0.11 and it says unsupported kernel when using the debug open to load it. so what version of xbtool is being used. |
No version. It can be unpacked or converted to BFM, but that's all. If you need to change the dash options you can unpack, hex it (not too hard for the dash stuff), then repack.
Post by: feflicker on November 15, 2003, 04:18:00 PM
| QUOTE |
| i havent tested with all games but so far it {.06} refuses to boot crimson skies. |
I just booted and started on the last mission I left off of on, seems to be working on mine
X2 Lite
4979.06
MXM Dash
EDIT: Gonna take a while to stop typing 4977 by accident
Post by: mrRobinson on November 15, 2003, 04:23:00 PM
Post by: Frag Daddy on November 15, 2003, 04:49:00 PM
Post by: feflicker on November 15, 2003, 04:54:00 PM
| QUOTE |
| How come i can't edit anything on this bios with xbtool. Is it because it's unsupported? If so, when will it be supported? |
4979 was just released today... NghtShd will release an update when he gets to it
Post by: Xeero on November 15, 2003, 04:54:00 PM
| QUOTE (Frag Daddy @ Nov 15 2003, 08:49 PM) |
| How come i can't edit anything on this bios with xbtool. Is it because it's unsupported? If so, when will it be supported? |
Unbelievable. Are you completely illiterate?
One more question as to why Xbtool won't open this BIOS, and I'm going to start deleting posts.
Post by: feflicker on November 15, 2003, 04:57:00 PM
| QUOTE |
| One more question as to why Xbtool won't open this BIOS, and I'm going to start deleting posts. |
What if something ever happened to NghtShd {god forbid}, martial law would be declared
Anyway, Crimson Skies ran for 30 minutes on my xbox, no issues with 4979.06
Post by: LESTAT on November 15, 2003, 05:36:00 PM
my post didnt describe that so i apologise,
my point being that the bios wont even boot the game now where as even 4977 brings up the loading screen,(it stops there but at least it loads, all other bios's at least let you get to the menus.)
also whether i use 4979.06 or 4979.67 when i have the dvd disconnected crimson skies refuses to boot.
just another point ive made time and time again that this game is suing some sort of alternative protection.
yeah yeah i know get a modchip.. and i plan on it. probably my self given xmas present.
anywho. just thought id throw this issue out there.
no other games seem to mind that the xbox dvd is unhooked.
games STILL arent recognised in evox when using the PC DVD rom. this is with any bios though.
i wish there was a fix for this as its a pain in the booty to have to open boxplorer and run the default.xbe just to make the game run.(if i boot from the dvd it works, im talking if ai put in a dvd from evox.)
the bios/evox isnt seeing the pcdvd rom as a drive so to speak.
evox reports the drive as being open when unhooking the Xdvd. just another thingy i wanted to point out, dont know if this is going to cause issues or not.
Post by: feflicker on November 15, 2003, 06:07:00 PM
| QUOTE |
| my post didnt describe that so i apologise, my point being that the bios wont even boot the game now where as even 4977 brings up the loading screen,(it stops there but at least it loads, all other bios's at least let you get to the menus.) |
Interesting point!
Post by: echto on November 15, 2003, 07:21:00 PM
Post by: jlm5151 on November 15, 2003, 07:22:00 PM
Post by: feflicker on November 15, 2003, 07:25:00 PM
| QUOTE |
| haha Rule #1, if it ain't broke, don't fix it |
But if you don't break it, how are you gonna have fun fixing it
Post by: Heet on November 15, 2003, 08:06:00 PM
Post by: feflicker on November 15, 2003, 08:18:00 PM
| QUOTE |
| nope not workin for me. 200GB doesnt see F but both bios work on my 120's but not the 200. Im not saying its the bios but I'll be damned if I know what im doin wrong. |
I thought all Uber did was add the same hack to his bios, so that you don't have to use xbtool any longer... Maybe not?
I wonder what would happen if you "prepped" the drive with 4979, and did it from scratch...
Post by: Heet on November 15, 2003, 08:21:00 PM
Post by: ray12944 on November 15, 2003, 08:56:00 PM
Post by: Grimfull on November 15, 2003, 09:30:00 PM
whats this ?
Post by: ray12944 on November 15, 2003, 10:04:00 PM
Post by: bernienoel on November 15, 2003, 11:21:00 PM
Post by: T-1200 on November 15, 2003, 11:32:00 PM
Anyone else get this
Post by: heinrich on November 15, 2003, 11:33:00 PM
| QUOTE (icefreon @ Nov 16 2003, 01:25 AM) |
| OK, after half the day of reading I have figured this new BIOS out. If you NEVER installed a HD with an LBA48 supported BIOS this new BIOS will NOT work. The for sure fix for this would be to Xfer all you XBOX HD data to your PC. Use the new 4979.06 BIOS to re-configure your HD (that means erase it), this will add LBA48 support for this and future BIOS updates. Also, make SURE you enable G: in the .ini file for those HD's larger than 137 gigs. Then flash your BIOS and re-Xfer everthing back to your HD. Sucks I know but looks to be the only fix, its not the BIOS fault, so I doubt there will be a "fix" for the BIOS coming out anytime soon. FLASH WITH-IN EVOX FOR BEST RESULTS!! For hard drives 120 gigs and smaller use 4979.06 For hard drives 137gigs and above use 4979.67 (then configure partition 7 for G:, and write the .ini to support G: ) (correct me if I'm wrong, just my gathered knowledge of the day) |
This makes 0 sense, as I went from using a bios, and hard drive with no lba48 support, I patched my bios and formatted, and have had a G drive for 2 months. No where in there did I need to format anything but my new G drive. I dont see why this bios would be any different at all.
Or maybe its just late and I am missing something....
Post by: heinrich on November 15, 2003, 11:35:00 PM
| QUOTE (T-1200 @ Nov 16 2003, 03:32 AM) |
| regarding the clock check thingy, I still get the 15/11/8097 date problem, but this only happens when I use Media X Menu as my main booting dashboard. Anyone else get this |
I think the only clock thing that this fixes is in the cases where you would have error 16.
Post by: selfer on November 15, 2003, 11:40:00 PM
Post by: madcake on November 16, 2003, 12:43:00 AM
You had one big F: drive before and installed the 6+7 bios? Do you understand what the 6+7 Bios does? It creates TWO extra partitions -> F: AND G: ... this can't be compatible with your previous (ONE extra partition) setup.
Once again:
6 = one F: drive (everything above original xbox hdd size goes to F:)
6+7 = one F: drive (everything above original xbox hdd size up to 137 gig goes to F:) and one G: drive (everything from 137 gig up to total hdd size goes to G:)
You don't have to use 6+7 if your drive is bigger than 137 gig ... just use the same setup you were using before installing 4979!
-cake
Post by: Xeero on November 16, 2003, 03:21:00 AM
| QUOTE (heinrich @ Nov 16 2003, 03:35 AM) | ||
I think the only clock thing that this fixes is in the cases where you would have error 16. |
Yep. The fix doesn't prevent the clock from losing time, it just prevents the Xbox from erroring out in such a case.
Post by: LESTAT on November 16, 2003, 03:34:00 AM
ok who the hell tested this thing ?
and you have to redo your entire hard drive ? no no no,, if they made the bios like that then i think it needs to be removed from the usual place and redone.
havent gone thru too many games but so far what i have crimson skies is the only one to refuse to boot if have your dvd unhooked.
also still looking for a fix or forget it, about having the dvd unplugged and using a pc dvdrom and evox mxm avalaunch., nothing will use the dvd.
evox reports the tray as being opened. well hello team X2 if the tray is open how are we suppose to use DVD's
make it say closed. or disks are useless unless boxplorer is used.
Post by: madcake on November 16, 2003, 05:18:00 AM
Post by: Morglum on November 16, 2003, 05:28:00 AM
| QUOTE (LESTAT @ Nov 16 2003, 01:34 PM) |
| ok so even though .06 is supposedly suppose to work for one big F drive 98% of the people here cant read from their F drive. |
How big is your HDD exactly? From other posts ive read, really big HDDs with everything set to F seem to crap out and get data corruption once you start to store data above the 280GB mark. But when they're set to use F and G everything seems to start running smoothly.
Post by: LESTAT on November 16, 2003, 06:41:00 AM
so far games run except the afore mentioned CS.
still though dont you think if the bios allows you to unhook the dvd, if you hook up a pc dvd rom it should still read the drive.
and actually its not 4979 i used 4977 and it does the same thing.. i thought 4979 was the only bios to allow removal of the xbox dvd.
so its a glitch of the entire xbox and or evox mxm and everything else.
still even with that in mind if you hook up the dvd and still use a pc dvdrom,, many things still have a hard time realising that the pc dvdrom is the dvd now,, since the ide cable is gone from the xbox dvd,, it thinks there is no disk.
over all since im using pbl i didnt expect to see anyhting new, if i had a chip then yes, but what i didnt expect to happen was that it would screw with how your F drive is read, and also not allow games to boot.
this again is just a step towards how bios's treat games and visa versa.
evox is even set to NOT use G and yet when using the .06 which is ONLY F drive, it messes with it. wierd stuff
possibly a conflict with evox 3291 pr whatever the newest ver number is.
Post by: ray12944 on November 16, 2003, 08:32:00 AM
So I Tried with the .06 Version now and is still the same problem.
Just to be safe I flashed the x2 bios on bank 1 and the M7 on bank 2, When I boot up
the x2 4979.06 Bios it wont detect my Stuff on the F drive and in my system info it says I only have 129 gigs totals.
But when i switch to bank 2 (M7 bios) its back to normal (155 GiGs total)
Just to add to the list my HDD is a Maxtor 160 GB HDD but i really thinkg it wont work
with any HDD bigger than 137 gigs with the Lba patch allready on it
Thanks for the help
Post by: XBoxgeek on November 16, 2003, 09:29:00 AM
| QUOTE (icefreon @ Nov 16 2003, 06:43 PM) | ||
Being that your HD is LARGER than 137gigs you MUST use 4979.67 All data above 137 gigs will go into G: after G: is configured for use. |
Why would he want to do that ( unless he wants to start again) He already has a drive formated to allow for a greater than 137GB partition. The one he should use is .06. If this is not working for him then there may be an issue with .06
If he flashed with .067 as you say, only 137GB will be available on F and as this has already been formated to 155GB he won't see any data.
Xboxgeek
Post by: ray12944 on November 16, 2003, 09:31:00 AM
| QUOTE (icefreon @ Nov 16 2003, 05:43 PM) |
| Being that your HD is LARGER than 137gigs you MUST use 4979.67 All data above 137 gigs will go into G: after G: is configured for use. |
The problem was the my hdd was allready full of data and I didnt want to loose it, so i did try the .67 bios but it woulndt detect the extra space and therefore looked like my F drive was emty, so further up this forum they told me i had to use .06 because I allready had it setup as one Big F drive before with the M7 Bios, So thats why i used that but With the same problem ,
The thing is that I didnt want to reformat because I dont have another HDD to put my data while I format this one
::EDIT:: thanks Xboxgeek , (you beat me in posting my explanation)
Post by: DynaMight on November 16, 2003, 09:37:00 AM
Heres what I make it out to be....
4979.06 = HDD Below 120GB or if you are gonna format a new (anysize HDD)
4979.67 = Use if you already have a 120GB+ HDD setup using an existing LBA48 patched BIOS
Am I completely wrong?
Post by: feflicker on November 16, 2003, 09:52:00 AM
| QUOTE |
| Heres what I make it out to be.... 4979.06 = HDD Below 120GB or if you are gonna format a new (anysize HDD) 4979.67 = Use if you already have a 120GB+ HDD setup using an existing LBA48 patched BIOS. Am I completely wrong? |
Yes.
If you have a < 120GB Drive, use 4979.06.
If you have a > 120GB drive, and have never installed an LBA48 bios, use 4979.67. You will need to partition the 7th partition and format it as G:, as well as enable it in your dashboard to claim your previously unrecognized space.
If you had a large F: before using LBA48, use 4979.06.
If you had a regular F: and a large G: before using LBA48, use 4979.67.
It is that simple...
(BTW, if you install the wrong bios right off the bat, and then boot it up, from that point on all results are "fishy" as you booted your drive with the wrong LBA bios, and it could have caused corruption. Make sure you flash the correct bios version the FIRST time.)
Post by: Ubergeek on November 16, 2003, 11:06:00 AM
| QUOTE (LESTAT @ Nov 16 2003, 01:34 PM) |
| ok so even though .06 is supposedly suppose to work for one big F drive 98% of the people here cant read from their F drive. ok who the hell tested this thing ? and you have to redo your entire hard drive ? no no no,, if they made the bios like that then i think it needs to be removed from the usual place and redone. havent gone thru too many games but so far what i have crimson skies is the only one to refuse to boot if have your dvd unhooked. also still looking for a fix or forget it, about having the dvd unplugged and using a pc dvdrom and evox mxm avalaunch., nothing will use the dvd. evox reports the tray as being opened. well hello team X2 if the tray is open how are we suppose to use DVD's make it say closed. or disks are useless unless boxplorer is used. |
we designed this bios to work perfect with our chip (and others)
if it doesnt work for you with your exploits - you really should try to code it yourself to work. PBL is nothing to do with us - perhaps you could ask them to fix it ?
bios tested with several boxes with several different HD combos and they all worked just fine with no problems.
If you have are installing ANY new drive ANY size use 4979.06 (you should use 4979.67 if using a drive bigger than 300GB as it handles the data better)
If you have a currently installed drive larger than 120GB, and have never installed a previous LBA48 bios use 4979.67. You will need to partition the 7th partition and format it as G: as well as enable it in your dashboard to claim your previously unrecognized space.
If you had a large F: when using any previous LBA48 use 4979.06
If you had a standard F: and a large G: when using any previous LBA48 use 4979.67
This works. Its tested. If it didnt work for you, you used the wrong bios.
Tested 4979.06 on a box with 120gb drive. Previous bios standard 4977. All data correct on 1 large F drive
Tested 4979.06 on a box with 120gb drive. Previous bios LBA48 (6) 4977. All data correct on 1 large F drive
Tested 4979.67 on a box with 200gb drive. Previous bios LBA48 (67) 4977. All data correct on standard F drive and large G drive
Tested 4979.06 on a new 200gb install. All data correct on large F drive.
Post by: rob1309 on November 16, 2003, 11:16:00 AM
good work
Post by: Ubergeek on November 16, 2003, 11:54:00 AM
Post by: kanaberra on November 16, 2003, 12:09:00 PM
4979.06 works fine 4 me on:
xbox v1.0
120gb barracuda
PC-Bioxx chip (flashed with Bioxx Flasher 1.4)
:::peace
Post by: damianlr on November 16, 2003, 12:37:00 PM
Post by: Thraxen on November 16, 2003, 12:51:00 PM
| QUOTE |
| Tested 4979.67 on a box with 200gb drive. Previous bios LBA48 (67) 4977. All data correct on standard F drive and large G drive |
OK... you covered everything except a previous >120 GB HDD with NO G: Drive then flashing to 4979.06 with no G: and still have F: work.
This is exactly the situation I described above and it seems to be that most of the other people who have posted problems are in this same situation.
Post by: Ozmods on November 16, 2003, 01:00:00 PM
I installed a 160gb in a V1.3 and it only gave me 120 gb in my f partition with 4979.06
Then i used 4976.02 patched it with Xbtool and it showed the full 140gb in F partition..
Post by: Heet on November 16, 2003, 01:34:00 PM
Post by: Ubergeek on November 16, 2003, 01:56:00 PM
read the news page guys and get the new file
Post by: Ubergeek on November 16, 2003, 01:57:00 PM
| QUOTE (Heet @ Nov 16 2003, 11:34 PM) |
| SSX tricky wont load, and GTA is hanging on loading screen. It works then I reboot, then it stalls, then i reboot and it works again. I dont get that. |
I posted about this - your clock is corrupt - set it correctly in ms dash
Post by: Heet on November 16, 2003, 02:20:00 PM
Post by: j0ey on November 16, 2003, 03:01:00 PM
for I can set my fan to 50%Also 4979.06 now works on my friend's xbox.....I think he even cried when his F went bye bye....but now hes happy.....
Post by: Heet on November 16, 2003, 03:01:00 PM
Post by: jlm5151 on November 16, 2003, 03:18:00 PM
Post by: Ubergeek on November 16, 2003, 03:26:00 PM
Post by: feflicker on November 16, 2003, 03:28:00 PM
Post by: Ubergeek on November 16, 2003, 03:30:00 PM
| QUOTE (Heet @ Nov 17 2003, 12:20 AM) |
| i did and i did forget to but Sniperkilla reminded me. |
did it fix your problems ?
really helps if you let us know results after been given advice
Post by: feflicker on November 16, 2003, 03:41:00 PM
ROM = "X2 4979.06",0x56be0f0146d1a69c0f1e6fa9a9558394
ROM = "X2 4979.67",0xf85d1d778ee80a3a9b5f57e4dedd13d3
Post by: Heet on November 16, 2003, 03:52:00 PM
Post by: ray12944 on November 16, 2003, 06:18:00 PM
Just got home and come to read these wonderful news!
Now works Perfect for me also, Ver 1.4 Xbox 160 gig HD
Keep up the good work
Post by: heinrich on November 16, 2003, 07:13:00 PM
| QUOTE |
| Then it hit us - one very drunken member of Xecuter packed the release of 4979.06 incorrectly. It's actually 4979.67 - DOH ! |
If this was the problem, then why were the orignal .06 & .67 bios not the same?
Post by: Xeero on November 16, 2003, 07:15:00 PM
| QUOTE (heinrich @ Nov 16 2003, 11:13 PM) | ||
If this was the problem, then why were the orignal .06 & .67 bios not the same? |
I agree, and that occurred to me earlier. The original hashes should have been the same, no? Unfortunately, I don't have the originals to check.
Post by: feflicker on November 16, 2003, 08:14:00 PM
Maybe something didn't get "flipped" all the way over, so there was enough difference in between the builds to give a different hash...
Post by: heinrich on November 16, 2003, 10:39:00 PM
| QUOTE |
| After many weeks of hardcore low level hacking we have successfully developed the Focus source code from scratch and are pleased to announce a fully working X2 bios with Focus support embedded for your enjoyment. |
Any chance that some of your findings/code will be shared with xbox-linux? Seems kind of silly to do all the work twice.
Post by: geeky2003 on November 16, 2003, 11:52:00 PM
| QUOTE (Ubergeek @ Nov 17 2003, 01:26 AM) |
| /me gives up booze and drugs |
Haha....nothing wrong with drinking good beer while writeing code!
-=-=geeky=-=-
Post by: Ubergeek on November 16, 2003, 11:52:00 PM
| QUOTE (feflicker @ Nov 17 2003, 06:14 AM) |
| My guess is that they are working from the same source on both releases, and they simply "flip a flag" when they do a build (depending on which LBA48 they want). Maybe something didn't get "flipped" all the way over, so there was enough difference in between the builds to give a different hash... |
correct
Post by: Ubergeek on November 16, 2003, 11:56:00 PM
| QUOTE (Thraxen @ Nov 17 2003, 08:47 AM) | ||
My SSX3 is doing the same thing as described above by Heet and it's not my clock. I checked my clock in the MS dash it has the correct time and date (always has). But after installing the new bios (4979.06 repack) it will hang at the loading screen about 50% of the time. When it does I have to reset the XBOX and then it will work. |
ok i just leeched ssx3
booting from dvd rom and HDD and im doing my best to get it to hang - sorry cant see a problem
try setting your clock to a different valid date / time and see if makes a difference
Post by: heinrich on November 17, 2003, 07:18:00 AM
http://forums.xbox-s...8&t=126534&st=0
Post by: Ubergeek on November 17, 2003, 08:41:00 AM
Post by: heinrich on November 17, 2003, 08:45:00 AM
Post by: kanaberra on November 17, 2003, 09:06:00 AM
xbox v1.0
120gb barracuda
PC-Bioxx chip (flashed with Bioxx Flasher 1.4)
:::peace
Post by: Ubergeek on November 17, 2003, 09:14:00 AM
| QUOTE (kanaberra @ Nov 17 2003, 07:06 PM) |
| THX again for da repack ! "Real" 4979.06 works fine TOO xbox v1.0 120gb barracuda PC-Bioxx chip (flashed with Bioxx Flasher 1.4) :::peace |
great news
more posts like this pls
Post by: bebrewer1 on November 17, 2003, 10:49:00 AM
I haven't tried 4979 yet but I will as soon as I can edit the colors & boot partition in XBTool. I have no doubts that this release will be da shizznit just like I have enjoyed all the other Xecuter releases!
Post by: Xeero on November 17, 2003, 10:52:00 AM
| QUOTE (Realm Lord @ Nov 17 2003, 02:47 PM) |
| I'm just waiting for XBtool myself, so it will find my apps on the F: drive. I tried loading .06 and it wouldn't boot off my F: drive. |
If you're getting really antsy you can unpack and hexedit the kernel to reflect this.
Post by: Ferris23 on November 17, 2003, 01:36:00 PM
Post by: feflicker on November 17, 2003, 02:43:00 PM
| QUOTE |
| How do I tell if I am downloading the proper file? |
Check the filename for the word "repack", or if it has been renamed check the nfo file. It was updated when the repack was released.
Running to check SSX3 on my box///
EDIT: SSX3 booted fine 4 times in a row...
-Matrix Chip with 4979.06 {repack}
-Game installed to HDD
-Game created with Craxtion{patched}
-Copied to HDD with dvd2xbox 0.49.
-MXM Dash as Launcher
Post by: feflicker on November 17, 2003, 03:10:00 PM
| QUOTE |
| Is it necessary to use the repack if you are only running a standard hard drive? I use PBL 1.3.5 with the audio exploit and I used 4799.06 from the first release - is that OK or should I switch? |
As it was an accidental and possibly corrupted release, I would say it is "unsupported" and anything that happens as a result of using it would fall on the person who installed it... What I am trying to say is, better safe than sorry, grab the repack
Post by: Ubergeek on November 18, 2003, 01:00:00 AM
ive been playing this for 2 hours now (cool game) - no problems
dont forget if games ever crash on you check the system clock
Post by: legueux on November 18, 2003, 01:18:00 AM
A question about LBA48.
Actually a friend have a 200GB HD with F+G partition (LBA48 patch, not yet flash his bios with 4979.xx).
The question is that he want to stop use the G partition and just use the F. There already have some files in partition G and he asked me if he flash with 4979.06, do the files in partition G will be "move" in F partition ?
For resume do it possible to delete partition G for use only an extend partition F without lost files already in partition G ?
Thanks for your help.
Post by: Ubergeek on November 18, 2003, 04:18:00 AM
| QUOTE (legueux @ Nov 18 2003, 11:18 AM) |
| Hi, A question about LBA48. Actually a friend have a 200GB HD with F+G partition (LBA48 patch, not yet flash his bios with 4979.xx). The question is that he want to stop use the G partition and just use the F. There already have some files in partition G and he asked me if he flash with 4979.06, do the files in partition G will be "move" in F partition ? For resume do it possible to delete partition G for use only an extend partition F without lost files already in partition G ? Thanks for your help. |
no - he will need to backup everything and set the HD up from scratch
Post by: legueux on November 18, 2003, 05:04:00 AM
Post by: dpr99 on November 18, 2003, 02:37:00 PM
Post by: Arizzle on November 18, 2003, 03:06:00 PM
Post by: Ubergeek on November 18, 2003, 04:12:00 PM
the bios works perfectly fine with a mod - so its not a bios problem
Post by: feflicker on November 18, 2003, 04:28:00 PM
| QUOTE |
| why not ask the PBL ppl how to fix it the bios works perfectly fine with a mod - so its not a bios problem |
Makes no sense for a softmod user to upgrade to this new build anyway, the "enhancements" are all for chip users. Might as well keep 4977 or EvoX M7...
Post by: JohnnyDoemrong on November 18, 2003, 04:31:00 PM
Post by: dacke on November 18, 2003, 04:33:00 PM
I have a PAL v1.4, 120GB Seagate hdd, TSOP flashed X2 4979 BIOS...
Post by: JohnnyDoemrong on November 18, 2003, 04:52:00 PM
Post by: dacke on November 18, 2003, 04:58:00 PM
Post by: JohnnyDoemrong on November 18, 2003, 05:03:00 PM
Post by: LESTAT on November 18, 2003, 05:16:00 PM
i dont have all those games, most the ones i do have all work fine,
i dont have the sprts ones except top spin i have that, and it works fine.
if you cant get THOSE games to work, which work on a modded xbox. meaning font exploit audio exploit, PBL modchip and TSOP,, if YOU cant get them to work then there is something seriously wrong with your xbox. whatever hack or modchip your using.
getting dirty disk errors while playing from the hard drive is a bad thing.
are you using an 80 cunductor IDE cable, ie Ultra100 cable ? if so get rid of it and put the regular back on.
your looking at games that owrk for 99% of the people. now granted there are those who have one or two games that dont work but you have a whole shit load. there is something wrong with your set up.
there are TWO versions of 4979 which one are you using.4979.06 or 4979.67 ?
and have you tried using X2 4977 ? A L L of those games work with 4977..
and i am not accusing you of anything, but. ALL thos egames are ones that if you had downloaded them, are KNOWN to be bad or give troubles, but if you had actually made a REAL copy with dvd2xbox then the problems are not there.
Post by: JohnnyDoemrong on November 18, 2003, 06:58:00 PM
Post by: LESTAT on November 19, 2003, 01:44:00 AM
Post by: desertboy on November 19, 2003, 04:08:00 AM
| QUOTE (feflicker @ Nov 19 2003, 02:28 AM) | ||
Makes no sense for a softmod user to upgrade to this new build anyway, the "enhancements" are all for chip users. Might as well keep 4977 or EvoX M7... |
Why does it make no sense?
X2 IGR is vastly superior to evolution-x's, it has 1.4+ support and large hard disk support built in both of those are features I might well want if I was a softmod lad.
X2 4977 no 1.4+ support, M7 no IGR.
Doesn't X2 bios support no dvd check (available in xbtool for M7 I believe) and no video cable check (Good for us lan junkies)
Post by: heinrich on November 19, 2003, 07:01:00 AM
| QUOTE (desertboy @ Nov 19 2003, 08:08 AM) |
| X2 IGR is vastly superior to evolution-x's |
The only thing I have yet to see work with evox's IGR in 3921 is FlashX. And for those that play emus/games off of dvd, evox's works better in that it returns you to the dash, where x2's resets the xbox, and of course, your game or whatever will run again. The way I see it: if you are using evox as your dash, use that IGR, if you are using any other dash, use x2.
Post by: LESTAT on November 19, 2003, 12:18:00 PM
these "back ups" your using what did you use to back them up ?
are you patching the games for media checks ?
i know the 4979 has built in media check removal but dont rely on that to work for YOUR set up. it may not.
use Craxion or ADR to patch all the ISO files or all the XBE files.
and i mean patch ALL the xbe files in every game.
if you dont patch them and IF 4979 doesnt work good for media checks, then your blank screen on start is exactly what happens when you have NOT removed the media checks.
your questions REALLY need to be asked in the back up forum, so be sure to ask people over there. i dont think this is a bios issue.
Post by: feflicker on November 19, 2003, 03:08:00 PM
| QUOTE |
| X2 4977 no 1.4+ support, M7 no IGR. |
Yeah, that is pretty much the only benefit I suppose... I thought of that when I was typing my response, but it seemed like something minor in my opinion... (Figured if you could play backups without a modchip, then an effective IGR would not be an issue...)
| QUOTE |
| The only thing I have yet to see work with evox's IGR in 3921 is FlashX. And for those that play emus/games off of dvd, evox's works better in that it returns you to the dash, where x2's resets the xbox, and of course, your game or whatever will run again. |
I know how you feel! I voiced my opinion in the "bios enhancement" post several times... Instead of "IGR" (In Game Reset), what we all really want is "IGRTD" (In Game Return to Dash). The current IGR implementation only helps when running games off of the HDD... For us dvd users, it isn't all that helpful... I also asked for "IGSD" (In Game Shutdown) but no one has done that either
Post by: Pobbe on November 19, 2003, 09:50:00 PM
Change the dvd boot name with xbtool if you don´t want it to boot of the dvd.
Post by: Pobbe on November 19, 2003, 10:22:00 PM
| QUOTE (JohnnyDoemrong @ Nov 20 2003, 09:11 AM) |
| You talkin to me? |
No
Post by: heinrich on November 20, 2003, 12:39:00 AM
| QUOTE (Pobbe @ Nov 20 2003, 01:50 AM) |
| The x2 IGR does return you to the dash, it doesn´t reboot the xbox. |
Run a game from DVD, use the x2 bios' IGR, and tell me what happens.
Post by: broona on November 20, 2003, 12:51:00 AM
Xbox 1.1
Bioxx
Evox +3921
Standard hard drive
Was Evox 3.6, now Xecuter2 4979.06
Post by: Pobbe on November 20, 2003, 04:35:00 AM
| QUOTE (heinrich @ Nov 20 2003, 11:39 AM) |
| Run a game from DVD, use the x2 bios' IGR, and tell me what happens. |
Ok, then it will reboot the game, I know, but I thought you talked about a cold reboot when you said that the x2 igr resets the xbox. Sorry about that.
But as I said before, you only need to change the dvd boot name with xbtool to get around that problem. But I get your point.
Post by: feflicker on November 20, 2003, 11:28:00 AM
| QUOTE |
| But as I said before, you only need to change the dvd boot name with xbtool to get around that problem. But I get your point. |
If you did that, you could never direct boot originals/backups (unless the original MS$ bios was loaded)? Right? (Unless I renamed the XBE on all the dvd-r's that I have already burned to this new name the bios is looking for -- don't see how that is possible...)
Maybe I am missing what you are saying... Heinrich, am I lost?
Post by: Rahszhul on November 20, 2003, 12:23:00 PM
My question? I'd prefer to have one large F:, but is it suggested/recomended that I split the remaining space to F: & G:?
Thanks in advance.
Post by: feflicker on November 20, 2003, 01:31:00 PM
| QUOTE |
| My question? I'd prefer to have one large F:, but is it suggested/recomended that I split the remaining space to F: & G:? |
Take advantage of part6 and part7. Just like Windows, it is better to have 2 150GB partitions then 1 300GB... Almost all of the apps out there are easily configurable to use both drives...
Post by: heinrich on November 20, 2003, 01:56:00 PM
| QUOTE (feflicker @ Nov 20 2003, 03:28 PM) | ||
If you did that, you could never direct boot originals/backups (unless the original MS$ bios was loaded)? Right? (Unless I renamed the XBE on all the dvd-r's that I have already burned to this new name the bios is looking for -- don't see how that is possible...) Maybe I am missing what you are saying... Heinrich, am I lost? |
hehe, that wasn't my suggestion
Post by: feflicker on November 20, 2003, 04:00:00 PM
| QUOTE |
| hehe, that wasn't my suggestion |
I know, I was asking if you were making more sense out of Pobbe's latest response than I... (since you were actively involved in the same discussion...)
Post by: heinrich on November 20, 2003, 04:16:00 PM
Or I can just continue to use the IGR in evox and not worry about it....
Post by: feflicker on November 20, 2003, 04:51:00 PM
| QUOTE |
| This presents a problem when you want to boot to an evox disc or what not, but I guess thats what we have multi-bank chips for.... |
Ok, that is what I thought was being suggested. That is not the most "user friendly" of options, as booting from default.xbe on the dvd drive is fairly important
So, Ubergeek, if you ever feel like adding it, "IGRTD" (In Game Return To Dash) would be the only other feature I can think of adding to this awesome bios
Post by: Pobbe on November 21, 2003, 03:12:00 AM
| QUOTE (feflicker @ Nov 21 2003, 03:51 AM) |
| Ok, that is what I thought was being suggested. That is not the most "user friendly" of options, as booting from default.xbe on the dvd drive is fairly important |
Actually it isn´t that important to boot the default.xbe
I have set the dvd boot name to xbox.xbe in my bios, and if I fuck up my dash or something so I need a boot cd I´ll just make one, naming the xbe xbox.xbe instead of default.xbe.But shure, it would be easier with an "IGRTD".
Post by: feflicker on November 21, 2003, 08:25:00 AM
| QUOTE |
| Actually it isn´t that important to boot the default.xbe |
You can't direct boot games... Not major, but still something I would rather not lose
Good discussion, maybe Ubergeek will get some ideas