jcarle

He may have a valid reason for his question, you know. Which is why I asked him why he wanted to do so.

Use a custom paper size for your printer, then in word.

I think you misread my post. I didn't say idle is off. I said whenever my computer would need to sit in a largely idle state for a long period of time instead of leaving my computer, I will turn it off. Therefore, for me, the idle state is of non-importance to me. You can't compare performance strictly on synthetic benchmarks as they don't deal with real-world performance. Also, some benchmarks axe more on memory usage, not processor usage. As for overclocking? The Core2 lineup are excellent overclockers.

Why are you trying to do this? Perhaps there's a better solution to your original problem.

I wouldn't recommend overclocking on stock cooling. Even though Intel makes great processors, their coolers are marginally acceptable.

Unless you do absolutely nothing with your computer, and I mean literally nothing, no services, no background applications, nothing... then you're never going to be fully idle. Everytime you do anything, you're not idle. Add background services and processes and you'll always have something to do. It also depends on how you use your computer. I run a lot of large processor intensive applications on a regular basis. Not to mention that I spend a lot of time encoding every day. Whenever my computer would be idle, it's off.

Generally, the 9xx series has been very succesful at overclocking. The amount of success tends to depend on the motherboard and ram you combine the processor with.

Okay, but why would you build a computer to leave it at idle all the time? The power consumption is most important during it's heavy usage, is it not?

Please do not double post.

VMWare Workstation.

I would NOT recommend installing Vista on your system if you have only 512MB of ram AND onboard video. You'll quickly regret it as your system will fall to a crawl. A dedicated video card (no matter how small) and a minimum of 1GB of memory is HIGHLY recommended.

You can read about the issue in detail at http://www.codinghorror.com/blog/archives/000811.html.

Not at all, unless the software was poorly written and assumes the system drive is C: without actually verifying it, but that's strictly a software point of view, it does not affect the Windows environment per se.

Not necessarily, the hard drive itself could also be defective.

I would never buy an AMD. Considering Intel owns 85% of the market share, and that AMD is facing financial difficulties, and there isn't a single AMD processor faster then the Intel Core 2 lineup, and in a performance for dollars comparison Intel is much cheaper, and Intels run cooler and use less power, there's simply no valid reason to buy an AMD right now.

Old, very old. I'm sure this has been posted before.

Again, that's a large assumption. The lack of going into details can be related to quite a few things, an inability to express one's self clearly or a lack of understanding of the problem will also yield the same kind of posts. How many times have people posted in these forums with questions like "My computer doesn't start, what's wrong?". Because there's a lack a detail it would usually mean the poster doesn't have the best intentions?

Indeed, registry cleaners can create a great deal of problems. Often a registry cleaner will delete registry keys which it believes are not important but are actually required by certain applications. A good example of which, running Registry Mechanic will hose your Visual Studio installation.

What he meant regarding the details of your hardware are things like, what motherboard do you have?

Why is it considered warez? Is it a corporate edition repackage?

Sure, but it's still a programming choice that was made within Windows itself. You simply don't just read a registry key that will return one or the other, you have to programmatically and implicitly read the HKCU key and if not found then programmatically and implicitly read the HKLM key.

Yes, it is. MSFN has grown around that concept. Many of us create software, write scripts, debug errors, create graphics and do research, sometimes taking hours and/or days to do it, all for charity. That's the core foundation of MSFN. We all exchange information, services, advice and help, all for free, simply because we can, simply because we want to. It's not for everyone, which is why I suggested that if you don't wish to fulfill his request for the creation of his graphic, to simply ignore it. Some people ask bigger things sometimes and some members do choose to help them. It's the way this community is.

The drive letters of drives using a FAT system is based on the following order: Primary Partition of the IDE Primary Master (or SATA Channel 1) Primary Partition of the IDE Primary Slave (or SATA Channel 2) Primary Partition of the IDE Secondary Master (or SATA Channel 3) Primary Partition of the IDE Secondary Slave (or SATA Channel 4) Extended Partitions of the IDE Primary Master (or SATA Channel 1) Extended Partitions of the IDE Primary Slave (or SATA Channel 2) Extended Partitions of the IDE Secondary Master (or SATA Channel 3) Extended Partitions of the IDE Secondary Slave (or SATA Channel 4) The drive letters of drives using an NTFS system is actually controlled entirely by the NT HAL, which means that directly in windows, you can change the drive letter attributed to any drive. Also, take note that although you can create more then one primary FAT partition, you will run into problems at some point or another. The reason that drive letters get attributed as I mentioned above is due to the fact that FAT was designed to have a single primary partition and a single extended partition. The extended partition can contain multiple logical partitions but the basis still remains that it's based around the primary/extended combo.

I'm curious as to the reasons behind why you would want to format in NTFS from DOS?

Go figure, good to know.