Post by: Lysip on June 10, 2004, 12:10:00 PM
Post by: PENiX on June 12, 2004, 04:20:00 PM
I want to know the same thing.
Post by: rob1309 on June 13, 2004, 08:00:00 AM
no clue what happened to it...
Post by: ViNCe_V on June 13, 2004, 10:18:00 AM
Apparently they have finished a 256K debug bios for the conexant chip, but not the focus one. They have not yet released the conexant version for reasons beyond me. I did meet a guy who had a beta? (or could have been final) version of the conexant one.
The development of the bios may have been put on the back burner once the v1.6 hit stores and every team started working on that.
Post by: rob1309 on June 13, 2004, 04:37:00 PM
too bad it isn't out to the public yet
Post by: fff on June 13, 2004, 10:43:00 PM
But it's true that the 1.6 stories, bug fixes and others stuff have delayed it for a long time.
As Vince_V says, a connexant version works.
Keep in mind that we don't want to release a buggy bios. Yoshi and our team are new on the scene so we don't want to make a mistake.
Please be patient
FFF, team Gueux' Net
Post by: rob1309 on June 14, 2004, 04:26:00 AM
ahwell i'm just happy there's one that actually works for the 1.0 and i will finally be able to stop using bios loader all the time for debug bios
Post by: fff on June 14, 2004, 05:44:00 AM
Post by: rob1309 on June 14, 2004, 09:27:00 AM
Post by: fff on June 14, 2004, 12:01:00 PM
And we don't want complain by "Focus" people having flashed their SST with the wrong bios.
Post by: ViNCe_V on June 15, 2004, 04:14:00 PM
| QUOTE (fff @ Jun 14 2004, 09:01 PM) |
| Understand that we don't release only the connexant version because we said we would release all in one time. And we don't want complain by "Focus" people having flashed their SST with the wrong bios. |
Its sad that a few stupid people have to ruin i for everyone else.
But, its up to you guys, after all, it is your bios. But, wouldn't it also be good to release the conexant bios now, instead of having to wait another few months dealing with the v1.6 and other projects, before you can get back to working on the focus one.
And, it was a while before the focus debug bios was released, but many people didn't make the mistake of formatting with the wrong debug bios (except in the beginning when people didn't realize there was a different gpu).
Or, you could release a beta version to a selected public (like the people in this thread
) and we could further test it for you. I'd gladly be willing to see how well the debug bios works on different versions of xbox's (I have over 7 xbox's, and have every version, except the 1.6. I also have the halo xbox to test on).So, how about it? I know I've been dying to get my hands on your great bios. The current one is good, but I hate having to switch back and forth between bios's every time I want to play halo...
Anyway, let me know what you decide.
Post by: fff on June 16, 2004, 10:37:00 AM
For all your requests (that I understand), i CAN'T answer you as I don't take these decisions.
Please be patient, the time will come!
Post by: ViNCe_V on June 16, 2004, 02:02:00 PM
Post by: Lysip on June 16, 2004, 04:12:00 PM
Post by: Yoshihiro on June 18, 2004, 02:32:00 PM
GueuX'NeT
Post by: Flexmaster Frag on June 18, 2004, 05:47:00 PM
Post by: rob1309 on June 18, 2004, 06:17:00 PM
, playin with it now and so far, so goodand no, i'm sure it didn't "ruin" a chip...
bad flashes can happen ya know
Post by: Lysip on June 18, 2004, 08:02:00 PM
Post by: ViNCe_V on June 18, 2004, 09:04:00 PM
Post by: Lysip on June 18, 2004, 10:22:00 PM
Post by: fff on June 19, 2004, 12:22:00 AM
| QUOTE |
| I Have a version 1 xbox NTSC and a whole lot of fragness thanks guys my chip was ruined! I had to pull out the MATRIX and reflash with WIN LPC to recover a big headache if ya ask me. not a very good expirience! |
DO you see now why we didn't want do release these bioses durin the beta tests???
For Halo, i can't answer you, I'm going to see with yosh
Post by: fff on June 19, 2004, 03:40:00 AM
If you encounter other bugs, please post them here.
Thanks
Post by: ViNCe_V on June 19, 2004, 05:39:00 AM
. Anyway, there were also a couple of glitches in Splinter Cell: PT. I randomly froze at times....Although i'm sure this is just a side-effect of using a debug bios on a retail game, it would be nice if a magical fix was produced . I believe the only real problem would be the halo issue. As that is the reason almost all people switch over to XDK for its screen capturing abilities.
Post by: fff on June 19, 2004, 06:15:00 AM
Yosh is working hard on halo bug and on the Svideo bug.
Post by: Lysip on June 19, 2004, 07:36:00 AM
Post by: Lysip on June 19, 2004, 08:07:00 AM
Post by: endresults on June 19, 2004, 08:45:00 AM
EDIT: Already been discussed...my apologies.
Post by: Lysip on June 19, 2004, 10:59:00 AM
Post by: Yoshihiro on June 19, 2004, 04:15:00 PM
one video of halo :
Halo on xbox debug
Post by: rob1309 on June 19, 2004, 04:39:00 PM
it's an issue that certain versions of halo use diff parts on memory which is also used for debug, not that it doesn't have enough
load halo without debug, boot into debug bios and itll load fine but without debug features
and yea this issue has been known since people first tried debug captures on halo
Post by: rob1309 on June 19, 2004, 09:06:00 PM
Post by: ViNCe_V on June 20, 2004, 07:15:00 AM
| QUOTE (Yoshihiro @ Jun 20 2004, 01:15 AM) |
| Halo work now with debug dash i need test other games one video of halo : Halo on xbox debug |
HOLY F*CKING SHIT!!!!!
That's the sweetest thing i've ever seen. I LOVE YOU, you guys are gods...hehe
[EDIT]
Hm....you didn't use the movie capture to produce that video (since it has sound). Does that video just mean halo works with the debug bios now. Or, that it can have screenshots taken too?
[/EDIT]
Post by: rob1309 on June 20, 2004, 07:55:00 AM
you'll never be able to record halo video with sound or even record video at playable framerate cuz xbox just isn't good enough
that vid wasn't debug recorded, just recorded using debug bios obviously so don't get your hopes up bout making your own series of red vs blue hehe
Post by: ViNCe_V on June 20, 2004, 07:57:00 AM
That's too much work for me...
Post by: BCfosheezy on June 20, 2004, 08:05:00 AM
| QUOTE (Lysip @ Jun 18 2004, 11:02 PM) |
| damnit, They dont work with halo. Thats the only reason i wanted it. but no, halo still wont boot. im just pissed now. God there has to be away to get it to work. And you know those douch bag that have the debug halo and wont make a PPF or something so everbody can share the love. Im gona go cry... |
hey motherfucker watch your mouth. I'm not sharing it with anyone because you can't run it anyways... it gives you the same black screen as you get with the current version you're trying to run.(when trying to run on retail xbox- patched to debug or not) also the xbe isn't the same size as the original version so you can't make a ppf. so keep crying until yoshi hooks you up bitch.
also I think the reason you can't take screeny's while the retail halo is loaded is because it's library's contain nodebug. so it removes all debug features from memory before launching. Yoshi apparently has a fix for this.
Post by: rob1309 on June 20, 2004, 08:23:00 PM
odd than i can still take screens and use xbox neighborhood though
i'm not even sure if it's worth messing with to use the other features again
i have no clue as to what happened....unless i disabled a service that the sdk uses
Post by: fff on June 20, 2004, 11:50:00 PM
Could everybody test this and give me their results?
Yosh keeps on working on this bios, don't matter!
Post by: rob1309 on June 21, 2004, 01:54:00 PM
Post by: ViNCe_V on June 22, 2004, 01:10:00 AM
. All videos are available at the bottom.On a side note - when capturing in 1/4 video size mode, there is no slow down in a game. When capturing in full screen, however, a great deal of slow down occurs. Transferring from xbox to pc also takes a long time (not to mention encoding, or even saving as uncompressed). This is not relevant to the bios, as it occurs on both bios's I tried. 1/2 video size results in a noticeable slow down in a video game, but is still playable. Reading from the xbox and encoding is also MUCH faster than full screen. The video quality also is good (imo anyway, you can judge for yourself below)
Once again, it doesn't work on Halo. But it should work for all other games...
BTW...My settings for the Movie Capture tool were:
- 1/4 Size
- 16 bpp
- Cache frames on Xbox hard disk
- Advanced Options - Minimum time between captured frames: 0
GueuX - Psi Ops (3.7MB file)
GueuX - Psi Ops - FULL SCREEN (3.5MB file)
GueuX - Ninja Gaiden (3.2MB file)
GueuX - Ninja Gaiden - FULL SCREEN (4.2MB file)
GueuX - Ninja Gaiden - HALF (½) SCREEN (3.1MB file)
Unless otherwise stated, all videos used the settings mentioned above. They were exported from Movie Capture in uncompressed format and then re-encoded with Windows Movie Maker, with similar settings (but not the same).
Hope this helps
Post by: Lysip on June 22, 2004, 12:46:00 PM
| QUOTE (BCfosheezy @ Jun 20 2004, 05:05 PM) |
| hey motherfucker watch your mouth. I'm not sharing it with anyone because you can't run it anyways... it gives you the same black screen as you get with the current version you're trying to run.(when trying to run on retail xbox- patched to debug or not) also the xbe isn't the same size as the original version so you can't make a ppf. so keep crying until yoshi hooks you up bitch. also I think the reason you can't take screeny's while the retail halo is loaded is because it's library's contain nodebug. so it removes all debug features from memory before launching. Yoshi apparently has a fix for this. |
Calm down, "motherfucker" is very nice... Dude are you so rich little boy that his daddy work for MS? he hooked you up huh??? well anyway its still a sign to the scene about you hideing useful things from everbody. just because "it gives you the same black screen as you get with the current version you're trying to run" it could still help everybody out it would be a neat thing for everybody instead of just your self. so my guess is you work for MS and thos are pic from them or your rich lil daddy hokked you up. or you dont have it. you found the pics and your fooling everbody... goodluck
Post by: rob1309 on June 22, 2004, 02:45:00 PM
EDIT: btw, only thing keeping me from using this as default bios again is that i had problems launching apps i use to flash my 256k chip so have to flash using external programmer and my chip has switches installed so it's not exactly fun to do
all i really want is for it to launch evox 100% each time cuz that's what i prefer for flashing
Post by: BCfosheezy on June 22, 2004, 05:21:00 PM
| QUOTE (Lysip @ Jun 22 2004, 03:46 PM) |
| Calm down, "motherfucker" is very nice... Dude are you so rich little boy that his daddy work for MS? he hooked you up huh??? well anyway its still a sign to the scene about you hideing useful things from everbody. just because "it gives you the same black screen as you get with the current version you're trying to run" it could still help everybody out it would be a neat thing for everybody instead of just your self. so my guess is you work for MS and thos are pic from them or your rich lil daddy hokked you up. or you dont have it. you found the pics and your fooling everbody... goodluck |
you're wrong on all counts and it's obvious that you're a jealous fool. Try not to make yourself look any more ignorant than you already have. So you don't have the debug version of halo and you never will and I do... so what? get over it junior.
Edit: also, how could it be a neat thing for everyone if only the people that have real debug kits can run it? I explained this to you but you obviously are not intelligent enough to comprehend. This is in no way useful to you or anyone else. It's merely a neat little toy... one of which you are not privelidged enough to have.
Edit: and further more, just to rub it in your face and make you feel that much dumber... go ahead and tell me what you'd like me to take a screencap of in halo. I'd be glad to do it and post it for all to see how truly stupid you are.
Post by: rob1309 on June 22, 2004, 05:50:00 PM
Post by: BCfosheezy on June 22, 2004, 06:10:00 PM
| QUOTE (rob1309 @ Jun 22 2004, 08:50 PM) |
| lysip, he actually does have a real debug kit i know from someone who knows him |
and does my dad work for ms or is he rich? ask andrew
Post by: rob1309 on June 22, 2004, 06:22:00 PM
he's been online a few times in irc but that's bout it
Post by: ViNCe_V on June 22, 2004, 08:04:00 PM
I too could get it a debug kit, and a debug halo, only it is not worth it. Why waste all that cash on something that is useless to me. I just want to play retail halo on a debug bios, which is what this thread is about.
Post by: Lysip on June 22, 2004, 09:12:00 PM
As for the 256K bios, Im glad someone is working on it but it sadens me that you cant take pictures yet. oh well. I guess eather someone will find away or we will have to wait for halo 2 anyway hope to have some good times playing it.
Post by: dankydoo on June 22, 2004, 09:26:00 PM
later,
dankydoo
Post by: Lysip on June 22, 2004, 09:40:00 PM
Post by: ViNCe_V on June 22, 2004, 09:51:00 PM
). And, it also helps to not have to run the nodebug.xbe, its not that big of a deal, but, nevertheless, its nice to have.
Post by: BCfosheezy on June 23, 2004, 04:30:00 AM
| QUOTE (ViNCe_V @ Jun 22 2004, 11:04 PM) |
| BCfosheezy, its just that in every post about a halo project in debug format, you go nuts and so...."oh, I have a copy. But it doesn't matter, cause it won't run. I am not contributing to the thread in any way. I just thought i'd say that I have one. HA!". This thread was not about a debug halo, it was about getting RETAIL halo to run on a debug bios. Not necessarily having all the debug features, but simply to be abel to play it. Therefore, your post is irrelevant, and I can see why lysip would be aggrevated by it. By the way, i'm not jealous I too could get it a debug kit, and a debug halo, only it is not worth it. Why waste all that cash on something that is useless to me. I just want to play retail halo on a debug bios, which is what this thread is about. |
to all of these posts that say I contributed nothing to the thread and that I just came in here for a flame war....... you need better reading for comprehension skills. I didn't even post until I was called a douche bag. Maybe you have a hard time reading the words and understanding what they mean. Vince I think the only reason you really posted in this thread was to flame me. Actually I know it was. You didn't contribute to the topic at all either so your whole post was hypocritical. and dankydoo is just a moron. If you read the whole thread and saw what provoked my replies you should have no problem with what I said. If you do.. there's something wrong with you.
Edit: and really what I was trying to do was show lysip, who keeps getting mad that I have it but won't distribute it.. that even if I DID distribute it nobody can do anything with it. Most people can even run it and even if they can it's useless. I only said I have it and you don't after he got really mad and flamed me (because I called him a motherfucker
) So I'm not bragging about it... merely defending myself and the fact that it's useless to distribute this file since it will help no one. so fuck all you bastards that have a problem with what I said. You can lick on my nuts bitches.
Post by: ViNCe_V on June 23, 2004, 07:23:00 AM
| QUOTE (BCfosheezy @ Jun 23 2004, 01:30 PM) |
| I didn't even post until I was called a douche bag. |
Nevertheless, you posted in a very childish manner. You could have simply said, "The debug version of halo has many differences between the regular version. It has already been proven that a debug halo won't run on a retail xbox, only on a devkit. So, there is no point in a ppf, as it would accomplish nothing. I would wait for Yoshi to make a fix for halo, as he seems the only one able to do so. Anyway, debug halo + retail xbox = useless."
| QUOTE (BCfosheezy @ Jun 23 2004, 01:30 PM) |
| Vince I think the only reason you really posted in this thread was to flame me. Actually I know it was. You didn't contribute to the topic at all either so your whole post was hypocritical. |
Hypocritical???
I have been posting useful posts since the beginning of this thread. I tested out the bios's video capturing features, I gave an in-depth review of what the bios does on a version 1.0 xbox flash, etc. (meaning, check the rest of the post for more examples). And I only flamed you (in a more mature manner I might add) because you were flamming other people in the topic. If you dont have anything nice [or contributing] to say, don't say anything at all. And I realize this post is not really contributing, nor nice, but I believe it is necessary nonetheless.I wish there was an ignore feature on these forums
Such so that I would not have to view the posts of certain users, making it easier to have a valuable and informative thread. Anyway, back to the topic at hand.I found another problem with the bios, although, once again, it may just be the problem of using a debug bios (i tried both the 256k from gueux and 512k from complex). Driv3r does not want to load any levels with a debug bios. Works fine on a x2 4983 bios though. This is the case when using the dvd-rom of the game, and when using dvd2xbox to run it off of hdd. Although I do not need, nor believe in, a fix, I just thought it would be useful to mention.
Post by: BCfosheezy on June 23, 2004, 12:40:00 PM
| QUOTE (ViNCe_V @ Jun 23 2004, 10:23 AM) |
| Nevertheless, you posted in a very childish manner. You could have simply said, "The debug version of halo has many differences between the regular version. It has already been proven that a debug halo won't run on a retail xbox, only on a devkit. So, there is no point in a ppf, as it would accomplish nothing. I would wait for Yoshi to make a fix for halo, as he seems the only one able to do so. Anyway, debug halo + retail xbox = useless." Hypocritical??? I have been posting useful posts since the beginning of this thread. I tested out the bios's video capturing features, I gave an in-depth review of what the bios does on a version 1.0 xbox flash, etc. (meaning, check the rest of the post for more examples). And I only flamed you (in a more mature manner I might add) because you were flamming other people in the topic. If you dont have anything nice [or contributing] to say, don't say anything at all. And I realize this post is not really contributing, nor nice, but I believe it is necessary nonetheless.I wish there was an ignore feature on these forums Such so that I would not have to view the posts of certain users, making it easier to have a valuable and informative thread. Anyway, back to the topic at hand.I found another problem with the bios, although, once again, it may just be the problem of using a debug bios (i tried both the 256k from gueux and 512k from complex). Driv3r does not want to load any levels with a debug bios. Works fine on a x2 4983 bios though. This is the case when using the dvd-rom of the game, and when using dvd2xbox to run it off of hdd. Although I do not need, nor believe in, a fix, I just thought it would be useful to mention. |
First of all... childish or not you got the point of what I was saying by what I said and that's all that matters. I'm not you so I don't have to use your phrasology. Hypocritical yes because the post towards me had no relavance to the topic.. plus what you said about the topic made no sense. If you just wanted to run halo with no debug features on the debug bios... why not just unmod your xbox and use the retail kernel? It doesn't make any sense. Anyways I know you don't like me because I've tried to help you in about 3 other topics and I corrected you and no one likes to be corrected. Sorry about that.. I actually liked you up until now. And you said you only flamed me because I was flaming... well I've already said this but I'll say it again. I only flamed because I was flamed.
I liked the part about the ignore button. Like my attitude or not I still know a thing or two that are relevant to discussion and when not provoked I can be pretty helpful. So that ignore button could make you just like it implies "IGNORant". I'm not saying I know everything but I can definitely help some people out here and there.
Also just to try to put an end to the flaming let me put a little useful information forth. The reason the 256k bios helped everyone out is because the image is mirrored 16 times in memory. With a 1 megabyte bios it take up obviously 16 megs. Knowing that the xbox has shared system and video memory, this leaves very little room for tinkering. 4 megabytes versus the 16 megabytes is a pretty good gain. Then when you run nodebug that throws out the debugging features and frees up more memory. This is really the cause and this is also why the debug units are able to play everything flawlessly. If you already knew this fine. If not fine. I'm just trying to contribute now and I am going to test and see how much memory the debug version of halo takes up when running. (I cannot test a retail version because of the previously stated library that disables debug features.)
Post by: ViNCe_V on June 23, 2004, 01:10:00 PM
| QUOTE (BCfosheezy @ Jun 23 2004, 09:40 PM) |
| If you just wanted to run halo with no debug features on the debug bios... why not just unmod your xbox and use the retail kernel? |
I want halo to run on a debug bios, I don't care about the debug features. This will allow me to keep just one bios on my xbox. No need to re-flash or use PBL or nodebug.xbe. Its not too important, but I would like this feature
Post by: Lysip on June 23, 2004, 05:11:00 PM
Post by: rob1309 on June 23, 2004, 06:36:00 PM
Post by: Lysip on June 23, 2004, 07:26:00 PM
Post by: BCfosheezy on June 23, 2004, 08:22:00 PM
| QUOTE |
| "I'd be glad to do it and post it for all to see how truly stupid you are." -BCfosheezy Truly a sign of an ignorant man. |
post a link to this thread so at least people can see all statements in context.
Post by: rob1309 on June 24, 2004, 12:38:00 PM
66 posts now wow!!!
this is getting very big for a topic relating to one specific bios
also any news on loading issues? cuz if i can't load evox to flash, i can't use as default
Post by: ViNCe_V on June 24, 2004, 03:32:00 PM
| QUOTE (rob1309 @ Jun 24 2004, 09:38 PM) |
| also any news on loading issues? cuz if i can't load evox to flash, i can't use as default |
what? evox doesn't load for you? It always loads fine for me...
Post by: Lysip on June 24, 2004, 06:14:00 PM
Post by: rob1309 on June 24, 2004, 06:50:00 PM
also some other chip flashing app failed
Post by: Lysip on June 24, 2004, 07:09:00 PM
Post by: rob1309 on June 25, 2004, 11:03:00 AM
ohwell not a problem
Post by: ViNCe_V on June 25, 2004, 03:33:00 PM
Post by: rob1309 on June 25, 2004, 05:37:00 PM
Post by: Yoshihiro on June 30, 2004, 10:15:00 AM
added :
1 : Launch evox under debug dash and all xbe retail
2: Launch all game retail under Debug dash (like Halo
)3: Launch all linux code under debug dash
Post by: bucko on June 30, 2004, 10:26:00 AM
love the color mods to .
Post by: Yoshihiro on June 30, 2004, 11:21:00 AM
Video of linux.xbe
Post by: rob1309 on June 30, 2004, 06:49:00 PM
the one thing that could make it a perfect bios.....built in IGR
dunno if possible but i would set it back to my default bios with built in IGR like x2 bios has
i know it has reboot via pc but sometimes my box isn't near the pc blah blah
anyways keep up the great work
i'll start crossing my fingers now
Post by: fff on June 30, 2004, 11:50:00 PM
Post by: rob1309 on July 01, 2004, 12:46:00 PM
Post by: Lysip on July 01, 2004, 11:30:00 PM
Post by: rob1309 on July 02, 2004, 12:19:00 PM
Post by: Lysip on July 02, 2004, 07:24:00 PM
Post by: TeonHarasymiv on July 02, 2004, 07:51:00 PM
What else do I need to actually use the features, and also, what exactly will this bios let me do?
Lastly, what size is the normal debug bios, and what does it have that this doesn't?
(I have a smartXX so I can fit a bigger bios on if it is better).
Thanks.
Post by: rob1309 on July 02, 2004, 08:07:00 PM
the bigger ones don't have better stuff either
Post by: TeonHarasymiv on July 02, 2004, 08:11:00 PM
Post by: rob1309 on July 02, 2004, 08:15:00 PM
very very nice
Post by: MicroChip on July 03, 2004, 04:10:00 AM
| QUOTE (Yoshihiro @ Jun 30 2004, 08:21 PM) |
| One video of linux xbe under debug dash Video of linux.xbe |
Hey Yoshihiro. You started to explain to me the other day on IRC the reasoning behind a bios for the 1.6 box being so different and taking so long for you or any other group to produce. Something about it taking 5 files, not 4.
Would it be possible for you either here or in a new thread in the bios forum to explain in a bit more detail what's so different about the 1.6 and its bios, and why it isn't just a simple matter of hacking it up to release a working bios? I think that might keep people from asking and expecting a hacked bios for the 1.6 like 50 times/day in these forums, it'd probably even make a good sticky thread, and you definitely seemed like the qualified person to write it.
Thanks!
MC
Post by: smokeingit on July 03, 2004, 07:47:00 PM
| QUOTE (Lysip @ Jun 23 2004, 06:11 PM) |
| Anybody know why he still has an X-S account??? ya think he would have gotten banned by now??? |
Dont know why he has to be a dick...
Post by: BCfosheezy on July 03, 2004, 09:00:00 PM
| QUOTE (smokeingit @ Jul 3 2004, 10:47 PM) |
Dont know why he has to be a dick...  |
hahahaha how hypocritical of you... but I do think it's hilarious.
Post by: smokeingit on July 03, 2004, 09:40:00 PM
Post by: TeonHarasymiv on July 03, 2004, 10:15:00 PM
Post by: bucko on July 04, 2004, 07:40:00 AM
(PBL1.4.1 by gueux.rar). I have Debug bios 256 V2 and XDK 5558 installed.
Post by: rob1309 on July 04, 2004, 04:19:00 PM
Post by: bucko on July 05, 2004, 03:18:00 AM
Post by: rob1309 on July 05, 2004, 11:25:00 AM
also, you might wanna try pbl 1.3 or whatever cuz it's signed for modchip use and the other versions aren't
Post by: Lysip on July 09, 2004, 06:08:00 PM
Post by: bucko on July 10, 2004, 04:32:00 PM