Detector Tools 1.3 refuses to run

[Ovencleaner]

You could also try running it in OllyDBG/Softice to figure out where/what exactly the error is, although that might be a little technical for you

[MEM-TEK]

Hi everyone,

I really need a computer guru to comment on my thoughts and observations below:

NOBODY TRY THE FOLLOWING! I AM AWAITING ONE OF OUR COMPUTER GURUS TO COMMENT IF THIS MIGHT WORK OR TO TRY IT FIRST!

I haven't installed Radar Detector Tools yet, but I did notice that the zip file contains two copies of:

WindowsInstaller-KB893803-v2-x86.exe

One copy is in the DotNetFX directory, and the other copy is in the WindowsInstaller3_1 directory.

What's up with that? The extra copy of Windows Installer 3.1 increased the size of the zip file by 2.5MB. Not only that, can you imagine what weird problems could occur if two copies of Windows Installer were running in order to update Windows Installer to 3.1 and at the same time trying to install the DotNetFX software and the RD Tools software?

Here is my idea:

1. Uninstall the RD Tools software.

2. Download and run Microsoft's MSI Cleanup Utility to be sure that RD Tools no longer is listed in the MSI database. If it is, delete it!

3. Obviously MSI 3.1 should already be installed on your computer, but it wouldn't hurt to run just one of the two included copies of MSI 3.1 just to be sure that MSI 3.1 is installed correctly.

4. Manually run the dotnetfx.exe file to install DotNetFX.

5. Reboot.

6. Manually run the DetectorTools.msi instead of setup.exe to install the RD Tools software.

[mswlogo]

Try running the program under Dependency Walker to track down where the problem is, and let Escort know if you find the problem.

Been there done that.

Dependcy walker is only partially useful due to dynamically loaded DLL's.

[mswlogo]

Hi everyone,

I really need a computer guru to comment on my thoughts and observations below:

NOBODY TRY THE FOLLOWING! I AM AWAITING ONE OF OUR COMPUTER GURUS TO COMMENT IF THIS MIGHT WORK OR TO TRY IT FIRST!

I haven't installed Radar Detector Tools yet, but I did notice that the zip file contains two copies of:

WindowsInstaller-KB893803-v2-x86.exe

One copy is in the DotNetFX directory, and the other copy is in the WindowsInstaller3_1 directory.

What's up with that? The extra copy of Windows Installer 3.1 increased the size of the zip file by 2.5MB. Not only that, can you imagine what weird problems could occur if two copies of Windows Installer were running in order to update Windows Installer to 3.1 and at the same time trying to install the DotNetFX software and the RD Tools software?

Here is my idea:

1. Uninstall the RD Tools software.

2. Download and run Microsoft's MSI Cleanup Utility to be sure that RD Tools no longer is listed in the MSI database. If it is, delete it!

3. Obviously MSI 3.1 should already be installed on your computer, but it wouldn't hurt to run just one of the two included copies of MSI 3.1 just to be sure that MSI 3.1 is installed correctly.

4. Manually run the dotnetfx.exe file to install DotNetFX.

5. Reboot.

6. Manually run the DetectorTools.msi instead of setup.exe to install the RD Tools software.

That might all be fine on XP, but not on Vista. That is probably a 2.0 DotNet and you cannot install 2.0 .Net or Uninstall it on Vista. It's part of the OS. But it can have a Service Pack applied to it. Which is what .Net 3.5 SP1 did.

[mswlogo]

I tried installing it at work for grins.

It also fails.

This Machine also has .Net 3.5 SP1 Which includes .Net 2.0 SP2

I believe .Net 2.0 SP2 Breaks it (And I suspect it's due to obfuscator).

[MEM-TEK]

Oh well, it was just a thought.

[Governator]

No problems running v 1.3 here on Vista 64 Ultimate SP1 thankfully and that was after uninstalling v1.2...

[mswlogo]

No problems running v 1.3 here on Vista 64 Ultimate SP1 thankfully and that was after uninstalling v1.2...

Just watch out when this come through as an automatic update. Poof.

Download details: .NET Framework 3.5 Service pack 1

[Governator]

Just watch out when this come through as an automatic update. Poof.

Download details: .NET Framework 3.5 Service pack 1

Interesting, thanks. I don't have my updates set to automatic, nor have I ever had it that way, always manual for good reason Having said that, I combed through my update/Hotfix list and don't see that particular update, maybe a good thing who knows nevertheless I've had zero issues with .dot net apps.

In the meantime, you might be interested in this little app:

DotNet (.NET) Version Check download page

This is what I get when I run it...

http://i306.photobucket.com/albums/n...8/runtimes.jpg

[mswlogo]

Interesting, thanks. I don't have my updates set to automatic, nor have I ever had it that way, always manual for good reason Having said that, I combed through my update/Hotfix list and don't see that particular update, maybe a good thing who knows nevertheless I've had zero issues with .dot net apps.

In the meantime, you might be interested in this little app:

DotNet (.NET) Version Check download page

This is what I get when I run it...

http://i306.photobucket.com/albums/n...8/runtimes.jpg

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.