Predator Software Versus Windows Vista

nootron69 · January 23, 2010

I got myself the Diablosport 7194 for my Sierra 5.3. Used reg tune first, didnt notice any huge difference, so next tank did the high octane tune. Seemed a little better, but I wanted to see about custom tunes and tweaking available through the predator home page and the included software (driver). I installed software, realized it wasn't for 64 bit windows, downloaded proper version (driver for handheld). Still wouldn't recognize it. I am not a computer illiterate, so went to device mangler (yes that is the word I meant) and when I would force a driver change, it would get to the end and say "windows was unable to install driver because of a duplicate title. If you know the manufacturer of your device. . .blah, blah blah. Additionally it would not install on com 3 like it is supposed to, and I cant figure out how to find out what is on com 3. Has anyone had any similar probs to this?

Prokopchuk_9 · January 23, 2010

i run a brand new MAC never have any issues like that...aaahhhh the windows blue's....

nootron69 · January 23, 2010

i run a brand new MAC never have any issues like that...aaahhhh the windows blue's....

Now THAT was helpful. Would any blues-playing users care to contribute something useful?

Visegrip117 · January 23, 2010

Sorry man, can't help you on this one.

The best I can do is BUMP it for you

fbachman · January 23, 2010

OK....you have Vista 64....

Let's get back to the beginning and start over.

Uninstall EVERYTHING/ANYTHING DS related... DSDownloader/Dataviewer... all that...

If you haven't done so already, I recommend turning User Account Control off completely. Google can tell you how. Search on "turn off UAC Vista64". I do this as a matter of practice, and I recommend doing so.

Make sure you are in an Administrator Account.

Re boot.

Log On to the/an Administrator Account (re-insure UAC is OFF)

On the 7194 support page, there is a DL for 64bit drivers for the PC Interface kit. DL that.

http://www.diablosport.com/index.php?modul...play&pid=88

listed as the "Prolific Drivers" near the bottom of the page....

Create a folder on the C: drive and name it DSDriver or something like that (really doesn't matter)

Copy the DLd driver exe file to THAT folder, then extract it there (within that folder)

Power up the predator, THEN plug it in via an available USB port. Let's make sure that it is a USB port connected directly to the machine, not one on an external USB hub for example..

At some point after plugging in the Pred via that USB port, you should get a message that a new device/hardware has been found. At that point, take a look at the message that pops up. Somewhere there, it should give you the option to search for drivers on the internet, or install them manually. Select to install manually, and browse to the DSDriver folder and let it find the driver there. It should find it, and the install should be fine. The Pred should now show up in Device Manager.

Let's get to this point and report back here, and we'll take it from there.

If you are already at this point, please forgive me. I may not have completely understood your issue. Again, let me know where you're at, and we'll take it from there.

I have everything working just fine on Win7x64. We'll get you there too on Vista64.

And, yes, it can be touchy. DS ain't exactly on the cutting edge with their software.

The COM3 thing... hmmm...Do you have another (external) device trying to use it and there is a collision?

GPSilverado · January 23, 2010

OK....you have Vista 64....

Let's get back to the beginning and start over.

Uninstall EVERYTHING/ANYTHING DS related... DSDownloader/Dataviewer... all that...

If you haven't done so already, I recommend turning User Account Control off completely. Google can tell you how. Search on "turn off UAC Vista64". I do this as a matter of practice, and I recommend doing so.

Make sure you are in an Administrator Account.

Re boot.

Log On to the/an Administrator Account (re-insure UAC is OFF)

On the 7194 support page, there is a DL for 64bit drivers for the PC Interface kit. DL that.

http://www.diablosport.com/index.php?modul...play&pid=88

listed as the "Prolific Drivers" near the bottom of the page....

Create a folder on the C: drive and name it DSDriver or something like that (really doesn't matter)

Copy the DLd driver exe file to THAT folder, then extract it there (within that folder)

Power up the predator, THEN plug it in via an available USB port. Let's make sure that it is a USB port connected directly to the machine, not one on an external USB hub for example..

At some point after plugging in the Pred via that USB port, you should get a message that a new device/hardware has been found. At that point, take a look at the message that pops up. Somewhere there, it should give you the option to search for drivers on the internet, or install them manually. Select to install manually, and browse to the DSDriver folder and let it find the driver there. It should find it, and the install should be fine. The Pred should now show up in Device Manager.

Let's get to this point and report back here, and we'll take it from there.

If you are already at this point, please forgive me. I may not have completely understood your issue. Again, let me know where you're at, and we'll take it from there.

I have everything working just fine on Win7x64. We'll get you there too on Vista64.

And, yes, it can be touchy. DS ain't exactly on the cutting edge with their software.

The COM3 thing... hmmm...Do you have another (external) device trying to use it and there is a collision?

In reference to the COM3 problem:

I believe the issue is caused the fact that the OP tried installing it once, and it didn't work, the tried installing it again using the proper procedures. It sounds like device manager probably has the device there on COM 3, although inproperly configured (left over from the first attempt). While in Device manager, there is an option under the view command for "show hidden devices" which may help. Also you can view devices by connection. You want to find the first attempt device, and uninstall it. Then re-install using the correct methods.

I ran into issies like this back in the days, where I wouldn't read instructions while hooking up a new printer. The instructions said to install the software first, then connect the USB cable, but I connected it first, and no amount of trying would let me install it after that, since windows didn't find the new printer being attached when prompted during software installation. Locating the failed first attempt device and deleting it solved the issue there.

Hopefully this helps, but I think the OP may have known to try this anyway, so basically just throwing this out there.

brims · January 23, 2010

For Vista I recommend this

fbachman · January 24, 2010

For Vista I recommend this

agreed....as long as you're using an armor-piercing, or explosive, round for maximum effect....

I would very much like the opportunity to fire a Barrett....must be awesome.

brims · January 24, 2010

agreed....as long as you're using an armor-piercing, or explosive, round for maximum effect....

I would very much like the opportunity to fire a Barrett....must be awesome.

I've wanted to fire one of those bad boys since I found out about them in high school.