Note that from the CMD prompt of a windows box, ROUTE with no arguments generates the help screen for the ROUTE command.
I thought you had real routers, not SOHO crap. Nevertheless, you can get there "on the cheap" with your present equipment and setup.
That article that you found, does look like you can enable the routing on the XP workstation that you have connected to each of the networks. I've never tried it personally, but it looks like it should work fine.
Let's say for example that
network A = 192.168.10.0/24 (sm 255.255.255.0)
network B = 192.168.20.0/24
your SOHO router on each network is .1
your workstation that's connected to each network is .5 on each respective network.
If your Netgear SOHO router is on Network A, then you add a static route in it to direct traffic destined for 192.168.20.0/24 to 192.168.10.5. This should take care of network A.
For Network B, with the SOHO router absent of the static route functionality, from the CMD prompt of a network B workstation:
ROUTE ADD -P 192.168.10.0 MASK 255.255.255.0 192.168.20.5
This above command modifies the routing table in the subject workstation such that all traffic destined for your other network 192.168.10.0 is sent through the "server" workstation at 192.168.20.5 instead of the default gateway. You will have to execute this command on each workstation on network B
For the sake of argument, without the static route in the netgear router on network A, the proper ROUTE command for a network A windows workstation is
ROUTE ADD -P 192.168.20.0 MASK 255.255.255.0 192.168.10.5
Hope this helps.
--C