Re: zoomfloppy with windows 10 ?

From: Steve Gray <sjgray_at_rogers.com>
Date: Tue, 15 Aug 2017 20:41:50 +0000 (UTC)
Message-ID: <265986001.2793527.1502829710986@mail.yahoo.com>
Trying not to be too negative here, but I find that there is a lack of good documentation. Perhaps due to the multiple sources needed to make a working solution, ie: buy Zoom Floppy here, get OpenCBM there, then CBM-Transfer somewhere else.
There needs to be some type of information page on the web that explains the different versions available, which works on what windows, which ones are signed/not signed etc. I've had to point people to specific pages to help them because they just couldn't find the right info. A user shouldn't need to download multiple zip files and search through every file to find which version is the correct one for them.
Windows 10 is going to be more challenging because of Microsoft's update policies. IE: "Windows 10" answers will depend on which release they are running due to the ever-changing, online-updating feature, This needs to be monitored and properly documented when something like driver signing changes.
Just my three cents.
Steve

      From: Spiro Trikaliotis <ml-cbmhackers@trikaliotis.net>
 To: cbm-hackers@musoftware.de 
 Sent: Tuesday, August 15, 2017 3:54 PM
 Subject: Re: zoomfloppy with windows 10 ?
   
Hello,

* On Mon, Aug 14, 2017 at 11:04:16PM +0100 smf wrote:
> On 14/08/2017 22:03, Steve Gray wrote:
 
> The ones I linked are signed as far as windows is concerned & the only way
> to do that is to actually sign them. There are no workrounds possible
> anymore. i.e. You can't install a certificate and use that to self sign the
> driver.

Yes. That's why zadig should not work on Windows 10 anymore, at least on
newer versions.

Thus, the version that is signed by Arnd is the only one that should
work reliably on Windows 10. However, even that one is an exception,
because it was signed BEFORE Windows 10 changed to a harder signature
policy. That is, if we will find a bug in the driver in the future we
want to fix, or if want to add functionality, we will not be able to
create a valid signature anymore. Windows will be completely left out.

At least, this was the state when I last checked the Windows 10 signature.

Regards,
Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/

      Message was sent through the cbm-hackers mailing list


   

       Message was sent through the cbm-hackers mailing list
Received on 2017-08-15 21:00:03

Archive generated by hypermail 2.2.0.