5eraph's post-SP2 Update Pack v2017-06_2
The following lines in WinNT.sif should prevent those warnings. If you copied that file from a previously nLited source then they should already exist.
The DriverPacks used to employ a workaround that continuously changed a registry setting to achieve this. I don't know how they currently work around it, or how nLite does this other than the aforementioned code in WinNT.sif.
Code: Select all
[Unattended]
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore
Thanks for that. I seem to have run into another problem, though.
RVMi seems to optimize out the sp2.cab file. The image works, but if I then further modify it to add some drivers or apply a mod to allow installing onto USB removable disks, the install procedure then starts to notice that sp2.cab is missing but is still listed in dosnet.sif, and complains.
RVMi seems to optimize out the sp2.cab file. The image works, but if I then further modify it to add some drivers or apply a mod to allow installing onto USB removable disks, the install procedure then starts to notice that sp2.cab is missing but is still listed in dosnet.sif, and complains.
RVMi merges Driver.cab and SP2.cab when adding an update pack to save space. This includes editing DosNet.inf, DrvIndex.inf and TxtSetup.sif to remove references to SP2.cab. If you are manually editing those files to add your drivers then you should edit the modified files after using an update pack to avoid reintroducing references to SP2.cab.
-
- Posts: 48
- Joined: Tue Jun 10, 2008 11:05 am
- Location: Atlanta GA USA
Heartfelt Thanks!
Your hard work is very much appreciated, here and around the globe.
Thanks for your kind wishes, from a new friend in Atlanta, GA.
I'll be lurking about and putting in my four cents if I think I can help.
Thank you again!
MARK STRELECKI
The Computer Man in Atlanta, GA.
Thanks for your kind wishes, from a new friend in Atlanta, GA.
I'll be lurking about and putting in my four cents if I think I can help.
Thank you again!
MARK STRELECKI
The Computer Man in Atlanta, GA.
Microsoft released KB979302 Wednesday which updates MSI.dll and MSIHnd.dll. While this update fixes a long standing problem, it still fails when dealing with certain installers. It will not be included in a future update pack of mine.
However, should anybody decide to slipstream it with nLite I have updated the KB967756_Rollback installer to remove it if necessary.
However, should anybody decide to slipstream it with nLite I have updated the KB967756_Rollback installer to remove it if necessary.
-
- Posts: 1
- Joined: Sat Feb 20, 2010 7:41 am
Hi,
I just wanted to post to thank you for building and maintaining this update pack. XP x64 is a wonderful OS, and I am saddened to see it so neglected by MS. Your efforts have increased its longevity significantly. Now I can have an up-to-date version and integrate AHCI drivers using nlite, and continue to use it on my new machines.
Thank you.
I just wanted to post to thank you for building and maintaining this update pack. XP x64 is a wonderful OS, and I am saddened to see it so neglected by MS. Your efforts have increased its longevity significantly. Now I can have an up-to-date version and integrate AHCI drivers using nlite, and continue to use it on my new machines.
Thank you.
-
- Posts: 48
- Joined: Tue Jun 10, 2008 11:05 am
- Location: Atlanta GA USA
THANK YOU AGAIN!
5eraph, your awesomeness knows NO BOUNDS.
I am always interested in how these updates affect the "Winver date", the system build date as shown in the winver dialog.
Can you tell us if this latest update advances this value from your previous work-of-art update packs?
Please accept this follower's THANK YOU, once again, for helping me keep up to date with the very latest and greatest update pack!
Best wishes always from Atlanta, GA.
MARK STRELECKI
I am always interested in how these updates affect the "Winver date", the system build date as shown in the winver dialog.
Can you tell us if this latest update advances this value from your previous work-of-art update packs?
Please accept this follower's THANK YOU, once again, for helping me keep up to date with the very latest and greatest update pack!
Best wishes always from Atlanta, GA.
MARK STRELECKI
Thanks again for the compliments, Mark. 
WinVer.exe reports the kernel build date and branch stored in NTOSKrnl.exe. The last update to this file was released on February's Patch Tuesday, KB977165.
This information is also shown on the desktop for 32-bit XP when the following registry entry is set. On 64-bit XP/2003 the painted desktop information only displays the currently installed service pack level and OS build.
Screenshots:

WinVer.exe reports the kernel build date and branch stored in NTOSKrnl.exe. The last update to this file was released on February's Patch Tuesday, KB977165.
This information is also shown on the desktop for 32-bit XP when the following registry entry is set. On 64-bit XP/2003 the painted desktop information only displays the currently installed service pack level and OS build.
Code: Select all
HKCU,"Control Panel\Desktop","PaintDesktopVersion",0x10001,1
Last edited by 5eraph on Thu Mar 11, 2010 5:37 am, edited 1 time in total.
-
- Posts: 48
- Joined: Tue Jun 10, 2008 11:05 am
- Location: Atlanta GA USA
That's what I'm talkin' about.....
PRECISELY what I needed to know, with a screen capture to make it even easier to digest.
You rock, man. Positively, absolutely rock. Your parents did a really good thing. <grin>
Thank you!
MARK STRELECKI
Atlanta, GA.
You rock, man. Positively, absolutely rock. Your parents did a really good thing. <grin>
Thank you!
MARK STRELECKI
Atlanta, GA.
Thank you for your feedback, maur0. It is true that Windows 2003 x64 shares its codebase with Windows XP x64, but several differences still exist between the two operating systems. In regard to the updates you mention:
- KB926122 - The files in this package (NTDSA.dll, wNTDSA.dll) do not exist in TxtSetup.sif on Windows XP x64 sources and are not installed. This update is specific to Windows 2003.
The files w03a2409.dll and ww03a2409.dll are resource files that are common to many updates and do not count in these instances. No update exists that solely updates these files. If they need updating, they will be included in another update that requires the updated resources contained therein. Other resource files for which no update specifically exists are w03a3409.dll, ww03a3409.dll, xpsp3res.dll and xpsp4res.dll. - KB948496 - This update has been considered previously. It seems to apply to server hardware. The hotfix contains no files to install, only the registry entries described in Method 3 of the KB article.
- KB971032 - The files necessary for Windows XP x64 are included in the update pack. Additional files for Windows 2003 x64 are not included, but require updating on that operating system: mqads.dll, mqdssrv.dll and mqdssvc.exe.
- TranceEnergy
- Posts: 98
- Joined: Wed Sep 17, 2008 9:16 pm
Hi guys! Long time no see i guess 
Question: How can i add QWORD values to registry in x64 xp using reg command(from batch file)? (reg add /?)
I'm sorry for bit off topic, but i dont know where to ask any longer. I've run into a single place in registry which has QWORD registry values (this is xp 64bit after all). I don't desperately need it, but it would be the icing on the cake..
Once i'm done i'm hoping to have a universal setup with tweak files the x64 variants of windows.
Thanks!

Question: How can i add QWORD values to registry in x64 xp using reg command(from batch file)? (reg add /?)
I'm sorry for bit off topic, but i dont know where to ask any longer. I've run into a single place in registry which has QWORD registry values (this is xp 64bit after all). I don't desperately need it, but it would be the icing on the cake..
Once i'm done i'm hoping to have a universal setup with tweak files the x64 variants of windows.
Thanks!
I can't find any reference to the QWORD datatype anywhere except in Microsoft's PowerShell documentation. However, since a QWORD (quadruple word) is twice the length of a DWORD (double word), and since a DWORD is nothing more than a bounded binary value, you could try entering it as a BINARY, which has no bounds.
That's just a wild guess, though.
Edit:
I just found KB256986 which basically says what I mentioned above.
That's just a wild guess, though.

Edit:
I just found KB256986 which basically says what I mentioned above.
The command would be:Microsoft wrote:Data represented by a number that is a 64-bit integer. This data is displayed in Registry Editor as a Binary Value and was introduced in Windows 2000.
Code: Select all
Reg.exe ADD %KEY% /V %VALUE% /T REG_BINARY /D 0123456789abcdef /F
- TranceEnergy
- Posts: 98
- Joined: Wed Sep 17, 2008 9:16 pm
-
- Posts: 7
- Joined: Tue Apr 06, 2010 6:07 am
I don't understand how people are able to use this update i.e. the windows installer service is always corrupted, there are other bugs too. But the main one is the windows installer. Half of the programs won't install after installing windows and microsoft updates do not work either etc 
I retested this issue about 12 times...same result.

I retested this issue about 12 times...same result.
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
-
- Posts: 7
- Joined: Tue Apr 06, 2010 6:07 am
I've always used the RVM integrator 1.6 with an original XP pro x64 SP2 cd. I did this on a clean workstation running Win XP pro SP3 (I tried this on x64 system but this made no difference). After the update pack is integrated, I make the ISO and burn it (verify everything too) i.e. no other update packs were used.
Then install on a hard disk from scratch (but same errors occur on virtual machines too)
Then install on a hard disk from scratch (but same errors occur on virtual machines too)
-
- Posts: 7
- Joined: Tue Apr 06, 2010 6:07 am
The most recent attempt included the IE8 update too. The Windows cd is from work and I can use it. Here is the log 
2010-03-05_17.07.48
Log Startup @ 17:07:48 local time, on March 05, 2010.
Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.6
"D:\nLite RELATED\RVM_Integrator_1.6.exe"
17:10:23 - English - Windows XP Professional x64 - Corporate SP2 Found
17:10:30 - English - Windows XP Professional x64 - Corporate SP2 Found
17:13:45 -
17:13:45 - Source Drive = F:
17:13:45 - Destination Drive = D:\WIN XP PRO X64 2010 UPDATED ORIGINAL
17:13:45 - Destination Size = 26.02 GB
17:13:45 - Working Directory = D:\WIN XP PRO X64 2010 UPDATED ORIGINAL\AMD64
17:13:45 - Temp Directory = D:\WIN XP PRO X64 2010 UPDATED ORIGINAL\AMD64\rvmtemp
17:13:45 -
17:13:45 - Starting Integration
17:13:45 -
17:13:45 - Copying Files To The Destination Directory.
17:13:45 - Copying Working Directory...
17:17:21 - 5202 Files Copied in 215 Seconds
17:17:21 - Copying \I386\ Directory...
17:18:43 - 2578 Files Copied in 81 Seconds
17:18:43 -
17:18:43 - Checking Destination For OS Type.
17:18:43 - English - Windows XP Professional x64 - Corporate SP2 Found
17:18:43 -
17:18:43 - Extracting 5er_UpdatePack_XPx64SP2_2010-02_3.7z
17:19:24 - MD5 Hash = d04c9ecfd707899c851f63a095100db9
17:19:24 - Extracting 5er_IE8_Addon_2010-02_1_x64.7z
17:19:35 - MD5 Hash = ec1dc9522b23333b500a0d7b7486d63b
17:19:35 - Clearing any Read Only Attributes.
17:20:20 -
17:20:20 - Gathering temp files
17:20:20 - Expanding driver32.cab
17:20:20 - CabLite.dll::CabExtract reports completion

2010-03-05_17.07.48
Log Startup @ 17:07:48 local time, on March 05, 2010.
Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.6
"D:\nLite RELATED\RVM_Integrator_1.6.exe"
17:10:23 - English - Windows XP Professional x64 - Corporate SP2 Found
17:10:30 - English - Windows XP Professional x64 - Corporate SP2 Found
17:13:45 -
17:13:45 - Source Drive = F:
17:13:45 - Destination Drive = D:\WIN XP PRO X64 2010 UPDATED ORIGINAL
17:13:45 - Destination Size = 26.02 GB
17:13:45 - Working Directory = D:\WIN XP PRO X64 2010 UPDATED ORIGINAL\AMD64
17:13:45 - Temp Directory = D:\WIN XP PRO X64 2010 UPDATED ORIGINAL\AMD64\rvmtemp
17:13:45 -
17:13:45 - Starting Integration
17:13:45 -
17:13:45 - Copying Files To The Destination Directory.
17:13:45 - Copying Working Directory...
17:17:21 - 5202 Files Copied in 215 Seconds
17:17:21 - Copying \I386\ Directory...
17:18:43 - 2578 Files Copied in 81 Seconds
17:18:43 -
17:18:43 - Checking Destination For OS Type.
17:18:43 - English - Windows XP Professional x64 - Corporate SP2 Found
17:18:43 -
17:18:43 - Extracting 5er_UpdatePack_XPx64SP2_2010-02_3.7z
17:19:24 - MD5 Hash = d04c9ecfd707899c851f63a095100db9
17:19:24 - Extracting 5er_IE8_Addon_2010-02_1_x64.7z
17:19:35 - MD5 Hash = ec1dc9522b23333b500a0d7b7486d63b
17:19:35 - Clearing any Read Only Attributes.
17:20:20 -
17:20:20 - Gathering temp files
17:20:20 - Expanding driver32.cab
17:20:20 - CabLite.dll::CabExtract reports completion
Code: Select all
17:20:20 - Expanding driver.cab
17:21:31 - CabLite.dll::CabExtractAsync reports completion [code=00001060]
17:21:31 - Expanding SP2.cab
17:21:35 - CabLite.dll::CabExtractAsync reports completion [code=000000A1]
17:21:42 - Copying/Moving files to driver.cab
17:21:44 - Compressing Files
17:23:08 - Processing new .CAT files found in SVCPACK
17:23:29 -
17:23:29 - Shifting Stuff Around
17:23:29 - Shifting x64_I386 Specific Files
17:23:44 - 392 Files Moved in 15 Seconds
17:27:16 - 843 Files Moved in 212 Seconds
17:27:16 - Analyzing 2 Entry Files
17:27:16 - Processing 5eraph's Update Pack v2010-02_3 Build Date: 2010/02/24
17:27:16 - Gathering Sysoc Entries
17:27:16 - Gathering Dosnet.inf [Files] Entries
17:27:17 - Gathering txtsetup.sif [SourceDisksFiles] and [WinntDirectories] Entries
17:27:17 - Gathering obsolete_files Entries
17:27:17 - Gathering ExtraFileEdits Entries
17:27:18 - Processing 5eraph's IE8 Addon v2010-02_1 Build Date: 2010/02/24
17:27:18 - Gathering Sysoc Entries
17:27:18 - Gathering Dosnet.inf [Files] Entries
17:27:18 - Gathering txtsetup.sif [SourceDisksFiles] and [WinntDirectories] Entries
17:27:18 - Gathering ExtraFileEdits Entries
17:27:19 -
17:27:19 - Preparing System Files...
17:27:19 - sysoc.inf
17:27:19 - svcpack.inf
17:27:19 - dosnet.inf
17:27:19 - txtsetup.sif
17:27:21 -
17:27:21 - Processing obsolete_files
17:27:21 - Processing ExtraFileEdits
17:27:24 - Processing Sysoc.inf
17:27:24 - Adding Components
17:27:24 - Processing svcpack.inf
17:27:24 - Processing dosnet.inf
17:27:24 - Modifying any SP?.cab areas in dosnet.inf
17:27:24 - Editing [Files]
17:27:35 - Processing txtsetup.sif
17:27:35 - Editing [WinntDirectories]
17:27:39 - Editing [SourceDisksFiles]
17:27:40 - Modifying any SP?.cab areas in txtsetup.sif
17:27:42 -
17:27:43 - Compressing Files ASMS...
17:27:50 -
17:27:50 - Processing [EditFile]
17:27:55 - Entire .ini Processing Completed in 39 Seconds
17:27:55 -
17:27:55 - Compressing and Moving Edited Files
17:27:55 -
17:27:55 - No mmssetup.cab Found. Skipping Messenger.
17:27:55 -
17:27:56 - Copying Files Found In 5eraph's Update Pack
17:27:56 - Moving Files Found In 5eraph's Update Pack
17:27:56 - Deleting Files Found In 5eraph's Update Pack
17:27:56 -
17:27:56 - Rebuilding driver.cab
17:31:40 - Compressed 4207 files into driver.cab [code=106F0001]
17:31:40 -
17:31:40 - Rebuilding drvindex.inf
17:31:40 - Rebuilding drvindex.inf Complete.
17:31:40 -
17:31:40 - Moving Files
17:31:40 - Replacing driver.cab
17:31:54 -
17:31:54 - Rebuilding driver32.cab
17:31:55 - Compressed 15 files into driver32.cab [code=000F0001]
17:31:55 -
17:31:55 - Cleaning Up.
17:31:57 - Integration Completed.
17:31:57 - Total Integration Time = 793 Seconds
17:31:57 - ==================================================================================
-
- Posts: 7
- Joined: Tue Apr 06, 2010 6:07 am
I just wanted to add that if 5eraph is not able to identify my problem for whatever reason I would be happy to pay/donate to obtain a CD with the update and the IE8 addon (without tweaks). Without a key of course. I don't use this at home but at work xp x64 is installed on about 20 servers and an updated disk would save me a lot of time in trouble shooting.
- TranceEnergy
- Posts: 98
- Joined: Wed Sep 17, 2008 9:16 pm
-
- Posts: 7
- Joined: Tue Apr 06, 2010 6:07 am
-
- Posts: 48
- Joined: Tue Jun 10, 2008 11:05 am
- Location: Atlanta GA USA
Many times when I have experienced corruption in the creation of customized XP setup media, it was due to one or more of these reasons:
Anti-virus or other security software running
Not starting with a clean (non-nLited/RVM'ed) source
Corrupted update file/bad download
System infection/corruption (have you scanned with 2 or more utilities?)
Rights-related issue (always run as Admin to create setup media)
System/domain policy interfering with setup media generation
I would setup a second PC and try the process there. Fact is, there are WAY too many vectors of infection and many modern malware are stealthy and silent to remain below your radar.
Are you CERTAIN your system is free of all infection, and HOW do you know this? I have special bootable DVD and USB flashdrive media that I can use to check any system with a verifiably clean boot sequence.
System Restore has also saved my bacon when cleansing progs did not work properly. It is amazing how simple and powerful turning back the clock can be for the reliable operation of XP.
I also use XP64Pro and I really like it a LOT, and so far it has held me in good stead and remained clean and reliable, and builds working XP media whenever and however I need.
I use nLite, not RVMI, just for the record, but I will be trying Ryan's program at some point to compare it with my years of using Nuhi's app.
P S - which version of RVMI are we using? Have you tried a different version?
Just trying to help. I know what tech problems can do to your head, and I'm always grateful when someone steps out to give me some help. Let's see if some fresh eyes can bring a new perspective on your issues.
Best wishes from north of Atlanta, GA.
MARK STRELECKI
Anti-virus or other security software running
Not starting with a clean (non-nLited/RVM'ed) source
Corrupted update file/bad download
System infection/corruption (have you scanned with 2 or more utilities?)
Rights-related issue (always run as Admin to create setup media)
System/domain policy interfering with setup media generation
I would setup a second PC and try the process there. Fact is, there are WAY too many vectors of infection and many modern malware are stealthy and silent to remain below your radar.
Are you CERTAIN your system is free of all infection, and HOW do you know this? I have special bootable DVD and USB flashdrive media that I can use to check any system with a verifiably clean boot sequence.
System Restore has also saved my bacon when cleansing progs did not work properly. It is amazing how simple and powerful turning back the clock can be for the reliable operation of XP.
I also use XP64Pro and I really like it a LOT, and so far it has held me in good stead and remained clean and reliable, and builds working XP media whenever and however I need.
I use nLite, not RVMI, just for the record, but I will be trying Ryan's program at some point to compare it with my years of using Nuhi's app.
P S - which version of RVMI are we using? Have you tried a different version?
Just trying to help. I know what tech problems can do to your head, and I'm always grateful when someone steps out to give me some help. Let's see if some fresh eyes can bring a new perspective on your issues.
Best wishes from north of Atlanta, GA.
MARK STRELECKI
-
- Posts: 7
- Joined: Tue Apr 06, 2010 6:07 am
AWESOME!!!!!!! IT WORKS NOW (will be testing it completely tomorrow at work). 5eraph's method was the key. What's annoying is that one could've logically guessed that it was related to that because the ISO's were 743mb, suggesting that the files were not actually integrated i.e. replacing the original ones. But I couldn't figure that out
Perhaps this is also related somehow to the unattended setup....which (with nLite) does work but then not really because it always throws unassigned driver errors...EVEN though all the settings are correct (WinNT etc set to ignore...) and no actual drivers or any other modifications are in place...
Thank you very much everyone, REALLY appreciate the input!!!!!!!

Perhaps this is also related somehow to the unattended setup....which (with nLite) does work but then not really because it always throws unassigned driver errors...EVEN though all the settings are correct (WinNT etc set to ignore...) and no actual drivers or any other modifications are in place...
Thank you very much everyone, REALLY appreciate the input!!!!!!!
-
- Posts: 48
- Joined: Tue Jun 10, 2008 11:05 am
- Location: Atlanta GA USA
Latest Update Pack Working GREAT
Just a quick THANK YOU and to say that my Core2 Duo laptop is singing your praises. I had no idea they could DO that.... <grin>
I see the WINVER date of Feb 16, 2010, making this THE latest version of XP you can get anywhere. I LOVE the Clean Install, 'cuz all updates and patches are rolled together and installed all at once so I can really hit the ground running.
I have upgraded this Acer AS6930 with a 120GB Corsair SSD and your updates make it fly (sing?) like a bird. Muchos Gracias, Amigo!
MARK STRELECKI
Atlanta, GA.
I see the WINVER date of Feb 16, 2010, making this THE latest version of XP you can get anywhere. I LOVE the Clean Install, 'cuz all updates and patches are rolled together and installed all at once so I can really hit the ground running.
I have upgraded this Acer AS6930 with a 120GB Corsair SSD and your updates make it fly (sing?) like a bird. Muchos Gracias, Amigo!
MARK STRELECKI
Atlanta, GA.
Why must WindowsServer2003-KB942288-v4-x64 hotfix be installed after installing a version of Windows XP x64 with your update packs? Without the hotfix, the Microsoft Installation Files are corrupted. I cannot install anything until I install this hotfix, and I'm wondering why this is so.
I've installed it twice now, with the same issue.
I've installed it twice now, with the same issue.
Your problem sounds a lot like michaelvqwerty's, but I need more information to be sure. Please post your RVMi log file or "Last Session.ini" so I can have a look.
Here it is.
Code: Select all
2010-05-03_18.05.14
Log Startup @ 18:05:14 local time, on May 03, 2010.
Running OS: WIN_VISTA Service Pack 2 X64
RVMIntegrator v1.6
"C:\Download\RVM_Integrator_1.6\RVM_Integrator_1.6.exe"
18:05:27 - English - Windows XP Professional x64 - SP2 Found
18:10:38 -
18:10:38 - Source Drive = D:
18:10:38 - Destination Drive = C:\XP
18:10:38 - Destination Size = 11.07 GB
18:10:38 - Working Directory = C:\XP\AMD64
18:10:38 - Temp Directory = C:\XP\AMD64\rvmtemp
18:10:38 -
18:10:39 - Starting Integration
18:10:39 -
18:10:39 - Copying Files To The Destination Directory.
18:10:39 - Copying Working Directory...
18:18:06 - 5202 Files Copied in 447 Seconds
18:18:06 - Copying \I386\ Directory...
18:21:36 - 2578 Files Copied in 209 Seconds
18:21:36 -
18:21:36 - Checking Destination For OS Type.
18:21:36 - English - Windows XP Professional x64 - SP2 Found
18:21:36 -
18:21:36 - Extracting 5er_UpdatePack_XPx64SP2_2010-04_2.7z
18:22:28 - MD5 Hash = bb01ef808ce9219cb87cc864dd6f112d
18:22:28 - Extracting 5er_MSSignedThemes_Addon_v6.1.1_x64.7z
18:22:33 - MD5 Hash = 7875801a85b3ea9ed21a628b676b8166
18:22:33 - Clearing any Read Only Attributes.
18:22:45 -
18:22:45 - Gathering temp files
18:22:46 - Expanding driver32.cab
18:22:48 - CabLite.dll::CabExtract reports completion [code=0000000F]
18:22:48 - Expanding driver.cab
18:23:42 - CabLite.dll::CabExtractAsync reports completion [code=00000FCE]
18:23:44 - Expanding SP2.cab
18:23:55 - CabLite.dll::CabExtractAsync reports completion [code=000000A1]
18:23:59 - Copying/Moving files to driver.cab
18:24:03 - Compressing Files
18:25:08 - Processing new .CAT files found in SVCPACK
18:25:36 -
18:25:36 - Shifting Stuff Around
18:25:37 - Shifting x64_I386 Specific Files
18:25:48 - 316 Files Moved in 10 Seconds
18:30:49 - 757 Files Moved in 300 Seconds
18:30:49 - Analyzing 2 Entry Files
18:30:49 - Processing 5eraph's Update Pack v2010-04_2 Build Date: 2010/04/27
18:30:49 - Gathering Sysoc Entries
18:30:49 - Gathering Dosnet.inf [Files] Entries
18:30:50 - Gathering txtsetup.sif [SourceDisksFiles] and [WinntDirectories] Entries
18:30:54 - Gathering obsolete_files Entries
18:30:54 - Gathering ExtraFileEdits Entries
18:30:55 - Processing MS Signed Themes Addon v6.1.1 Build Date: 2010/03/14
18:30:55 - Gathering Sysoc Entries
18:30:55 - Gathering Dosnet.inf [Files] Entries
18:30:55 - Gathering txtsetup.sif [SourceDisksFiles] and [WinntDirectories] Entries
18:30:55 -
18:30:55 - Preparing System Files...
18:30:55 - sysoc.inf
18:30:55 - svcpack.inf
18:30:55 - dosnet.inf
18:30:56 - txtsetup.sif
18:31:06 -
18:31:06 - Processing obsolete_files
18:31:07 - Processing ExtraFileEdits
18:31:09 - Processing Sysoc.inf
18:31:09 - Adding Components
18:31:09 - Processing svcpack.inf
18:31:09 - Processing dosnet.inf
18:31:09 - Modifying any SP?.cab areas in dosnet.inf
18:31:09 - Editing [Files]
18:31:21 - Processing txtsetup.sif
18:31:21 - Editing [WinntDirectories]
18:31:28 - Editing [SourceDisksFiles]
18:31:30 - Modifying any SP?.cab areas in txtsetup.sif
18:31:36 -
18:31:36 - Compressing Files ASMS...
18:31:50 -
18:31:50 - Processing [EditFile]
18:31:55 - Entire .ini Processing Completed in 66 Seconds
18:31:55 -
18:31:55 - Compressing and Moving Edited Files
18:31:56 -
18:31:56 - No mmssetup.cab Found. Skipping Messenger.
18:31:56 -
18:31:56 - Copying Files Found In 5eraph's Update Pack
18:31:56 - Moving Files Found In 5eraph's Update Pack
18:31:56 - Deleting Files Found In 5eraph's Update Pack
18:31:57 -
18:31:57 - Rebuilding driver.cab
18:38:50 - Compressed 4207 files into driver.cab [code=106F0001]
18:38:50 -
18:38:50 - Rebuilding drvindex.inf
18:38:51 - Rebuilding drvindex.inf Complete.
18:38:51 -
18:38:51 - Moving Files
18:38:51 - Replacing driver.cab
18:38:57 -
18:38:57 - Rebuilding driver32.cab
18:38:59 - Compressed 15 files into driver32.cab [code=000F0001]
18:38:59 -
18:38:59 - Cleaning Up.
18:39:00 - Integration Completed.
18:39:00 - Total Integration Time = 1043 Seconds
18:39:00 - ==================================================================================
18:39:00 -
19:22:05 -
19:22:05 - Creating ISO
19:22:05 - Command Line = C:\Windows\system32\cmd.exe /c C:\Windows\System32\rvmisofs.exe -joliet-long -iso-level 2 -N -d -relaxed-filenames -duplicates-once -D -boot-load-seg 0x7C0 -boot-load-size 4 -o "C:\XP x64 April 2010.iso" -b rvmintegrator.img -hide rvmintegrator.img -hide boot.catalog -J -hide-joliet xpboot.img -hide-joliet boot.catalog -no-emul-boot -volid "RVMi" -sysid "Win32" "C:\XP"
19:22:05 - Using Internal mkisofs 2.01-bootcd.ru (i686-pc-mingw32)
19:27:58 - Total translation table size: 2048
19:27:58 - Total rockridge attributes bytes: 0
19:27:58 - Total directory bytes: 577888
19:27:58 - Path table size(bytes): 1370
19:27:58 - 364839 extents written (712 MB)
19:27:58 - ISO Complete
Log Shutdown @ 2010-05-03 19:29:38 local time.
It's the same problem...

The same solution applies.own3mall and [url=http://www.ryanvm.net/forum/viewtopic.php?p=103632#103632]michaelvqwerty[/url] wrote:Code: Select all
Source Drive = [optical drive]

5eraph wrote:Try copying the files from your source disc to a folder on your hard drive manually, including the files at the root of the disc. Then direct RVMi to use that folder as the source with no Destination Directory. It should then work.
Updated to 2010-05_2. Please read the Changelog for full details.
It is important for all to read the Notes section of the current release post, which is quoted below. In summary: If nLite throws errors with this update pack then try temporarily disabling your antivirus product. And MSI.dll has been updated; solutions are available if you experience MSI installation errors.
It is important for all to read the Notes section of the current release post, which is quoted below. In summary: If nLite throws errors with this update pack then try temporarily disabling your antivirus product. And MSI.dll has been updated; solutions are available if you experience MSI installation errors.
5eraph wrote:Notes:
- It has been reported that some antivirus products may interfere with nLite 1.4.9.1 when integrating this update pack and others. nLite may throw one or more errors, including:
If this occurs, please disable your antivirus product temporarily and try running nLite again on a fresh copy of your source.
- "H-The process cannot access the file '<SourceDirectory>\SVCPACK.INF' because it is being used by another process."
- "CabLib Extract ERROR while extracting files from cabinet archive: Failure writing to target file"
Thank you, Kurt_Aust, for initially reporting and solving this problem with nLite and this update pack.- An updated version of MSI.dll (KB983280) has been included. Although I have performed some limited testing with this update, previous updates newer than KB967756 were known to cause problems when installing certain software. To revert to KB967756, please use the updated rollback installer or addon.
- Please see a previous release's bump post regarding blocked updates.