NetBurner Community Forum

Hello,

The latest Native Boot Monitor is revision 1.06, 5/2/2024
The latest Alternate Boot Monitor is revision 1.05, 7/17/2020

It is true that the firmware is kept in our version control system and does not have a part number. For that, can you create your own part number? We could select a random ...

Other than that, it could be your pc's environment variables mixing up releases.

I just ran a test of a clean install and do not get any duplicates. Does your new install still do that? You did not install over an old version (there was no \nburn folder when you installed) correct?

Sounds like you might be using an old predef.h? What is the version number at the top?

Hello,

I think there is something wrong with your install, you should not have to uncomment the SSL in 2.9.7, as its always enabled. Can you rename your \nburn directory and do a clean install of 2.9.7?

I think the only way to know for sure would be to test it.

If you are generating certificates, and not cpp files, then you should be able to use the newer version.

If you have any of your tasks at MAIN_PRIO-1, that would be 49

Its not used by the system anywhere else. What do you get if you add TCP update to an example like SimpleHtml?

I don't see the string "TcpUpdate Error:" anywhere in our code. Is that something in your app?