[Crossle86]

Originally Posted by jhersh

It makes sense that the creation date would change if you copied it.

I can't imagine what you were seeing either. Maybe a strange Windows installer thing? No idea.

I think I may have confused all this by having a very incorrect view of the version number although I did see a case where running the installer did not place driverstation.exe on the PC. Enough has happened here I will just wear this one as me getting confused.

Originally Posted by jhersh

Sure. I agree. The versions we generate in our build system have the form major.minor.updatePHASEbuild. E.g. "15.0.0f7".

This is the form I intend to have used in all utilities, however the display in the title bar will be the abbreviated version. There is a set of rules for abbreviating that we use. You may notice that the DS title bar shows "15.0". That's what the above build version is abbreviated to.

Seems that abbreviated version does not communicate anything useful if the last part does not change when the version of the program changes. ie, if 15.0 is the first ver of 2015, then update 1 should be 15.1 for the title bar display to have any value.

Originally Posted by jhersh

I agree that there should not be 2 different versions. The version generated by our build system is adapted to the Windows File Version that you were looking at in the properties. That 15.0.0.49159 is the same as 15.0.0f7. If you convert the 49159 to hex, you'll see it is 0xC007. The 2 most-significant bits indicate the phase. Options are d, a, b, f for development, alpha, beta, final respectively. The 14 least-significant bits are the build number.

I'm not getting this completely. The C007 2 most significant bits are 11 or 3. How does that relate to the option letters (index?) or is the f truncated when converted to windows 16 bit version component?

Thanks for this info.