Editing Talk:1.00 CEX
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 25: | Line 25: | ||
** This could be for non-retail Hardware for sure since my experience showed that Version "X.XX" got always released for DEX, SEX, <!-- why they called it SEX ??? :P --> DECR, AV, ARCADE and so on way before the same Version "X.XX" got released for a retail CEX version, which makes sense, since Sony use probably at least DEX hardware to test out things on newer Firmwares (see 3D functionality on DEX FW vs. CEX FW for example). | ** This could be for non-retail Hardware for sure since my experience showed that Version "X.XX" got always released for DEX, SEX, <!-- why they called it SEX ??? :P --> DECR, AV, ARCADE and so on way before the same Version "X.XX" got released for a retail CEX version, which makes sense, since Sony use probably at least DEX hardware to test out things on newer Firmwares (see 3D functionality on DEX FW vs. CEX FW for example). | ||
*** I don't know if the following Sony did for the PS3 Firmware Releases but on PS4, the newest Firmware is always finished and "ready or installment" way before it's publlc release. See the latest Firmware Update 5.01, which got released on '''24<sup>th</sup> October 2017''' but the direct download link shares the '''filedate''' together with the MD5 checksum, which mismatches in this case --> [http://djp01.ps4.update.playstation.net/update/ps4/image/2017_1018/sys_8606691c0201e4db2a4100f80fbaddb3/PS4UPDATE.PUP?dest=jp http://djp01.ps4.update.playstation.net/update/ps4/image/'''2017_1018'''/sys_8606691c0201e4db2a4100f80fbaddb3/PS4UPDATE.PUP?dest=jp] (6 days before public release but no one can download this Update File before since the ps3-updatelist.xml needs to get updated as well). This means that [[1.00 CEX]] could be finished on 11<sup>th</sup> November 2006, but also on October or even way longer before. If Sony worked with this system for the PS3 as well, then I think you will never can say if there was a [[1.00 CEX]] Update File since there is no 100% proof that Sony worked this out like above mentioned with the DEX and DECR versions compared to the CEX releases. And with those Date mismatches, it makes it way more difficult to find any [[1.00 CEX]] Update File, especially without any MD5 hash. On the other hand, no one knows when Sony started to implement this ps3-updatelist.xml feature especially if they implemented it already on Day 1 after release. Sadly the waybackmachine has only entries until March 2007 :( | *** I don't know if the following Sony did for the PS3 Firmware Releases but on PS4, the newest Firmware is always finished and "ready or installment" way before it's publlc release. See the latest Firmware Update 5.01, which got released on '''24<sup>th</sup> October 2017''' but the direct download link shares the '''filedate''' together with the MD5 checksum, which mismatches in this case --> [http://djp01.ps4.update.playstation.net/update/ps4/image/2017_1018/sys_8606691c0201e4db2a4100f80fbaddb3/PS4UPDATE.PUP?dest=jp http://djp01.ps4.update.playstation.net/update/ps4/image/'''2017_1018'''/sys_8606691c0201e4db2a4100f80fbaddb3/PS4UPDATE.PUP?dest=jp] (6 days before public release but no one can download this Update File before since the ps3-updatelist.xml needs to get updated as well). This means that [[1.00 CEX]] could be finished on 11<sup>th</sup> November 2006, but also on October or even way longer before. If Sony worked with this system for the PS3 as well, then I think you will never can say if there was a [[1.00 CEX]] Update File since there is no 100% proof that Sony worked this out like above mentioned with the DEX and DECR versions compared to the CEX releases. And with those Date mismatches, it makes it way more difficult to find any [[1.00 CEX]] Update File, especially without any MD5 hash. On the other hand, no one knows when Sony started to implement this ps3-updatelist.xml feature especially if they implemented it already on Day 1 after release. Sadly the waybackmachine has only entries until March 2007 :( | ||
**** And yes, they | **** And yes, they did the same for the PS3, check the "imageBuildDate" from the following two pictures right after the Version Number: | ||
***** http://www.psdevwiki.com/ps3/images/9/9c/MoreSystemInformation-CECHA01-102.JPG | ***** http://www.psdevwiki.com/ps3/images/9/9c/MoreSystemInformation-CECHA01-102.JPG | ||
***** http://www.psdevwiki.com/ps3/images/d/d3/IMG_0148.JPG | ***** http://www.psdevwiki.com/ps3/images/d/d3/IMG_0148.JPG | ||
**** [[1.02 CEX]] and [[1.10 CEX]] were already finished way before the PS3 was released. This could even mean that if you bought a PS3 on 11<sup>th</sup> November 2006, you already had Firmware [[1.02 CEX]] pre-installed, which would also make sense that all japanese Launch titles shares the same MD5 hashes for the included disc-based Update File, which is the MD5 hash for the disc-based [[1.02 CEX]] Update file like on this Mobile Suit Gundman Game (Google for "df96debb4c014f5673e0ce259e4fb835" and you will find a lot of hashes shared on several japanese launch titles) | **** [[1.02 CEX]] and [[1.10 CEX]] were already finished way before the PS3 was released. This could even mean that if you bought a PS3 on 11<sup>th</sup> November 2006, you already had Firmware [[1.02 CEX]] pre-installed, which would also make sense that all japanese Launch titles shares the same MD5 hashes for the included disc-based Update File, which is the MD5 hash for the disc-based [[1.02 CEX]] Update file like on this Mobile Suit Gundman Game (Google for "df96debb4c014f5673e0ce259e4fb835" and you will find a lot of hashes shared on several japanese launch titles). | ||
As an interesting comparison, the only difference in between ps2_emu.elf (decrypted) from firmwares [[1.30 AV]] and [[1.30 CEX]] are 3 bytes of the timestamp, ps2_emu.elf for [[1.30 CEX]] was compiled at 06/12/05/05:33 and ps2_emu.elf for [[1.30 AV]] 06/12/05/07:15... around 2 hours after, based on this we can deduce the ps2_emu.elf for [[1.00 CEX]] was compiled a couple of hours before the ps2_emu.elf for [[1.00 AV]] and the code of that ps2_emu.elf was exactly the same (except the timestamp with the delay of two hours) | As an interesting comparison, the only difference in between ps2_emu.elf (decrypted) from firmwares [[1.30 AV]] and [[1.30 CEX]] are 3 bytes of the timestamp, ps2_emu.elf for [[1.30 CEX]] was compiled at 06/12/05/05:33 and ps2_emu.elf for [[1.30 AV]] 06/12/05/07:15... around 2 hours after, based on this we can deduce the ps2_emu.elf for [[1.00 CEX]] was compiled a couple of hours before the ps2_emu.elf for [[1.00 AV]] and the code of that ps2_emu.elf was exactly the same (except the timestamp with the delay of two hours) | ||
* Hmm, maybe we could compare this with the relase from the PS4. Launch Day Devices where on 1.00 ??? | * Hmm, maybe we could compare this with the relase from the PS4. Launch Day Devices where on 1.00 ??? | ||
====PS3 launch games availables==== | ====PS3 launch games availables==== | ||
Line 57: | Line 55: | ||
* Actually there was a time I liked the entry from the official Wikipedia itself since it listed every update and all functions in detail in a big table but for some reasons, they removed it. Several people claiming it in the Talk page to bring this back but you can look for an older revision like here --> https://en.wikipedia.org/w/index.php?title=PlayStation_3_system_software&oldid=676645457 | * Actually there was a time I liked the entry from the official Wikipedia itself since it listed every update and all functions in detail in a big table but for some reasons, they removed it. Several people claiming it in the Talk page to bring this back but you can look for an older revision like here --> https://en.wikipedia.org/w/index.php?title=PlayStation_3_system_software&oldid=676645457 | ||