xboxscene.org forums

Author Topic: 5035+duox Question  (Read 145 times)

shiz

  • Archived User
  • Jr. Member
  • *
  • Posts: 62
5035+duox Question
« on: December 20, 2005, 03:54:00 AM »

so aside from 5035 not working with the duox clones, there's no other problems running it on the authentic duox versions correct? Im reffering to the white duox2

Does the 5035 need to be manhandled in any way or its ready to go as it comes off xbins with no further modifications?

thanks
 uhh.gif
Logged

FSUNolez336

  • Archived User
  • Jr. Member
  • *
  • Posts: 53
5035+duox Question
« Reply #1 on: December 20, 2005, 05:09:00 AM »

I am currently running 5035 on a Duox2 Cromwell without any problems. It will work straight off of Xbins (make sure you choose multiversion if you don't have a 1.6). You can edit the XConfig.ini file so you can customize the flubber screen and all your settings, but it is not neccesary.
Logged

shiz

  • Archived User
  • Jr. Member
  • *
  • Posts: 62
5035+duox Question
« Reply #2 on: December 20, 2005, 03:49:00 PM »

well the reason i ask is because i tried flashing 2 duox (authentic) on bank 1 via network flash (flashbios 303) with 5035 and both times after the flashing was 100% complete i got a message saying "flash failed"! Upon reboot bank 1 was toast and had to reflash it through cromwell with the eurasia disc....
any suggestions?
Logged

Chancer

  • Archived User
  • Hero Member
  • *
  • Posts: 5751
5035+duox Question
« Reply #3 on: December 21, 2005, 04:51:00 AM »

The JPEG error or blank screen is a common glitch in flashbios depending on the version of 1.6 you have.
You only usually see the problem with chips other than the Xecuter chips because Flashbios on the Xecuter chips is only for the Xecuter chips. Its customised to work on other chips. Thats why people who obtain and mistakenly flash Flashbios to their non Xecuter chip can end up in trouble if they have re-flashed with the Xecuter only version.
I can't comment on 5035 as I have not tested it. I did some extensive tests with  blue Duo X 2 and 5032 and it gave  flashing problems when flashed via evox but flashed fine using Eurasia. Couple that to glitches when coldbooting Slayers and a virgin HDD from 5032 makes me stick with M8+.16 from which the same disc with slayers on coldbooted every time
Logged

shiz

  • Archived User
  • Jr. Member
  • *
  • Posts: 62
5035+duox Question
« Reply #4 on: December 21, 2005, 05:30:00 AM »

i have not tried 5035 with eurasia yet! its an idea thou!

The jpeg error is common and im used to it (all thou a PITA none the less)

one thing i did notice thou when i flashed with eurasia and subsequently another CD for the bios is that sometimes id get flash write errors at certain addresses. It would flash successfully in the end, however the bios  would still not boot properly and id have to do it all over again. However if i used a samsung drive (instead of the phillips i normally use) the whole thing would work perfectly fine on the first try, which indicates i would think, that its very important to use either a good drive or a disk that "works" with your particular drive.

Whats the deal with flashing via DHCP with cromwell? it keeps hanging at "detecting DHCP"? Somebody mentioned that its due to the drive not being locked?! that true?
Logged