Print

[pjfan281]

gotta say these guys are sloppy. bios errors....chip delays...whats next =P

[SniperKilla]

QUOTE (pjfan281 @ Apr 7 2004, 04:51 AM)

gotta say these guys are sloppy. bios errors....chip delays...whats next =P

heh, i dont think you know what goes into making a chip that caliuber of the xecuter 3

its alot more then soldering some chips to a PCB and shipping it out...

and also, i dont see anyone else pushing xbox bios's to the level that the xecuter team is, so i wouldent be talking shit and or expecting every release to be 100%....


BTW smooth sailing here with 4982 on tsop running avalaunch 0.48.70

[k3rn3l]

QUOTE (cool_guy @ Apr 7 2004, 05:25 AM)

k3rn3l, please do your team and the scene as a whole a favor - get some beta testers, and use them.

we did - all worked fine

but they dont get paranoid about keeping cromwell on their mods as they are confident so all flashed the 1mb file we gave them

I guess we should have tested every single eventuality before release - We humbly apologize  

[cool_guy]

Well, its not like this is the first time.  One would think that over time you would learn to test every possibility (at least on your own chips).

[82ross]

Update: The problems below occured when flashing a 256k version of the bios to 3 and 4 seperately. When 3+4 was flashed with a combined 512k version everything works fine. All programs load and none of that crazy shit i wrote about below happns.

[In one case a 512k 4982.06 flash on banks 3+4 corrupted a (previously working) 512k 4978.03 on 1+2 (1+2 wouldnt make it past the fluuber anim) Havent been able to recreate since reflashing. Putting it down as a freak occurance.]
-------------------------


Im having the same problems.

X2 Lite Origional Version
4982.06
XB version 1.1

Flashed with FlashX 1.2
Using RemoteX dashboard.

When flashed to banks 1+2 Dash loads, nothing after that.


On banks 3+4 i get a very wierd problem. Flashing any previous X2 bios to 3+4 they can be read fine. Flashing this new bios, the chip seems to boot from banks 1+2 still.


Ive repeatedly tested it, wierd problem

Example

1+2            3+4
4978.03      4982.06        
booting 1+2 4978.03 loads as normal
booting 3+4 evox bios hash still shows as 4978.03 and bios ftp is available

1+2            3+4
4982.06       4978.03        
booting 1+2 bios/dash loads but programs dont, evox recognises 4982.06
booting 3+4 4978.03 loads as normal

Ive tried this with 4981.06 and 4982.06 and also 4979.06.bin and 4982.06.

All other combos of bios work as normal.


Ive tried todo this as many times as i can to make sure that still being up at 7am isnt  affecting my judgement

Im gonna keep fucking about with it anyway. As far as im concerned keep up the good work k3rn3l. Its appreciated here.

[jive]

cool guy: Be happy you have a free bios to play with. if you dont have anything constructive to say, then dont.

We are clearing up our threads right now in the teamxecuter forums and if you have any PERTINENT info which may help in figuring this out, please post in this thread  http://www.teamxecut...ewtopic&t=11788

Also here is the latest on the bios:

Xecuter:

QUOTE

Ok I have duplicated the problem - a weird one for sure btw thanks for everyones input There seems to be some bug where it doesnt like being on banks 1 & 2 of X2 lite - and if you have another bios on banks 3 & 4 (havent tested pro just yet) I have been testing as a full 1MB flash this is why didnt see this at first I flashed a full 1MB with banks 12(4982) and banks 34(cromwell) Indeed it crashes on loading an xbe from dash I flashed a full 1MB with banks 12(cromwell) and 34(4982) - worked perfect I flashed a full 1MB as 4982 and both banks 12 and 34 with 4982 - worked just fine also (this is what we were testing with originally) Also people who are getting corrupt slave drive info in AVAlaunch - I find this is when you boot up the xbox with a disc in the dvd rom unit (i tested with a cromwell disc. This happened on AVA 0.48.64 and with other bios versions too so is not an issue with the bios) I wonder which basher is the first to jump about the fact that its buggy on our own chips

Ok, so its confirmed, bios doesnt run well on bank1/2 (xbe dont boot off a dash) of a lite chip when there is a DIFFERENT bios on bank3/4   but will run fine if all banks are 4982. Thats the latest.

[SniperKilla]

weird problem i have it in the "3rd bank" position on my tsop, after the 512k debug, and before the 256k 4981.06 blue animation, and its fine

[Xbox-Savage]

Xbox v1.0
Xecuter 2.2 PRO
120GB HD with 50 games (all work with 4982)
Running THC DASH as main


 Runnng smooth here.  

[k3rn3l]

Rom = "X2 4983.06 - 256k",0x5a1e9bce94dd8183906745841850f839
Rom = "X2 4983.67 - 256k",0x80690587d8b936dd5c3e689fcaef8ae6

[k3rn3l]

QUOTE (SniperKilla @ Apr 7 2004, 06:28 AM)

weird problem i have it in the "3rd bank" position on my tsop, after the 512k debug, and before the 256k 4981.06 blue animation, and its fine

thats not a weird problem SK

anything after the first 512k is fine if its a mixed setup

i think i know what it is but im tired - ill sort it later

[k3rn3l]

http://forums.xbox-s...howtopic=198557

[CrayZEE]

QUOTE

and its not about insulting our users - its about insulting persistent bashers who have nothing better to do than post crap about us every day.

Well he made an asslong post (that basher as you call him, in your place i'd call
him a paying customer i would care for his problem). Indeed i'd rather see it as
he wanting to help you, find out why it acts weird in his situations, so you will fix
it. All you given him back was rudeness, where he just given you a properly written
bug report. Indeed he added some notes of frustration to it, think you paid money
for a modchip that has the error, from the modchip maker that makes the bios.

QUOTE

The bios is free. Not paid for and used by other Mod makers. Without it their chips are worthless to the majority.

The paying factor was said above, i don't need to repeat.

Actually, your bios's don't add much, we got IGR (EvolutionX dashboard had it
2 days after that, you don't add a feature to a dash within 2 days, or copy it,
it required work too) and now after many months the Xbox Live Blocking was added, but i just read a post below, that someone got banned using 4982, that
is indeed not a good sign if its only working half.

The last big step was done by paul_b if you remember, its the LBA48 patch, which
seemed so easy, yet never made by xecuter. Why not? because it wouldn't sell
more modchips; and an X3 as only LBA48 modchip would have rocked for your
wallet, no?

QUOTE

where were those guys when the xbox was first cracked and where they when LPC was cracked ?

Well actually, you were the first to publish it, that you were the first to know it;
i can't say yes or no to it. Was it only for the good of the users? I don't think so.
It was again marketing strategy, "if we get our mods working via LPC, with less
solderring required, and working on 1.3+ machines, we get more customers,
as we are the first modchip to ship it"
This indeed doesnt look to me like xecuter did it out of just being good guys.
It of course was to be the first to get all the people with newer xbox's feeded,
and have a monopoly for a range of time.

Just thinking of it, the Xtender, 29 modchip
(which didnt use the TSOP like enigmah did, and enigmah as we all know is team
xecuter), it still works on all machines. So was LPC necessary? I'm rather concerned when MS will ban all those LPC modchip users because the 3.3v
we take from the LPC bus are noticeable, then you given more of a problem then
a gift.

Of course its all a matter of opinion, and i kinda bash xecuter from time to time,
but if there was a properly 100% working modchip, i wouldn't have ever said a
word, and could say to anyone who asks "you can buy any modchip, all are good
to go". But the issues with Xecuter modchips are really giving alot of trouble to
people.

[k3rn3l]

http://forums.xbox-s...howtopic=198557

[CrayZEE]

QUOTE

We dont have to make the bios but we do. Xenium Smartxx and all the others make didly squatt in that area.

Oh, so only because they arent making a bios, they're doing less? To remember
you, their OS is out, and thats work too. It's by far more innovative to work
on something new, aka an OS on the modchip, then touching the bios. Plus there
isn't much more necessity to bios development, they leave you the area, be
happy it is that way.

If i had the choice to work on an onboard OS or a bios another team works on
since years, i'd do the thing nobody done before

QUOTE

It is far more complex to add hacks to a kernel than it is to code xbe.

Complexity doesnt matter, its the result that i see which matters. And if your
coders worked 300 hours more then evox coders on it, the result is nowadays
the same.

I'm tired of your blunt replies, you keep on ignoring straight facts, and trying
to make xecuter look good all the time.
I said what i felt was necessary, and in the end of the day, users can read what
i said, and if it only shows some people the way i think about xecuter with reasons.
It's their decision to choose your mod, or another modchip, and as your bios
seems to work better on other people's modchips, i sure recommend those. I can
use all banks with different bios's without a problem, this isnt the case using the
latest bios from the same team, sad sad sad.

Have a good one!  

[k3rn3l]

http://forums.xbox-s...howtopic=198557