ross_aveling

Originally posted by dosfreak: Quote: There should be 0 problems with authentication, but looks like Valve's servers are overloaded.... Yep, it took me about 45 minutes to get HL2 & CS:S activated. Once done though I haven't had a problem with Steam since, *crosses fingers*. I purchased the UK retail DVD edition thinking it would come with Half-Life Source but apparently not! The only way I can see to get it is to purchase either the Silver or Gold packages directly from Steam, but seeing as I have already got HL2 I'm not doing that. Anyone know if they will release it for free; they can't really charge for it can they?

The only real way to know is by contacting Microsoft directly. Otherwise there is no harm in trying activating using the COA key, you'll soon know if there are any problems.

Apparently you can use the RC with NT 4.0, http://support.microsoft.com/kb/293314/EN-US/ Although it talks of booting off the 2000 installation media. I wonder if you can install it as well. No mention of NT 3.x, although I don't see why it wouldn't work. [Edited by ross_aveling on 2004-11-04 06:23:56]

A partition manager such as PartitionMagic will do the trick (although there are others out there). You'll be able to create, copy, resize and merge disk partitions from one drive to another. When you copy your 20Gb partition to the new drive you can then resize it to fill the entire space (or you can create further smaller partitions and assign them drive letters). Just make sure to set the new partition to be the active one (you have to do this even if you only have one partition). Windows will cope fine with the change of disk and continue to run normally. Although daunting at first, the wizards in PartitionMagic should guide you through ok. BTW - If you can, make sure you backup all the important data that you wish to keep. I personally have never had any problems with PM (or others) but you can never know sometimes.

Glad to hear it. We got there finally. I should do this for a living .

Please ignore my last post, I think that is correct. Are you able to ping 10.10.10.2? There isn't anything special about the switch on that subnet is there?

Bah, You may need to remove the static route; 10.10.10.2 255.255.255.255 192.168.1.55 vlan0 The Win2K routing machine should be forwarding packets to this address. BTW - What device is using IP 192.168.1.57.

OK, we'll get there in the end. Try adding another static route (as before), but; Network address: 10.10.10.255 Netmask: 255.255.255.255 Gateway address: 192.168.1.55 See if that works.

Excellent, perhaps we'll get there after all . It's going to be something like (it's difficult to say without actually looking at the configuration page and it's options); Network address: 10.10.10.0 Netmask: 255.255.255.0 Gateway address: 192.168.1.55 Good luck!

Originally posted by masterlodi: Quote: It can't see the 10.x network and never has. That's because it doesn't know that subnet 10.10.10.x exists. If there is no way to add a new static route (ie, "to get to 10.10.10.x, go through 192.168.1.55" ) into it's routing table then we've come to a dead end I'm afraid. If someone knows different with this model of 2wire switch they may be able to lend a hand, otherwise one choice would be to get hold of a more advanced ADSL switch. Also, have found this page where someone wishes to use a 2wire 1800 switch with two subnets. Looks like there are some limitations with the hardware. Sorry I couldn't help you further though .

Originally posted by ross_aveling: Quote: Even before making any changes, you should [currently] be able to ping from the 10.10.10.x subnet to a client on the 192.168.1.x one but not visa versa. As long as the switch on the 10.10.10.x subnet is acting just as a switch. If not, you'll have to tell this one about the hop to subnet 192.168.1.x and set the clients gateway's accordingly.

Am I right in saying that your switch (192.168.1.1) is actually an ADSL Modem/Router (also providing domain name resolution)? If so, what I think is happening is that the router (192.168.1.1) doesn't know anything about subnet 10.10.10.x and is thus going to the internet to find it. I am not entirely familar with combined Modem/Routers, but there must be a way to configure it (as long as it not beyond the modem/router's capability) so that it knows to hop to the Win2K machine (NIC 192.168.1.55) to get to the 10.10.10.x subnet (through the machine's second NIC,10.10.10.2). Sort of like adding a persistent route but to the Modem/Router. A couple of things to make sure of though; - The 10.10.10.2 NIC in the Win2K router has NO gateway set and NO DNS set - The 192.168.1.55 NIC in the Win2K router has it's gateway set to 192.168.1.1 and it's DNS set to 192.168.1.1 - The clients on the 10.10.10.x subnet have their gateway set to 10.10.10.2 and their DNS set to 192.168.1.1. - The clients on the 192.168.1.x subnet have their gateway set to 192.168.1.1 and their DNS set to 192.168.1.1 Even before making any changes, you should [currently] be able to ping from the 10.10.10.x subnet to a client on the 192.168.1.x one but not visa versa. Hopefully I'm on the right track .

Hello, I think we're getting there. This is correct (and would have been configured by making your Win2K machine an 'IP forwarder'. Quote: ================================================================ Active Routes: Network Dest Netmask Gateway Interface Metric 10.10.10.0 255.255.255.0 10.10.10.2 10.10.10.2 1 10.10.10.2 255.255.255.255 127.0.0.1 127.0.0.1 1 10.10.10.2 255.255.255.255 192.168.1.57 192.168.1.55 1 10.255.255.255 255.255.255.255 10.10.10.2 10.10.10.2 1 Your Win2K machine is correctly forwarding the packets from one subnet to the other, what I think isn't happening properly is that packets from client machines to opposite subnets are being routed out over the internet first through your broadband connection (as seen in the TRACERT). How is your internet connection integrated into your network in relation to the Win2K machine? Quote: Also, the NIC for 10.10.. does not have a default gateway That's fine (for the moment). BTW - You only need to add persistent routes when you need to specify where the next hop is [for any given subnet] for when you have more than 2 subnets. Eg, this will tell one router what is the next router (hop) to forward packets to a third subnet.

Hi masterlodi, Gotcha. At first glance the Win2K machine *should* be routing (after simply applying the registry hack). But I'm probably missing something (if someone notices, please shout ). From the Win2K machine, can you provide here a dump of the 'ROUTE PRINT' results from a command prompt? Also, I'm sure you have already done this, but check to make sure that the default gateways of the clients are set to their respective NIC's address in the Win2K box. Also, if you can dump out the results from a TRACERT from one of your XP clients (when pinging across the subnets) would be a great help.

Not to worry. Originally posted by masterlodi: Quote: I can't ping across subnets. I may be jumping the gun, but are you using more than one machine to perform routing duties, ie; Quote: Machine 1 NIC 1: 192.168.0.1 NIC 2: 192.168.1.1 Machine 2 NIC 1: 192.168.1.2 NIC 2: 192.168.2.1 Hopefully not (it gets way more complicated), can you outline your network structure for me - to make sure I'm not going down the wrong route.

Microsoft have since removed this option from the GUI on all versions of Windows since NT 4.0 (excluding the Server versions). That is why the registry hack is required (we had a recent topic on this on NTC but I can't, for the life of me, find the exact one :x). Quote: I've made the registry change as outlined in the MS knowledge base and rebooted. Then your machine should now be acting as a router. You haven't made it clear whether you're still having problems; are you able to ping from a machine on one subnet to a machine on the other subnet?

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q230082

The 64-Bit edition of Windows XP (Windows XP Professional x64 Edition is it's full title) is currently in beta and can be downloaded as a trial from Microsoft's website. The software is a new distribution of XP and as you suspect, is a 'whole' OS in it's own right. So no upgrade I'm afraid.

If I recall correctly, Win98 won't install over an NT based OS (it's been a long time since I used Win9x). You'll have to blank the target hard drive before you boot off the 98 CD and begin the installation.

http://support.microsoft.com/default.aspx?scid=kb;en-us;234562

Originally posted by latino85: Quote: Funny thing is when i first boot the pc and it asks for my password, the optical light on my mouse is on and WORKING but then suddenly it goes OFF!!! no more damn optical light?!!?!?! Do you mean at the POST stage (ie, you have a power on password)? Make sure that the computer's onboard USB Controller isn't disabled in the BIOS. On most motherboards, if it's set to disabled it won't actually turn them off until the POST process has completed which would explain the flashing of the optics. Having it disabled would also explain the USB Controller's absense in Device Manager. The worst case scenario is that the controller circuitry is shot (unlikely), you could pick up a cheap PCI USB controller in that case though.

I've not had any problems with Alice on my XP SP2 machine (P4 2.4c/ATI9800XT).

http://www.perli.net/projekte/privateer2win95/

Welcome to the forum Rayden, A long shot perhaps, but I couldn't format a new 160gb drive to NTFS (using Partition Magic 8 or Windows) until I enabled 'IDE Bus Mastering' in the BIOS. Worth a try I suppose.

Well I haven't experienced any problems whatsoever using SP2 (I did install from fresh). If anything, it runs better than before. Perhaps I'm lucky.