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.
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
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.
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
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...
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.
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.
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.
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 !
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
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....
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.
There's tons of people running this.
QUOTE
seeing as the stock file doesnt work
Are you saying the non modded X2 5032 is also not working for you?
Can't be right because in stock form it definetely works ok on the DuoX 2
Okay for the sake of clarity, this is the exact order...
1. Connected to usual places
2. Downloaded X2.5032 rar file
3. Unrared to my desktop
4. Flash the DuoX2 with BIOS file
5. Tested it was all working okay, it was fine
6. Uploaded stock config to E, using UltraFXP
7. Tested again, this time it failed
8. Removed the config
9. Tested again, this time it was fine
10. Used X2ool to transfer the stock config
11. Test again, this time it failed
Do you have a standard DuoX2, the blue one?
I've followed the proceedure to the letter, and used the EXACT stock files to try and get it running, yet it fails.
Standard Blue DuoX 2. Well 2 actually while i was testing some stuff last week. 1 In a 1.6 1 in a 1.4 Stock config (no mods to it at all) works fine other than problems starting a boot with Slayers and a blank HDD(That should obvioulsy not have any effect on your issues)
the only problems I had was flashing it to the chip through evox. kept halting so I flashed it to the chip with eurasia and it worked no problems
quit using the stock config and maybe make your custom one. Maybe the default config has screwed the pooch. Like if you use the default ini from before 5028 on the 5032 bios.
I can get all the custom colors and logos going but when I flashed it on a 1.6 with the old bios to test on an old machine it seemed really unstable on the old machine untill it was re-flashed on the intended machine.
Hrrm I'm trying to break it and now I cant so I can get a screenshoot for the user's guide, oh well. If you can capture that scrambled screen put it up somewhere.
I will take a couple of pictures in a minute, however I must state that using the same two unmodded files (BIOS and config) from the set, that my X2.3 has NO prblems whatsoever!
QUOTE
I thought it was just me!
No I have had this with further testing today.
Its a shame but this bios I don't like. The old X2 bios were great. M8+ is both stable and reliable everytime I use it.
Then try the new version 5035 or something.
Looks like they mostly added flubber options, pretty useless.
You can add things in evotool but let's be honest when you inject a .dds file in to a bios terrible things can happen. When making the bios below I had such a catistrophic mess that it actually powered off during flashing. I re-checked it and the same thing. So although the bios can turn out okay the one below took about 8 tries before getting this working one.

And the X2 bios turned out just as cool, I wish the X2 bios was bigger. But it didn't take any flashes and the issue with the blank hdd is bound to get squashed, speakingof which, today...
