| Author |
|
renard
Groupie
Joined: November 01 2009
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: October 09 2015 at 14:00 | IP Logged
|
|
|
I am upgrading for 32-bit to 64-bit Win7 in anticipation of moving to Win10. I am having trouble with the 64-bit driver for the virtual USB port I use for the PLM. I downloaded the 64-bit driver package from FTDI but Windows complains that the driver package which seems to install fine is corrupted. PH fails to connect to the PLM. Is the PH 2.1.5c package supposed to be clever enough to load the 64-bit driver, that did not seem to work at all, or where should I get the PH compatible driver?
Stuck for now.
Thanks
__________________
Terry
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 09 2015 at 15:02 | IP Logged
|
|
|
Terry,
Not sure why the FTDI driver included with PowerHome
didnt work for you. To the best of my knowledge,
everyone that is using PowerHome on a 64 bit system
just used the included drivers.
That being said, I checked the FTDI website and they
don't make a distinction between 64 bit and 32 bit
drivers (they have two separate links listed for the
zip file but they both resolve to the same file). In
any event, the latest driver I found (exe) is here:
FTDI Driver which should work (this may the same driver you already tried).
Dave.
Edited by dhoward - October 09 2015 at 15:09
|
| Back to Top |
|
| |
renard
Groupie
Joined: November 01 2009
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: October 10 2015 at 00:02 | IP Logged
|
|
|
Thanks Dave,
I'll try it again. That was the same file. This PC has only PH and my SQL server and only PH is loaded so I am just getting to start over fresh.
__________________
Terry
|
| Back to Top |
|
| |
renard
Groupie
Joined: November 01 2009
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: October 10 2015 at 10:12 | IP Logged
|
|
|
Here is the interesting story. Spending some time on Google regarding driver signing, Windows complaining that 'the driver package has an invalid digital signature that can not be verified (Error 52)', I found a workaround. During the Win7 boot process, tap F8 repeatedly until you get the Advanced Boot Menu and turn off driver signing enforcement. PH then works fine.
The drivers in PH 2.1.5c and on the FDTI site have defective digital signatures and until that is fixed by FDTI, apparently you can not use a virtual USB serial port to talk to your PLM. This is a problem that will affect both 32-bit and 64-bit usage.
Somebody at FDTI probably let the digital signing certificate lapse. I believe they are only good for a year.
I now have PH running on 64-bit Windows 7.
__________________
Terry
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 10 2015 at 10:35 | IP Logged
|
|
|
Terry,
Awesome! Thats the first Ive heard about the driver
signing issue and never encountered it in my own setup
(I have PowerHome installed on Win 7/32).
Great detective work though and really appreciate you
posting back with your findings. I'll make a note of
this to include this info in future PowerHome releases
in case someone else encounters this problem.
Glad to hear you got your installation working as
well.
Dave.
|
| Back to Top |
|
| |
renard
Groupie
Joined: November 01 2009
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: October 10 2015 at 19:55 | IP Logged
|
|
|
N.B. The 'fix' only works for the current boot. Reboots including unattended ones :) will require the same procedure until this is fixed at the source.
__________________
Terry
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 11 2015 at 15:12 | IP Logged
|
|
|
Terry,
That sucks. I wonder if this behavior is a result of a
patch or service pack for Windows 7 since I havent heard
of anyone else having this problem.
I'll do some research and see if I can find out
anything. Please let me know if you discover any
additional info.
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 11 2015 at 15:34 | IP Logged
|
|
|
Terry,
Looks like its an x64 bit issue. Found out its a
common problem with no good solution. This site seemed
to have some good info:
https://www.raymond.cc/blog/loading-unsigned-drivers-
in-windows-7-and-vista-64-bit-x64/
However, everything that I can turn up seems to
indicate that the FTDI drivers are signed so should
not be a problem. As a test, I took my wife's Windows
7/64 laptop (never had PowerHome installed) and the
FTDI exe driver listed a couple of posts ago and
copied it to her machine. I then right-clicked and
selected "Run as Administrator" and it went right
through and loaded the drivers with no problems at
all.
Wondering if it might be some other software or
something else causing a conflict.
Dave.
|
| Back to Top |
|
| |
renard
Groupie
Joined: November 01 2009
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: October 11 2015 at 16:23 | IP Logged
|
|
|
OK, I think we turn off the bit (or 64 bits) off on this one. Here is the deal. I did a partition backup on the Win7/32 partition and did a clean install of Win7/64. As this PC is dedicated to running the house as well as my SQL server, I loaded PH before anything else so PH was down as little as possible. PH or rather the FTDI driver behaved as cited above. After finding the sort of workaround above, I continued loading my standard utilities and the MySQL software.
I then got to the 201 Win/64 updates (the system was loaded with Win/64 SP1 DVD which is four years old.
One of those updates refreshed the Windows Certificate Store (that is what is called) with a current certificate that matched the one FTDI offered- end of problem.
The moral of the story here is when you are reloading or upgrading a PC, perhaps to get to 64 bit in anticipation of going to Win10. Let the system do all the Windows updates before you try to use it, even of you have to walk around and turn the lights on and off yourself. Be prepared to spend 6-8 hours loading all the updates and hope it does not burn up your C:\ drive. Mine was at 53C for most of the day, in the warning zone.
All is well now.
__________________
Terry
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 11 2015 at 18:30 | IP Logged
|
|
|
Terry,
Glad it had an (ultimately) happy ending. I know what
you mean about the Windows update crap though. It takes
FOREVER. Im just happy to hear that there was an
explanation for all of the bizarre behavior. Hate it
when you just cant figure out WHY something happens the
way it does.
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Virtual USB Driver for 64-bit Win7
