No point tracing the IP, DoS attacks are pretty much anonymous as they are ping flood attacks from several thousand innocent PCs that have been exploited security-wise, and all controlled from one DDOS server. Me and xper are working on hosting the DX9 OPK and WMP9MM2 Bundle on the MSFN server at the moment.
I don't think this has been mentioned yet, but for those who have trouble adding PATA/SATA/RAID controller drivers to your CD you can use this method to manually install the drivers with a floppy and still get the $OEM$ folders copied over. As some people may be aware, having OemPreinstall=yes will break F6 to install drivers, whereas OemPreinstall=No doesn't. Cmdlines.txt - This is executed no matter whether OemPreinstall is enabled or not, so we're going to launch a .cmd file from cmdlines.txt. Open up notepad and paste the following: @echo off
IF EXIST D:\$OEM$ set CDROM=D:IF EXIST E:\$OEM$ set CDROM=E:IF EXIST F:\$OEM$ set CDROM=F:IF EXIST G:\$OEM$ set CDROM=G:IF EXIST H:\$OEM$ set CDROM=H:IF EXIST I:\$OEM$ set CDROM=I:IF EXIST J:\$OEM$ set CDROM=J:
XCOPY /E /Q %CDROM%\$OEM$\$1 %SYSTEMDRIVE%XCOPY /E /Q %CDROM%\$OEM$\$$ %SYSTEMROOT%XCOPY /E /Q %CDROM%\$OEM$\$Docs "%SYSTEMDRIVE%\Documents and Settings"XCOPY /E /Q %CDROM%\$OEM$\$Progs "%PROGRAMFILES%"
EXITSave this as OemPreinstall.cmd in the \$OEM$\ folder. Add to (or make) a cmdlines.txt file: [COMMANDS]"OemPreinstall.cmd"And save in the \$OEM$\ folder. There is a disadvantage to this method - you cannot use OemPnpDriversPath= to install your drivers as the folders are copied over far too late for Setup to detect and install them.
Are you sure you viewed the correct Technet bulletin willpantin? http://www.microsoft.com/technet/security/...n/MS04-011.mspx Security Update Replacement: This bulletin replaces several prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list. FAQ section says it supercedes Q828028 (MS04-007)
Hi Bakura, welcome to MSFN. I think whoever told you was misinformed, MSFN is a news and forum site for Technology and Microsoft news, as well as providing support for the growing Unattended XP CD trend. We don't build websites or anything like that. But we do have a Web Development forum for getting help with web dev related topics.
heh a last minute change. Last time I saw the technet article it said: "Security Update Replacement: None" but I might have been wrong. Will make the change in the main list rightaway
Is OEMPreinstall="yes" in the winnt.sif file? This is the most overlooked problem, please make sure you read all of http://unattended.msfn.org/xp/winnt_sif.htm because its mentioned there.
Sorry for the delay! Changes: 5 New Updates added today: Q828741, Q831167, Q835732, Q837001, and Q837009. Q831167 may be 2 months old, but its appeared on WU today and is a 'fix' for the February 2004 IE Cumulative Update. Q330994 is now superseded by Q837009. Q828028 is also superseded by Q835732.
Appears to be different according to the Virus Bulletin website, where NOD32 catches the most viruses in the wild, and a fast scanning engine too. I plan to switch from Symantec to NOD32 soon.
Yes, just about everything on the site should work for Win2k, except the svcpack.inf entries, which should be: [Version]Signature="$Windows NT$"MajorVersion=5MinorVersion=0BuildNumber=2195
[setupData]CatalogSubDir="\i386\svcpack"
[setupHotfixesToRun]KBArticleNumber.exe /optionsOr you could use a batch file to install the hotfixes instead. You may want to search the forums for IE6SP1 installation instructions if you want to include that.
Looks like it may be corrupt. Try grabbing BANANA.AN_ file from your original Windows XP disc and replace it. Alternatively you could remove the banana.ani = 1,,,,,,,,3,3 line from TXTSETUP.SIF in the i386 directory.