Topic: Duox2 Installed Fine, Loads Bios Fine, Then Errors (Read 157 times)

WebLOCH · « **on:** June 03, 2005, 09:46:00 AM »

Hey all,

My problem is this... I have installed a DuoX2, I then proceeded to flash it with X2.5032. I then change the colorscheme for the flubber animation so that it was blue.

Now whenever I boot modded, the flubber comes up blue etc and nice, and then at the end it scrambles the screen and shows a "13" in the top corner. I cannot tell why... I should also mention that it can still boot from an EvoX DVD I made up.

I had originally thought that I did not have any valid dash files for it to load, but obviously the original dash is in place, aswell as an EvoX on the HDD aswell.

Any thoughts or any shared stories of woe are welcome!

Regards,
Baris

hippo · « **Reply #1 on:** June 03, 2005, 10:43:00 AM »

I seen this one before.

With me I made my nice orange X bios then it was cool cuz I didn't have to flash and with sunday you are down to one bank. Then I decided toi test the bios on another board and when I booted the other board that orange X it froze and distorted the screen in the flubber exactly as you say.

The fix is to remove your custom ini file from E and let the bios find none and write a new one. But you need another chip to do that. If you are a noob you are fucked without ever flashing your biois and it's corrupt. Enjoy.

Xecuter says this bios is rock solid yet I can find this bug in testing less than 15 minutes. Maybe they hire me as the new tester heh.

ModdingManiac · « **Reply #2 on:** June 03, 2005, 11:40:00 AM »

QUOTE(hippo @ Jun 3 2005, 06:54 PM)

Xecuter says this bios is rock solid yet I can find this bug in testing less than 15 minutes. Maybe they hire me as the new tester heh.

Chancer · « **Reply #3 on:** June 03, 2005, 12:38:00 PM »

If you can boot an Evox boot disc you have no worries. Grab Hackdabox reflash disk and boot from it to flash one of the evox M8+ bios to your chip.
If you still have any remaining dash problems you acn always rebuild the drive with slayers

hippo · « **Reply #4 on:** June 03, 2005, 01:10:00 PM »

Ya maybe just boot to evox and ftp into e and delete the ini. I never tried booting the dvd with mine I had a pile of chips in front of me, also I dont remember error 13.

Chancer · « **Reply #5 on:** June 03, 2005, 01:31:00 PM »

Here Ya go Error 13 Dashboard launch fail (due to missing/bad key, or anything else that would prevent it from running) and the dashboard didn't specify why it failed

Usually a missing or corrupt xboxdashdata folder on C

WebLOCH · « **Reply #6 on:** June 04, 2005, 07:50:00 AM »

Hey guys, thanks for all the attention...

Chancer, I knew the error code and what it corresponded to, and that is why I posted, because there is no dash problem.

hippo, cheers for the advice, I'm going to give it a go now, if it works is it safe to recustomise the colouring?

Wish me luck...

WebLOCH · « **Reply #7 on:** June 04, 2005, 09:21:00 AM »

Mad props to hippo. I deleted the config and it works just fine now, but I have noticed that it did not rebuild a config, so now there does not appear to be one... any ideas? I really wanted to customise the bootup to make it look pretty and change a few of the options...

Clue me in on some more of that wisdom hippo.

Chancer · « **Reply #8 on:** June 04, 2005, 03:47:00 PM »

QUOTE

Chancer, I knew the error code and what it corresponded to, and that is why I posted, because there is no dash problem.

HeHe The error code was a reminder for Hippo as he said

QUOTE

also I dont remember error 13.

hippo · « **Reply #9 on:** June 04, 2005, 06:31:00 PM »

Does the logo not import on a 1.6 on this because I upload the logo and still get the default x3 one and I know I hasd the logo on a 1.4 and 1.0.

Also you are the ones teaching me I only spent 15 mins and found you needed to clear the ini to fix the frozen screen. You found you can still boot from the disk I never even tried.

HackDaBox · « **Reply #10 on:** June 04, 2005, 08:39:00 PM »

Just a heads up guys,

Dont test this new X2 bios on DUOX2 LITE as you dont have the other bank to boot from. Only use it on your own console and have the other bank programmed with a decent bios like X2 4981 or 4983 or Evox M8+.

Don't install this beta crap on a customer's machine. Remeber not everyone is like us , your customers just wanna play games and enjoy the benefits of what a hacked bios offers but most important is stability and ease of use for them.

X3 has an update everyday and the new X2 has an update every second day and each one says ... all the bugs now seem to be fixed... yeah right, this new bios does little more than take me too much time to get into my dashboard ! i mean before i removed the animation on x2 4981 and i was in in seconds ! now i wait for the chip to read the config file , then the ani to run then finally i boot to dashboard. and IGR seems to work to a less percentage than it did in previous versions ! anyone else foind this !

I think i will revert back for a while i need speed and stability more than fancy colours.

HackDaBox !

Chancer · « **Reply #11 on:** June 05, 2005, 02:39:00 AM »

I can not understand why you would be so bothered about using the new X2 bios just for a Blue X logo. You can do this with just about every other bios available to you and without it causing problems.
You already have been given the solution but prefer the problem. Flash another bios and customise it first if you have to

hippo · « **Reply #12 on:** June 05, 2005, 04:02:00 AM »

Because it's damn fun to play with I had a kick right until it blew up. And the recovery after the blow up took 15 secs.

On the other hand it is a senseless waste to have a bios that big that basicly has a loading screen that might as well be a flashing screen with a bar running through it Because that lasts as long as any flash screen. Also for 512k I want god damn ftp in the bios. They aren't addressing these concerns.

I still enjoyed playing with it. And no users aren't like us they are even more curious. Also I don't think a noob would replicate the error I had and as it's special circiumstances. Normally I HATE anything X3 or X2 but I got to hand it to them on flashbios 3 and this bios is okay. I'm a freak that only runs evox bios so....

WebLOCH · « **Reply #13 on:** June 05, 2005, 07:11:00 AM »

Apologies for the mixup on the error codes, wasnt sure who was being told what.

Chancer the specification was that I wanted to use the X2 BIOS with the DuoX2, so you haven't give me a solution, and I am not choosing the problem. Thats almost like saying I have a problem with not being able to fly, because I chose a car.

I want to run the X2 5032 BIOS, the BIOS and coloring was specifically requested BY a customer, and my friends appear to have it running fine.

I personally run an x2.6 and x3 both with custom BIOS' that load as little as possible, mainly because I haven't had time to bother prettifying them. I am also a software engineer so I am totally for the whole "functionality before aesthetics" argument.

Thanks for all your suggestions, I think I shall have to tell the guy it's not possible until the BIOS gets debugged further.

hippo · « **Reply #14 on:** June 05, 2005, 09:37:00 AM »

There's tons of people running this.

Author Topic: Duox2 Installed Fine, Loads Bios Fine, Then Errors (Read 157 times)