Another question, does Team TOXiC have a website??? i want to check our what theyve done in terms of OS concerned. I bought a Crystal Chip based on what I saw was the best thing for trying out different firmware because of its infallible system and its features, did I make the right descision with the chip? thanks again.
Team TOXiC doesn't have a website (though the cynical might tell you its www.dms3.com). As it is though, it won't matter for you, since firmwares are chip-specific. TOXiC bios and TOXiC OS will only work on DMS4 chips. This is the reason why your Matrix 'SE' failed in the first place.
I dont know if you follow me here. I no longer have a Infinity SE, i scrapped it with the 1.54 firmware fromt the matrix team. I have now purchased a DMS4 PRO and a Crystal Chip, as I myself am a chipper looking fo rthe best possible thing out there.
Another thing I forgot to add... Firmwares do not have ot be chip specific. If i made a chip with identical parts to a DMS4 and then put DMS4 firmware on it- It would WORK. I just would not be able to flash the chip using conventional methods. (Putting cd in drive, following prompts). Do not forget I work out of a Microelectronics business in the southern hemisphere. I have access to tools worth up to 6000 dollars each. Im not some crappy chipper that works out of his mothers shed in the back yard with a 50 cent microscope and a soldering iron with a tip the size of his thumb.
Quote:I bought a Crystal Chip based on what I saw was the best thing for trying out different firmware because of its infallible system and its features, did I make the right descision with the chip? thanks again.
the crystal mod is a nice chip since as of the hacked R15v2 version of the firmware they have been able to play backups online with ease... what is interesting both the dms4 & the matrix have the ability to do this aswell but the code has yet to be implimented "publicly"..
the dms4 has a webpage but its only for homebrew developers so you wont find any of the toxic updates there...
Quote:Im not some crappy chipper that works out of his mothers shed in the back yard with a 50 cent microscope and a soldering iron with a tip the size of his thumb
lol, ha :D
then you should have known that the matrix infinity se doesnt use all of the same parts as the real infinity and the chip would probably not accept the 1.54 update ;) for one thing the SE uses a differnt IC then the "Actel" used in the real chip. the clones dont use identical parts therefore they usually wont accept the firmware updates...sometimes they dont even use the same code in the version shipped with the clone chips. its a semi-hacked code by whomever..
lol, i spose. I thought this way, Firmware all sizes within chips size range, therefore, chip would accept firmware.
I admit, saving money was my main reason. but I guess now that Ive outifitted DMS4s everyones happy with their slim Ps2s. Which comes to another question. Why on DMS website do they say their chips are v1-v10, when they DO work on a V12??????
And becuase all chips use identical soldering points i was under the impression that they are using a universal language to alter the Ps2s thinking, therefore nearly all ps2s chips are the same apart form lo-end ones. DMS has backup firmware stuffup mode doesnt it, ill try flashing it with the crystal chip altered FW and see what happens if thats the case.
Ahh I didn't know you had a DMS too. But yeah, Team Toxic definitely doesn't have a website. They do have a lot of notices and beta announcements on ps2nfo.com though.
Quote:Another thing I forgot to add... Firmwares do not have ot be chip specific. If i made a chip with identical parts to a DMS4 and then put DMS4 firmware on it- It would WORK.
Not true. Just because it uses the same Actel Programmable Logic doesn't mean you can put any firmware in and expect it to work. Why? The firmware doesn't program all the gates. For example, if the firmware gets corrupted somehow, there is usually a way to revert to a failsafe boot (like hold down reset, or tap reset six times). This internal code that doesn't get programmed might reject your non-compatible firmware.
Secondly, each firmware probably uses different output lines to connect to the CDVD controller and BIOS.
Finally, I haven't checked myself, but I'm pretty sure DMS and IM firmwares are encrypted (supposedly to prevent "fakers"). Therefore, when they accept a firmware, they will (after doing CRC check), attempt to decode.
