Have no idea what that does, but I tried it, and the scope ran
[root@Hantek /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &
[root@Hantek /]# s3c2440_clkcon=00FFFFF0
s3c2440_clkcon=00FFFFF0
save exit: isCheckpointed 0
well yes, when started manually it will run, but not when started from rcS. It looks like the dso.exe from 2.01.1_(140408.0) is not initializing properly when runned from rcS (i can't connect via USB to my dev board, so it deos NOT run properly). When killed and started manually it does works. So there must be general problem with that executable version.
I did tested it now with older version, 2.01.1_(140214.0) and there are no issues, runs from rcS or manually and it allows USB connection/access. I did tested (just for sake) 2.01.1_(140408.0) but from B and not S model, and guess what, it works as well. So it seems to be specific problem with dso.exe for S model, version 2.01.1_(140408.0).
So i would say do the downgrade as described. Don't play with other scripts, you will run in trouble during next update, so leave them all as they are. Replace only the English.lan (and different languages if necessary) in /OurLanguages/ directory and the /dso.exe in root, chmod 777 * in root and power cycle.
Tinhead, do you have contacts at Hantek to get this solved, or should I make contact with them and tell them the findings?
feel free to contact them, you have such handheld - i don't. Tests on dev boards, like i'm doing, are good but sometimes not sufficient (especially when firmware is waiting for soemthing missing on dev board).