edmoncu

im having the same problem here and i did not find the the aec6280.sys file in the i386 folder. i used the latest driverpack from bts though.

try the script i made (on the same thread SiMoNsAyS posted)... perhaps it will work for you.

great! can't wait for an updated MSI! thanks alanoll.

hi, if im going to use this in conjunction with ryanvm's pack (as well as mass storage pack of bashrat's), which of these should i integrate with the xp cd, this pack or ryan's? thanks.

i saw an article at tom's hardware on enabling raid 5 under windows xp, which involves hex-editing some files... i was wondering if it could be applied to the source xp files (by hexediting them and recompressing them with makecab)... the files needed to be hex-edited were: dmboot.sys, dmconfig.dll and, dmadmin.exe. although i already tried hexediting the files, im hesitant if it will automatically enable raid5 support once i re-compress the hex-edited files. note: the article at tom's is somewhat not consistent with my setup, especially at the dmboot.sys file... the offset was different on my setup. i am using winxp pro.

yeah. compressing the trimmed down office installer does help further reduce the installer size.. mine got roughly the same resulting capacity. i only bundled word, powerpoint and excel.

tried looking for "doom" words in the registry... so far, i have found a couple of appearances, but this one seems to be relevant. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RemovalTools] "MydoomTool"="OK"i wonder if this in combination of adding a dummy log file (%windir%\doomcln.log) on the debug folder is enough to trick WU into thinking the doomcln.exe has been executed. sorry for the succeeding questions... i just happened to look at the %windir%\setuperr.log file... and i saw these... (snippets only) Error: Setup had problems registering the following OLE control DLL: C:\WINDOWS\system32\blastcln.exe Contact your system administrator, who may provide assistance in diagnosing this problem. *** Error: Setup detected that the system file named [c:\windows\system32\blastcln.exe] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. ***

this is wierd... i tried decompressing the blastcln.ex_ file i just integrated onto the source with the one i re-downloaded from the web... thinking there was just an integrity problem with the files that were burned... i found no differences using the FC /B command. however, when i tried re-compressing the downloaded file to a cab via makecab and did a file comparison... i saw some differences... grrr... im confused now... 00000036: 02 93 00000038: 5C 2A 00000039: 73 61

oh... hmm, i did the same... however, an error appeared during the registering component stage... kinda forgot what the exact message was but it was a fatal error or something... checking at the log file (%windir%\debug\doomcln.log), i found the following message... Microsoft MyDoom removal tool (build 1.227) started on Sun Dec 19 12:52:12 2004 Checking 23 processes. Checking startup registry keys for current user. Checking keys for 1 other users Insufficient memory - 0 bytes needed Can't query value for `Startup`, datasize=148, err=00000002 Deleted registry key 80000002:Software\Microsoft\Windows\CurrentVersion\Shell Checking known MyDoom filenames. Microsoft MyDoom removal tool stopped on Sun Dec 19 12:52:12 2004 wonder if i did something different. i just repacked the doomcln.exe file with the makecab...

hi ryan. would like to confirm this... to remove the latest KB836528 patch from WU, ill just have to do this... - download the KB836528 update (for english language) - decompress the DoomCln-KB836528-v4-ENU.exe file. (english file) - on the decompressed folder, rename the uncompressed doomcln.exe to blastcln.exe - compress the blastcln.exe file to blastcln.ex_ to the source i386 folder.

great scripts... up to now, im stuck at issuing CMD to launch a fileexist command, as well as installing entire apps on a subdirectory. great tips! will have to redo my scripts to use pure autoit commands.

i believe notepad isn't recommended on editing binary files such as bootfix.bin.

Microsoft Security Bulletin MS04-040 Cumulative Security Update for Internet Explorer (889293) Severity: Critical Issued: December 1, 2004 Version: 1.0 Affected Components: Internet Explorer 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 3, on Microsoft Windows 2000 Service Pack 4, or on Microsoft Windows XP Service Pack 1: Download the update Internet Explorer 6 Service Pack 1 on Microsoft Windows NT Server 4.0 Service Pack 6a, on Microsoft Windows NT Server 4.0 Terminal Service Edition Service Pack 6, on Microsoft Windows 98, on Microsoft Windows 98 SE, or on Microsoft Windows Me: Download the update Internet Explorer 6 for Windows XP Service Pack 1 (64-Bit Edition): Download the update Systems not affected: Internet Explorer 5.01 Service Pack 3 on Windows 2000 SP3 Internet Explorer 5.01 Service Pack 4 on Windows 2000 SP4 Internet Explorer 5.5 Service Pack 2 on Microsoft Windows Me Internet Explorer 6 for Windows Server 2003 Internet Explorer 6 for Windows Server 2003 64-Bit Edition and Windows XP 64-Bit Edition Version 2003 Internet Explorer 6 for Windows XP Service Pack 2 Site: Microsoft Technet Security

i suppose with the newer catalyst drivers, the need for ISS file is not a necessity anymore since the /K switch supplants it.

hi all, i've made a new autoit script from scratch that automates that silent installation of outpost firewall pro 2.5.xxx... i tried not to use the sleep (delay) command since it may add some inconsistency with fast or slow pc's. here's my autoit script Run(@HomeDrive&"\Others\outpost\OutpostProInstall.exe /s") WinWait("Create New Configuration") ControlClick ("Create New Configuration", "", "Button5") WinWait("Configuration Wizard") $e= ControlCommand("Configuration Wizard", "", "Button5", "IsEnabled", "") While $e=0 $e= ControlCommand("Configuration Wizard", "", "Button5", "IsEnabled", "") WEnd ControlClick ("Configuration Wizard", "", "Button5") $c= ControlCommand("Configuration Wizard", "", "Button8", "IsVisible", "") While $c=0 $c= ControlCommand("Configuration Wizard", "", "Button8", "IsVisible", "") WEnd ControlClick ("Configuration Wizard", "", "Button8") WinWait("Install", "This system must be restarted to complete the installation. Click the OK button to restart this computer. Press Cancel to return to Windows without restarting.") ControlClick("Install", "This system must be restarted to complete the installation. Click the OK button to restart this computer. Press Cancel to return to Windows without restarting.", "Button3") ProcessWaitClose("OutpostProInstall.exe") DirCreate(@ProgramsDir&"\Agnitum") DirCopy (@HomeDrive&"\Agnitum", @ProgramsDir&"\Agnitum", 1) DirRemove(@HomeDrive&"\Agnitum", 1) RunWait("REGEDIT /S "&@HomeDrive&"\Others\outpost\register.reg") so, without the delay command, this script will be as responsive between a slow and a fast pc. what this script does is it checks if buttons are clickable/visible or not, as in the case of outpost installation, some buttons starts up unclickable yet during the progress of the installation on the same window... this script monitors it. also, during the testing, i've found a way on cutting back much of the time outpost pro installs and the lines of the script as well... i just dunno if this one will install outpost properly... here's the alternative script: Run(@HomeDrive&"\Others\outpost\OutpostProInstall.exe /s") ControlClick ("Configuration Wizard", "", "Button6") WinWait("Install", "This system must be restarted to complete the installation. Click the OK button to restart this computer. Press Cancel to return to Windows without restarting.") ControlClick("Install", "This system must be restarted to complete the installation. Click the OK button to restart this computer. Press Cancel to return to Windows without restarting.", "Button3") ProcessWaitClose("OutpostProInstall.exe") DirCreate(@ProgramsDir&"\Agnitum") DirCopy (@HomeDrive&"\Agnitum", @ProgramsDir&"\Agnitum", 1) DirRemove(@HomeDrive&"\Agnitum", 1) RunWait("REGEDIT /S "&@HomeDrive&"\Others\outpost\register.reg") with that does compared to the first script is that this time, the installation finishes even at the first part of the wizard. Anyways, the folder \Others\outpost is just a sample location i used, you can set it anywhere you placed the outpost installer and the registry file. The registry file pre-contains the registration key of my outpost. You may use yours. Remember, when placing the registration key for ourpost to the registry file, just place the entire keys in one line like so... (example) if the registration key is like this... ABCD EFGH IJKL MNOP you should enter the key to the registry file like this... Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Agnitum\Outpost Firewall] "Key"="ABCDEFGHIJKLMNOP" hope this clears some things.

i've got a similar problem (but setting only the year) and i was able to find a way on circumventing it. hope it helps.

no problem simon, your guide's awesome!

cool! thanks a bunch for this guide!

thanks in advanced!

was hoping for a guide.

Hi... first off, i should say that i dont have a radeon card, which is why i cannot test the catalyst driver i got... I've downloaded the latest catalyst 4.11 from ati and i was hoping you could guide me on a way on installing the catalyst control panel that came with it silently... Its said that the setup file is an Inno file and it requires running the setup with the -r parameter in order to create a silent setup.iss file script. However, during inspection of the files i downloaded, i found out that the control panel folder of the catalyst 4.11 installer already has 2 *.ISS files (setup.iss and setup_shortcut.iss). My question is, would it be okay to use any of these files as references when making a silent install of the control panel via: if exist %systemroot%\system32\atiddc.dll setup -s -f1 setup.iss anyway, for your reference... here are the contents of both files... setup.iss [InstallShield Silent] Version=v6.00.000 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-DlgOrder] Dlg0={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdWelcome-0 Count=6 Dlg1={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdLicense-0 Dlg2={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdAskDestPath-0 Dlg3={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SprintfBox-0 Dlg4={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SprintfBox-1 Dlg5={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdFinishReboot-0 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdWelcome-0] Result=1 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdLicense-0] Result=1 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdAskDestPath-0] szDir=C:\Program Files\ATI Technologies\ATI Control Panel Result=1 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SprintfBox-0] Result=6 [Application] Name=ATI Control Panel Version=3.00.000 Company=ATI Technologies Lang=0009 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SprintfBox-1] Result=6 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdFinishReboot-0] Result=1 BootOption=0 setup_shortcut.iss [InstallShield Silent] Version=v6.00.000 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-DlgOrder] Dlg0={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdWelcome-0 Count=5 Dlg1={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdLicense-0 Dlg2={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdAskDestPath-0 Dlg3={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SprintfBox-0 Dlg4={0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdFinishReboot-0 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdWelcome-0] Result=1 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdLicense-0] Result=1 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdAskDestPath-0] szDir=C:\Program Files\ATI Technologies\ATI Control Panel Result=1 [Application] Name=ATI Control Panel Version=3.00.000 Company=ATI Technologies Lang=0009 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SprintfBox-0] Result=1 [{0BEDBD4E-2D34-47B5-9973-57E62B29307C}-SdFinishReboot-0] Result=6 BootOption=3 otherwise, would anyone here be generous to hand me his pre-created setup.iss th at can work with installing the catalyst 4.11 control panel? thanks in advanced. i've read at this page also an alternate method at running a silent install... that is by running setup with the /k parameter. would like to confirm if this method is better than the ISS method. please don't get me wrong guys, i've searched through the posts here first... or perhaps i was looking at the wrong places... hope you could excuse me if this question has been raised before. thanks in advanced for the help.

sorry for the noob-ish question, but my friend has motherboard that has an integrated soundstorm, and he also has a PCI SBLive soundcard. he made sure on his board's bios that the onboard sound is disabled... upon installing windows (using the latest driverpack sound), both the drivers for the sblive and soundstorm were installed. it actually wasn't the problem, but even as sblive drivers were installed, it doesnt produce sounds at all.

Try to install latest drivers for nForce chipset. Download'em from nVidia web-site. oh, i thought the mass storage drivers that came with bashrat's driverpack are already the latest ones, including the ones from nvidia? does my friend still has to re-install the IDE drivers even if it is installed from the driverpack via xp installation?

the old switches works for me even with this new nero 6.6.0.1... what does not work is the old serial number.

my friend has an nforce2-based board (epox ep-8rga), he is having problems burning with nero (latest 6.6.0.1) as it stalls at the middle of the burning process... and on his device manager, all his IDE drives were enumerated as SCSI drives... same instances on my similar nforce2-board (epox ep-8rda3+). though i dont have any problems burning under nero 6.6.0.1.