nmX.Memnoch

Errrr...yeah, because all of my database servers at work have to be replaced every year since they're being hammered. Vista isn't going to make your hardware die faster.

The $99 includes one year of support and upgrades. You don't have to pay the $75/year after the first year, but you won't get "free" upgrades or support. PrimalScript is kind of the same way. They are even charging for upgrades from 4.0 to 4.1 if you don't migrate your licenses within a specified timeframe. PrimalScript is also more expensive, almost twice the price just for the Standard edition...and I would recommend opting for the Professional edition simply for one or two features it has over the Standard edition (which, of course, they did on purpose).

The price should run about the same from other online retailers. It may run a little higher than NewEgg, but it shouldn't be by much (usually within $10-15).

Do those other editors have proper color coding for KiX? The trick is finding one that has syntax highlighting for KiX. A GOOD editor will also have popup features that offer help along the way. For instance, in AdminScriptEditor if I type the @ symbol it'll popup a list of all the built-in macros that I can choose from. Or if I'm doing a section to read a registry value using ReadValue() it'll popup tips and bold the current section of the command you're at. This is called ScriptSense in AdminScriptEditor. Here's a flash video: http://www.adminscripteditor.com/editor/sc...riptTips20.html There are several other really nice features in the editor that I like (a wizard for MessageBox(), for Chr() and a few others). They're planning a major upgrade in the near future that will add some more features and support for other scripting languages.

Yeah, specifics of the hardware would definitely be helpful. Also, are you running 32-bit or 64-bit WinXP? PAE will work with AMD processors, but 32-bit WinXP still won't "see" anymore than 4GB.

Hmmm...yeah, I'll have to figure something out for deleting older save games. I have a few ideas though. I remembered another editor that I've used before. The previous editors I mentioned are good for editing KiX scripts, VB scripts, XML, HTML, CMD scripts, etc, etc. This one is geared specifically towards KiX only and is free. It require's .NET 2.0, but so does AdminScriptEditor. http://www.thatguyssoftware.com/kixtarter.html It has some nice features, but again I prefer AdminScriptEditor. One of the main reasons is that of the three, AdminScriptEditor is the only one that correctly interprets block commenting.

Ahhh...thanks for the explenation. So would it be turned off if you had NoExecute=AlwaysOff in the boot.ini? Not that I want it off...I'm just curious.

You really don't need it in anything but the Administrators group for the backup account. The account would be used strictly for unlocking the main admin account.

Again, that's a hardware issue...not a WinXP issue. And I should clarify my statement about the 3.25 or 3.50. If you have a 32-bit only processor that's what it will show. But if you have a 64-bit capable processor, but 32-bit WinXP installed then WinXP will show the full 4GB. The General tab of System Properties will also show that PAE (Page Address Extensions) is enabled if you have 32-bit WinXP installed on a 64-bit capable CPU...no matter how much RAM you have (i.e. I have 2GB and it shows PAE enabled). I don't know if PAE actually is enabled (I don't have it turned on in the boot.ini) or if it's just something that 32-bit WinXP does with 64-bit CPUs.

That will not get everything. There are keys in the registry that even the built-in Administrator account doesn't have access to. The only way to do it properly is with a System State Backup.

Yeah...you're on the right track. Since you're only checking $Result and $Result1 once each now (using an OR) you can go back to an If...EndIf. If @USERID = "2nd OCCT" $Result = CompareFileTimes("C:\Scripts\testfile.txt", $TQBackup + "\CHKFileDir\testfile.txt") $Result1 = CompareFileTimes("Painkillersavefile", "Painkillersavefile") If $Result = 1 OR $Result = -3 messagebox ("Backing up Titan Quest Save-Game Files & restarting folding...","alert", 48) ? COPY "C:\Scripts\testfile.txt" $TQBackup + "\CHKFileDir\" @error? COPY "C:\Scripts\" "$TQBackup\$DATE\" /s @error ? EndIf If $Result1 = 1 OR $Result1 = -3 COPY "C:\Scripts\testfile.txt" $TQBackup + "\CHKFileDir\" @error? COPY "C:\Scripts\" "$TQBackup\$DATE\" /s @error ? EndIf EndIf PainKiller is a game I play so I'll see if I can come up with some good code for doing backups for that. How long do you want to keep the backups for? Like say the last 2 months worth? I have some code in my backup scripts at work that only keeps the last six months worth of backup logs...it does a check and automatically deletes anything older than 180 days.

Yes, it should be on there. To further my answer to jftuga, the following is from the NTBackup Help regarding System State Backups:

I've never had that problem. I do, however, typically do the critical and recommended updates seperate from each other. On Windows 2000 (and even XP/2003 for that matter) you will run into the case where some pieces have to be updated before you can use Windows Update. This includes the installation of MSI 3.1v2, BITS 2.0 and a few other things. Once you do that then you shouldn't have any problems running Windows Update (or Microsoft Update).

A system restore point does sort of the same thing, but on a larger scale. Creating a restore point copies a lot more than a system state backup does. It also allows you to recover from less serious errors. A system state backup will allow you to recover your registry should it become corrupted, or should parts of it get deleted that shouldn't have been deleted.Also, the NTBackup utility will still work when System Restore has been disabled. Are you running XP Home? If so I believe you can install NTBackup from the CD. See the following knowledge base article for instructions:http://support.microsoft.com/?kbid=302894

Sorry I missed these questions before...I got wrapped up in trying to figure out why the services code would all of a sudden stop working. Nesting commands is when you do something like: If @USERID = "Account1" Use X: "\\SERVER\SHARE1" Else If @USERID = "Account2" Use X: "\\SERVER\SHARE2" EndIf EndIfOr Select Case $X = "XValue1" COPY "$XFILE1" $XFILE2" Case $X = "XValue2" Select Case $Y = "YValue1" COPY "$YFILE1" "$YFILE2" Case Y$ = $YValue2" COPY "$YFILE2" "$YFILE1" EndSelect Case $X = "XValue3" COPY "$XFILE2" "$XFILE1" EndSelectNotice how in both examples I've started another If...EndIf or Select...EndSelect command before the first one had finished. That's nesting commands. Unless you're writing extremely large scripts, declaring a lot of variables and/or nesting a lot of commands then memory shouldn't be much of a problem. My logon script at work is between 1100 and 1200 lines long...and I'm not anywhere close to worrying about it. 2. Where did you learn this from? I ask because I looked at the command reference to see if there were examples like this but what it showed was pretty basic. Is there a resource available that I can use to study this kind of thing or is it just something that comes with experience? I've just picked it up from looking through other people's scripts. When you Split something you turn it into an array of variables. The number in the [] brackets represents an item in the array. In this case we split @DATE using the / character. So item [0] represents the first item in the array, which is the year in this case. Item [1] represents the second item in the array, or the month in this case. And item [2] represents the third item, or the day in this case. Personally, I always use spaces instead of tabs...but that's just my preference. KiX doesn't really care if you use tabs or spaces, it's a free form language. What I mean by free form is that all three of the following are technically correct, but most people use the same type of formatting I've used throughout this post because it's easier to read: If @USERID = "User1" Use X: "\\SERVER\SHARE" EndIf If @USERID = "User1" Use X: "\\SERVER\SHARE" EndIf If @USERID = "User1" Use X: "\\SERVER\SHARE" EndIf With older versions of KiX you could only use the semicolon ( character for commenting out lines or adding explenation text. That meant that to comment out a section of the script you had to add a semicolon to the beginning of every line. It would end up looking like this: ; Select ; Case $X = "XValue1" ; COPY "$XFILE1" $XFILE2" ; Case $X = "XValue2" ; Select ; Case $Y = "YValue1" ; COPY "$YFILE1" "$YFILE2" ; Case Y$ = $YValue2" ; COPY "$YFILE2" "$YFILE1" ; EndSelect ; Case $X = "XValue3" ; COPY "$XFILE2" "$XFILE1" ; EndSelect And explenation text looked like this: ; Script created by xxxxxxxxxx xxxxxxxx ; Last Updated: YYYY/MM/DD ; ; This script does this and that ; edit line 23 to change the value of $X ; etc etc etc With the new /*.....*/ block commenting, anything between /* and */ is considered a comment and not processed by KiX. This means you can comment out entire sections of a script simply by adding /* before the section and */ after the section, like so: /* Select Case $X = "XValue1" COPY "$XFILE1" $XFILE2" Case $X = "XValue2" Select Case $Y = "YValue1" COPY "$YFILE1" "$YFILE2" Case Y$ = $YValue2" COPY "$YFILE2" "$YFILE1" EndSelect Case $X = "XValue3" COPY "$XFILE2" "$XFILE1" EndSelect */ You can also use it to format an explenation block so it's a little more noticeable /* --------------------------------------------- Script created by xxxxxxxxxx xxxxxxxx Last Updated: YYYY/MM/DD This script does this and that edit line 23 to change the value of $X etc etc etc --------------------------------------------- */

Use the Backup utility in System Tools under Accessories (or enter ntbackup.exe in a Run prompt). To make a proper backup of the registry you want to do a System State Backup. This will backup the registry and your SAM (user account) database, as well as a few other items.

It took me a few minutes of looking at it to figure out what's going on. You have an errant charactor in your net start command. should be

Holy cow that's one BIG card!!

If that were true those applications wouldn't have stopped working because the rendering engine would still be exactly the same. I know what you're talking about. A friend of mine uses an older version of QuickBooks Pro. Certain features (that he doesn't use) don't work with IE7 and Intuit says they have no intention of releasing a patch for that version to work with IE7. Of course they aren't...they want him to buy the latest version, which is several thousand dollars. BUT, is it Microsoft's or IE7's fault that Intuit won't fix it? Would that application work if he switched his browser to Firefox or Opera? The answer is No to both. My point is, there were a lot of changes from IE6 to IE7. Microsoft did this to fix problems and complaints from previous versions. IE7 was in beta for a year and has been released for 6 months. Every application developer has had plenty of time to fix any potential issues. The problem is that some of them aren't even working on it or they want you to purchase the latest release.

There's nothing wrong with using IE7.

Add/Remove Programs > Add/Remove Windows Components It's a selectable option about halfway down the list.

Yeah, you can reorder the information after it's been split into an array. However, I recommend keeping it in YYYY.MM.DD format so it's listed alphabetically in chronological order in Windows Explorer. But, if you want to reorder it to MM.DD.YYYY, here ya go: $DATE = Split(@DATE,"/") $DATE = $DATE[1] + "." + $DATE[2] + "." + $DATE[0] That would be great, thanks! Hehe...scroll up. I'd already looked at it and replied again.

Just because you don't use it doesn't mean it you shouldn't be patched. An unpatched vulnerability can be exploited by malware whether you use the application or not. Simply having the application installed on the computer can be enough to have your system compromised.

I found the answer. http://www.microsoft.com/technet/prodtechn...I.mspx?mfr=true Fortunately I can make four drives work. The live cluster has the database data and log drives seperated for each database (two databases use four drive arrays). I can consolidate that in the testing/development environment and make four drives work (Quorum, MSDTC, two databases with data and logs on same VHD for each).

I really don't have the ability to test that for your specific setup since I only have the one NIC in my machine. I suspect it may very well though. Which Intel driver version are you using? They've been releasing new ones like crazy lately. What really gets me is all these net admins forcing switches to 100/Full instead of just leaving them on Auto. It's like a left over from YEARS ago when Auto didn't exactly work like it was supposed to. I hope they fully understand that the GigE standards calls for Auto or nothing to run Gig speeds. I'm fighting this battle with our config management shop at work right now as well. They have some ports left on Auto but most are on 100/Full. We have a policy of forcing the NICs to 100/Full when deploying a workstation...and then waiting to see if the user complains about slow network before we know if the port is actually on Auto or not. What really ticks me off is that when we finally deploy GigE (within the next 6 months I hope) that we'll have to go around and manually set all of those NICs back to Auto. Heh...we even have one of our net admins trying to tell me that 100/Half is faster than 100/Full!!