Manuals And Guides And Os Updates
Posted 26 September 2004 - 04:34 AM
>> From www.teamxodus.com
The build is stable, a large number of the bug reports you have so vigilantly submitted have been fixed, and new features have now been fully implemented. With the complete integration of Webserver, FTP, SMB and USB interfaces, we have proven that we mean what we say and that we will continue to lead and to set the standard in this industry. Our objective, right from the onset, was to make the best, most functional, most efficient, most reliable, and most user friendly chip on the market, and we have done that! It is no surprise that we have been dubbed "The creators of the easiest Xbox modification.."
We are extremely happy that our decisions to take the risk of starting over from scratch and to make the bold move of developing our own fully legal OS have paid off. It has been a lot of work, but now that we have a firm and stable foundation in place to build upon, the OS will really begin to expand and grow. We are confident that our developments have created the pathway for a wealth of limitless possibilities. We are already working on some great new features for you!
On a side note, we recently did a count of the lines of code in our CVS repository for Xenium OS(info), and were surprised to find that the current count is over 1.35 million lines of code! As much as we would love to say we wrote all of that from scratch, much of it is library code. Regardless, this should show you how much technology and complexity we have put into this product.
We are sure you will like this release, and we always encourage suggestions and feedback.
Changelog for Xenium OS 2.0.0:
+Webserver up and running, but still some minor bugs to be worked out.
+Web-flashing enabled, will be adding configuration and utilities
+Support for DVD remote
+Ability to restore EEprom from .BIN backup on hdd, cd/dvd, usb, or smb drives
NOTE: This does *NOT* currently do cross-version restore
+Added support for additional 3rd party controllers
+Added option to repair HDD previously affected by Beta1 Hdd-upgrade-wizard Live bug
+Added telnet based debugging ("info" command, currently very buggy and meant for internal use)
*Improved quickboot usability
*Modified LCD timings to improve compatibility
-Fixed an integer overflow bug in crypt/hashing libraries
-Fixed kernel panic caused by booting without hdd attached
-SMB should now work properly with static IP
-Fixed an internal problem with the heap manager; potential performance gains
-Fixed "Hang at boot with blinking green eject led and no video" bug
-Improved SMB upload speeds in some scenarios
-Fixed a couple of typos in on-screen text
- Bug fix
(September 26 04:02 CEST) -
Posted 02 October 2004 - 12:55 AM
>> From TeamXodus.com
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 Xenium OS(info).
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.
+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
- Bug fix
Official Site: http://www.teamxodus.com
Buy Xenium: Extreme-Mods.com, BMMods, Divineo.com, Divineo.co.uk, Divineo.cn, XboxChips.com.
(September 30 22:57 CEST)
Posted 26 October 2004 - 12:47 AM
Posted 01 November 2004 - 04:13 PM
(*) Make sure you have the correct date and time set in m$dash
(*) Make sure your xbox is working fine before modding it, unless u mod it to solve a problem
(*) Find what xbox version u have
(*) Save yr time and efford, you dont hav a v1.5 xbox
(*) UPDATE TO LATEST XOS v2.3.0
(*) Don't blame the chip for everything, try the xbox without the chip!
(*) Errors are explained at http://www.xbox-scen.../errorcodes.php
(*) No led on chip means no power to the chip, check pin 2 (ground) and pin 9 (Vcc 3.3v)
(*) Led on chip is fine, but xbox boots to M$ dash, THEN CHECK D0
(*) Flashing Red and Green (aka FRAG) mean one of the LAD lines is not correct, check soldering or adapter
(*) Scrabled tv signal, b/w etc, check the regional setting, Pal/Ntsc, cables etc
(*) No unsigned code is loaded by XOS, http://www.xbox-scen...ios_retail.html for bioses running unsigned code
(*) XOS cant read bioses from Slayers Installer CD, XOS cant read X-isos
(*) No hard disk locked on another xbox can work on your xbox
(*) Xenium connector pinout: http://www.xbox100.c...spi_diagram.jpg
(*) LCD for xenium: compatible models are 632 (2x16) and 634 (4x20) by www.crystalfontz.com
(*) Parallel LCDs will not work unless u use and adapter SPI2PAR (green giant can provide u one)
(*) Prefered method of XOS update is by CDRW
(*) Putting Recovery.bin in E: drive and selecting Recovery in XOS will also do the trick
(*) If recovery screen appears, check if the switch is over the spot
(*) For Xbox v1.6 u must hav the hard disk unlocked for the upgrade
(*) And remember, if you used the XOS2 HDD wizard be sure to delete the files in E:\CACHE on the upgraded drive!
If you fail to do so, LIVE enabled games (That is, games that can use LIVE)
will freeze when you try to load them.
Edited by fujitech, 01 February 2005 - 12:04 AM.
Posted 02 November 2004 - 12:15 AM
The blue/black wire loom (Bottom right in pic below) is for a removable d0/ground. If you decide to use this, solder the blue wire to d0 on the motherboard (You can extend it if it's too short) and the black one to the ground ring around the nearest screwhole. NOTE: Ground isn't really needed, but if you don't use it, tape/cut it off so you don't short anything out. Also, if you use the d0/ground loom you DO NOT need to solder another d0 to the chip.
The USB adapter (middle right) just plugs into a controller port. It's that simple. Note: it slides in under the black plastic connector bar in the middle of the xbox controller ports, and goes in with the USB plug up. (IE, on the top side of the board). It's a tight fit at first, but it does indeed just slide in.
The Xternal LED bar (bottom middle) is a mirror of the chip's multicolor LED and can be installed anywhere on your xbox you like and can route the cables to. On translucent xboxs, it can even be mounted internally to shine through. On black ones, a popular mounting choice is under the front panel routing the wires through the overhanging holes on the front panel. The multicolor wireloom plugs into the chip as shown in the picture below. If your loom has a ground ring, it screws under the nearest screw on the nearest screwhole (Again, not needed unless you have a lot of LEDs stringed together but it doesn't hurt; if you don't use it, tape it off). The other connector plugs into the LED bar.
Edited by appleguru, 02 November 2004 - 12:58 PM.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users