Seems like Microsoft claims they can detect illegitimate copies of Halo 3: ODST. Xbox Live Chief of Police Stephen Toulouse told kotaku.com:
I can be clear however that this applies to illegitimate copies only, the ban covers the Xbox LIVE account and could possibly include their console depending on the results of our investigations (which are ongoing). We do this from time to time with titles to combat piracy.
Well, here's a bit of a curious situation. As Joystiq reports, it wasn't long after the PS3 firmware 3.0 went live that the first reports of problems started cropping up, with one particularly nagging issue being that some controllers (specifically the CECHZC2H Ceramic White DualShock3) seemed to be locked out of the console once the update was installed.
FairTrade, the company that's making this claim, bases their little theory on failure rates correlated with purchase date. Before the Jasper chipset, they were atrocious. But after? Not too bad!
The method only works for Xenon motherboards (the first ones without an HDMI out). Hopefully it will soon work with the rest of the models. Altough it has been found that it is not possible to use the exploit with the most recent jaspers.
Last week, GameInformer released a survey of 5,000 gamers that claimed the Xbox 360 console had a failure rate of 54.2, and a secondary failure rate much higher than that of other consoles. The survey looked at the entire run of the Microsoft console -- so it isn't necessarily representative of Microsoft's latest less-failure-prone version of the console.
By default GAE comes with a file named logging.properties in the WEB-INF folder. To be able to record a message to the log you have to use the method Logger.warning() or change the logging level in the loggin.properties file from
.level = warning to .level = info
Regards.
On Belzar. com an engineer claims to have a functional PS3 modchip, after a sample and install when its available Ill post an update...
Team Jungle released a new version of JungleFlasher.
What's new/fixed:
* Lite-On 83850c support
- added full LO83info extract, OpenKey to Dummy.bin
- checks added to LO83info.bin.key load, blank data aborts
- 140F0F1011B5223D79587717FFD9EC3A from bad LO83info extract will be rejected
- Many thanks to C4eva for this hack.... We wish you well
**** WARNING ****
BUT beware...
you should always try to use a spare drive to check the key
* Lite-On support General
Dump Dummy.bin from lite-On iXtreme file (in target context menu)
Identify Barcode reversal in Dummy.bin