Router Upgrade Check by Neo @ RouterTech.Org
============================================

NOTE: From version 1.3.0 onwards, the RUC does NOT require the Winsock (MSWINSCK.OCX), Microsoft Internet Controls (shdocvw.oca and shdocvw.dll) or Microsoft HTML Object Library (MSHTML.TLB).

The Router Upgrade Check (RUC) utility is designed to help you find out if your (Class II) router can be upgraded to a RouterTech.Org firmware.

Before you use the RUC, please make sure your router is a Class II one and that LAN-side telnet access is enabled (it should be by default).

To use the RUC simply follow the instructions it provides and fill in all the information required. Once the RUC has completed, you should get a good idea of whether your router is upgrade-able and which firmware to choose, if it can be upgraded. If you are unsure about the results or have a question regarding the results, please copy-n-paste the contents of the results in to your forum post.

Please note that some parts of the 'check' may take a while to complete, so even if you think the RUC has frozen it may be working in the background. Normally, the check can take up to a minute but it may take longer.

** Files created **

By default, the RUC will create several files in the same folder as the RUC:

# check-*.txt = check summary and router information. This can be very useful as it will effectively backup some of your router's most important settings.

# env-*.txt = You router's environment - this file can be used with PC-Tool to recover your router if something goes wrong during an upgrade, so please keep it safe.

# *_current_config.bin = Your current router configuration.

# *_default_config.xml = The default router configuration.

# *_mtd3.bin = The router's MTD3 partition.

It is recommended you do NOT delete these files as they can be very useful for router recovery.

-------------------------------------------

If you have any problems running the RUC, please check the following:

1) ensure the following files are in the SAME directory -

cm_cli_tty
debug.bat
firmwares.lst
mac_oui.txt
readme.txt (this file)
routers.txt
ruc.exe
settings.ini
vista-telnet-fix.bat

2) if you have a software firewall running on your PC, ensure that the firewall gives the RUC access to your router.

3) check that you have the VB runtime files (http://support.microsoft.com/kb/290887) installed on your system.

4) check that you have nothing running on port 5000 (this port is used by the RUC to communicate with the router).

5) check that you have ws2_32.dll DLL file installed on your system.

7) for some firmwares, the 'Backup current config' option may not work. You can untick this option if the RUC experiences problems completing (usually around the 100% mark).

8) if you are using Windows Vista, try running the vista-telnet-fix.bat file (you will need to have administrator privileges) before running the RUC. You must reboot for the fix to take effect.

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 you have a NAT-NAT configuration, you must disconnect your other router temporarily when running the RUC (or perhaps switch on the DCHP on your router that you are testing and connect a switch between your two routers).

10) if you are using Windows Vista, try running the RUC in Windows XP compatibility mode.

11) if you get "Runtime error 5: Invalid procedure call or argument" when you try to run the RUC, make sure the "Language for non-unicode programs" is the same as your primary language or set it to "English (United States)". This setting can be found in Control Panel -> Regional and Language Options -> Advanced tab.

12) if you see messages relating to the HTTP Daemon, you may need to edit the RUC's settings.ini file: under "[Router]" change the value for "Last http daemon" to match the name of the daemon on your router. You might need to experiment with entering just the name of the daemon or the full path. For example, change "Last http daemon=thttpd" to "Last http daemon=/usr/sbin/thttpd" or whatever it is called. You can find the name of the daemon by typing "ps" at the Telnet command prompt.

--------------------------------------------

If you still have problems after checking the above:

1) Run the the RUC (using the debug mode [see below]) as far as it will go (it should go beyond 0%).
2) When you are sure it is not getting any further (wait for at least 30 seconds) then click on 'Abort'.
3) Click on 'Show Report'.
4) Select all the report (press Ctrl+A) and copy it to the clipboard (press Ctrl+C).
5) Create a new PM (private message) on the RouterTech.Org forum addressed to me (Neo).
6) Paste the report in to the PM (Ctrl+V) and add a description of what the problem is, what steps you have already taken etc and send the PM.

Note: I am fairly busy nowadays, so you might get a quicker response if you post details of the problem etc in a new thread on the RouterTech.Org forum.
Also, try the Telnet Scripter with the script provided here: http://www.routertech.org/viewtopic.php?t=1062 - that should obtain most of the information required to find out which firmware you need.

--------------------------------------------

DEBUG Mode

For people experiencing problems with the RUC, it is possible run the RUC in debug mode. To do this:

1) Run the "debug.bat" file
OR
2) Run the RUC from the command line with the /debug switch - e.g "ruc.exe /debug"
OR
3) Create a shortcut to the RUC, add " /debug" to the end of the target field and then double click on the shortcut