After more advice from thechief, the 3 point system has been re-instated in version 1.3.8 - this time, if the score indicates the router has an Adam2 bootloader but it's not 100% sure it will say:
"Bootloader: adam2 (probably)"

The RUC has developed and evolved since version 1.0.0 back in 2007. The code to determine the type of bootloader has been edited several times: notably for 1.2.7, 1.3.4 and 1.3.6. Prior to 1.3.4, there was a three pronged approach: 1) See what the bootloader version is: - Adam2 = 0.x (e.g., 0.22.x) ...

Thanks for the information, fatbozz I will add this tweak to the next release of the RRT. In the mean time, if people are having a similar problem, they can always follow your instructions here

Anyway when I try and start logging I get an Error 6 - Overflow error dialog. The only other factor is that its the first time I've run it in 2010...Oddly, I'd changed no settings since November I think , but just tried for the umpteenth time and after altering ALL the settings around Pinging and L...

For the record, the RUC doesn't intentionally create that key in the registry (nor anything else in the registry). It seemed to be a bug with an API call and I believe I have resolved it in v1.3.7. In any case, users need not be concerned about safety when using the RUC. Due to the nature of the RUC...

Using 1.0.29 I got the frozen stats file effect after 10 minutes, 10 recorded values. Both countdown clocks were running. The values in the "show log" display matched with the same timestamp. On closing the end of snr_stats.txt file appeared to match the stats.txt entries. Second Edit: OK it ran ov...

Hi Kevin, I haven't seen the problem myself (or heard similar reports), but then I haven't been monitoring my router stats for some time. If you did have the log files open in something else (like notepad or Excel) then that could explain it. Another possibility is the file size might cause problems...

Hi, If enabling/using Telnet requires a special command then the RSL is unlikely to be able to obtain all the info it needs. The RSL was written with the RouterTech firmware in mind, so it is going to work most efficiently with that firmware. The main telnet commands the RSL use are in the RSL scrip...

Is your router a Class II router? The Router Stats Logger (RSL) is designed with Class II routers in mind. If you can get the RUC to run to 100%, then that should provide enough information on your router's characteristics.

Erm...yes to what? Can you please explain your post?!?

Thanks for the feedback - I forgot that all my downloads needed to be transferred to the new location. I've moved all the files now so there should be no more zero-length downloads

Hello, Due to the recent move of the forum to phpbb3 ( https://www.routertech.org/viewtopic.php?f=5&t=2917 ), there are a few niggles that will need be ironed out. This includes the current problem with downloads from my website - I will try and resolve this as soon as possible ;) Neo Edit: download...

Have you looked at the readme file? I suggest this point in particular: 9) if the RUC fails around the 74% your router may be blocking access to the /var directory or you may have difficult uploading from the RUC to the router - your software firewall must allow the RUC to run as a server. Also, if ...

...I tried to run RUC tools to check if my router suits to routertech's firmware, but failed. It reported as following: "The Http Daemon seems to have been stopped - this can occur if the RUC can not complete for some reason. Would you like to restart it?" , ok, I follow the instruction and put OK ...

Well I've just tried running the RSL in Windows 7 (in a virtual machine) and it worked fine, first time No configuration, compatibility settings etc whatsoever!