Quote:
Originally Posted by GeoffR
Perhaps we can combine the Windows and Linux pachages, with the same instructions for both except for running a different batch/shell script?
|
Exactly what I was thinking!
On a side note: I think I will change the bat-file for easier maintenance. Right now, one would have to edit the variables for source and target paths, if one wants to apply it to another FW version. It would be more convenient if the values of those two variables would be generated based on the name of the bat-file. Then one would only have to provide a folder {FWNAME}_source that contains the configuration files, and the (otherwise unmodified bat-file) with the name {FWNAME}.bat.
It would be convenient if you could rename your executable. The reason is that under (more recent?) Windows versions executables that contain certain strings like patch, update, and so on require elevated user rights. This might be a problem in some cases. The other way would be to include a manifest in the executable.
Edit: I replaced the package in post 46. I did the change that I mentioned above to the bat-file. I renamed the executable to pa32lsb.exe.