Skip to main content
added 6 characters in body
Source Link
Robert Harvey
  • 200.7k
  • 55
  • 470
  • 683

So create and maintain your own internal minor version/build number in the EEPROM.

All you need is one byte; that will give you 256 iterations before your client finally OK's a change to their version number. When that happens, you can start counting again from zero.

The PC software doesn't have to display the build number. You can get that using a special outboard utility that you write, if you need it.

Think outside the box.

So create and maintain your own internal minor version number in the EEPROM.

All you need is one byte; that will give you 256 iterations before your client finally OK's a change to their version number. When that happens, you can start counting again from zero.

So create and maintain your own internal minor version/build number in the EEPROM.

All you need is one byte; that will give you 256 iterations before your client finally OK's a change to their version number. When that happens, you can start counting again from zero.

The PC software doesn't have to display the build number. You can get that using a special outboard utility that you write, if you need it.

Think outside the box.

Source Link
Robert Harvey
  • 200.7k
  • 55
  • 470
  • 683

So create and maintain your own internal minor version number in the EEPROM.

All you need is one byte; that will give you 256 iterations before your client finally OK's a change to their version number. When that happens, you can start counting again from zero.