Print

[SlaYer]

!! WARNING FROM SLAYER: !!

Do not use the initial X2 4980 Bioses YET!!!

There is still a posibility of getting banned by XBL if the game updates your dash ( Unreal Championship is an example )

Team Xecuter is aware of this so please wait till they patch this issue!

[jusluv2play]

[screamstone]

Searched this thread... and didn't see my answer. Also searched rest of forums for info... Apologize if I missed it (start getting fuzzy around page 30).

Created a new bios for myself, added the bios name and hash to my evox.ini... and I'd like to flash from within evox. Can I simply add a line to the .ini to make it do it like the installer? I did this with 2.1, but can't remember how. I have already copied my new bios to c:BIOS and F:BIOS

What would the code for my .ini be to add a menu item to flash chip with this bios (modified 4979.67)?

Thanks! Slayers is the best... got my foot in the door- working on my own installer... just have to learn how to create the ISO properly... never reads mine right...

rs

EDIT---

Got it figured out. Didn't realize it was a feature of EVOX... thought it was something that the Slayer's installer did. check out the evox thread if you have the same question... it's relatively easy.- in the Pinned FAQ for that forum. (Flashing Bios for NOOBS or something like that).

[GreenArrow2003]

QUOTE (beaglebc @ Jan 6 2004, 03:44 PM)

>>Do not use the initial X2 4980 Bioses YET!!! For those of use who have already upgraded, I am sure it is OK to use the 4980 Bios just DO NOT GO "LIVE"...

What happens if I use this latest release? I've this bios flashed and a Slayer 2.5 installed.

[wireless g]

jusluv2play - come up with Error 13

= 90% of all problems posted here relate to the classic "DVD Drive did not read Media properly"


GreenArrow2003 - What happens if I use this latest release?

= use 4979 till they fix 4980

[meclo]

Hey all,

The new 2.5 kicks absolute @$$, I was at the end of my rope trying to get my 250GB drive up and running!!  Slayer 2.5 made it easy-peazy...I do have one problem though:

I flashed my mod with 4979.67, I have a big ol' F: drive and a big G: drive as well, I can FTP and run games from F: with no problem, but I can't run anything from my G: drive.  I can FTP the files onto G:, and I can see the G: drive from boXplorer, but the games don't appear in the "Launch Games from HDD" menu, nor can I launch the default.xbe file from boXplorer (it takes me back to the main dashboard menu when I try).  I have added the G:Games path to the AutoAdd section of the evox.ini already, and the Settings give me the right size for the G: drive but I can't launch anything from it.  Any ideas?

Once again Slayer kicks ass!!  Keep up the good work bro!

[meclo]

I forgot to add in my last post, is there any benefit to having both F: and G: drives, as opposed to having one huge F: drive?  I see that there are a few compatibility issues with G:, and I'm tempted to fix my problem by flashing with 4979.06 and reformatting my drive...any pluses to splitting up the space between 2 drives?

Thanx again

[ashlvsya]

Can't connect to the channel sum1 pz help

[screamstone]

QUOTE (meclo @ Jan 7 2004, 07:28 PM)

Hey all, The new 2.5 kicks absolute @$$, I was at the end of my rope trying to get my 250GB drive up and running!!  Slayer 2.5 made it easy-peazy...I do have one problem though: I flashed my mod with 4979.67, I have a big ol' F: drive and a big G: drive as well, I can FTP and run games from F: with no problem, but I can't run anything from my G: drive.  I can FTP the files onto G:, and I can see the G: drive from boXplorer, but the games don't appear in the "Launch Games from HDD" menu, nor can I launch the default.xbe file from boXplorer (it takes me back to the main dashboard menu when I try).  I have added the G:Games path to the AutoAdd section of the evox.ini already, and the Settings give me the right size for the G: drive but I can't launch anything from it.  Any ideas? Once again Slayer kicks ass!!  Keep up the good work bro!

Making sure you didn't make the same mistakes I made at first...

First of all, make sure on G you have a "games" folder. (I don't think it's case sensitive.) SECOND... make sure you put your games there. ( I made my folder but missed the folder when I dragged in FTP prog and transferred them all to G: instead of G:games)

Secondly, the line in your .ini must read G:games instead of G:games- copy and paste the F drive line and just change the F to a G. Figured you may have done this right, but in your post you typed G:games... so double check it...

As far as WHY you do a G... not positive, but I think that it has something to do with keeping g hidden from the retail bios, and may have something to do with not even being able to go over 120 GB  on F even with a new bios (like it's a hardware issue.)

I may be wrong in the second half here... but definately check your evox.ini... mine's working off of F&G...

screamsone

[meclo]

QUOTE (screamstone @ Jan 8 2004, 12:28 AM)

Making sure you didn't make the same mistakes I made at first... First of all, make sure on G you have a "games" folder. (I don't think it's case sensitive.) SECOND... make sure you put your games there. ( I made my folder but missed the folder when I dragged in FTP prog and transferred them all to G: instead of G:games) Secondly, the line in your .ini must read G:games instead of G:games- copy and paste the F drive line and just change the F to a G. Figured you may have done this right, but in your post you typed G:games... so double check it... As far as WHY you do a G... not positive, but I think that it has something to do with keeping g hidden from the retail bios, and may have something to do with not even being able to go over 120 GB  on F even with a new bios (like it's a hardware issue.) I may be wrong in the second half here... but definately check your evox.ini... mine's working off of F&G... screamsone

Hey screamstone,

Thanx for the reply...I actually did it exactly like that, copied & pasted the AutoAdd section (partially to get the formatting right, partially 'cuz I'm lazy   )...I re-did my drives, re-installed Slayer's EvoX and utils, made the same changes to the evox.ini file, and for some reason it worked.  I must have messed up something in the evox.ini file, but I don't see what or how...strange!  But there was definitely a Games folder, it was referenced as G:Games (in spite of what my original post may have said...), I don't know.  Pretty weird, but glad it worked, for sure!

Thanks again for the help!


Meclo

[GreenArrow2003]

[1sleeper]

I am having trouble on the IRC.  Seems the biotch isn't handing out love.  Anyone else?

[ashlvsya]

Sorted all working now

[binaryjoe]

*****n00b warning*****

I've done the reading (slayer's Instructions and Readme, as well all every post on this thread) -- but I've managed to f*ck it up anyhow-- in 2 ways:

Current rig:
XBox 1.1
X 2.3 Lite Mod Flashed to XC 4977

Problem #1)
After the xbox has been powered up for a while, when I reboot,  the video is black and white (grayscale to be exact). Otherwise functions normally (sound, dash, etc) -- seems to be heat related, if left off for a while (15-20 min) boots in color as usual.  Any ideas what is wrong?  The modchip functions flawlessly in everyother way (b/w video issue began after mod-chip install).

Problem #2)
I've read and re-read the instructions for using the slayer auto installer to format and use a new larger HD (I'm starting with a cheap 40GB Maxtor before I go crazy) -- but I can't seem to get it to work -- the instructions.pdf is unclear about 1 thing -- after I boot up with the slayer disc (original HD) -- when do I swap the old HD for the new?  Is this a hotswap (ie after the box has booted the slayer disc with the orig HD) - or do I power down and swap, then try to boot the slayer disc with the new HD connected?  Neither appears to work for me--

When I hot swap, video goes out when I plug the power into the new HD.

When I cold swap, I get errors on powerup (no dashfound, bad hd, etc) -- doesn't seem to be booting from the slayer disc at all.

I would appreciate any help you guys could give.

Props to Slayer -- this is great isht.


BinaryJoe

[knownzero]

  Anyways, thanks a bunch for the great software, it rocks.  Your instructions on burning the image helped a lot also, I got it to go on the first try with a Thompson drive and the first cdrw I tried as well (tdk 650M 4-10x burned at 4x with nero).