The .exe versions are installers that can auto install the zip file in the correct directory via MLInstaller's process. MLInstaller doesn't know what to do with a zip file.
So for example,
into the MLServer\Data directory.
MLGenericDevice plugin then can Import a file from that directory and auto unzips the files appropriately for use.
There is a MLGD_XantechZPR68_Device_Setup.exe
and a MLGD_XantechMR88_Device_Setup.exe
Xantech files available via MLInstaller.
I am hoping that more users will be using MLGD and sharing of device files once it is in production.
If Cinemar gets good feedback from users that a contributed device file works well, then we will wrap an installer around it and make it available via MLInstaller for ease of installation. As we develop device drivers, surely they too will be added (like several of the ones already in there).
Please move all discussion off of this thread, that was intended only for device sharing. Thnx
I think that the problem is more with the way the directories are arranged in the installer. I would sugest that you make a new header for the user contributed drivers and get them out of the mix of ML created drivers. That would help seperate the two and actually make them easier to locate.
Chris; Yes, you previously sent me the driver, but it crashes the current version of MLGenericDevice and actually took MLServer down.