[WT-support] EZMaster and Windows 8

Mon Jul 20 09:17:34 CEST 2015

Thanks for sharing this, Oliver.

Well done on finding the solution.

73

Don, G3BJ / G5W

www.g3bj.com

-----Original Message-----
From: support-bounces at f5mzn.org [mailto:support-bounces at f5mzn.org] On Behalf
Of Olivier Le Cam
Sent: 19 July 2015 22:26
To: support at win-test.com
Subject: Re: [WT-support] EZMaster and Windows 8

Hello,

Well thanks everybody, I've been able to get my EZM recognized!

It's a bit more tricky on win8.1 because the .INF files are digitally signed
for integrity garantee. So, when you modify it, the operating system refuses
to install the driver anymore, stating for a "hashing error".

Here is the step by step workaround which worked for me:

1) Get "Microsoft USBView" tools from
http://www.ftdichip.com/Support/Utilities.htm. Connect the EZmaster, then
launch USBView in order to get the VID and PID for your EZMaster:
idVendor: 0x0400
idProduct: 0x6001

2) Disconnect EZMaster from the USB port

3) Download the latest driver from ftdi:
http://www.ftdichip.com/Drivers/CDM/CDM%20v2.12.04%20WHQL%20Certified.zip

4) Unzip it. Open both ftdibus.inf and ftdiport.inf and add some row with
the VID/PID of the EZMaster.

Here are the modifications I have done, in "patch" format:

--- ../CDM v2.12.04 WHQL Certified-origin/ftdibus.inf	2015-07-19 
22:51:04.000000000 +0200
+++ ftdibus.inf	2015-07-19 22:52:33.000000000 +0200
@@ -273,6 +273,7 @@ FtdiBus.NTamd64.Copy3 = 10,syswow64
 
%USB\VID_0403&PID_601C&MI_03.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_601C&MI
_03
  %USB\VID_0403&PID_0FEC.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_0FEC
  %USB\VID_0403&PID_0000.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_0000
+%USB\VID_0404&PID_6001.DeviceDesc%=FtdiBus.NT,USB\VID_0404&PID_6001

  [FtdiHw.NTamd64]
  %USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6001
@@ -296,6 +297,7 @@ FtdiBus.NTamd64.Copy3 = 10,syswow64
 
%USB\VID_0403&PID_601C&MI_03.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_60
1C&MI_03
  %USB\VID_0403&PID_0FEC.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_0FEC
  %USB\VID_0403&PID_0000.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_0000
+%USB\VID_0404&PID_6001.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0404&PID_600
+1

  [ControlFlags]
  ExcludeFromSelect=*
@@ -384,5 +386,6 @@ USB\VID_0403&PID_601C&MI_02.DeviceDesc="
  USB\VID_0403&PID_601C&MI_03.DeviceDesc="FT4222H Interface D"
  USB\VID_0403&PID_0FEC.DeviceDesc="UMFT4222PROG"
  USB\VID_0403&PID_0000.DeviceDesc="USB Serial Converter"
+USB\VID_0404&PID_6001.DeviceDesc="EZMaster"
  SvcDesc="USB Serial Converter Driver"
  ClassName="USB"



--- ../CDM v2.12.04 WHQL Certified-origin/ftdiport.inf	2015-07-19 
22:51:04.000000000 +0200
+++ ftdiport.inf	2015-07-19 22:53:45.000000000 +0200
@@ -257,6 +257,7 @@ ExcludeFromSelect=*
 
%VID_0403&PID_6014.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_0403&PID_6014
 
%VID_0403&PID_6015.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_0403&PID_6015
 
%VID_0403&PID_0000.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_0403&PID_0000
+%VID_0404&PID_6001.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_0404&PID
+_6001

  [FtdiHw.NTamd64]
 
%VID_0403&PID_6001.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_0403&PID
_6001
@@ -265,6 +266,7 @@ ExcludeFromSelect=*
 
%VID_0403&PID_6014.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_0403&PID
_6014
 
%VID_0403&PID_6015.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_0403&PID
_6015
 
%VID_0403&PID_0000.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_0403&PID
_0000
+%VID_0404&PID_6001.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_040
+4&PID_6001

  [FtdiPort.NT.AddService]
  DisplayName    = %SvcDesc%
@@ -355,6 +357,7 @@ VID_0403&PID_6011.DeviceDesc="USB Serial
  VID_0403&PID_6014.DeviceDesc="USB Serial Port"
  VID_0403&PID_6015.DeviceDesc="USB Serial Port"
  VID_0403&PID_0000.DeviceDesc="USB Serial Port"
+VID_0404&PID_6001.DeviceDesc="EZMaster"
  SvcDesc="USB Serial Port Driver"
  SerEnum.SvcDesc="Serenum Filter Driver"


5) Now if you try to install the driver again, it won't work because the
digital signature does not match. It is necessary to disable the Driver
signature verification in Windows.

First method: 
https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8

Second method, the one I have used: Open a elevated command prompt (Windows
+ X, cmd/admin) and run:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS & bcdedit -set TESTSIGNING
ON

6) Reboot

7) You can know install the drivers (just run "dpinst-amd64.exe", on
right-click/install on ftdibus.inf then on ftdiport.inf). You will be
prompted to accept installation of drivers that are "unknown".

8) Connect again the EZMaster: it should now be detected!...

9) Enable again the server signature, in an elevated command prompt enter
the following:

bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS & bcdedit -set TESTSIGNING
OFF

Reboot and you are done! :)

Thanks everybody for their help, especially G3BJ, F6BEE, I4UFH and CT3FQ.

PS: I also have an MK2R+, and I like both products. I just wanted to have
them both working on my new setup, so don't waste your time with comments.
Thanks in anticipation.

Best 73,
--
Olivier

_______________________________________________
Support mailing list
support at win-test.com
http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6081 / Virus Database: 4392/10265 - Release Date: 07/19/15

