Suggestion for the packaging of the software client
Posted: Tue Jun 14, 2016 8:22 am
Having spent what was far too long debugging the failed install of the driver, much of the issue was because of the way the driver is packed in an msi, nested in an .exe, further nested inside another exe.
The rich information for debugging was only available when installing the actual driver from the raw files, the inf file and gave the obvious clue as to the install failure which rolled back, deleting all the installed files!
Installing it via the all in one exe just masked all the underlying issues and failure of the process.
Therefore please package and make available as follows:-
All in one package at present but then also,
Driver only .msi (nobody needs an exe wrapping an msi these days)
Zip archive with just the driver installation disk components, i.e. .inf, .cat, .sys
Having the last one in particular would have saved me a bunch of time reading msi log, catching the .exe's as they unpacked and then finally grabbing the driver components.
The rich information for debugging was only available when installing the actual driver from the raw files, the inf file and gave the obvious clue as to the install failure which rolled back, deleting all the installed files!
Installing it via the all in one exe just masked all the underlying issues and failure of the process.
Therefore please package and make available as follows:-
All in one package at present but then also,
Driver only .msi (nobody needs an exe wrapping an msi these days)
Zip archive with just the driver installation disk components, i.e. .inf, .cat, .sys
Having the last one in particular would have saved me a bunch of time reading msi log, catching the .exe's as they unpacked and then finally grabbing the driver components.