As many of you may have noticed, we have decided to temporarily disable *ALL* updaters, with the exception of the repair tool, over the weekend. All updater versions will currently report a "404: not found" message when run. We apologize for this inconvenience, but have found it a necessary measure in order to prevent some problems from spreading, and further bogging down the support staff unnecessarily.

The root of the problem:
A few weeks ago, we began a beta of the version 1.1.1 which shipped on the 2GB units. During this beta period, a specific bug with the suspend/resume feature of the DS-X firmware was discovered. Unfortunately, a fix for this issue was not found before the 2GB parts were programmed, and the units were shipped with this bug.

During the time between the programming of the units, and their arrival at customer's doorsteps, a fix for 1.1.1 was implemented in the form of 1.1.2, and a second beta was started. None of our beta test group had received a 2GB unit, so we were only able to test the 1.1.1 to 1.1.2 update process on the new devices internally, which revealed no issues. Believing all to be well, we released the 1.1.2 update for public use, with what would turn out to be less then ideal results.

The problem:
This upgrade was the first to include non-trivial changes to the firmware of the USB 2.0 controller onboard the DS-Xtreme in support of the 2GB version, and the first update in which all 3 portions of the device (DS-X firmware, FPGA logic, and USB controller firmware) were updated together. As it turns out, there was a dormant bug in the updater which only manifests on the 2GB devices. If a 2GB devices fails programming, it leaves the DS-X in a state in which the USB controller firmware is either corrupted or missing entirely. This can result in a variety of symptoms including the device being unrecognizable by windows and/or the DS.

The aftermath:
Many users began seeking RMAs for their new 2GB parts, believing them to contain faulty hardware. In every case we have reviewed, we have not seen any indication of faulty or unrecoverable hardware, and have no reason to believe that such faults may exist. In every support case and return which we have reviewed, we have seen:

1) The device is a 2GB device which has fallen to the firmware-erasure problem mentioned above
2) The user is attempting to update on a 64 bit OS, or Vista, which are not currently supported
3) The user had a 1.1.1 part, had data corruption related to the aforementioned bug in this version, and either attempted to upgrade to 1.1.2 for the fix (resulting in #1 or #2!) or has sought support without the upgrade.

The resolution:
As was mentioned earlier, we have now pulled the upgrade tools with the exception of the repair tool which, although it also exhibits the same bug, is necessary for support staff's use in resolving unrelated issues. Again, it should be noted that this repair tool is *NOT* recommended for end users unless guided by support staff, *ESPECIALLY* in light of these recent developments.

We have now identified and isolated the bug in the update tool (for those who are technically minded, the problem is an intermittent assertion of the CS lines of both NAND dies on the 2GB part, due to mishandling of interleave during partial erasure) and are working on a fix to this, and a few related issues (in order to avoid any additional problems) and will release a new update tool when we are confident in it's stability.

Let us also reiterate that there are at this time *no* known issues with the 2GB hardware, and returns are not necessary. We recommend that all users who have not yet upgraded do not attempt to do so, and remain with 1.1.1 firmware until a fixed updater is released.

Again, I would like to apologize for the inconveniences this has caused to both users and support staff, and thank both for pulling together to put an admirable amount of time into helping us manage and mitigate this situation over the past week.