If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
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.
__________________
Radar detectors which I use: 9500ci, STi, 9500i and V995.
Check out my Vintage Radar Detector collection.
Quotes of the Month: ersin: "Gotta love Radio Shack. 'You've got questions. We've got blank stares.'" tactical22: "Please lean forward so I can slap you ..."
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.
__________________
Radar detectors which I use: 9500ci, STi, 9500i and V995.
Check out my Vintage Radar Detector collection.
Quotes of the Month: ersin: "Gotta love Radio Shack. 'You've got questions. We've got blank stares.'" tactical22: "Please lean forward so I can slap you ..."
No problems running v 1.3 here on Vista 64 Ultimate SP1 thankfully and that was after uninstalling v1.2...
__________________ (Click-->"Here" to see my ride)
Countermeasures: Escort9500ix (v1.1, Hardwired, Up High) "Expert Mode" - Custom Installed (Dash & Center Console)"Escort Direct Wire Cord w/ Round Mute Button & Dual Blue (Alert)/Red (Power) L.E.D.s" LI Dual (Rev. 2.8, CPU v 7.05, [7.06 on ???]) Heads: v 8.05
2x "Laser Shields" VEIL G4 Member: National Motorist Association
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:
__________________ (Click-->"Here" to see my ride)
Countermeasures: Escort9500ix (v1.1, Hardwired, Up High) "Expert Mode" - Custom Installed (Dash & Center Console)"Escort Direct Wire Cord w/ Round Mute Button & Dual Blue (Alert)/Red (Power) L.E.D.s" LI Dual (Rev. 2.8, CPU v 7.05, [7.06 on ???]) Heads: v 8.05
2x "Laser Shields" VEIL G4 Member: National Motorist Association
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:
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.
Radar Roy's Detector and Jammer Buyer's Guide!
For pros or novices, this FREE 22 page consumer report is a must read for anyone considering any speed counter measure device. Radar Detector Buyer's Guide
Visit RadarBusters for all your Speed Countermeasure Equipment RadarBusters.com
Re: Detector Tools 1.3 refuses to run 
"
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.
