Win64 driver for unsupported camera

[Forum_2016]

Hello friends,
one of my camera is a 1602E based camera, the producer is gone, website also, the drivers that I have are developed for win32 (up to win XP), my observatory PC is running win 7 64 so I cant use that camera in this moment, is there any possibility to "revive" it? Some sort of recompiling the driver? What about developing an ASCOM driver? Any ideas?

The inf file

; FTDIBUS.INF
; Copyright (c) 2000-2006 FTDI Ltd.
;
; USB serial converter driver installation for Windows 2000 and XP.
;

[Version]
Signature="$Windows NT$"
DriverPackageType=PlugAndPlay
DriverPackageDisplayName=%DESC%
Class=USB
ClassGUID={36fc9e60-c465-11cf-8056-444553540000}
Provider=%FTDI%
CatalogFile=ftdibus.cat
DriverVer=05/19/2006,2.00.00

[SourceDisksNames]
1=%DriversDisk%,,,

[SourceDisksFiles]
ftdibus.sys = 1
ftdiunin.exe = 1
ftdiun2k.ini = 1
ftbusui.dll = 1
ftd2xx.dll = 1

[DestinationDirs]
FtdiBus.NT.Copy = 10,system32\drivers
FtdiBus.NT.Copy2 = 10,system32

[Manufacturer]
%Ftdi%=FtdiHw

[FtdiHw]
%USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus,USB\VID _0403&PID_6001
%USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus,U SB\VID_0403&PID_6010&MI_00
%USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus,U SB\VID_0403&PID_6010&MI_01
%USB\VID_0403&PID_e169.DeviceDesc%=FtdiBus,USB\VID _0403&PID_e169

[ControlFlags]
ExcludeFromSelect=*

[FtdiBus.NT]
CopyFiles=FtdiBus.NT.Copy,FtdiBus.NT.Copy2
AddReg=FtdiBus.NT.AddReg,FtdiBusUnInst.NT.Reg

[FtdiBus.NT.HW]
AddReg=FtdiBus.NT.HW.AddReg

[FtdiBus.NT.HW.AddReg]
HKR,,"ConfigData",0x00010001,0

[FtdiBus.NT.Services]
AddService = FTDIBUS, 0x00000002, FtdiBus.NT.AddService

[FtdiBus.NT.AddService]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\system32\drivers\ftdibus.sys
LoadOrderGroup = Base

[FtdiBus.NT.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,ftdibus.sys
HKR,,EnumPropPages32,,"ftbusui.dll,FTBUSUIPropPage Provider"

[FtdiBus.NT.Copy]
ftdibus.sys

[FtdiBus.NT.Copy2]
ftdiunin.exe
ftdiun2k.ini
ftbusui.dll
ftd2xx.dll

[FtdiBusUnInst.NT.Reg]
HKLM,%WINUN%,"FTDICOMM"
HKLM,%WINUN%\FTDICOMM , "UninstallString",,"%11%\ftdiunin.exe %11%\ftdiun2k.ini"
HKLM,%WINUN%\FTDICOMM , "DisplayName",,"FTDI USB Serial Converter Drivers"
HKLM,%WINUN%\FTDICOMM , "URLInfoAbout",,"http://www.ftdichip.com"
HKLM,%WINUN%\FTDICOMM , "Publisher",,"FTDI Ltd"
HKLM,%WINUN%\FTDICOMM , "DisplayVersion",,"2.00.00"

[Strings]
Ftdi="FTDI"
DESC="CDM Driver Package"
DriversDisk="FTDI USB Drivers Disk"
USB\VID_0403&PID_6001.DeviceDesc="USB Serial Converter"
USB\VID_0403&PID_6010&MI_00.DeviceDesc="USB Serial Converter A"
USB\VID_0403&PID_6010&MI_01.DeviceDesc="USB Serial Converter B"
USB\VID_0403&PID_e169.DeviceDesc="SIGMA CCD-Kamera"
WINUN="Software\Microsoft\Windows\CurrentVersion\U ninstall"
SvcDesc="USB Serial Converter Driver"
ClassName="USB"


Take care and clear skies
Emil

[Forum_2016]

That driver seems only a sort of USB-serial converter, maybe an updated one from FTDI?
http://www.ftdichip.com/FTDrivers.htm (it's unlikely, but not impossible).
Maybe a WindowsXP virtual machine inside your Win64? (you will need to configure/bridge one USB port)

[Forum_2016]

Nope unfortunately no luck the drivers stuff, I will keep trying

[Forum_2016]

So update on this one, restarting Win 10 64 bit so that can accepted unsigned drivers did the trick after I modified the latest FTDI drivers to recognise the camera.
QUESTION:
Im into the journey of developing an ascom driver for my camera, some ideas, templates, or just infos?

Take care
Emil

[Forum_2016]

If a template exists, it's inside the ASCOM platform, but when I looked for it some years ago I didn't find one. So, to develop an ASCOM driver for a dome, I used an utility which extracted the type library and all the function definitions from another driver, then I re-implemented it. I made it as a exe (instead of dll) to make debugging easier.
I suggest to start with a "simulator mode", where your driver does not connect to the camera, but just exposes all the ASCOM interfaces correctly.
Fabio.