jcarle

Sometimes you ran run your memory at 400MHz instead of it's rated 333MHz if you leave the timings at the memory's default.

MemTest86+ is what I usually use to test my client's machines. I find it's pretty accurate. It's helped me diagnose more then a few odd machine lock ups. MemTest86 was the original bad boy of memory testing. The standard if you will. But the developers stopped working on it, so some fans of MemTest86 picked up the source code and continued development with MemTest86+. As for overclocking, your FSB will affect your processor's speed, your memory's speed and your peripheral bus speed. Generally speaking, overclocking tends to fail because something gets too fast. Sometimes it's the processor, sometimes it's the memory and sometimes it's the PCI bus. Technically, as long as each part stays within it's supported speed, there's not too much problem. However, depending on the motherboard, sometimes when you try to get one part up to speed, you sometimes get the other parts past their limits. For example, if you clock up your FSB to get your memory running at it's maximum speed, your processor may end up getting clocked higher then it can support. So the memory and the PCI bus might be running fine, but the processor is so clocked up that it won't even boot. Sometimes it the other way around, sometimes you'll clock your processor up to get some extra performance but then your memory will be getting clocked too high and you'll start getting memory errors across the board. My particular problem I had when I used to have my PIII-800EB was that I could overclock my FSB to 150MHz (up from 133MHz) and the CPU would run fine at 903MHz (up from 800MHz), my ram would run fine at 113MHz (down from 133MHz) but my PCI bus would reach it's limit at 37MHz (up from 33MHz). My board had no individual control on clock multipliers, so I could only pay with FSB settings and ratios (FSB:RAM:PCI - 133:133:33 / 133:100:33 / 133:66:33 / 100:100:33 / 100:66:33 [i think those were the settings...]). The fact that you can set your clock multiplier on your processor gives you great advantage in clock setting. This way you can increase your FSB to match the speed of your memory and reduce your clock multiplier on your processor to keep it running at it's original frequency. Whether you run a processor at 10*133MHz or 13*100MHz, it does not make a difference to the processor. It's 1,300MHz (+/-30Hz) either way. What does change however is your FSB which DOES affect the rest of your components. However, if you take a motherboard which is rated to run with up to a FSB of 400MHz (200MHz system clock), then everything on the actual motherboard can support that frequency. What is left to decided whether you can run at that frequency or not are the components plugged into your motherboard. If the memory is rated for 400MHz, the memory portion will be fine. And if your FSB*MULTIPLIER equals a speed your processor can handle, you're in business. Of course, you receive a much higher performance boost with 10*133MHz then 13*100MHz because the extra 33MHz shows across the board on all components of the motherboard (including, obviously, the motherboard itself). Ideally, I'd try running your system with your processor at 8*200MHz (if you can set the muliplier that low) and see if you can get your memory to run at the speed error free. If you do, then I'd try upping the processor multiplier by 0.5 to see how far you can push it. Unless you boost voltages, you can't damage your components by simply having them run at higher frequency clocks. Worse that'll happen, your machine won't boot. At which point you reset the CMOS and back up a step to the last stable configuration. Once you find that point, you test it heavily with MemTest86+ for integrity. Then after that you burn the system in using heavy games and things for stability. Oh and if you look at the memory bandwidth in MemTest86+, you'd be amazed at how much of a difference there can be by a few MHz increase in the system clock.

I discovered the bug during our giant debate with Mr. Publicity over his cutting edge anti-virus software.

I've done the old \\ to \ switch in appended paths so often that I can't help but to think of it everytime I see a replace for \\.

Saw this today on a French VLK installation I did. MS Finally got smart.

I don't know if this has been posted before, but I've been looking for this for a while and happen to run into it just now somewhere on the net when I wasn't even looking. By changing your Windows Explorer shortcut to the following, the next time you open Windows Explorer, instead of having My Documents highlighted, My Computer will be. explorer.exe /e,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

Often times, when you see a replacement of \\ for \ in a path variable, it's usually because somewhere there's possibility of a path being appended that can do that. Example: If the original variable contained: C:\Program Files\ And you appended \CompanyFolder to it, you'd end up with C:\Program Files\\CompanyFolder which is an invalid path, therefore a replace on \\ for \ is a quick and dirty wait to prevent that error from occuring.

You know, all this just to come back to the original point. None of us have a tangible copy for us to physically test ourselves.

Quick question. How come if I do a Windows Update on a freshly slipstreamed SP2 version of XP Pro, I don't see nearly as many updates as the ones listed here?

Doesn't matter which version of XP you have. Your one on one support with Microsoft may terminate in 2006. But Microsoft's overall support, meaning Service Packs and whatnot, will be extended until at least 2011. Probably longer considering you can still use Windows Update in Windows 95.

He already has a base station. That's what a wireless router does. That's why I suggested a Wireless bridge because it's cheaper then that.

So are you saying the LAN nic should point to itself in the DNS entry? I tried using updated drivers which didn't change anything, so i too am convinced its DNS problems... Yes because the LAN NIC cannot access outside of the LAN directly, so it has to resolve using the DNS of your Active Domain. If you leave the DNS to your ISP's DNS, then when you resolve a local host, you will be sent to your ISP's DNS which will send you back to your local Active Domain instead of going there right off the bat.

Books by Wrox for programming are my bibles (a lot of people's bibles actually...).

Zxian, start off by loading your BIOS default settings. Then run a MemTest to make sure you don't have a bad stick of Ram. After you're sure your Ram is good, then try changing your FSB to 166 and your multiplier to 10. Run memtest again and check for errors. Memtest is always a good way to make sure your system is running stable because it involves a lot of math and it involves the most sensitive part of your system, the memory. If you get errors after changing to 10x166, then something is not liking the change. Overclocking on itself will not damage anything right off the back. All you're doing is increasing the system clock frequency. It can shorten the life of your parts, but you're talking about a small reduction over a very long period of time. What can severly damage components is too much voltage. And the other culprit, is obviously heat. As long as everything stays cool and you don't overload the voltage factor, everything will be fine. I used to overclock a PIII 800EB I used to have to about 937MHZ without any voltage adjustments. Just straight FSB. I think after that my PCI frequency started getting to high and I'd start freezing up everywhere. That's also something to check for. If you have them, try playing with FSB:RAM:PCI ratios.

Make sure you get the latest version of the official nVidia reference drivers from their website. The control panel for nVidia drivers is complete enough that you should be able to accomplish what you want. Also, your TV should have a zoom feature to allow you to fit the movie to the width of the TV and cut out the top and bottom bars.

I think it's the licking that turned everyone off...

Oh... my... god...

If the problem fixes itself over time, I'm convinced you have a DNS issue. If you do have a DNS conflict or misconfiguration, then the problem may appear to seem to fix itself over time as DNS entries become cached. Try setting the DNS entry on your machine to the local Active Directory server. Also make sure that the server's DNS is properly setup to forward requests outside of the domain to your ISP. On your server, the NIC that is connected to your ISP should have your ISP's DNS. However, the NIC that is connected to your LAN should have your LAN's DNS entry.

When there are more then 10 uses of the quote tag, the quote tag no longer renders... Example:

Hey denzilla? What did you end up doing? Did you clean it? Does the CPU work? UPDATE!

Go to Network Connections. Right-Click on your wireless connection and choose Properties. Click on the Wireless Networks tab. Click on the connection that you would like to automatically connect to and click on Properties. Click on the Connection tab. Put a checkmark next to "Connect when this network is in range" Additionally, you can also move the connection up the list and put it at the top.

Oh please let it be your last.

@dman - Granted, you were able to see it, but the fact that you didn't try it first hand means that it could very well be simple program that deletes files without any actual logic programmed into the program, simply for the sake of the demo.@rhythmnsmoke - You started as Co-CEO then the story changed to the fact that you were a junior programmer for the team and then now you're not even that? So what the hell are you then? Why do you keep changing your story? Oh and by the way, congratulations, you showed us how you can search the web, copy and paste other web page content and create hyperlink to said copied material. Still haven't proved anything.

Straight means that the cable's wire run straight through, while cross over means that the transmission wires are crossed over to the reception end and the reception wires are crossed over to transmission end. The is no difference in speed, it's just a method of communicating. It depends on the hardware. To connect a computer or modem to a switch/hub/router, you use straight. To connect two computers to each other, you use a crossover cable.

They also patented the "double click". God....