krose
Content Type
Profiles
Forums
Events
Posts posted by krose
-
-
I am happy to report that with 1.79_ beta_c the file versions in sourcess\i386 are now 9.0.0.4504. May I ask what code you changed to achieve this? Thanks and Merry Christmas!
0 -
Oh I am in no hurry for a fix. I realize the effort HFLSIP takes. I have one box with a quad so I need to use XP or I would be using Win2k on it too. I will just use the replace folder for now and if there is a fix, fine; if not, the replace method works too.
0 -
I added REM to line 1368 and ran HFLSIP. Files in sourcess\i386 are still 9.0.0.4503. I paid close attention the the extraction of the hotfix and discovered that HFSLIP is extracting the files from the folder "mceur2" which are version 10.0.0.4362. WTF is mceur2? Here is a table of all the files from the hotfix from the MS bulletin at http://support.microsoft.com/?kbid=952069.
Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5,
and Windows Media Format Runtime 11 for Windows XP Service Pack 3
Folder name File name File version File size Date Time Platform
Logagent.exe 10.0.0.4362 96,768 11-Jun-2008 07:47 x86
mceur2 Wmnetmgr.dll 10.0.0.4362 988,672 11-Jun-2008 07:58 x86
Wmvcore.dll 10.0.0.4362 2,330,624 11-Jun-2008 07:58 x86
Logagent.exe 10.0.0.3703 96,768 10-Jun-2008 14:17 x86
wm10 Wmnetmgr.dll 10.0.0.3703 1,026,048 10-Jun-2008 16:37 x86
Wmvcore.dll 10.0.0.3703 2,364,472 10-Jun-2008 16:57 x86
Logagent.exe 10.0.0.4066 96,768 10-Jun-2008 10:52 x86
wm10l Wmnetmgr.dll 10.0.0.4066 1,028,096 10-Jun-2008 11:28 x86
Wmvcore.dll 10.0.0.4066 2,376,760 10-Jun-2008 12:07 x86
Logagent.exe 11.0.5721.5251 100,864 18-Jun-2008 06:09 x86
wm11 Wmnetmgr.dll 11.0.5721.5251 938,496 18-Jun-2008 10:03 x86
Wmvcore.dll 11.0.5721.5251 2,458,112 18-Jun-2008 10:03 x86
Logagent.exe 9.0.0.4504 103,936 10-Jun-2008 08:11 x86
wm9 Wmnetmgr.dll 9.0.0.4504 1,053,696 10-Jun-2008 11:11 x86
Wmvcore.dll 9.0.0.4504 2,174,976 07-Nov-2008 21:45 x86How does HFSLIP know which ones to extract? It would appear that for my purposes it should have used the wm9 files. Can HFSLIP be coded to use the correct files for a particular build? This looks like a real pita to fix.
Edit: Sorry I can't seem to get a table of data lined up right.
0 -
see next post
0 -
First, thanks for HFSLIP 1.79 beta. Win2K works perfectly. However, for XP and HFSLIP 1.79, Windows media KB952069 hotfix is still showing up in WU for me. I extracted the hotfix, and each WMxx folder contains the files logagent.exe, wmnetngr.dll, and wmvcore.dll which are all v. 9.0.0.4504 for WM9. The files in my sourcess\i386 folder are v. 9.0.0.4503. I compressed the files from the hotfix with makecab, put them in my replace\i386 folder, and ran it again. No complaints from WU now. I can see the hotfix being extracted during the HFSLIP run but the files are not copied or are overwritten somehow. It also works placing the hotfix in the hfsvcpack_sw1 folder.
0 -
Do you also have the line
OemFilesPath="..\$OEM$"
in your winnt.sif?
0 -
I had the same problem with HFSLIP and XP sp3. I extracted the KB952069 hotfix then searched for the filenames wmvcore.dll, wmnetmgr.dll and logagent.exe and found them in the windows system32 folder of my install. They were all file version 9.0.0.4503 and the hotfix files are 9.0.0.4504, so they are not being copied or are being overwritten somehow. You can fix this one of several ways. To fix your current install just copy the extracted hotfix files to the system32 folder and reboot. Windows update should no longer complain. For future installs, you can shorten the hotfix name to kb952069 and place it in the HFSVCPACK_SW1 folder to have it installed by svcpack.inf at T-13. Or you can compress the three files with makecab and place them in the replace\i386 folder. I tried the latter and it worked, but I did have one strange thing happen. WU said I needed the December malicious software tool even though it was slipstreamed. I ran the tool, rebooted and WU no longer complained. Don't know what happened there.
Edit: I just use media player 9 so I used the files in the wm9 folder of the extracted hotfix.
0 -
I would try not using the $OEM$\$1\1\Drivers directory and just use $OEM$\$1\Drivers. In your winnt.sif do not use a space after the semicolon separating the entries in your OemPnPDriversPath. Perhaps setup is only seeing the chipset driver because of the 1\ usage. That is the reason for using the 000_xxx, 001_xxx, etc. folders as setup looks for incremental folders for the drivers and setup stops at \1. So drivers\000_xxx will work but 1\drivers won't? At least this is what works for me. Any particular reason you are using 1\drivers directory?
0 -
I tried to email but it came back as undeliverable. Check your PM for a download link.
0 -
I don't use nlite so I can't answer that. Since it is an installshield installer, you can use the /r switch to install it, selecting the options you want. Setup will create a file setup.iss in the C:\Windows (or C:\WINNT) directory. Subsequently you can use the /s /f1<path>setup.iss switches to do an unattended install. If this can be used for nlite I don't know. Check your Gmail I just sent you the installer and the setup.iss file that I used.
0 -
Please check your PM.
0 -
I use this for the Ghostscript 8.54 msi installer from RunOnceEx:
REG ADD %KEY%\077 /VE /D "Ghostscript" /f
REG ADD %KEY%\077 /V 1 /D "%CDROM%\install\pdfwriter\GPLGhostscript854.msi /quiet /norestart" /fYou can use the /verysilent switch for CutePDF but it wants to connect to the internet after install so I just made a simple cmd file to install it then kill iexplore.exe:
cwnd /hide @
@echo off
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\win51ip.sp3 SET CDROM=%%i:
start /wait %CDROM%\install\pdfwriter\cutewriter.exe /verysilent
taskkill /f /im iexplore.exe
exitRun the cmd from RunOnceEx:
REG ADD %KEY%\078 /VE /D "Cute PFD Writer" /f
REG ADD %KEY%\078 /V 1 /D "%CDROM%\install\pdfwriter\cutewriter.cmd" /fA bit tedious but it works.
0 -
Sounds like the theme from "A Summer Place" by Percy Faith.
0 -
Regarding KB898461, I let WU install it to see what would happen. WU then asked for a roots update that appears to be from May. Roots Update. This is with SP3, IE7 and hotfixes from the dynamic SP3 list. I am not 100% sure, but I believe this only happened after I started using the latest WU agent. I think the previous version of WindowsUpdateAgent30-x86.exe worked fine, WU did not ask for KB898461. I think I still have the old version and will test.
Edit: WU does ask for KB898461 using the previous version of WU Agent. I did use the roots update I linked to and WU does not for that after installing KB898461.
0 -
@cool400
I found the setup.inf parameters in the Avira Antivir Professional manual. They are covered in section 4.5.4. All versions must use the same installer so I would think any of the setup parameters except for the mail scanner would work in the free version. The only way to find out is to test them. Thanks for your help.
0 -
cool400,
Thanks for the information. I didn't realize that version 8 was out. Looking at the documentation I have discovered that there is a new setup.inf entry. Add the line
ScanMode=0
to setup.inf and you can eliminate the use of the cmd file to kill the post-install scan. The setup command will now run from the advanced SFX options setup program run after extraction window:
%windir%\Temp\Avira\basic\setup.exe /inf="%windir%\Temp\Avira\setup.inf"
Tested and totally silent for me.
0 -
USB function might only be as good as implemented in the hardware, in this case the southbridge. I have an XP laptop with an ATI Radeon Xpress 200M northbridge paired with the SB 450 southbridge. USB performance is not nearly as good as my Win2K desktop with Intel ICH9R southbridge. IIRC the SB 450 was known for crappy USB performance.
0 -
-
I used the McAfee Wireless Security program with Win2K. It's free and works with most wireless cards. I used it on a laptop, and two different desktop PCI cards. One older A/B card did not support WPA with the vendor's utility but with McAfee it worked fine.
0 -
The registration key file is named hbedv.key. It is in the antivirpec folder to which you extracted Antivir_workstation_win7u_en_h.exe. The setup.inf file you created refers to the key file location, which in this example is C:\Windows\Temp\Avira. The paths you enter in the WinRAR Advanced SFX Options window tells the installer to extract to C:\Windows\Temp\Avira, then to run the antivir.cmd file you created, which in turn runs the setup.exe. Make sure your setup.inf and antivir.cmd files have the proper file extension and check all your paths to make sure they are the same as the example. I can't explain it any better than that.
0 -
As I mentioned in my post, Taskkill is only available for XP Pro users, process.exe is only for XP Home and Win2k users, unless someone can enlighten me otherwise.
@ahmedah - if you followed my example exactly it should work. Make sure that the paths are correct. What OS are you using?
0 -
I figured out a way to do a totally silent switchless installer for Avira Antivir Personal Edition Classic. It involves a little work but in the end works nicely. You will need the following:
Antivir_workstation_win7u_en_h.exe http://www.free-av.com/
WinRAR http://www.rarlab.com
Cwnd.exe http://www.ryanvm.net/forum/viewtopic.php?t=5017 , executable is in the “release” folder
Process.exe http://www.beyondlogic.org/consulting/proc...processutil.htm
Download Antivir and extract it with 7-zip or WinRAR to a folder, I called it antivirpec. We are going to create two files and add them to the folder. Open a text editor such as notepad and copy the following text.
[DATA]
DestinationPath="C:\Program Files\Avira\AntiVir Workstation"
ProgramGroup=1
DesktopIcon=0
ShellExtension=1
Guard=1
MailScanner=0
KeyFile=C:\Windows\Temp\Avira\hbedv.key
ShowReadMe=0
RestartWindows=0
ShowRestartMessage=0If you want a desktop icon change the 0 (no) to 1 (yes). MailScanner must be 0 because it is not included in the free edition. If you want to change the path of the install or the path to the registration key just make sure it is an absolute path, variables such as %windir% will not work. Save the file as setup.inf and place it in the antivirpec folder.
Open notepad again and copy the following text.
cwnd /hide @
@echo off
start /wait %windir%\Temp\Avira\basic\setup.exe /inf="%windir%\Temp\Avira\setup.inf"
process -k avscan.exe
exitcwnd.exe is a utility to hide the DOS box when the command runs. You could also use cmdow.exe. Just be sure that whichever you use is in your system32 folder.
The setup command uses the switch /inf which uses the parameters in the setup.inf file we created and causes the setup to be run silently.
Process.exe is a utility to kill processes in Windows 2000 and Windows XP Home. If you are using XP Pro you can use the taskkill command instead. This command kills the automatic scan that starts after install. If you use process.exe be sure it is in your system32 folder. Save the file as antivir.cmd and place it in the antivirpec folder.
Now make the installer with WinRAR. Open WinRAR and browse to the antivirpec folder. Right click on a file and choose “select all”, making sure all the files and folders are highlighted, then click “Add” on the Toolbar. You’ll get the “Archive name and parameters” window. On the General tab Select “best” as compression method, and check “create solid archive” and “create SFX archive”. Change the archive name if you like but it must have the .exe extension.
Switch to the Advanced tab and select “SFX options” to open Advanced SFX options window.
On the General tab in the “Path to extract” box type the path you want to extract the installer to. Make sure it is the same path you have in the antivir.cmd file. Then in the “Run after extraction” box type in the path to the antivir.cmd file.
Change to the Modes tab and select the “hide all” and “overwrite existing files” radio buttons.
Close the “Advanced SFX Options” window by clicking OK, then click OK on the “Archive name and parameters” window to start creating the installer. The finished installer is created in the antivirpec folder.
0 -
TC, I suspected as much after reviewing what I had done. I can figure it out from here. Thanks for your help.
0 -
I forogt to mentioned that I used nlite to integrate RAID drivers and remove some stuff. I have never had any problems using nlite after HFSLIP before. I had copied the SOURCESS folder and ran nlite on it. Attached are the txtsetup.sif files from the original SOURCESS folder (txtsetup-sourcess) and the one after nlite was run (txtsetup-nlite). Thanks for your help.
0
Slipstreaming Intel Matrix Storage Drivers in XP Pro
in Device Drivers
Posted · Edited by krose
I followed the instructions in the sticky here and it worked fine for me. It takes a bit of time and requires editing txtsetup.sif but if you are documenting the process then it should be OK for you.
Edit: this is not a Microsoft documented process but I don't know what else you can do.