• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question about crack

N

nickdakick

Platinum Member
I have one machine @ work running for more than a week. Dnet client is installed as a service of NT 4.0. It seems that nothing has been flushed yet. Buff-out.rc5 is about 370 K. What to do ?
 
a) start the taskmanager and shutdown Dnet there.
b) start the dnet client self.
c) minimize it.
d) there's your cow in your tray again.
e) right mouse click on the cow and select flush (or fetch&flush)
 
Or just go to the command line, go to the distributed.net folder, and type:

DNETC.EXE -FLUSH

Hopefully that will do it. If it's at work, you may be having problems with a firewall. Also, check to make sure you are not cracking OGR (unless that's the project you are wanting to crack for).

If either of these flush methods don't work, post back with the error messages from the flush attempt.

Ray
 
UH Excuse me, maybe you sould do dnetc -update so you don't do a bunch of ramdoms over the weekend.

My 2¢
 
Kilowatt is correct. The best is to use the -UPDATE option.

Hehe, I'm so used to doing the -FLUSH to squeeze out all the blocks I can before the daily cutoff time to stay ahead of The Federation. 😉
 
Does anyone else have this problem. My machine at work has Win2k and the client is installed as a service. I use a dialup connection but the client won't flush automatically, no matter what the dial-up detection options are. It uses virtually the same INI as my machine at home, so I know that can't be the problem. I can also flush manually but not automatically when I connect to the internet.

Has anyone else had this problem?
 
sciencewhiz:

I had that problem with a box at work!

Seemed like the admins were doing some changes to the firewall, finally I couldn't use the standard 2064 port anymore and had to change to 80.

Try that, maybe it'll help!

Hope you get it to work 😎

With love and respect your fellow TA member

Two-Face
 
sciencewhiz, you don't say whether it tries to flush, but can't, or if it just never tries.

If you have multiple IP addresses, one from a workplace NIC and another from the dial-up, your client may never see the new dial-up IP that you want it to flush through. I don't know the solution, but that may be the problem.
 
According to my log file, it never tries. I seem to remember it working with an earlier version (I am using 463). I don't have the time to play around with it, but I do seem to remember a bug report on dnet similar to my problem.

I guess the thing about IPs maybe the problem. There is a network card installed. It was supposed to go the the networkable printer that we never got.

There isn't any firewall. It is a small company and no one knows enough about networking to put one in.

Actually, I have plenty of time, just not when I'm at work. 🙁
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top