nmX.Memnoch

Or he could download the WMI Diagnosis Utility 2.0 from the Microsoft site and run that as a local admin... ;D It backs up and clears the repository as well. We found it when we found out that some custom stuff done to our workstations sometimes causes the repository to grow to astronomical sizes (several GB...yeah). Running WMI Diag on the workstation fixes the problem.

No, what he has is a stuck pixel (the blue sub-pixel is stuck on). Dead pixels are completely different. If it were a dead pixel, it wouldn't go away after a few minutes.tim_ver, you can find some "stuck pixel fixer" programs with a quick google search. One such is JScreenFix.

No, two 8800's in SLI with an Intel chipset is a no-no. A single 8800 will run just fine on an Intel chipset. If you want to run SLI and want an Intel CPU then you'll have to look at a motherboard with an NVIDIA chipset (their current chipset is the 680i but I don't think it supports the CPU you're looking at...however, the 780i should be released soon). All new x86 CPUs (save the current Celeron's) are x64 capable. That doesn't mean you have to run a 64-bit OS, it just means that you can. You'll be able to run 32-bit Windows, Linux or any other 32-bit x86 OS just fine on those CPUs. This depends on whether you want speed or redundancy. RAID0 is faster, RAID1 offers more data protection. If you want the best of both worlds get 4x500GB drives and setup RAID10. Weak power supplies can indeed cause some issues, but 1K W is overkill. I have a Dual Xeon 3.06GHz setup (the very power hungry Xeon's) with 6GB RAM (6x1GB DIMMs), two PCI-X RAID controllers, a 6800XT AGP video card, onboard GigE NIC, six hard drives (used to be eight), a SCSI CD-ROM drive and a SCSI tape backup...all running off of a 680W PSU.

You still want that some one burns his fingers on this and starts to hack the hardware and drivers? (And later MSFN.org will be blamed) No...not at all. Where you said "Intel and SLI is NO-GO", that would imply that you can't use SLI if you want to use an Intel CPU. The full story is that you can't do SLI on an Intel chipset, but if you use an nForce 680i based motherboard you can do SLI with an Intel CPU without hacking any drivers. That's what I meant by "slight correction".

I think they added more mutli-core support...specifically better HD decoding support for multi-core CPUs. Apparently it's supposed to make viewing HD videos possible on "lower-end" dual-core processors.

Slight correction...Intel and SLI is possible, if you use an NVIDIA chipset based motherboard with an Intel CPU. I wouldn't worry about SLI anyway. Either get yourself an 8800GT or if the money really is burning a hole in your pocket get the new 512MB 8800GTS. The 8800GTS 512MB will run on par with the 8800 Ultra anyway, and costs less. Onboard sound? Nah, I'd still rather throw in a cheap SB Live! or Audigy 2 rather than use onboard sound. I certainly wouldn't trade my Audigy 2 ZS for onboard sound. I do agree on the 2x500GB RAID0 vs. a single 1TB drive though. It'll give much better performance. But, on the same token since he's already looking to spend sooooo much money on the system why not just go with a couple SAS drives and throw a SAS RAID controller in one of those unused PCIe X16 slots? Yeah, it's overkill, but it looks like that's what he's shooting for anyway...plus it'll perform like a beast! ;D

It's still solvable by using a single script (be it KiX, VB or whatever your chosen language). Yes, your solution works just fine...all you're doing is pulling the same data from an XML file. I prefer not to use more files than I have to though. Calling that other file means that the originating script has to call another process to open another file...adding run time to the logon script. The less files you call, the quicker it runs. And trust me...we have that many or more shares here. Not at my level, but at this location as a whole. There are somewhere between 10-15K users at this single location. Every single one of them uses the same logon script, and in some cases (such as mine) a seperate script is called for their organization. I would much rather it be a single one, but that's not a call I get to make. My script currently calls one other script, but that's about to get merged into the main script (if I add major functionality to my script I begin by using a seperate file and then merge it into the main one once all the bugs are ironed out). As has been proven in this thread alone, there are multiple ways to do the same thing...it's just a matter of what you're most comfortable with and what works best for a given situation. ;D

Double post...see my reply in the other thread. Also, about putting the Word Viewer on the CD, one might want to check the EULA to see if it allows redistribution. If it doesn't, just include a link to the download.

If you want to make it professional looking you can get something that will allow you to create an autorun application. I use Autorun MAX! 2.0. It's pretty easy to use and you can create some nice looking menus with it. Short of that you could just create a basic HTML file that would autorun from the CD. The downside to using an HTML file is that the user will be prompted to Save or Open the file instead of it just opening.

If I'm not mistaken you can currently only have one password policy in the domain (this may change with Windows Server 2008). I believe it also has to be specified in the Default Domain Policy (or the Default Domain Controller Policy). Keep in mind that the user accounts are stored on the Domain Controller(s) so applying this setting to any other computers will only apply to local accounts on those computers, not the domain accounts. This is a setting that needs to be enforced on the Domain Controllers since there's where the user accounts are stored.

Yeah, I prefer it because I'm familiar with it (I've been using it for some 8 years or so now). One of the main reasons I prefer it though is that it's very well documented, easy to learn and once you get the basics down you can do some pretty advanced stuff with it. There's also a wealth of information (1, 2, 3) and a ton of User Defined Functions (UDFs) the other people have already made that can be used in your scripts. Full COM object support makes it really easy to do some of the more advanced stuff. If you want a good example of what can be done see the thread I linked above. I included a cleaned up version of my logon script in that thread. The editor I use is AdminScriptEditor 3.x. Originally it was KiXScript Editor and was (as the name would imply) only for KiX scripts. But they extended it to support VBS, AutoIt, PowerShell, Batch/CMD files, HyperText Applications and the last update added syntax highlighting for ADM templates (find that in another script editor!). The last update also added a script formatter (hit Enter at the end of your line and it reformats the line to "recognized coding standards"). The script formatter is a little buggy right now but it was a first release. Guaranteed they'll have it right in the next release or two. I highly recommmend downloading the demo to check it out (the current demo is a version or two back, but it has all of the important features).

Yes. It supports 64-bit operating systems, but will run 32-bit operating systems just fine. It's an "either/or" situation...

Overheating in 3 seconds just booting up though? Capacitors...check the capacitors on the motherboard. Particularly the ones in the immediate area of the CPU. The top of the capacitors should be relatively flat. If they're the least bit "domed" or appear to be leaking then that's your problem. A "thermal shutdown event" is the exact error message that the Dell OptiPlex GX720's give when the capacitors start going on them (as an example). Eventually they get to where the system won't even boot. What kind of system is this? If it's a custom built what's the motherboard model number? The Intel D865PERL motherboards also had a capacitor problem.

Since you've already installed it just go to Microsoft Update: http://update.microsoft.com/microsoftupdate/

Why do all the extra work? If you're mapping multiple groups to multiple shares there are several ways to handle it with a quick script (be it KiX or VB) that don't require creating yet another file that would have to be modified if group membership changes. Here are a couple of KiX examples: Example 1: Select Case InGroup("Production") Use P: "\\SERVER\Production" Case InGroup("Testing") Use P: "\\SERVER\Production" Use T: "\\SERVER\Testing" Case InGroup("Development") Use P: "\\SERVER\Production" Use T: "\\SERVER\Testing" Use X: "\\SERVER\Development" EndSelect Example 2: If InGroup("Production") Or InGroup("Testing") Or InGroup"(Development") Use P: "\\SERVER\Production" EndIf If InGroup("Testing") Or InGroup("Development") Use T: "\\SERVER\Testing" EndIf If InGroup("Development") Use X: "\\SERVER\Development" EndIf The difference being that with the "Select...EndSelect" the code section stops processing on the first true "Case". So for example if the user is in the "Production" group then it'll process that part of the Select...EndSelect statement without processing the "Testing" or "Development" sections. This results in code that runs a bit faster, especially if you order the groups logically (which does need to be thought out in the event there's say a user in both the "Development" and "Production" groups). My main logon script is ~1330 lines of code, and calls another script that's ~350 lines of code. The script maps drives, checks AV version and definitions, sets Office user values, configures settings and checks other application versions. It all runs in under a second.

Honestly, I have to agree. While they are expensive, you can't beat multi-monitor support on the Quadro's. To the point that I wish NVIDIA would include the "Allow taskbar to span displays" option in the drivers for their non-Quadro cards.

If you plan on this drive running constantly get one with a fan. I have a SATA one attached to my DVR...which runs 24/7. I had an AZIO enclosure with a 300GB 7200.8 Seagate drive. It lasted about a year before it died (technically it still worked but the DVR started acting weird). I replaced it with a Rosewill that has a fan and a WD WD5000AAKS 500GB drive...no problems since.

Yes, that will definitely provide better performance. I was just recommending against it if you didn't already have the hardware.

Yeah, that'll work although I'd recommend RAID1 for the data unless you have a good backup strategy. Also, that's a lot of money to spend for SCSI especially when the difference probably won't be as much as you might think since you're using it in a single user environment. SCSI is a parallel technology and is quickly being replaced by SAS, even on the low end.

I hope you're not trying to run them in dual channel mode. If so, that could be causing unknown problems as well. Your system may seem to be running fine now but that doesn't mean it'll stay that way with the mixed RAM. I don't even like mixing sticks in non-dual channel systems.

Are both of those sticks on the same motherboard?

The X6800 is dual core @ 2.93GHz. I have this CPU in my system.

We did talk about it before and apparently it used to be easy to modify the NVIDIA drivers to remove the Intel chipset check. But it appears that NVIDIA got smart and made some other change to the drivers that hasn't been undone yet. http://forums.extremeoverclocking.com/show...d.php?p=2465093 I'm pretty sure it stands to reason that if the 945GM chipset can do SLI in laptops that the 965/975/P35/X38/etc could do it on the desktop.

Actually...that's only half true. SLI works on Intel chipsets...but NVIDIA disables it via the driver if an Intel chipset is detected...unless it's a 945GM chipset in one of the SLI laptops. It's some licensing thing. I've read (last sentence of first paragraph) that SLI has been seen working on the X38 chipset using some hackery. No instructions were provided on how to hack the driver though. Intel has also done something so that the Skulltrail platform supports SLI (that's an expensive route to go though).

"SLI" and "CrossFire" are terms for linking the video cards for better (mostly) gaming performance. Yes, using two NVIDIA or two ATI cards will allow you to run all four monitors at once. They don't have to be linked for that to work. The problem then becomes whether or not the server actually has two PCIe 16X slots for the two cards.