Detector Tools 1.3 refuses to run

[Governator]

I said WHEN it comes through as an automatic update. It's not being push out yet but will eventually. I've rarely had a service pack or automatic update ever break anything. And when it has it's usually been the application that was not doings things right.

Thanks, but that .Net Version check utility is useless. The Sub Version, Build # etc. for each .Net Version is the same regardless if a Service Pack is applied or not so that the interface "looks" identical.

Well I'll keep en eye out for it then, thanks.

[leo68]

I can't get the program to RUN !!!

I'm not stuck loading it into the detector. I'm not stuck installing it.

It just won't run at all on the desktop.

Is the Anti-Virus software on your computer stopping the program on your computer. You may want to call escort for technical support?

[mswlogo]

It's not AntiVirus, I don't run it on most of my machines.

It is .Net 2.0 SP2 That it trips over.

I have 4 Vista Machines 3 Had .Net 2.0 SP2 and 1 did not. The one that did not still runs.

There is nothing Escort can do until they release a version compatible with .Net 2.0 SP2 (more likely until their thirdparty Vender that does obfuscator).

I believe they are using RemoteSoft Obfuscator. I used this product in a past company and it was a nightmare.

Look in Detector Tool folder and you'll see rscoree.dll this is a HACKED interface to mscoree.dll (.Net run time). Note the name starts with rs (RemoteSoft).

The thread below is running into the same problem with another application using RemoteSoft Obfuscator.

I installed VS 2008 SP1 which installs .Net 3.5 SP1 which installs .Net 2.0 SP2.

Notice the comments at the bottom of this thread. RemoteSoft has confirmed it is a problem.

https://connect.microsoft.com/Visual...&wa=wsignin1.0

[billy1ear]

I just updated to 1.3 and it did not work at first either.
They put the program in a new location and the shortcut I saved pointed to the old one.


The app is now in:
C:\Program Files (x86)\Escort\Detector Tools\
and the application is:
Detector Tools.exe

oh yeah, i am running vista 64

[swarga]

There is nothing Escort can do until they release a version compatible with .Net 2.0 SP2 (more likely until their thirdparty Vender that does obfuscator).

I believe they are using RemoteSoft Obfuscator. I used this product in a past company and it was a nightmare.

Look in Detector Tool folder and you'll see rscoree.dll this is a HACKED interface to mscoree.dll (.Net run time). Note the name starts with rs (RemoteSoft).

The thread below is running into the same problem with another application using RemoteSoft Obfuscator.

So basically all this hassle is due to some bull**** copy-protection scheme?

What's next, installing a rootkit on your PC? Oh, wait - that's already been done by Sony...

[mswlogo]

So basically all this hassle is due to some bull**** copy-protection scheme?

Yes, exactly.

You know there isn't a whole lot of intelligence in the stupid program. All it does is read the data merge it and write it back.

You could easily figure out what that is all doing with a USB sniffer.

[swarga]

You could easily figure out what that is all doing with a USB sniffer.

Shhhh!!!! Don't give them any ideas, or they'll make the USB functionality useless, too!

[yeswork]

Hi,

Any update to this problem?

I just got a 9500ix and installed Detector Tools 1.3 on Vista Home Premium with .Net 3.5 SP1 and Detector Tools won't run/start.

I installed Detector Tools on an old laptop running XP and everything works fine. I can connect to my 9500ix.

On Vista, tried un-iinstalling Detectors Tools 1.3 and re-installing as administrator, running as administrator. Tried running detector tools.exe directly. No luck! It just dosen't start.

Any word from Escort? Is a fixed 1.4 on the way? Should I bother calling tech support?

Thanks.

[Governator]

Just curious here, why are some of you running .Net 3.5 anyhow? Not many programs require it and in fact any program I've ever used thus far in Vista 64 that requires any .Net support such as D-Tools 1.3 has been fine with just the native .Net in the OS...

[mswlogo]

Just curious here, why are some of you running .Net 3.5 anyhow? Not many programs require it and in fact any program I've ever used thus far in Vista 64 that requires any .Net support such as D-Tools 1.3 has been fine with just the native .Net in the OS...

Because I write code that uses .Net 3.5 for a living.

Also .Net 3.5 SP1 includes service packs for .Net 2.0 which improves performance and fixes bugs. That's why .Net 3.5 SP1 breaks Detector Tools that is based on .Net 2.0. Microsoft didn't break it either, it's the thirdparty company Escort used that's doing some very ugly stuff that is not Service Pack compatible.