Problem with Sneaky.

[Russ]

I've been using Sneaky to fetch/flush several offline machines and, until now, it's been working perfectly. I was setting it at 2^28, but I just tried 2^33 and it whacks out.

Specifically, I set it to fetch 500 at 2^33 and it starts a perpetual loop of fetching 2000. If I don't shut it down, it just keeps going and going; finishing one fetch and starting another and creating temp files for each.

It does this on any setting other than 2^28. Any ideas what I'm doing wrong?

Russ, NCNE

 

[Polo]

What is the client version you are using ? The latest I presume ?

Sneaky is not meant to work with the latest release of DNECT.EXE because I actually don't have enough time to code and test it.
DNet made a lot of changes in the structure and syntax of the latest dnetc.ini file. Sneaky uses this file to work and some parameters should not be supported anymore by this client (I think that the syntax has change...) so Sneaky acts foolish...
I'm sorry but with the new baby at home (3 children now ) I don't think to have enough time to look at this before August...

I'll try to have a look but I can't promise you a soon release...
I have edited my profile to delete Sneaky from my sig.
Again sorry.

 

[Polo]

Can't let you down...
I'm searching right now. I've downloading the latest client and I'm playing with it...
One bug already found and corrected.
I have to search for more...
I'll keep you informed.

 

[Lord Demios]

Any chance you will open source it and release it under GPL? With this idea, all the coders here can help you maintain it. Just a thought

LD

 

[Polo]

Beware !!! Sneaky fetches PACKETS of WUs !!!
When you request it to fetch 500 2^33 packets, it will fetch 500 X 32 = 16000 WUs and needs 8 loops to do this !
So Sneaky will launch and stop the DNETC cracker 8 times in order to be able to feed your appetite of WUs.
The little bug I've found appears when there is no buff-out.rc5 file in your directory so it is not a critical bug because the client always creates one (even an empty one).
Hope this helps.

 

[Batti]

Heh, I figured out it was fetching PACKETS too. Took me a while to munch on all those blocks!!!

 

[Russ]

AHHH. Well, I let it cycle this time and, sure enough, it went thru 8 rounds of fetching and than eight rounds of shutting down the client. And, sure enough, it fetched about 14,000 WU's.

Russ, NCNE

 

[Viztech]

Another bug that I discovered was if you have the client configured to fetch by the TIME threshold, it will disobey the number of WUs (er packets) that you request, and fetch the number that would be required for the host client to crunch. I just disabled the time function, going back to that number of WUs that I required and this was solved. This occured with the 458 client.

Polo- Don't feel bad about these problems! Your cute little progy has just gotten a bit obsolete with these changes. It still works fine with the older clients.

viz

 

[Polo]

Viz : I'll try to correct this bug too and release a new version 2.21 this week-end.

 

[Viztech]

Thanx Polo

Your the best!

viz

 

[Polo]

Viztech : OK. Sneaky 2.21 is online. It should be able to bypass the "fetch-time-threshold" parameter. Try it and let me know if it's good.

 

[Viztech]

I'll give it a work out tonight!

Thanx for your work on behalf of TA Polo.

viz