Jump to content

Predator Software Versus Windows Vista

nootron69

Recommended Posts

nootron69 Enthusiast

nootron69

Posted
Posted

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? :thumbs:

nootron69 Enthusiast

nootron69

Posted
  • Author
Posted
i run a brand new MAC never have any issues like that...aaahhhh the windows blue's.... :thumbs:

 

 

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

fbachman Senior Enthusiast

fbachman

Posted
Posted

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 Enthusiast

GPSilverado

Posted
Posted
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.

fbachman Senior Enthusiast

fbachman

Posted
Posted
For Vista I recommend this 82a1field.jpg

 

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

 

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

brims Senior Enthusiast

brims

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

 

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.

havo Enthusiast

havo

Posted
Posted

Use compatibility mode. Right click > Properties > Compatibility > Vista 32 bit (Or even XP SP2 if you want)

 

Hopefully that'll fix it

fbachman Senior Enthusiast

fbachman

Posted
Posted
Use compatibility mode. Right click > Properties > Compatibility > Vista 32 bit (Or even XP SP2 if you want)

 

Hopefully that'll fix it

 

Excellent suggestion. OR---upgrade to Win7 Pro, or above, download the XP virtual machine (free) and run it all from there..(?)

 

Never think to recommend that as I have had NO issues (at all) with compatibility (7x64)...maybe I'm just lucky...

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • newdude
      2020 Trailboss 6.2 replacement

      By newdude · Posted

      Correct.  2019-2020 are serviced by a different p/n.  19420611.   The recall engines 2021-2024 are serviced with 12740076.     What the difference is between the two, I'm not sure, but 2019-2020 only show 19420611 as the replacement engine p/n.  
    • 2017Z
      2020 Trailboss 6.2 replacement

      By 2017Z · Posted

      Looking for advice from this group. Took my flawless 2020 6.2 TB to an unnamed shop for routine rear brakes and oil change. Tech forgot to put oil back in after the full service and needles to say, destroyed my engine.  It’s all on their shop video so they are responsible.   I had my Chevy dealer do the analysis and they confirmed its compromised and said engine replacement. The manager said they only get GM reman engines from GM with full 3 yr warranty and the one they would put in is not same as what’s they are swapping out on 21-25 for recall.    I am looking for advice why that would be a different engine because obviously I had the good 6.2 year and replacing it has my concerns with that recall for 21-15   Also what’s the pros and cons of accepting the engine swap vs telling the shop that bricked the truck to pay up so I buy a new truck. I’m concerned about stigma resale eventually if I just decide to get rid of it after the swap or other issues showing up after the swap out.  
    • GN2018
      AFM Disabler Question

      By GN2018 · Posted

      Just looked up my records.  I've never gone over 5000 miles between oil changes.  At 46K miles, I have 10 oil changes.  I hope that will help.  I also installed the disabler last year.  I've still had a few times when it didn't seem to engage (which I can tell because the start stop feature kicks in), but for the most part, I think it's working.  For some reason, GM did not include the number of cylinders running in the information screen like I had on other models.  In my Cadillac, it shows me when it's running on 4 cylinders on the fuel milage screen.  I can't find that on my '21 Denali.
    • davester
      Wiring Help, Please

      By davester · Posted

      you might read through the info on gmupfitter.com for your truck, to find a good power source.
    • Grumpy Bear
      AFM Disabler Question

      By Grumpy Bear · Posted

      Melling I believe is/was the OEM on the lifters who explored this problem some years ago. The white paper they generated on the topic indicated two items of note when I read it. 1.) They only fail on the switch. Prevent the switch, prevent the failure. 2.) The majority fail due to deposits messing up the timing of that switch. Anyway that's what I got from it.    Mine have always been active, 195K+ now, and my oil maintenance is surgically clean.    Of course this assumes good parts. That is no heat treat issue or machining flaws. I get comfortable that these issues are in the rearview mirror by about 30K. IMHO naturally. 

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...