For those of us who've already created and installed from a new XP disc with the update pack, is there any way to apply some of these changes manually without needing to reformat and reinstall?code65536 wrote:Yea, that's how I first noticed the problem. Fixed ini+infs (changes) for anyone who's interested.RogueSpear wrote:This may explain why a good deal of the .msi dialog boxes for my installers contain no text.
RyanVM Post-SP3 Update Pack 1.0.0a - Released August 27, 200
One of the cool things about the RVM Integrator is that you can just use the fixup 7z file as an addon pack, without having to modify the update pack itself. Don't think this trick works with nLite.TechnoHunter wrote:[edit] any idea what settings to use for re-compressing this addon back to small like it started? i cant seem to get it the same size as it began..
Create a new directory named 0409 in %SystemRoot%\System32\mui, and move msimsg.dll.mui from 0009 to 0409. The reason I wouldn't just rename the entire directory is that hhctrlui.dll is also installed to 0009, and I think that might be intended (with the original unmodified RTM disc, hhctrlui.dll gets installed to 0009, so whether or not it's intended, it's certainly a long-standing thing).kal wrote:Sure, easily : just rename %SystemRoot%\System32\mui\0009 to %SystemRoot%\System32\mui\0409.
Last edited by code65536 on Wed Aug 27, 2008 10:49 am, edited 1 time in total.
Since the 7z file name does not contain the word Addon, it cannot be selected for use by the Integrator unless typed in manually, but nLite can use it as is.code65536 wrote:One of the cool things about the RVM Integrator is that you can just use the fixup 7z file as an addon pack, without having to modify the update pack itself. Don't think this trick works with nLite.

fortunato, most don't use those anymore
for wmp 11:
you got a WMP11 slipstreamer
or OP WMP11 addon
WGAN is more useless! to be concerned about ...and dropped by most ..
and yea ...
thanks, ryan for the update
for wmp 11:
you got a WMP11 slipstreamer
or OP WMP11 addon
WGAN is more useless! to be concerned about ...and dropped by most ..
and yea ...
thanks, ryan for the update

-
- Posts: 5
- Joined: Wed Feb 27, 2008 10:45 pm
I'm getting one error with qfecheck /v:
Windows Update immediately wants to re-install the hotfix, which fixes the problem.
I'm integrating with nLite and the following addons:
Maybe it's just an ordering problem? I've been using this same order for the last 6 months or so, but maybe it just didn't show up as a problem before.
Code: Select all
KB946648: This hotfix should be reinstalled.
The following files are incorrect for this hotfix:
C:\PROGRAM FILES\MESSENGER\MSGSC.DLL
I'm integrating with nLite and the following addons:
- ryanvm updatepacksp3 1.0.0 (fixup)
DirectX 9.0c 0.5.1
OnePiece IE7 WinXPSP3 Addon v2.3.0
RVM Addons WGAN 1.7.18.7b
RVM Addons 1.9.0
Kel's CPLBonus 8.4
Kel's Uber Addon v13.2
Maybe it's just an ordering problem? I've been using this same order for the last 6 months or so, but maybe it just didn't show up as a problem before.
Use the Integrator on the Update Pack. That file is located in MMSSetup.cab, which nLite may not be able to update. The Integrator can.
EDIT 1: I can confirm this is an issue with nLite 1.4.8 and the Update Pack in my own testing. The following code may serve as a workaround in entries.ini, but is untested.
EDIT 2: Workaround confirmed to be working for nLite 1.4.8. No adverse effect on Integrator function. 
EDIT 3: nLite 1.4.9 corrects the underlying issue. This workaround is no longer needed.
EDIT 1: I can confirm this is an issue with nLite 1.4.8 and the Update Pack in my own testing. The following code may serve as a workaround in entries.ini, but is untested.
Code: Select all
[UpdateCabs]
I386\mmssetup.cab, UpdateMMS
[UpdateMMS]
msgsc.dll

EDIT 3: nLite 1.4.9 corrects the underlying issue. This workaround is no longer needed.
Last edited by 5eraph on Mon Sep 01, 2008 12:04 am, edited 2 times in total.
Yeah, that's pretty bad. *sigh*code65536 wrote:Unfortunately, I think I may have found something that does warrant a re-spin...RyanVM wrote:None of the nits people have brought up warrant a re-release.
1.0.0a coming right up

Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Looks like Iran is no longer in need of changes. Updated locally.RyanVM wrote:I'll check it out, thanks for noticing.yumeyao wrote:kb951072v2 not only has a newer version of tzchange.exe but also changes a little in tzchange.exe commands. check the hotfix installer.
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
OK, here's a script that can be run on existing installs to fix the Windows Installer 4.5 issue.Download HERE.
I'll put up a 1.0.0a to fix this issue for new installs, but there's certainly no point in reformatting over this when a simple script can fix it.
Code: Select all
@echo off
TITLE RyanVM Windows Installer 4.5 Fixup Script
SET MUI=%systemroot%\system32\mui
IF NOT EXIST %MUI%\0409 (mkdir %MUI%\0409)
MOVE %MUI%\0009\msimsg.dll.mui %MUI%\0409\msimsg.dll.mui
ECHO Windows Installer 4.5 should be fixed now. Sorry for the hassle!
PAUSE
I'll put up a 1.0.0a to fix this issue for new installs, but there's certainly no point in reformatting over this when a simple script can fix it.
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
1.0.0a is now available. Sorry for the hassle.
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
-
- Posts: 5
- Joined: Wed Feb 27, 2008 10:45 pm
Thanks 5eraph, that fixed it!5eraph wrote:Use the Integrator on the Update Pack. The following code may serve as a workaround in entries.ini, but is untested.
Code: Select all
[UpdateCabs] I386\mmssetup.cab, UpdateMMS [UpdateMMS] msgsc.dll
And thanks Ryan for the quick turn-around on 1.0.0a!
-
- Posts: 5
- Joined: Wed Feb 27, 2008 10:45 pm
Ryan, I noticed that 5eraph's little nLite hack didnt' make it into 1.0.0a. Do you plan to add it to next month's version? I know nLite isn't officially supported, so I understand if you don't want to clutter your files 
Is this something I should take up with nuhi to get nLite to handle properly?
Thanks again!

Is this something I should take up with nuhi to get nLite to handle properly?
Thanks again!
-
- Posts: 506
- Joined: Sun Feb 26, 2006 4:13 am
Worked for me at release, TechnoHunter. I'm currently seeding with a share ratio of 3.6:1 with several peers.
That's something you may want to take up with nuhi, WolverineFan. Ryan plans to remove the workaround for the Integrator at some point as well. I'm glad my fix helps.
That's something you may want to take up with nuhi, WolverineFan. Ryan plans to remove the workaround for the Integrator at some point as well. I'm glad my fix helps.

Last edited by 5eraph on Thu Aug 28, 2008 12:02 am, edited 1 time in total.
-
- Posts: 506
- Joined: Sun Feb 26, 2006 4:13 am
You could try enabling DHT. Unfortunately, my Azureus client's implementation of DHT is not compatible with µTorrent's. But maybe other µTorrent clients currently seeding or leeching can connect to you. µTorrent seems to be very popular from what I see in my peerlist.
i've done that.fortunato wrote: But only thing i want to know is can I also integrate RVMAddonsWMP10_3.1a over ?
session 1: integrator 1.53
- ryan post SP3 1.0
- RVMAddonsWMP10_3.1a
- 5er_MSSignedThemes_Addon_v3.0_x86
session 2: nlite
- WindowsXP-KB941569-x86-ENU.EXE
- WindowsMedia10-KB936782-x86-ENU.exe
no errors
Not planning on adding that workaround. I'm sure nuhi will fix nLite when he feels like it.WolverineFan wrote:Ryan, I noticed that 5eraph's little nLite hack didnt' make it into 1.0.0a. Do you plan to add it to next month's version? I know nLite isn't officially supported, so I understand if you don't want to clutter your files
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
It's the same "trick" that use Xable in his update pack. In his forum, he say that is more a "missing feature" of nLite, that doesn't yet support the [mmssetupcab_move] section of entries.ini, according to nuhi.RyanVM wrote:Not planning on adding that workaround. I'm sure nuhi will fix nLite when he feels like it.
Correct me if I'm doing something wrong here, but I'm trying start a fresh install from scratch. I have tried to do the following:
1) Copy all files/contents from an existing Windows XP SP1 CD to my hard drive.
2) Slipstream Service Pack 2 into the folder containing all files and contents.
3) Update all files with Ryan's Post SP2 pack (April of 2008).
4) Slipstream Service Pack 3 into the folder containing all files and contents.
5) Update all files with Ryan's Post SP3 pack and any other additional addons.
When I go to burn the CD, everything appears to be fine - although I have encountered a few errors. Either the CD does not boot, OR it tells me that there's an error in the .txt file (Something about a ".sif" file). Can anyone advise on what I'm doing wrong here? Thanking you all in advance.
1) Copy all files/contents from an existing Windows XP SP1 CD to my hard drive.
2) Slipstream Service Pack 2 into the folder containing all files and contents.
3) Update all files with Ryan's Post SP2 pack (April of 2008).
4) Slipstream Service Pack 3 into the folder containing all files and contents.
5) Update all files with Ryan's Post SP3 pack and any other additional addons.
When I go to burn the CD, everything appears to be fine - although I have encountered a few errors. Either the CD does not boot, OR it tells me that there's an error in the .txt file (Something about a ".sif" file). Can anyone advise on what I'm doing wrong here? Thanking you all in advance.
- laddanator
- Posts: 131
- Joined: Thu Jan 17, 2008 9:26 pm
- Location: virginia
Slipstream Process
Hello first off you dont want to slipstream sp2 then Ryans Pack then slipstream sp3 then Ryans sp3 pack.First just slipstream sp3 to your source(skip sp2 steps)then add Ryans sp3 update pack along with any other addons you may want to use,so order:(Everyones order is diffrent this is the basic)Correct me if I'm doing something wrong here, but I'm trying start a fresh install from scratch. I have tried to do the following:
1) Copy all files/contents from an existing Windows XP SP1 CD to my hard drive.
2) Slipstream Service Pack 2 into the folder containing all files and contents.
3) Update all files with Ryan's Post SP2 pack (April of 2008).
4) Slipstream Service Pack 3 into the folder containing all files and contents.
5) Update all files with Ryan's Post SP3 pack and any other additional addons.
When I go to burn the CD, everything appears to be fine - although I have encountered a few errors. Either the CD does not boot, OR it tells me that there's an error in the .txt file (Something about a ".sif" file). Can anyone advise on what I'm doing wrong here? Thanking you all in advance.
SKIP SP2 STEPS
1.XP SP1 SOURCE
2.SLIPSTREAM SP3
3.ADD RYAN'S SP3 PACK 1.0.0A(ALONG WITH ANY OTHER ADDONS YOU MAY WANT)
"I'LL BE BACK"
Beautiful! Thank you so much, guys!
The reason why I was slipstreaming SP2 and Ryan's Post SP2 update pack into my SP1 source disk is because I was under the impression that I would be missing out on any critical updates found in Ryan's Post SP3 update pack. I'll presume that everything till present can be found in Ryan's Post SP3 pack. Thank you once again, much appreciated!
The reason why I was slipstreaming SP2 and Ryan's Post SP2 update pack into my SP1 source disk is because I was under the impression that I would be missing out on any critical updates found in Ryan's Post SP3 update pack. I'll presume that everything till present can be found in Ryan's Post SP3 pack. Thank you once again, much appreciated!
WhoWeAre wrote:Beautiful! Thank you so much, guys!
The reason why I was slipstreaming SP2 and Ryan's Post SP2 update pack into my SP1 source disk is because I was under the impression that I would be missing out on any critical updates found in Ryan's Post SP3 update pack. I'll presume that everything till present can be found in Ryan's Post SP3 pack. Thank you once again, much appreciated!
think of sp3 as having sp2+ some extra stuff
Now that I can run Firefox using my QuickLaunch during installation, I don't want any black cmd window during Windows setup. I don't want a black cmd window to remove Windows Update link neither. So here is what I've done modified in your inf RyanVM, if you're interested :
As pointed yumeyao, there's also two blacks cmd window launched by tsoc.inf, which can be fixed by adding these lines in ExtraFileEdits section of entries.ini :

Just wanted to share in case you're interested.
Cheers,
Kal
Code: Select all
--- RVMUpPck.inf 2008-08-28 02:42:06.611125000 +0200
+++ RVMUpPck.inf 2008-08-29 13:14:05.968750000 +0200
@@ -24,7 +24,7 @@
[T13]
RunPreSetupCommands =T13.UpdateTimeZones.RunCommand:1
-AddReg =T13.KB932716.AddReg,T13.UpdateTimeZones.AddReg
+AddReg =T13.KB932716.AddReg,T13.MU.AddReg,T13.UpdateTimeZones.AddReg
RunPostSetupCommands =T13.KB922120.RunCommand:1,T13.KB931125.RunCommand:1,T13.MSXML.RunCommand:1,T13.ResetWMI.RunCommand:1
SmartReboot =N
@@ -2869,7 +2869,6 @@
[MU.AddReg]
HKCU,"Software\Policies\Microsoft\Internet Explorer","Windows Update Menu Text",0,"Microsoft Update"
-HKLM,"%RUNONCE%","MU-1",,"REG ADD ""HKLM\%RUNONCE%"" /v ""MU"" /t REG_SZ /d ""CMD /Q /C DEL \"""%16406%\Windows Update.lnk\""" /Q/F"""
[Flash.Register]
11,Macromed\Flash,Flash9f.ocx,1
@@ -2913,6 +2912,9 @@
HKCR,"Interface\{27354133-7F64-5B0F-8F00-5D77AFBE261E}\ProxyStubClsid32",,,"{27354130-7F64-5B0F-8F00-5D77AFBE261E}"
HKCR,"Interface\{27354133-7F64-5B0F-8F00-5D77AFBE261E}\TypeLib",,,"{2735412F-7F64-5B0F-8F00-5D77AFBE261E}"
+[T13.MU.AddReg]
+HKLM,"%RUNONCE%","MU",,"rundll32.exe advpack.dll,DelNodeRunDLL32 ""%16406%\Windows Update.lnk"""
+
[T13.UpdateTimeZones.AddReg]
HKLM,"%TZ%\Alaskan Standard Time\%DDST%","FirstEntry",0x10001,0x7d6
HKLM,"%TZ%\Alaskan Standard Time\%DDST%","LastEntry",0x10001,0x7d7
@@ -3045,14 +3047,14 @@
[T13.KB931125.RunCommand]
rootsupd.exe /Q
-CMD /Q /C DEL "%10%\rootsupd.exe" /Q/F
+rundll32.exe advpack.dll,DelNodeRunDLL32 %10%\rootsupd.exe
[T13.MSXML.RunCommand]
regsvr32 /s msxml4.dll
[T13.ResetWMI.RunCommand]
resetwmi.exe
-CMD /Q /C DEL "%10%\resetwmi.exe" /Q/F
+rundll32.exe advpack.dll,DelNodeRunDLL32 %10%\resetwmi.exe
[T13.UpdateTimeZones.RunCommand]
"tzchange.exe /F ""Alaskan Standard Time"" /S 3 0 2 2 0 0 0 /E 11 0 1 2 0 0 0 /G"
But, I found there was still one cmd flash box remaining, launched by pcheath.inf. This one can be fixed the same way :;This one fixes the issue that two cmd black boxes flash at T-13
tsoc.inf|;Modified to make T13 cmd windows not shown.<NEXT>HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","TerminalService-T13",,"rundll32.exe advpack.dll,LaunchINFSection tsoc.inf,T13"|; to register Salem/WMI Compoenents<NEXT>HKLM,"Software\Microsoft\Windows\CurrentVersion\RunOnce", "TS WMI tscfgwmi", 0x00000000, "regsvr32.exe /s tscfgwmi.dll"<NEXT>HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","TSClientAXDisabler",,"cmd.exe /C ""%systemroot%\Installer\TSClientMsiTrans\tscdsbl.bat"""<NEXT>; To uninstall OOB client hotfixes<NEXT>HKLM,"Software\Microsoft\Windows\CurrentVersion\RunOnce", "TSClientMSIUninstaller", 0x00000000, "cmd.exe /C ""pushd %systemroot%\Installer\TSClientMsiTrans && cscript %systemroot%\Installer\TSClientMsiTrans\tscinst.vbs && cscript %systemroot%\Installer\TSClientMsiTrans\tscuinst.vbs && popd"""|0
tsoc.inf|; to register Salem/WMI Compoenents<NEXT>HKLM,"Software\Microsoft\Windows\CurrentVersion\RunOnce", "TS WMI tscfgwmi", 0x00000000, "regsvr32.exe /s tscfgwmi.dll"<NEXT>HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","TSClientAXDisabler",,"cmd.exe /C ""%systemroot%\Installer\TSClientMsiTrans\tscdsbl.bat"""<NEXT>; To uninstall OOB client hotfixes<NEXT>HKLM,"Software\Microsoft\Windows\CurrentVersion\RunOnce", "TSClientMSIUninstaller", 0x00000000, "cmd.exe /C ""pushd %systemroot%\Installer\TSClientMsiTrans && cscript %systemroot%\Installer\TSClientMsiTrans\tscinst.vbs && cscript %systemroot%\Installer\TSClientMsiTrans\tscuinst.vbs && popd"""|;Modified to make T13 cmd windows not shown.<NEXT>HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","TerminalService-T13",,"rundll32.exe advpack.dll,LaunchINFSection tsoc.inf,T13"|1
tsoc.inf|[T13]<NEXT>RunPostSetupCommands =T13.TS.RunCommand:1<NEXT><NEXT>[T13.TS.RunCommand]<NEXT>; to register Salem/WMI Compoenents<NEXT>regsvr32.exe /s tscfgwmi.dll<NEXT>cmd.exe /Q /C "%systemroot%\Installer\TSClientMsiTrans\tscdsbl.bat"<NEXT>; To uninstall OOB client hotfixes<NEXT>cmd.exe /Q /C "pushd %systemroot%\Installer\TSClientMsiTrans && cscript %systemroot%\Installer\TSClientMsiTrans\tscinst.vbs && cscript %systemroot%\Installer\TSClientMsiTrans\tscuinst.vbs && popd"<NEXT><NEXT>[Strings]|[Strings]|0
tsoc.inf|[Strings]|[T13]<NEXT>RunPostSetupCommands =T13.TS.RunCommand:1<NEXT><NEXT>[T13.TS.RunCommand]<NEXT>; to register Salem/WMI Compoenents<NEXT>regsvr32.exe /s tscfgwmi.dll<NEXT>cmd.exe /Q /C "%systemroot%\Installer\TSClientMsiTrans\tscdsbl.bat"<NEXT>; To uninstall OOB client hotfixes<NEXT>cmd.exe /Q /C "pushd %systemroot%\Installer\TSClientMsiTrans && cscript %systemroot%\Installer\TSClientMsiTrans\tscinst.vbs && cscript %systemroot%\Installer\TSClientMsiTrans\tscuinst.vbs && popd"<NEXT><NEXT>[Strings]|1
That's it. No more cmd flash box window during setup and on first boot. I know it may look useless, but I like itpchealth.inf|HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","PCHealth-T13",,"rundll32.exe advpack.dll,LaunchINFSection pchealth.inf,T13"|HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","DelayedHscUpdate",,"Cmd /c copy %10%\pchealth\helpctr\binaries\hscsp_w3.cab %10%\pchealth\helpctr\batch\"|0
pchealth.inf|HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","DelayedHscUpdate",,"Cmd /c copy %10%\pchealth\helpctr\binaries\hscsp_w3.cab %10%\pchealth\helpctr\batch\"|HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","PCHealth-T13",,"rundll32.exe advpack.dll,LaunchINFSection pchealth.inf,T13"|1
pchealth.inf|[T13]<NEXT>RunPostSetupCommands =T13.PCHealth.RunCommand:1<NEXT><NEXT>[T13.PCHealth.RunCommand]<NEXT>Cmd /c copy %10%\pchealth\helpctr\binaries\hscsp_w3.cab %10%\pchealth\helpctr\batch\<NEXT><NEXT>[Strings]|[Strings]|0
pchealth.inf|[Strings]|[T13]<NEXT>RunPostSetupCommands =T13.PCHealth.RunCommand:1<NEXT><NEXT>[T13.PCHealth.RunCommand]<NEXT>Cmd /c copy %10%\pchealth\helpctr\binaries\hscsp_w3.cab %10%\pchealth\helpctr\batch\<NEXT><NEXT>[Strings]|1

Just wanted to share in case you're interested.
Cheers,
Kal
I just want to thank everyone for their help. The install went without a hitch yesterday. Although a few error messages came up pertaining to the IE7 update - but I think that was normal. Strangely enough, I downloaded an add-on called "IE7 Cosmetic" but it still didn't work - oh well. So far so good ... I just need to get everything back up and running. Thank you again!
Ah, this reminds me of something that I've been meaning to ask about but keep forgetting to. Ryan, I noticed that you're using these T13.RunCommand sections to run things, which is a relatively new thing that you are doing for your update packs. In my private pack, I still have rootsupd and resetwmi running from svcpack--only 1 line each in entries.ini (vs. 2), and there's no need to worry about deleting the files after execution. So is there a benefit to doing this via the INF instead of via svcpack? Likewise with registering msxml4 via T13.MSXML.RunCommand instead of RegisterDlls.Code: Select all
[T13.KB931125.RunCommand] rootsupd.exe /Q -CMD /Q /C DEL "%10%\rootsupd.exe" /Q/F +rundll32.exe advpack.dll,DelNodeRunDLL32 %10%\rootsupd.exe [T13.MSXML.RunCommand] regsvr32 /s msxml4.dll [T13.ResetWMI.RunCommand] resetwmi.exe -CMD /Q /C DEL "%10%\resetwmi.exe" /Q/F +rundll32.exe advpack.dll,DelNodeRunDLL32 %10%\resetwmi.exe
Just curious, and TIA...
code65536 : that's a great idea for svcpack method. Maybe RyanVM use this method to prevent any flashing window, I need to check.
About MSXML4, you're wondering why he's using this :
Instead of simply registering msxml4.dll with a RegisterDlls instruction ? I guess I know why, RyanVM will confirm. T13 section is launched with advpack.dll. When I use advpack.dll to launch a RegisterDlls section, it simply doesn't work, I don't know why. I need to use a RunPostSetupCommands/RunPreSetupCommands. By the way, RegisterDlls instruction works well when using setupapi instead of advpack.dll.
Cheers
About MSXML4, you're wondering why he's using this :
Code: Select all
[T13.MSXML.RunCommand]
regsvr32 /s msxml4.dll
Cheers

- RogueSpear
- Posts: 1155
- Joined: Tue Nov 23, 2004 9:50 pm
- Location: Buffalo, NY
I'll take a guess at it. First I think doing it his way makes sure that it happens prior to any installers set to run from svcpack.inf and second is that it lessens the chance of someone saying "hmm.. what's this doing in svcpack.inf? I think I'll delete it."code65536 wrote:So is there a benefit to doing this via the INF instead of via svcpack? Likewise with registering msxml4 via T13.MSXML.RunCommand instead of RegisterDlls.
Kind of a third reason... I remember when you were maintaining an update addon to the update pack last year and introduced resetwmi.exe and had it execute from svcpack. One question that lingered in my mind was when should it execute? Should I put it first? last? before installing .NET runtimes or after? This has kind of brought up that question for again because I notice some WMI related errors in the event log during install. I know they're related to my .NET runtimes installers and so I am curious if setting the execution of resetwmi.exe dead last would make a difference for good or ill.
Both rootsupd (and the updroots helper contained within) and resetwmi are compiled to use the GUI subsystem; they would never flash a window, no matter how they are run.kal wrote:to prevent any flashing window
I mean from a RegisterDlls in the main RVMUpdatePack section (e.g., MU.Register, Flash.Register), and not from T13 at all.Instead of simply registering msxml4.dll with a RegisterDlls instruction ?
Nothing depends on rootsupd and resetwmi, so the order in which they are run shouldn't matter.RogueSpear wrote:I'll take a guess at it. First I think doing it his way makes sure that it happens prior to any installers set to run from svcpack.inf
Hehe, good point.RogueSpear wrote:and second is that it lessens the chance of someone saying "hmm.. what's this doing in svcpack.inf? I think I'll delete it."
It made no difference when it was run. resetwmi only schedules the file operations. The actual "reset" happens during the reboot, regardless of when resetwmi was invoked.RogueSpear wrote:One question that lingered in my mind was when should it execute?
- RogueSpear
- Posts: 1155
- Joined: Tue Nov 23, 2004 9:50 pm
- Location: Buffalo, NY
The first three work fine for me. The last mirror's server is down at the moment.
If you're behind a software firewall, disable it temporarily to allow referrer information to pass to the server. If you are not then you may want to try the tracker link with a Bittorrent client.
If you're behind a software firewall, disable it temporarily to allow referrer information to pass to the server. If you are not then you may want to try the tracker link with a Bittorrent client.
-
- Posts: 101
- Joined: Wed Feb 16, 2005 4:05 pm
If you use an INF-based installer at T-13 then it's a known issue.
-
- Posts: 101
- Joined: Wed Feb 16, 2005 4:05 pm
Those using nLite should update to v1.4.9 which renders my workaround obsolete. I took the liberty of editing the first post to reflect this.
-
- Posts: 101
- Joined: Wed Feb 16, 2005 4:05 pm
Read nuhi's post in the nLite forum regarding how he compiled the latest version. 1.4.9 should no longer need the VC runtimes.
Read that whole thread for symptoms.
Read that whole thread for symptoms.
Hi all. I finished making a WinXp CD (more of a DVD really) using RVMi 1.5.3 to integrate SP3, RVM Post-SP3 addon, nearly all of Bashrat the Sneaky's drivers and several other addons. The result was excellent (maybe the best integration I ever did), but still there were one or two issues I would like to mention.
First of all, during the first phase of XP installation (I don't know its name, I call it "The Blue Screen Phase"), when all the mass storage drivers are loaded and it is time to choose the drive you want to install to, there is no more alert about having already a WinXp installation on that same drive. If you procced, it doesn't allow you to re-format the drive and it begins to copy the files, creating a "windows.0" folder for the former installation instead of deleting it. To perform a format of the drive during this phase of the installation, you have to delete the partition and re-create it. I believe this to be a bug or something.
Secondly, during the next phase, it doesn't let you choose additional languages, thus if you are making a bilingual installation (like I do), you end up only with the english language. Of course, you can always add the desired language afterwards, inside XP, but nevertheless this is something it shouldn't be happening.
Thanks
First of all, during the first phase of XP installation (I don't know its name, I call it "The Blue Screen Phase"), when all the mass storage drivers are loaded and it is time to choose the drive you want to install to, there is no more alert about having already a WinXp installation on that same drive. If you procced, it doesn't allow you to re-format the drive and it begins to copy the files, creating a "windows.0" folder for the former installation instead of deleting it. To perform a format of the drive during this phase of the installation, you have to delete the partition and re-create it. I believe this to be a bug or something.
Secondly, during the next phase, it doesn't let you choose additional languages, thus if you are making a bilingual installation (like I do), you end up only with the english language. Of course, you can always add the desired language afterwards, inside XP, but nevertheless this is something it shouldn't be happening.
Thanks
Those sound like issues with your install source, not the Update Pack. FWIW, I do #1 all the time without issue when testing my packs.
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357