m4dh0

Ive seen the 100% usage on machines with sfc enabled both xp and 2000, shouldnt there be a poll option for that ?

A bad workman blames his tools .......

Slipstreaming also breaks the local install source as well

Think about it this way, a multi core cpu uses one physical socket on the motherboard at the moment. XP Pro can support 2 sockets XP Home can support 1 socket At the moment it dosnt matter if its multicore or not as unlike oracle ms licences by socket

You can get the WSUS client diagnostic + readme from http://www.microsoft.com/windowsserversyst...ds/default.mspx

The Pilot should not be punushed until an enquiry has determined if it was him at fault or a failure outside of his control (due to bad maintainance of aircraft for example)

Firewall: Router Anti-Virus: Nod32 Advanced Windows Tuning (software like tweakXP): regedit Download Utilities: built into firefox E-Mail: Outlook 2003 and Thunderbird Webdesign: Dreamweaver MX2004, NVU Graphics Development: Photoshop CS2 Hard-Drive optimization tools (defraggers for example): O&O Defrag Windows error Checking (Like Norton Utilities): N/A Video Player: Media Player Classic Audio Player: Foobar DVD/CD Burning: Nero Antispyware: Adaware SE personal, Spybot 1.3 and MS antispyware

AS i dont have access to SMS + SMSI i cant really answer that

the following registry file "should" do it Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\TCL] "Driver"="C:\\WINDOWS\\System32\\sqlsrv32.dll" "Description"="TCL" "Server"="MyTCLServer" "QuotedId"="No" "AnsiNPW"="No" "Trusted_Connection"="Yes" [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources] "TCL"="SQL Server" as the above is all under HKLM it automaticaly becomes a system dsn available to all users You also dont need to add anything under HKLM\Software\ODBC\ODBCINST.INI as the needed entries are already in place. Ps. ive not tested this

You can create sql server dsns via registry files, example below. [HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\DSNNAME] "Driver"="C:\\WINDOWS\\system32\\sqlsrv32.dll" "Description"="Description" "Server"="sqlservername" "Database"="databasename" "LastUser"="sqlusername" [HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\ODBC Data Sources] "DSNNAME"="SQL Server" oops edited to be HKEY_LOCAL_MACHINE to make into system dsns

the ms sql server odbc drivers is included with windows, however installshield can create odbc sources during installing an app

I know but it will be shortly. Takes a few days normally. Was just released on windows update yesterday. <{POST_SNAPBACK}> Not quite true. It was released on windows update v6 beta only

http://forums.winforums.org/showthread.php?t=7331

no microsoft does not update the IE download with each security update so it would be identical to the 6 month old version

no the compact framework is for pocketpc devices ie ipaq etc

msiexec /i filename.msi /qn

it should be ECHO. ECHO instlaling XML V4.0 SP2 ECHO Please wait..... start /wait %systemdrive%\install\Hotfixs\KB832414_MSXML4.0_x86.exe /C:"dahotfix.exe /q /n" /q

kurt476 ... no problem in case you dont find it on pubforum there is also http://www.pubforum.net/security/w2k3/index.htm

also http://www.pubforum.net/w2k3postrtm.htm

http://www.microsoft.com/downloads/results...&DisplayLang=en http://www.microsoft.com/windowsserver2003...ds/default.mspx

changing the config.txt used to build the install program to the following fixed it for me

Ryan, Ive been building some sfx installs based on what you do and was just wondering how you changed the sfx files icon ? ie. the java icon for your jre 5.0 installer

this is already included in sp2

the only version of sql 2000 that can be installed on a windows 2000 pro machine is sql 2000 personal edition. IIS in windows 2000 pro is limited to 1 site and 5 concurrent connections, there is no way round this other than installing server unfortunatly

.net 1.1 obviously needs to be installed before installing the service pack, but try this for the service pack NDP1.1sp1-KB867460-X86.exe /q