Ah. So you need COMP1 to be a router. This is doable using features built into Windows, but there are some sticky points and risks involved. Make sure you understand what is happening before you start.
First of all, make sure there is no other 192.168.1.x network connected anywhere to the 10.66.25.x network. If there is, chances are you are going to break it and someone in a bad mood is going to come looking for you. It would be a lot easier to change your 192.168.1.x network to something else at this point than later. Just for discussion, we will assume there is no potential conflict.
Now we need to start the routing process so COMP1 knows how to pass packets from one network to another. Rather than typing in a lot of stuff I will point you to this Tutorial.
Be sure you check the Tips and Warnings at the bottom of the page.
Now there is just one key piece that is missing - how to tell the other computers to use COMP1 to talk to each other. This is easy on your Linux machine. Since there is only one way to any other network you can use the address of COMP1 as your default gateway and all will be well. Of course, this eliminates any isolation of your Linux box from the outside world that may have been the reason you connected it this way in the first place, but you can't have it both accessible and not accessible at the same time.
Your COMP2 machine, however, is a bit trickier. It probably already has a default route on the 10.66.25.x network. That route will be used for all networks other than the local, including 192.168.1.x, which will ship our packets intended for the Linux machine into network nothingness (or the other 192.168.1.x network that may exist connected to that gateway). We need to tell COMP2 where the router is to reach your 192.168.1.x Linux network. This is done by adding a Static Route on COMP2. Note that doing this will drive someone crazy if, in the future, this machine is moved to another network, particularly if that network is or is connected to a 192.168.1.x network. Put a big sticker somewhere on the machine to remind the owner that this route exists and must be removed manually if the machine is relocated, network wise. Really. Now on COMP2 go into the cmd screen and type "route print". You should see a short list of known network routes. If you see an entry for 192.168.1.x STOP. It should not exist, and if it does you are about to break something. Assuming all is well, type "route -p add 192.168.1.0 mask 255.255.255.0 10.66.25.100" where 10.66.25.100 is the address of COMP1, your router. This adds a persistent (doesn't get deleted on reboot) route to the 192.168.1.0 subnet via your COMP1 "router" at 10.66.25.100. This will override the default route on COMP2 only for that subnet. You should now be able to ping back and forth and access whatever is living on your Linux box. Note that your Linux box should also be able to access everything on the 10.66.25.x network and beyond, but chances are you won't get a response from anything beyond the 10.66.25.x because nobody except COMP2 knows the return path to route packets back to your "private" 192.168.1.x network.
By the way, the command to delete the route added above is "route delete 192.168.1.1 mask 255.255.255.0".