QUOTE(cjack @ Dec 5 2005, 12:12 AM)
Just checked DVD player labels that are very similar but .... 2 different rom versions!
Core:
DVD PLAYER model: GDR3120L (X800475-008)
Rom version: 0046DH
Premium:
DVD PLAYER model: GDR3120L (X800475-009)
Rom version: 0047DJ
It's possible that rom versions are not compatible........it'just an hypothesis!
No, I think your initial thoughts were correct. From what MS said many months ago, hardware would be signed!! This means, DVD is locked to CPU, and possibly other things. I know they were talking about signed RAM chips not long ago, but I think that was with detachable memory modules, not soldered in ones, and applied to general PC manufacturing. I would guess that it's possible that the DVD-ROM firmware is signed, in a small flash chip? It's worth looking how easy it would be to swap logic boards on the DVD drives. In your case that might not work as you have a different revision.
It is also possible, like you said, that it's purely a compatibility issue, but I doubt that they would make the firmware incompatible...
QUOTE(flashfreak @ Dec 5 2005, 10:51 AM)
Locking DVD-Roms would be a dodgy idea, as I was thinking, if a drive died, your stuck with it, but as people have said, it'll create more work for MS to have it sent in to fix.
Not as silly as it sounds!
1) MS will sub contract the work out, and make some kind of small profit on the drive. This is one reason why hardware manufacturers are considering hardware signatures, to reap profit from the repairs and upgrades market. Sounds just like the sort of thing MS would do.
2) If the drive needed replacing, it would be a 2 minute job to change it, and the engineer could do some kind of controller combination to get the kernel to lock the new drive.
QUOTE(Xevious @ Dec 5 2005, 10:04 AM)
This is pure speculation...
Given the small size of the optional ROM, it could be a patch or configuration ROM designed to "fix" 360 processors (or assembled systems) that didn't completely pass validation. Specific examples could be disabling sections of cache that fail testing, modifying default RAM timings on boards that were unstable at full speed, etc.
Keeping with this theory, MS may have designed a certain margin of "error" in the 360 system spec in order to increase yields. For instance, the lowest common denominator could be 90% of "full speed" or full cache, with anything above being cream.
If there indeed is a positive correlation between core systems and the presence of a small ROM, this could indicate that MS binned systems, allocating the top bin to the Premium package.
Again, this is speculation, but it is based on practices that are commonly used by the industry to increase yields.
Whilst I agree this is possible, I think it's unlikely! For these reasons:-
1) User community would go mad! Think about it, do you want to buy a 360 not knowing if yours is 3 fps slower than your m8s? This just isn't an option, people are buying a console and they want an identical version to everyone else, period.
2) Problems with GPU pipelines etc would be flagged within the GPU and or it's assistant IC's. As for the CPU, I think the chances of limiting this baby for x number of cycles is mad! Think about it, games run with very precise timing, and limiting a CPU core or 2, even by as little as 0.001% would have some kind of compatibility issue with some code. Trust me!
I think in all likelyness, the fact he has 2 slightly different revision DVD-ROM drives, says to me that they are producing new revisions of the board as they go... Maybe the one with the EEPROM is a newer revision? Or maybe they dropped it, and it was a security feature that is causing more problems than it was worth? Again, speculation.