xboxscene.org forums

Author Topic: Highway 007/mech/flash Pack Process  (Read 56 times)

juno

  • Archived User
  • Newbie
  • *
  • Posts: 4
Highway 007/mech/flash Pack Process
« on: January 27, 2004, 08:34:00 AM »

Hello,
I have the package and was reading the readme files and have some questions that I hope someone could answer. I have MechAssault and have been using it quite successfully with raincoat. Looking for a faster and easier way to do these tsops.

The readme.txt states the following:

Eurasia flash:
   For 007:AUF put 4541000d in e:UDATA
   For Mech Assault put both in e:UDATA
   put the bios.bin in e:UDATA4541000d00000000000 (always)

Evox flash :
   For 007:AUF put 4541000d in e:UDATA
   For Mech Assault put 4d530017 in e:UDATA
   put your bios's in the respective evox bios directory

Now for the Eurasia flash I will have to put both the 451000d and 4d530017 directories into their respective places. I examined the evox.ini in the 4d53001762D648EBF155 and I can see the line pointing to eurasia.xbe in e:UDATA45451000d0000000000 in the evox.ini in that directory. As pointed out by the readme.txt it says to put the bios.bin in that directory always. I assume that this is the bios that eurasia is looking for when trying to flash so I understand that. There is a bios directory in there also with a .txt that tells me to put the bios.bin for evox in there. Going back to the e:UDATA4d53001762D648EBF155 there is also the basic evox bios folder in there. So my confusion is this:

1. Can't I just put the bios.bin 256K in the e:UDATA451000d000000000bios direcotry for evox and the bios.bin in the root for eurasia? I don't understand why I have to put another bios in the MA default e:UDATA4d53001762D648EBF155 bios for evox.

2. If the the bios has to be in e:UDATA4d53001762D648EBF155 bios for evox then what is the bios folder in the eurasia directory? The only thing I can see is this bios folder will be used for 007 evox flashing. Is this the correct assumption? If so then I assume I can put the bios.bin for evox in the MA default evox bios folder and not worry about the eurasia bios folder for evox. Please correct me if I'm wrong.

3. This has probablyl been answered but if you can humor me...I can use evox to flash the 1MB tsop with a 256K as it will resize accordingly and use eurasia/raincoat to flash the winbond chips. Are all winbond chips 256K? I was thinking of just putting 256K bios.bins in their respective directories and not have to ftp over a 1MB bios.bin everytime I encounter one. If this isn't possible can I add two bios to the eurasia directory named something like bios256k.bin and bios1024k.bin or do I they have to be named bios.bin?

I'm looking forward to using this package but I want to understand the process of how the package is working. If this has been answered I apologize as the search function here has been offline quite a bit. I would appreciate any replies to enlighten me of the innerworkings of this package. Thanks.  <
Logged

venturahighway

  • Archived User
  • Sr. Member
  • *
  • Posts: 278
Highway 007/mech/flash Pack Process
« Reply #1 on: January 27, 2004, 09:13:00 AM »

the eurasia path to bios.bin is hard coded.  one bios.bin in the 007 save

evox looks for any bioses in the bios dir of the current working directory.  that depends on what game you loaded it from.  

all winbonds are 256k.  i use eurasia to flash them.  i put a 1M in the evox bios dir (of the game I am loading from)  do 1.0 and 1.1 boxes.  eurasia will not mirror bioses for you, in fact it will refuse to flash wrong sizes

both saves plus a 1M and a 256k is less than 8M (fits on standard memcard) you may be able to get more.

This post has been edited by venturahighway: Jan 27 2004, 05:14 PM <
Logged

venturahighway

  • Archived User
  • Sr. Member
  • *
  • Posts: 278
Highway 007/mech/flash Pack Process
« Reply #2 on: January 27, 2004, 09:21:00 AM »

dup

This post has been edited by venturahighway: Jan 27 2004, 05:28 PM <
Logged

venturahighway

  • Archived User
  • Sr. Member
  • *
  • Posts: 278
Highway 007/mech/flash Pack Process
« Reply #3 on: January 27, 2004, 09:28:00 AM »

QUOTE (juno @ Jan 27 2004, 07:28 PM)
I can put the bios.bin for evox in the MA default evox bios folder and not worry about the eurasia bios folder for evox. Please correct me if I'm wrong.

you mean: you can put the bios for evox in the MA default bios folder and not worry about the evox bios folder for 007

for MA evox flashing, correct.
and you can put more than one and call them what you want.

This post has been edited by venturahighway: Jan 27 2004, 05:28 PM <
Logged

juno

  • Archived User
  • Newbie
  • *
  • Posts: 4
Highway 007/mech/flash Pack Process
« Reply #4 on: January 27, 2004, 09:29:00 AM »

Thanks for the reply it cleared up the previous questions.

Okay so if I use the MechAssault game to run the hack it will use the evox in it's directory (For Mech Assault put 4d530017 in e:UDATA) and locate the bios in the bios folder. So there is no need to add the bios to the bios folder in Eurasia directory as this would pertain to 007 I assume?

Since evox will resize the bios couldn't I just use 256K bios.bin for 1MB tsop? Now I'm not familiar with the eurasia kit but i've read that it will backup the current bios into the root and flash the tsop automatically without having to telnet in and do this manually. Is this correct? This would save me alot of time. :-)

Thanks again, I do appreciate you taking the time to answer.  <
Logged

juno

  • Archived User
  • Newbie
  • *
  • Posts: 4
Highway 007/mech/flash Pack Process
« Reply #5 on: January 27, 2004, 09:30:00 AM »

haha, i was replying and got your other responses too late. Thanks.  <
Logged

venturahighway

  • Archived User
  • Sr. Member
  • *
  • Posts: 278
Highway 007/mech/flash Pack Process
« Reply #6 on: January 27, 2004, 09:32:00 AM »

are you sure evox will mirror when flashing?  not just when backing up?

no telnet required.    <
Logged

juno

  • Archived User
  • Newbie
  • *
  • Posts: 4
Highway 007/mech/flash Pack Process
« Reply #7 on: January 27, 2004, 09:44:00 AM »

I know that the current evox will resize for you but not sure which version is included in the package. Somehow though evox couldn't erase my tsop the other nite but raincoat worked fine.

btw, the first thing i could find to substantiate this is the post by h3inrich in the slayers 2.5 thread in the evolution-x forum. But if anyone uses evox to flash a 1MB with a 256k please share your experience.

Just thought of something else though. I've been using the 3935 evoxdash.xbe to do the flashing and thought that the evox .xbe that comes with the installer is a BFM. Would there be any difference in evox resizing between the two?

This post has been edited by juno: Jan 27 2004, 06:10 PM <
Logged