Tool # 0.2 Beta RELEASED!!

Thanks guys. I suggested the Guerilla layout because I figured it would be a familiar environment to work within for the end-user. Now, all we need are decent suggestions. Anyone have any ideas?

I thought this would be another Tool++ but this is quite unique. Good job :P

at first malwarbytes' anti malware said it had a trojan banker in it, but now it just says this: http://i37.tinypic.com/n2ltub.jpg bug perhaps?

Malware Anti-Bytes could have been referring to the program Tool # was trying to initialize. There are no viruses in Tool #, and for all I know, the only thing that could have triggered it would have been that I embedded the help file and it writes it as bytes to the hard drive, or the detection of the Tool files.

Try changing the selected Tool from the menu list at the top, and see what happens.

EDIT: Here's a Jotti scan of Tool #:
http://virusscan.jotti.org/en/scanre...5dc9da532e23bd

And here's a virus-scan of the toolpro.exe I'm testing for Tool #, which as you can see has been picked up by one AV to contain Trojan.Crypt.Gen, it is possible that we have the same version of Toolpro and your AV picked it up.
http://virusscan.jotti.org/en/scanre...377b77b1ec1bc7

The AV is alerting because of Process.Start()

now that i look at it, it said tool pro is the virus. i might have downloaded a bad version of it. can you upload yours for me so i can see if thats the problem?

oh and one more note, i see that normal tool is greyed out in the menu, but its right there in my halo ce folder

nice stuff

Quote:

---

Originally Posted by CrAsHOvErRide

The AV is alerting because of Process.Start()

---

If that was the case, Rambo's AV would have gone off like crazy when we were testing it and so would have mine.

As for my version of Toolpro, as you can see the AV says it has a Trojan as well, but I can upload it later on when the next release comes.

And the final bug of Tool not being enabled has to do with detection. Make sure it's an unmodified Tool.exe that has an MD5 hash of: 1f18ecb6f0acdcd0b0455aa4f7e06b73. The Filename won't matter because I don't do a check based on the filename (avoids major bugs that way)

You can easily check the hash of your tool.exe right here and make sure it matches with the one that I have. My tool.exe is the one installed with HEK, and that's how I base my detection function inside Tool #

Sure I can upload Toolpro for you. My build is clean. I used AVG to scan it and Chaos used Jotti to scan it. Virusbuster did find a Trojan Crypt in it but ignore it because it's proven harmless on our computers. It probably has to do with Kornman00's old hacks to the tool itself. We've never noticed any problems with our computers as a direct or indirect result of toolpro.

awesome thanks. but do you know why normal tool wont let you click on it in the menu?