well, you can allow Windows to check for new drivers in local computer and MS Update (if not found on local comp) and then you will get generic ePass driver from MS Update downloaded and installed as middleware between token HW and Windows OS.
FTK300 is a “Driverless USB device” meaning the user does not need to install any hardware drivers for Windows ( As a CCID USB devices, the hardware driver is already provided with Windows ). PKCS#11 or MSCSP is the Application level libs in between hardware layer and the Apps. [Hardware Device]<->[Hardware Driver]<->[Middleware: API/Lib (PKCS#11/MSCSP)]<->[Application].
So, we usually call the PKCS#11 “Middleware” or “CSP” instead of a “Driver”.
However I'd recommend to use our (Fortinet) middleware, at least dll, or whole app which also allows token management like cert installation, user PIN change etc. (don't worry, there is master PIN and admin app so regardless user changed PIN and is uncooperative when token is returned, admin will be able to reset and re-use such token again).
For middleware (aka token management tool) for the FTK300 see image download section on support site: https://support.fortinet.com/Download/FirmwareImages.aspx (login with valid support contract account needed)
Our FTK300 middleware and hardware are designed to only work with each other, so the standard Feitian ePass3000 token wont work with our FTK300 middleware and vice versa.
Installation is composed of dll and token management tools. You can use just dll and link it with application, like when adding security device in FireFox by pointing to it's dll, in this case to Windows / System32 or SysWOW640 / FortinetCsp11_2003.dll .
But then you need to handle additional token/certs/PINs management somewhere else.
