3 ms·
It's not as awful if you compare it to the gen 1 360 (RROD anyone?) Eh? I had (well, it's still in the garage) a launch day box. It did the RROD under the exte
by mikestew 11y ago
It's not as awful if you compare it to the gen 1 360 (RROD anyone?)
Eh? I had (well, it's still in the garage) a launch day box. It did the RROD under the extended warranty period, sent it in and got it refurbished, it ran until the Xbone launched. A one-time problem with a one-time fix that had a quick turnaround. Your mileage obviously varies, as did that of others, but for me over the course of nearly ten years, it was a minor inconvenience.
In comparison to the Xbone, the foibles of which I endure nearly every time I turn it on. I dropped my Xbone in the DMZ and called it good, and that works well. But that does me little good with my friends as we ask, "why can't I join? Why doesn't chat work?" My personal fave is the "it says my NAT is 'strict', but it was 'open' yesterday and I haven't changed anything." That even happened to me once. Now how the network stack thinks that a machine with its own IP address, sitting wide-open exposed to the Internet at large, is behind a NAT befuddles me.
- FussyZeus 11y agoThe failures of the foxconn 360's were incredibly erratic, some died after a month, others are still working. A company that produces hardware that fails with such a range is somewhat more worrisome than one that produces it where it fails consistently. And yeah I too noticed oddness with DMZ. For a long time the only way to have two in the house was to have mine in the port forward (since we used mine as a media center and it needed access to the other bits of the network) and to have the wife's DMZ'd, but neither worked terribly well and we would run the gamut from Strict to Open with zero predictability. UPNP seems to keep them happy though, so whatever works.