Anyone else seeing this bug?

a_riot42

In 3.3.1.525 I accidentally unchecked the "automatically select reboot when sending a TKN file" in the preferences dialog and now, even though I've rechecked it, it is never getting checked. So I am constantly uploading code to a master that won't reboot once the file has been transferred. Talk about annoying! I almost never remember to check that box before a transfer, since its not even normally visible in the transfer dialog. Whatever you do, don't uncheck that box or you'll regret it. I will probably have to reinstall to get it to work properly again. I've suffered quite a bit of egg on my face when I've promised clients I've fixed something and yet the problem still exists because the master didn't reboot. Arrgghh!
Paul

Joe Hebert

I thought maybe you could manually change a registry key to fix it but the closest thing I found on my PC was:

HKEY_CURRENT_USER\Software\AMX Corp.\NetLinx Studio\Batch Transfer User Options

And inside of there is TKN Reboot value.

But that doesn’t sound like the same TKN Reboot that would be tied to the File Transfer preferences or maybe it is.

I’d uncheck mine as a test and then change the registry but there is no sense in both of us having messed up preferences.

I’ve never changed that file transfer option so maybe a key is only written when you change it for the first time?

Whatever the case thanks for the heads up.

yuri

This applies to projects with Duet modules in them.
Are you using Duet modules?

jeff.gardiner

I have also seen this bug on someone else's system. We were using a Duet module, but I am sure I've had it reboot no problem in the past while using a Duet module. Curious...

ericmedley

a_riot42 wrote: »

In 3.3.1.525 I accidentally unchecked the "automatically select reboot when sending a TKN file" in the preferences dialog and now, even though I've rechecked it, it is never getting checked. So I am constantly uploading code to a master that won't reboot once the file has been transferred. Talk about annoying! I almost never remember to check that box before a transfer, since its not even normally visible in the transfer dialog. Whatever you do, don't uncheck that box or you'll regret it. I will probably have to reinstall to get it to work properly again. I've suffered quite a bit of egg on my face when I've promised clients I've fixed something and yet the problem still exists because the master didn't reboot. Arrgghh!
Paul

I did see this but honestly just wrote it off as one of many bugs I was seeing in this version. It and all the other bus I've seen went away when I wen back a back a couple versions. Fortunately for me I noticed it while remotely workinig on a system where we had a tech on hand working on the head end rack anyway. He was able to power cycle the master for me. But, yeah, it's a really annoying bug.

jjames

I saw it when sending code with Duet modules in it right out of the gate. I quickly downgraded . . . I'd suggest staying away from this version.

rrdbstudios

I have this problem as well when using duet modules, however I am also locked out of the master until a power cycle occurs.

After that, all is well again until I upload the tkn again, remove the duet, and its fine.

Colzie

What other bugs should I watch out for in v. 525? I upgraded and then found this thread...

nicholasjames

Joe Hebert wrote: »

I thought maybe you could manually change a registry key to fix it but the closest thing I found on my PC was:

HKEY_CURRENT_USER\Software\AMX Corp.\NetLinx Studio\Batch Transfer User Options

And inside of there is TKN Reboot value.

But that doesn’t sound like the same TKN Reboot that would be tied to the File Transfer preferences or maybe it is.

I can confirm that it is. Make sure to check in both HKCU and HKLM. This is also an option for the FileTrasfer2 software.

jjames

My question is: why was this changed in the first place? *shakes head*