| QUOTE |
| Team Xodus releases XeniumOS 2.0.1 This update is being released to address several minor/moderate bugs, and 2 potentially serius bugs. It is reccomended that all users upgrade to this version of XeniumOS. A few notes: This update comes with 2 recovery.bin files. The standard recovery.bin will no longer erase bioses, settings, or eeprom backup. recovery-ResetToFactoryDefaults.bin behaves like previous updates, and will restore the chip to a factory default state. The 2.0.0 release of XeniumOS would allow the user to use the "Recover from BIN" option in the EEprom tools with a .bin file which was not an EEprom backup, resulting in a corrupted system EEprom. Also, when the system EEprom was corrupted by this action, or any other means, XeniumOS would fail to boot properly. We would like to point out, once again, that improper and uninformed use of the EEprom tools can have destructive results, and users should proceed with caution. In the case of a corrupted EEprom, XeniumOS will now enter a special boot mode, and will prompt you to press a button when you can read some text on a blue background. This is done so that the video can be properly initialized independant of eeprom settings. If you have a corrupted EEprom currently, and XeniumOS will not boot, upgrading to this version of XeniumOS should allow you to recover. If this is the case, it is reccomended that you update using the CD upgrade method, and disconnect your harddrive if you had previously used the harddrive upgrade method. Changelog: +Added some diagnostics reporting to filesystem drivers, in preperation for performance profiling +Added monitoring of PIO/UDMA switching, in preperation for performance profiling +Added "EEpromless video region" screen *Other minor changes in filesystem drivers, shouldn't make any difference *Substantial changes to usb subsystem, should be a bit more stable now *Better integration of usb flash drive and filesystem drivers *Fixed issue with third party controller compatability *Finishing/Improving usb keyboard and mouse drivers in preperation for integrating with UI *Minor internal change to hashing library *Replaced one of the Xbox hw version detection routines. May still report some boxes as 1.0, when they are not, and vice versa, but this is not confirmed yet *Some IP stack changes, nothing that should have major impact *Several improvements to ARP handling *Several internal kernel additions -Fixed a very minor bug with drive mounting -Small change in ftp protocol handling and ftp->filesystem path translation -Fixed bug that caused "Restore from BIN" to not appear if the system EEprom was invalid -Fixed some SMB file ID handling bugs (should now properly close files opened over smb) -Fixed a minor problem with interrupt servicing in usb subsystem -Fixed a minor dhcp error handling bug -Fixed a minor problem with handling ICMP pings -Fixed a double free bug in ip stack -Fixed a critical bug with EEprom restore-from-bin which could render a box unbootable if used improperly -Fixed a critical bug which caused Kernel Panic on boot when EEprom was invalid, when attempting to set video mode Legend: + Addition - Bug fix * Change |
| QUOTE |
| +Added some diagnostics reporting to filesystem drivers, in preperation for performance profiling +Added monitoring of PIO/UDMA switching, in preperation for performance profiling |
| QUOTE (from beta1 readme) |
=================== UPGRADE PROCEDURE =================== We recomend upgrade procedure is done with cdrom ISO version, simply unpack and burn the ISO .. ensuring you set Disk at once option (please follow the manual, should you require further assistance) alternatively: Place the recovery.bin file on your console's E:\ and entering Recovery Mode thru the Xenium-OS menu or by changing the position of the switch on your Xenium, once update has been completed we strongly suggest that the recovery.bin file is either renamed or deleted, to prevent the Upgrade process from being performed unintentionally and your Xenium-OS settings being reset. |
| QUOTE (acemilo @ Oct 1 2004, 05:44 AM) |
| Yes this update looks great, however the eeprom fix does NOT WORK ON A 1.6!!! I have an old thread I was looking (and still am) for help about a corrupt eeprom on a 1.6. I just saw this release so I threw it on. Upon booting, I do get a weird behavior where the chip is green, the eject is green, flashes, goes to flashing red for a few seconds, then the chip changes colors, and it goes back to green and the cycle starts all over. I am assuming that this is the new boot method for a corrupt eeprom but I NEVER GET A SCREEN SAYING TO PUSH A BUTTON. This leads me to believe that it does not work on a 1.6. Hey apple, since you tested the eeprom yourself, does what I describe happen when yours repaired itself? I'm guessing it is since it never did that before. I let it cycle thru for like 5 - 10 minutes and it never came up with a screen. Damn I thought this would fix it. |
| QUOTE (acemilo @ Oct 1 2004, 05:53 AM) |
| Absolutely sure I flashed it twice to make sure and it never did this before. When I put 2.0.0 on it it behaved differently than its doing now. Artifex, if you could msg me on aim I could really use to talk to you about this. Obviously I'm not a noob you should know that by now but this 1.6 is killing me. The worst part is its not mine its a customers and he did it himself, I'm trying to salvage it for him. Please im me or email me asap I really need your input. |
| QUOTE (cresent @ Oct 1 2004, 09:40 AM) |
| i couldnt get 2.0.0 or 2.0.1 to work i always get a "file doesnt fit" error doing it the hdd way |
| QUOTE (ProphetX @ Oct 1 2004, 10:17 PM) |
| hey can someone give me a link to ugrading using the hdd version of the 2.01 version. i can seem to find it anywhere not even on the homesite. |
| QUOTE (EmperorPsiblade @ Oct 3 2004, 02:46 AM) |
| XBMC doesn't have (a good) file manager.. use boxexplorer instead to copy it... it HAS to be in E: PS: why does someone with a name of X3rules use a Xenium? |
| QUOTE (appleguru @ Oct 3 2004, 03:06 AM) |
| By itself on E BTW, if you need to use XBMC... Go to Files... hit the black button and navigate to E. That will set your destination as E:. Then hit the black button again to go back to source... navigate to your file on D:. Press the white button, and when it asks you if you want to copy choose "yes".... Should work |
| QUOTE (ProphetX @ Oct 3 2004, 07:29 PM) |
| how do i get to the launch menu. sorry for the dumb question but i've never had to go to it before. |
| QUOTE (ProphetX @ Oct 4 2004, 02:13 AM) |
| ok did the upgrade, now how do i get back to my dashboards?? |