Print

[mp3boy]

QUOTE(carranzafp @ Oct 26 2008, 06:04 PM)

Also Its strange how people can do test with backup data, the tests should be done with real drives.  Also they didnt specify if they did the test with xtractor hardware or with a homebrew device wich (if bad soldered/wire routed) can cause bad readings due to hardware.

I checked my backup data for the keys that would trigger the bug, then dumped those 4 drives again using your software to see what would happen and it triggered the bug as expected.

Hardware:
NForce onboard SATA and VIA 6241 PCI SATA.
RROD 360 as power supply for the drive.
Homebrew extractor I made myself that's dumped over 60 LiteOn keys correctly so far.

[carranzafp]

QUOTE(Iriez @ Oct 26 2008, 06:39 PM)

The evidence is sitting in this thread. Perhaps you need to re-read it. He has clearly defined and explained how the bug works. What do you want, for him to fix your code too? LOL. christ.

Dumping it 5 times WILL NOT fix the problem. Dumping it 5 times will produce the SAME problem...every...single..time. Thats why its a bug. Hell, oggy and mp3boy just tested over 70 drives, and showed you exactly how many were affected by your bug. What more evidence do you need? Fix your shit.

Iriez sorry for telling you but the one who needs to re-read is you: What he did is an explanaition on how the key frame travels over serial cable, there is no evidence of a bug on that, thats what I already knew (from Logic analyzer and from Geremias direct explanaiton). And the reason he says is a byte dropped and that could be caused also for a bad routing on the cable or poor soldering cable on the max232 hardware and thats is not ALL-TIME replicable.  

If you restart the drive and the application I could not see how magically the buffer offset displacement is still there (data retention batteries on the UART registers?).  

QUOTE(OggyUK @ Oct 26 2008, 06:48 PM)

No need for nasties, all we did was advise there is a bug, put the other thread to bed and move on FFS. This was never intended as a personal attack on you or your work.

Really?  can u check who was the last who post on that old topic?  mmhh let me see.. wasnt you?  asking ironically for the 0.9999999999 release ?  Dont back off on your comments m8, what you have said has been said, dont try to look like a victim now.

QUOTE(mp3boy @ Oct 26 2008, 06:59 PM)

I checked my backup data for the keys that would trigger the bug, then dumped those 4 drives again using your software to see what would happen and it triggered the bug as expected.

Based Only on the podger technical explanation: I could not see how you can see the keys and predict a bad reading.  

As I told you before, use whatever you want/like/trust.

[OggyUK]

QUOTE(carranzafp @ Oct 26 2008, 06:56 PM)

Really?  can u check who was the last who post on that old topic?  mmhh let me see.. wasnt you?  asking ironically for the 0.9999999999 release ?  Dont back off on your comments m8, what you have said has been said, dont try to look like a victim now.

Thats what moving on is about ??

No?

Ill stick to what I trust for sure (IMG:style_emoticons/default/wink.gif)

As for mp3boy, I done similar AFTER manually viewing it in HW5

Search for 'trigger'

use Inq.bin to locate drive, hook up, dump using xtractor 2.3 - compare keys.

Its just coincidental we all get the same bug, using the same triggers and your program?

We have different hardware setups, outlined above.

The keys we searched are gold, the consoles are working fine up and down the UK to this day.

This post has been edited by OggyUK: Oct 26 2008, 07:30 PM

[mp3boy]

QUOTE(carranzafp @ Oct 26 2008, 07:56 PM)

Based Only on the podger technical explanation: I could not see how you can see the keys and predict a bad reading.

I have a little more information than that. Trust me, the bug is there. I can make a video of it if you want (IMG:style_emoticons/default/tongue.gif)

[Iriez]

QUOTE(carranzafp @ Oct 26 2008, 01:56 PM)

Iriez sorry for telling you but the one who needs to re-read is you: What he did is an explanaition on how the key frame travels over serial cable, there is no evidence of a bug on that, thats what I already knew (from Logic analyzer and from Geremias direct explanaiton). And the reason he says is a byte dropped and that could be caused also for a bad routing on the cable or poor soldering cable on the max232 hardware and thats is not ALL-TIME replicable.  

If you restart the drive and the application I could not see how magically the buffer offset displacement is still there (data retention batteries on the UART registers?).  
Really?  can u check who was the last who post on that old topic?  mmhh let me see.. wasnt you?  asking ironically for the 0.9999999999 release ?  Dont back off on your comments m8, what you have said has been said, dont try to look like a victim now.
Based Only on the podger technical explanation: I could not see how you can see the keys and predict a bad reading.  

As I told you before, use whatever you want/like/trust.

He explained the exact environment and varibles in which the bug occurs. If you are not intelligent enough to figure out how to fix it, given his explanation, then perhaps you need to rethink your software development.

It is NOT the cable, NOT poor soldering. It is replicable 100% given a specific key pattern. Did you not gather that? Did you not read what the others are posting? This is absurd.

And this is the LAST time im going to say this, before I start deleting EVERYONES posts on this topic. This is NOT a playground or flamewar thread. This is supposed to be a relevant discussion to help improve YOUR software. Podger has moved on, has been courteous and polite in this thread, and I expect you to do the SAME or you will not post here. understand?

I expect this rule to be followed by every participant here, in this thread, and any future threads. You are developers, not lamers trolling forums.

[carranzafp]

QUOTE(Iriez @ Oct 26 2008, 11:47 PM)

He explained the exact environment and varibles in which the bug occurs. If you are not intelligent enough to figure out how to fix it, given his explanation, then perhaps you need to rethink your software development.

It is NOT the cable, NOT poor soldering. It is replicable 100% given a specific key pattern. Did you not gather that? Did you not read what the others are posting? This is absurd.

And this is the LAST time im going to say this, before I start deleting EVERYONES posts on this topic. This is NOT a playground or flamewar thread. This is supposed to be a relevant discussion to help improve YOUR software. Podger has moved on, has been courteous and polite in this thread, and I expect you to do the SAME or you will not post here. understand?

I expect this rule to be followed by every participant here, in this thread, and any future threads. You are developers, not lamers trolling forums.

The absurd is the position you take.  re read the post, he is saying he got a byte overrun on one read he is not giving details on how to replicate the "ghost" bug.  the buffer overrun can be lead more to HARDWARE problem than a software problem, the hardware (UART) is the one who handle the asincronous signal.  

Stop saying you say what you say on protection of development, because its obvious you have choosen a side now.  And yes I should be stupid but for barely thinking this discussion have a good intention or even will have an end, when the root problem is other than the discussed the things never end.

Im totally disappointed now, you dont seems to be same guy who I used contact, you appear have 2 faces.

[nilezon]

QUOTE(carranzafp @ Oct 27 2008, 07:13 AM)

The absurd is the position you take.  re read the post, he is saying he got a byte overrun on one read he is not giving details on how to replicate the "ghost" bug.  the buffer overrun can be lead more to HARDWARE problem than a software problem, the hardware (UART) is the one who handle the asincronous signal.  

Stop saying you say what you say on protection of development, because its obvious you have choosen a side now.  And yes I should be stupid but for barely thinking this discussion have a good intention or even will have an end, when the root problem is other than the discussed the things never end.

Im totally disappointed now, you dont seems to be same guy who I used contact, you appear have 2 faces.

Well, if it is a hardware problem, maybe the software could identify bad keys and warn the user?

[Iriez]

QUOTE(carranzafp @ Oct 27 2008, 12:13 AM)

Im totally disappointed now, you dont seems to be same guy who I used contact, you appear have 2 faces.

Look at it from my point of view. Several sources have confirmed a bug, and they have put out a detailed explanation of how it was replicated. Yet, you still seem to doubt the situation.

This is not about sides, it is about the community. I will always do whats in the best interest of this scene, not any particular developer.

[DeXteR_CwB]

QUOTE(podger @ Oct 25 2008, 02:42 PM)

Hi folks, just did some testing.... In SOME cases this utility will give the incorrect DVD Key.....

*** Use it at your own risk ***

I will pass the details to Maximus later.....

gtg

 I have this problem here, retrieve a invalid key. ( last numbers is 8320 )

 But i used the Dvdkey 1.1 in DOS and everithing is ok!!

[carranzafp]

QUOTE(nilezon @ Oct 27 2008, 10:04 AM)

Well, if it is a hardware problem, maybe the software could identify bad keys and warn the user?

Yes, and thats exactly what it does now (version 2.4) if detects hardware problems will notify the user. I hope other tools do it too.

Also, there is no way a man can predict a buffer overrun based on "backup data" obviously such comment has another objective.  Anyway, all is said on the topic no need to add more.

[calloused labia]

QUOTE(carranzafp @ Oct 27 2008, 10:17 PM)

Yes, and thats exactly what it does now (version 2.4) if detects hardware problems will notify the user. I hope other tools do it too.

Also, there is no way a man can predict a buffer overrun based on "backup data" obviously such comment has another objective.  Anyway, all is said on the topic no need to add more.
 

Through-out the thread you mention the problem is caused by a (well known) hardware issue.   Which makes me wonder why you would wait to put a fail safe in place until  others pointed it out.

Why doesn't DVDKEY and DVDKEY32 have the problem?
Is it because that software already has a fail-safe in place?

[sparky2k1]

Been watching this thread with interest as I got hold of this tool (quite late I must add)
Now
I have modded a few Lite-ons recently, all using a Max232 interface before and using dvdkey 1.2 in dos, got keys and spoofed drives, all work fine, so I'm certain the keys are good and keep them for support BUT read podgers post the other day and decided to test out ma Xtractor and found 2 drives with the "83 20" bug, seen 2.4 and said to myself jezz that was quick. Fair Play!  So I tried the drives again but now it gives me some daft message saying my setup is wrong  (IMG:style_emoticons/default/uhh.gif)

It would appear to me that the SW developer aint just got it right yet so again I say the tool should have been withheld before pouncing on a famous site, and promotion on many a web site selling it if all's not correct!

sparky2k1's final thoughts:
Fake bug! somehow I dont think so. Spend some time testing and less time covering your mistakes and we'll all be better off when the tools does as its been advertised to do.

 (IMG:style_emoticons/default/blink.gif)

This post has been edited by sparky2k1: Oct 28 2008, 07:28 PM

[GothTech]

QUOTE(carranzafp @ Oct 28 2008, 04:17 AM)

Yes, and thats exactly what it does now (version 2.4) if detects hardware problems will notify the user. I hope other tools do it too.

Also, there is no way a man can predict a buffer overrun based on "backup data" obviously such comment has another objective.  Anyway, all is said on the topic no need to add more.

its a shame that i went out payed 53$ for this and cant even get the person who made it to pm me to answer my Q seems to me he wants to get mad at every one for helping him out hope he can do a little growing up

[farntheplaya]

your not buying something made for the average joe

the product was launched not too long ago give the dev some time, he cant answer everyones PMs

just hang on if you have a problem post here, maybe someone will help

[MODMANMIKE]

I luv my new xtractor it wks great !! might have a couple bugs but so what