Last
Update: Sunday, 24 December 2023 13:31 (v3.2d) |
This page is
for 64-bit users of OmniFlop (Windows Vista64,
Windows 7x64/8x64/10x64/11). If you are
running a 32-bit version of Windows (2000, XP, Vista or 7) then go here. |
v3.2d has
been tested on Windows 7 64-bit OK v3.2d has been
tested on Windows 10 64-bit OK |
Thanks to Chris Richardson and 8BS for starting this all off.
On This Page You Will Find |
|
Overview |
|
Download & Installation |
Installation (Windows Vista/7/11 64-bit) |
The 64-bit version
of OmniFlop is written for Windows XP,
Windows Vista, Windows 7, 8, 10 and 11.
I do not have a complete set of machines to test on, but
v3.2d has been tried on:
Windows 7 64-bit, and
Windows 10 64-bit
Windows 11 has been documented but is not yet confirmed.
Please help me by confirming if it works - or not.
In all cases, you must turn Driver Signing Enforcement
OFF. See below for more details.
The 64-bit version of OmniFlop does not require a license if it works (like the 32-bit). I would appreciate any reports of it working (using the Contact in 'About' or 'Get a license'/'Register by e-mail') - or not - as otherwise I get no feedback and I don't know if it works.
There is an
additional installation step for 64-bit users of OmniFlop
compared with 32-bit users. You must 'disable driver signature enforcement'
which varies depending on whether you are using Windows 7, 8, 10, or 11.
Detailed instructions are provided in the User Guide included as part of the
download but repeated here for ease of reference.
The download contains installation instructions in Adobe 'pdf' format. You can read these with the free Adobe Reader at http://www.adobe.com/products/acrobat/readstep2.html, if you don't already have it installed. If you want to read them immediately on-line they are also available here.
The download contains a user guide (OmniFlop.pdf), a Windows Floppy disk controller driver (OmniFDC.inf, OmniFDC.sys), a Windows Floppy disk drive driver (OmniFlop.inf, OmniFlop.sys), and a Wizard (OmniFlop.exe).
The Wizard can be used without installing the drivers, but only the 'standard' DOS formats can then be read, written or tested - none of the 'extended formats' will be available.
The drivers can also be used by your own software from v2.01 onwards. See support.
64-bit OmniFlop
The instructions for the 32-bit version of OmniFlop apply to the 64-bit version but you must 'disable
driver signature enforcement' first (described below). Without this Windows
will refuse to run the drivers - see below.
Download the latest release of
OmniFlop64 here
Download the archive. Install the drivers following the instructions below ‑ either temporarily or permanently ‑ then run the Wizard.
Temporary Installation - Windows Vista, Windows 7 and
Windows 11
Use the Advanced
Boot Options menu of Vista/7/11 to 'Disable Driver Signature Enforcement'.
Thanks go to Aleksandrs
Ribalka for testing this method.
Temporary Installation - Windows 10 and Windows 11
Use the Startup Settings menu of Windows 10 to 'Disable Driver
Signature Enforcement'.
This involves the
download of a Windows configuration utility and the signing of the OmniFlop drivers by your own system.
C:\Windows\System32\drivers\OmniFlop.sys
C:\Windows\System32\drivers\OmniFDC.sys
Thanks go to Aleksandrs
Ribalka for this method.
For help or suggestions, use the 'Support' contact for OmniFlop in the 'About' box from the Wizard.
From the 64-bit
version of Vista onwards Microsoft changed its policy on drivers and their
installation on Windows (see here). Under 'Global Issues for Driver Loading'
it states:
Digital signatures are required for 64-bit kernel-mode drivers. Signed catalog (.cat) files are required for all kernel-mode packages that are to be installed on the 64-bit editions of Windows Vista. This applies to any software module that loads in kernel mode, including device drivers, filter drivers, and kernel services. The operating system does not load unsigned kernel modules that lack a signed catalog file.
There are two ways to obtain an appropriately signed catalog file:
(1) Obtain a Windows Vista logo. Drivers that pass Windows Hardware Quality Lab (WHQL) testing receive a catalog file that is signed with the WHQL certificate.
(2) Obtain a publisher identity certificate (PIC) and use the PIC to sign the package's catalog file. To obtain a PIC, a publisher must first obtain a VeriSign Class 3 Commercial Software Publisher Certificate and then use that certificate to obtain a PIC from Microsoft that can be used to sign kernel-mode modules intended for 64-bit Windows Vista.
32-bit Windows is
able to use 'free' un-certified drivers, but not 64-bit versions.
To digitally sign
these drivers will require payment to Microsoft. The proceeds from donations to
OmniFlop over the past 6 years do not cover the cost
of submitting OmniFlop to Microsoft's WHQL for
certification nor obtaining a PIC.
For 64-bit users of OmniFlop this means you must explicitly allow Windows to use the OmniFlop64
driver. The sections above tell you how. You can either temporarily enable the OmniFlop
driver - for use of OmniFlop as and when you need it
- or permanently sign the OmniFlop driver specifically for use on your system and
allow it to run all the time.