Clint
Posts: 2151
Joined: 9/11/2001 From: Australia Status: offline
|
quote: Yeah I believe the moon is made of cheese as well. I used to be a Plextor Die-hard man just like you 2. But answer this they say "We don't plan to 'address this issue'. We don't do anything to make our drives read copy protected discs, and we don't do anything to prevent them reading copy protected discs" So answer this when they first released new firmware for the 12x why did it stop copying Safdisk 2 and since then this has always been an issue I know what you are going to say " It was nothing to do with Miicrovision but I will never believe that Plextor or as previously mentioned Sanyo did not do a deal with Microvision. This has been an issue for quite a few years now and choose what anyone says they will not convince me otherwise. I will just never buy another Plextor again now the are Overpriced, Over Rated and Over Microvisions Arse. But if it is Sanyo why havn't Plextor changed to Lite-on like Sony and TDK have just done? Anyway enough Said. Laffin Assassin
You got this story through part of this article, here is a passage form it: ----------------------- What's the conclusion of this? First thought is, that this is a real hardware problem. Yep, sounds quite logical... but only quite! If it really would be a hardware-problem, why can these sectors then be read in the burner? If the EFM-encoder would have messed the data, you won't be able to read this sector with any drive - including the writer itself. Also there's something very strange regarding the firmware releases and the approach of SafeDisc2: It seems that this "bug" has been implemented with full intense in newer firmware-releases of some major CDR manufacturers! Affected by this are as far as I know Plextor, Sony and Teac. There seems to be an unholy "marriage" between Macrovision (the developers of SafeDisc2) and these manufacturers... How I can prove this claim? Well, I did some tests here with my Plexwriter 1210TA: I downgraded the firmware to version 1.01 (which I luckily kept on my HD) and suddenly the writer was able to re-produce these weak sectors like a charm! Not enough proof? Ok, here we go: I tested with various firmware releases for this writer and figured out, that firmware revision 1.04 seems to be the last "good" release. What a chance that Plextor has removed all revisions below 1.05 from their web page... And another proof: Newer revisions of this writer (recognizable by a TLA number other than 0000) have been protected against such a firmware downgrade. You won't be able to flash a revision lower than 1.05 to the internal eeprom... Somebody now discovered that the old firmware revisions still seem to exist on Plextor's servers. But somehow the file-size has changed. When a normal firmware-update package had about 530 kb, these packages only have about 440kb now... is this pure chance or did the guys from Plextor remove/change some stuff in these old revisions? Strange, strange... Blindread/Blindwrite Author --------------------- Laffin, I cannot explain this. I do NOT know why this happened. I have never owned a PX-W1210A/S so I can't comment. But I know where your coming from and your argument. I am NOT a Plextor "die hard". I just like their quality and commitment to the customer. In fact I even ordered a Lite-On LTR-3215W which should be here by Friday. I know how to turn it in to a LTR-40125W....hehe (without any differance to the "actual" 40X you buy in the shop!). Best part about it is P-CAV writing But I will (al)most certainly buy the next Plextor, because I love their "fit and finish" something that Lite-On lacks.... Even if it fails latest CD v2.51.021 (MOHAA) and up (cause I'll have my 32x Litey for that ). BTW, the last SD2 revision the Plex 24X & 40X could do perfect without the need for AWS is in fact v2.51.020; as found on Tiger Woods Golf 2002. So indeed no evidence to support your claim that Plextor are wroking with Macrovision. If that was the case, Plextor wouldn't have had an even "Partial" ability to write regular bit patterns (SD2.XX.XXX)... _________________ You get what you pay for... Edited by - Clint on 05/22/2002 08:52:42
|