Deflate scan test

[Razor12911]

Originally Posted by felice2011

seems to me that you have never asked any help on your job

The only reason I don't ask is because I always believe that I can do something even if it's way beyond me, asking for help is my last resort, I'll just keep trying until I succeed, ask Panker or Ramiro, those are the people I speak with on a daily basis, I ask them sometimes to help me with something but before they comes with solution, I would have already figured it out, I only ask for help only if I give up on something which isn't really giving up but taking a break, like for example, "Where would you start if you wanted to replace raw2hif without bruting?" This is a question from me to you. (I already figured out the answer to that as I was writing)

Furthermore the interest and the feedback is always high on all your tests you post of some application alleging a future result of a compressor or precompressor, from our side for that that falls to us, we republish with pleasure the results negative or positive they are.

For example the test, I knew 80% of the outcome of the test, the 20% came from one of the users saying that not all streams were detected, I took note of that besides the test of seeing how fast the scanner can be plus I saw that you yourself were unable to get the information from it since it really didn't write anything, I also wasn't any of that expecting that, secondly, my target of this test was 50mb/s, I'm still using my old 2007 Core 2 Extreme, I'm getting 20-40mb/s using all 4 of my cores, all I wanted was to see whether rawdet can really be replaced or not but hey Chronocross would rather send cannons but if you were not referring to this test, maybe brute or fzr tests, well those projects are abandoned and I was a noob when I wrote those and the only good that would come out of them is just slowness when decompressing but if you're expecting something out of them and even if I continued with the project, the only responses I would get from you guys is just confirming what I already know "It's slow" but just so you know I uploaded the sources, you can finish them up because I already know the outcomes of the project onces it's done.

Regarding the chickens and the eggs do you a small example, a farmer has a goose that lays golden

eggs, and has confidence in her, as we have confidence in you, we are proud of her, as we are

proud of you, believes in her, as we believe in you, she takes care of her, the care and respect

day by day, waiting for the result of excellent eggs with the result of healthy chicks, but if

day after day, week to week the farmer sees that not getting any results, the poor hen loses

credibility.

Please do flip the page and look at it this way, week to week the programmer sees that not getting any results, the users lose credibility.

Now for goodness sake do not want to compare yourself to a chicken..ha ha ha this was just a

story with a precise concept, but remember bro, all of us we expect so much from you.

Well from what I remembered back in school, chickens aren't the only things that can lay eggs so in my defence, I wasn't comparing myself to a chicken

_____________________________
And as I said, the tests I post is to just to get you guys working although I know 80% of the outcomes, I only do this when I'm about to post a project or an important update and since I developed the project by myself, after posting the test and have received feedback, In my mind I say, "At least they tried to help", I then post the update or new program which is related to the test itself.

Someone recently asked why do I have many variants of reflate, the reason for this is I keep old variants of reflate then I post tests that I know their outcomes, 80% of the outcomes, the tests are almost meaningless but sometimes I'm lucky, I get 20% of the un4seen outcomes to see that you guys tried at least then once a new faster project is created, I just post it's predecessor, with reflate, I just post the predecessor before the predecessor because of that frustrations one encounters while creating it plus, I have never heard of a a dad buying his son or daugther a car better than the piece of crap he is currently driving, instead the car he is driving is passed down then he drives the new car.

Since I have a phobia with asking for help and after struggling to create a new project, I just can't post it, posting it's predecessor is better, this is why there is private and public project, whenever there is a breakthrough in something, predecessor is shared, I just made a breakthrough with the test I just posted, then I got tackled by felice and Chronocross. The reflate which is private may be available to public in the future, but not right now, it's successor is still and I'm having problem writings it's code, but heck no, I won't ask for help, people must have that mindset.

Originally Posted by ChronoCross

Of course you work for me!. And for all users of this comunity. You make very good tools public also in some cases you share your source code. How many reflate tools are here?. (in delphi). Your reflate tool, ramirocruzo, and the other guy with the crc extract problem. All this versions it's your source. And then when the people request something you do it. And this is nice! Because no one make applications like you. I mean very useful application. So i asking you if this test tool is for implement in a project more bigger like a super precompressor or something like that. And yeah i have very fast results.

Well then I quit, when was I appointed? Just joking.