AWS

Raid 0 = striping = one drive goes bad all data lost. Raid 1 = mirroring = one drive goes bad no data lost.

You must be getting a cached page. There are there.

I use them both. AMD as desktop and Intel as servers.

Suse and Mandrake have a x86/64 port.

Got them up. Chat is up also.

Excelent. I'll add them while I'm setting up the chat page.

Great. I have PS CS, but, I'm still learning it. Maybe add a red x on the screen for the new gif.

I'm looking for new gifs to use on the forum main page to replace the V images next to each folder. I found one and need the 2 more. Take a look at the attachment. That would be the gif to replace the one for new posts in forum. I need one that would have the screen unlit for no new posts and one with a lock on it for locked forums. I've been searching for these for a week now and can't find them.

This sounds more like a monitor problem. Try it with a different monitor.

Once the 64bit OS is gold eveything will work. When MS went from 16bit to 32 bit everything was in place. It took software developers a couple years to upgrade their software, but, you could still run 16 bit apps on the new OS.

If you have access to another computer hook it up and try it. It could be something wrong with your OS. If you can access all sites with another box then you will probably have to wipe your OS. Only thing I can think of is to check your network connections properties and if you run a firewall turn it off an try to connect.

The server is up and services now work.

Yes it's up. No services as of yet. Still woking on getting them up.

IRC server will be up sometime later this evening of tommorrow morning. I have to reconfigure the router and DNS to point to the new box.

Could be just a problem with the software the keyboard uses or it could be you inadvertently changed the config to show the volume meter. I have at times right clicked o bring up a config menu and unchecked an option by mistake. Check the config settings of the software.

The best gooing now is Epox. Check out http://epox.com

More than likely a hardware or driver problem. Did you install any new hardware or update any drivers?

I'll have it running by this weekend. I have the OS loaded just have to install Unreal and Epona. If the ExVBF people want a place to hang out they can create the room after it's up and use it until they get their own server. Simon shoot me off an email with your hostmask and a password so I can make you an admin on the server.

I should have read the first post better. With Win2k Pro you can only run one site and that site is limited to 10 connections at one time. All you can do is modify the default site to add host headers for domains you want to use and add content by editing the files in the default root.

In the tree under you computer name you should have something like this depending on what you have installed. Internet Information Services [-]Computer Name [+]FTP Sites [+]Applications Pool [+]Web Sites [+]Web Service Extensions Right click Web Sites. Select New Then select site. If you don't have the above listed then right click Internet Information Services and select connect. Your snapin might not ne connected to the server.

Tracing route to pcp05837078pcs.jdover01.nj.comcast.net [68.***.***.***.Ip_removed] over a maximum of 30 hops: 1 2 18 ms 17 ms 25 ms 209.212.174.237 3 18 ms 21 ms 17 ms 207.251.180.230 4 19 ms 18 ms 27 ms 0.so-0-0-1.hr1.chi2.alter.net [152.63.64.181] 5 18 ms 17 ms 19 ms 0.so-6-3-0.xl1.chi2.alter.net [152.63.73.34] 6 18 ms 17 ms 18 ms 0.so-7-0-0.br6.chi2.alter.net [152.63.71.94] 7 21 ms 20 ms 21 ms 204.255.168.58 8 20 ms 21 ms 21 ms tbr1-p013902.cgcil.ip.att.net [12.122.11.205] 9 41 ms 42 ms 41 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1] 10 40 ms 40 ms 46 ms gar1-p310.nw2nj.ip.att.net [12.123.219.130] 11 42 ms 41 ms 42 ms 12.119.12.18 12 42 ms 43 ms 46 ms ar01-pos-9-1.dover.nj.nj03.comcast.net [68.87.19 .246] 13 43 ms 45 ms 42 ms fe-0-0-ubr02.dover.nj.nj03.comcast.net [68.87.52 .38] 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. Pinging 68.87.0.52.38 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 68.87.0.52.38: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) Tell them you are getting 100% loss on the router after your gateway. I am amazed that you can even get here.

Tell them you get ping timeouts on your gateway. Have them do a traceroute back to you and they should see where the problem is. You'll need to get to a second level tech. Have them connect you with a manager right away.

I figured it wouldn't help. One of their routers is having problems. Try here for help: http://www.dslreports.com/forum/comcast There are some Comcast techs that hang out there. It is possible that Comcast is doing the upgrade to their network. I know that while the upgrade was going on in some areas the kinds of problems you're having was commonplace.

If you're getting timed out messaages then the problem is on the Comcast network. Use 66.93.186.15 as the only DNS server and test again. This is my DNS server. If you still experience timeouts post back.

Take a look at http://kernel.org That is the pivot point for kernel devel for Linux.