[Addon] Updates for RVM Update Pack 2.1.11 (R13: 2007-09-06)
...what exactly's the problem there?
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
@jeckhack
you're lookin on the 'directx files' tab, the version is listed on the bottom of the 'system' tab. My version, for example, is 9.0c (4.09.0000.0904).
and even though it will probably say 9.0c, directx is updated every 2 months (usually) for the developers. It's not requried to install these updated dx9 files, but some games do require them.
i prefer to install the updated files. I'm weird that way.
you're lookin on the 'directx files' tab, the version is listed on the bottom of the 'system' tab. My version, for example, is 9.0c (4.09.0000.0904).
and even though it will probably say 9.0c, directx is updated every 2 months (usually) for the developers. It's not requried to install these updated dx9 files, but some games do require them.
i prefer to install the updated files. I'm weird that way.

Dok's Law: The simplicity of a solution is directly proportionate to its elusiveness.
thx joll 
Look. 4.09.0000.0904 = dx9c. if you go to http://en.wikipedia.org/wiki/Directx you can see in release history that 4.09.0000.0904 started in 2004 and there're bimonthly files updates which do not change that number.
--
Problem is in that i installed latest august direct x pack, then compared directx files versions with non-updated directx on other machine since xp sp2 released (
) and there're no changes. Why ?

Look. 4.09.0000.0904 = dx9c. if you go to http://en.wikipedia.org/wiki/Directx you can see in release history that 4.09.0000.0904 started in 2004 and there're bimonthly files updates which do not change that number.
--
Problem is in that i installed latest august direct x pack, then compared directx files versions with non-updated directx on other machine since xp sp2 released (

Russian Mafia 

-
- Posts: 288
- Joined: Mon Oct 02, 2006 6:32 am
- Location: Ottawa, Ontario, Canada
@RougeSpear,
Interesting your synopsis of NTKRNLMP.EXE is missing or corrupt......I have been getting this error intermittently, and very rarely, since I upgraded to E6850 C2D and Gigabyte GA n680SLI DQ6. I run two 150G raptors striped 64KB...now...and have never had this error before on any of my previous setups; ASUS A8N32SLI Deluxe and an AMD FX55 Clawhammer and so on; same HDD-before 150G I ran four 74G Raptors, etc.
The error occurs after post and as Windows is loading; of course the system crashes and a forced reset is required. That said, the system always boots normally to Windows-XP Pro, SP2-after the first and only reset. I usually see this error some time after a fresh install and then it either disappears or, at most, recurrs two or three times there after. There are no entries in any of the system logs, of course, and a thorough checkdisk reveals no bad sectors or MBR errors. I, therefore, concluded that the source of this concern for me is the BIOS; which Gigabyte has told me through there support, will be updated, basically, when there good and ready!. I can no longer run my tried and true Terabyte software with no worries since this Gigabyte contraption. I am going to upgrade again to an X38 motherboard-ASUS-in a couple of months and will report back.
.....as you say those kinds of errors are most likely hardware, all else being equal.....
Interesting your synopsis of NTKRNLMP.EXE is missing or corrupt......I have been getting this error intermittently, and very rarely, since I upgraded to E6850 C2D and Gigabyte GA n680SLI DQ6. I run two 150G raptors striped 64KB...now...and have never had this error before on any of my previous setups; ASUS A8N32SLI Deluxe and an AMD FX55 Clawhammer and so on; same HDD-before 150G I ran four 74G Raptors, etc.
The error occurs after post and as Windows is loading; of course the system crashes and a forced reset is required. That said, the system always boots normally to Windows-XP Pro, SP2-after the first and only reset. I usually see this error some time after a fresh install and then it either disappears or, at most, recurrs two or three times there after. There are no entries in any of the system logs, of course, and a thorough checkdisk reveals no bad sectors or MBR errors. I, therefore, concluded that the source of this concern for me is the BIOS; which Gigabyte has told me through there support, will be updated, basically, when there good and ready!. I can no longer run my tried and true Terabyte software with no worries since this Gigabyte contraption. I am going to upgrade again to an X38 motherboard-ASUS-in a couple of months and will report back.
.....as you say those kinds of errors are most likely hardware, all else being equal.....
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
- Mavericks choice
- Posts: 273
- Joined: Wed Nov 24, 2004 3:39 am
- Location: Downunder
- Zyx_Maiden
- Posts: 128
- Joined: Mon Mar 12, 2007 9:32 pm
- Location: Québec, Canada
-
- Posts: 53
- Joined: Fri Dec 22, 2006 1:41 pm
- Mavericks choice
- Posts: 273
- Joined: Wed Nov 24, 2004 3:39 am
- Location: Downunder
- RogueSpear
- Posts: 1155
- Joined: Tue Nov 23, 2004 9:50 pm
- Location: Buffalo, NY
WScript 5.7 Oddities
I've come across something a little strange when I integrate WScript 5.7 into my source. It took me quite a while to discover this because I don't do too many installs on units with a floppy drive enabled anymore.
My post setup scripts, which are all in VBscript, search for an .ini file in the root of all available drive letters. It seems that computers with an enabled floppy drive will always throw the following:

I've Googled it and haven't come across anything helpful. If I don't integrate WSH5.7 the error does not pop up, so it seems to be isolated to WSH5.7.
Here are some additional strange findings: usually when there is an error in the script itself you get a dialog with what the error is and the line number in the script. And the script is toast at that point. With this it does not seem to be throwing a WSH error at all. It seems OS level because if I hit "Continue" the script will carry along like nothing happened. Also this isn't confined to RunOnceEx - it will happen if execute one of these scripts by double clicking on it or via command line post RunOnceEx.
Considering the shoddy workmanship in the WScript 5.7 package by Microsoft as outlined by Code, I'm wondering if this is yet another bug. On the flip side, if this is going to be included in XP SP3, is it a part of some new security mechanism?
My post setup scripts, which are all in VBscript, search for an .ini file in the root of all available drive letters. It seems that computers with an enabled floppy drive will always throw the following:

I've Googled it and haven't come across anything helpful. If I don't integrate WSH5.7 the error does not pop up, so it seems to be isolated to WSH5.7.
Here are some additional strange findings: usually when there is an error in the script itself you get a dialog with what the error is and the line number in the script. And the script is toast at that point. With this it does not seem to be throwing a WSH error at all. It seems OS level because if I hit "Continue" the script will carry along like nothing happened. Also this isn't confined to RunOnceEx - it will happen if execute one of these scripts by double clicking on it or via command line post RunOnceEx.
Considering the shoddy workmanship in the WScript 5.7 package by Microsoft as outlined by Code, I'm wondering if this is yet another bug. On the flip side, if this is going to be included in XP SP3, is it a part of some new security mechanism?
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
Heres another way to make sure Windows Update link does not get added (tested works 100% of the time)
Added to the RVMUpPck.inf it edits syssetup.inf during windows setup.
Added to the RVMUpPck.inf it edits syssetup.inf during windows setup.
Code: Select all
[RVMUpdatePack]
UpdateInis = WU.DelShortcut
[WU.DelShortcut]
%17%\syssetup.inf,StartMenuCommon,%%windowsupdate%%=*
%17%\syssetup.inf,Strings,windowsupdate=*
Last edited by ricktendo64 on Tue Oct 09, 2007 12:04 am, edited 1 time in total.
- RogueSpear
- Posts: 1155
- Joined: Tue Nov 23, 2004 9:50 pm
- Location: Buffalo, NY
In my search for answers regarding this issue, I saw a lot of discussion about what you describe, except it's a different set gibberish in the dialog box. This is actually another reason that it seems like an OS level error as opposed to a WSH error. Whatever is throwing up the error seems to be the same component (not WSH). The error that you describe unfortunately seems to be so prevelant that it made my searching a bit difficult. But I can say for certain that with everything else being identical, WSH5.7 is the difference between error and no error.kof94 wrote:I've also seen this error but only on systems that have an internal card reader (SD, XD, CF etc) connected and I didn't integrate WSH5.7.
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
Fair enough, I gave up looking for a complete answer with my issue since so few PC's I come into contact with have card readers anyway.RogueSpear wrote:In my search for answers regarding this issue, I saw a lot of discussion about what you describe, except it's a different set gibberish in the dialog box. This is actually another reason that it seems like an OS level error as opposed to a WSH error. Whatever is throwing up the error seems to be the same component (not WSH). The error that you describe unfortunately seems to be so prevelant that it made my searching a bit difficult. But I can say for certain that with everything else being identical, WSH5.7 is the difference between error and no error.kof94 wrote:I've also seen this error but only on systems that have an internal card reader (SD, XD, CF etc) connected and I didn't integrate WSH5.7.
Sorry if this has convoluted your search RoughSpear, I couldn't exactly remember the error code (gibberish) just the error message.
Happy hunting.
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
Here are the Official October Updates:
Microsoft® Windows® Malicious Software Removal Tool (KB890830)
http://www.microsoft.com/downloads/deta ... b8eb148356
Security Update for Outlook Express for Windows XP (KB941202)
http://www.microsoft.com/downloads/deta ... layLang=en
Cumulative Security Update for Internet Explorer for Windows XP Service Pack 2 (KB939653)
http://www.microsoft.com/downloads/deta ... layLang=en
Security Update for Windows XP (KB933729)
http://www.microsoft.com/downloads/deta ... layLang=en
Windows Update Engine v7.0.6000.381
http://xable.net/board/index.php?showtopic=49
Cannot find this update at the original Microsoft Website.
And this Updates are for the Windows Components (Like FAX, IIS ...):
Security Update for Windows XP (KB926247)
http://www.microsoft.com/downloads/deta ... layLang=en
Security Update for Windows XP (KB939373)
http://www.microsoft.com/downloads/deta ... layLang=en
Security Update for Windows XP (KB917537)
http://www.microsoft.com/downloads/deta ... layLang=en
Microsoft® Windows® Malicious Software Removal Tool (KB890830)
http://www.microsoft.com/downloads/deta ... b8eb148356
Security Update for Outlook Express for Windows XP (KB941202)
http://www.microsoft.com/downloads/deta ... layLang=en
Cumulative Security Update for Internet Explorer for Windows XP Service Pack 2 (KB939653)
http://www.microsoft.com/downloads/deta ... layLang=en
Security Update for Windows XP (KB933729)
http://www.microsoft.com/downloads/deta ... layLang=en
Windows Update Engine v7.0.6000.381
http://xable.net/board/index.php?showtopic=49
Cannot find this update at the original Microsoft Website.
And this Updates are for the Windows Components (Like FAX, IIS ...):
Security Update for Windows XP (KB926247)
http://www.microsoft.com/downloads/deta ... layLang=en
Security Update for Windows XP (KB939373)
http://www.microsoft.com/downloads/deta ... layLang=en
Security Update for Windows XP (KB917537)
http://www.microsoft.com/downloads/deta ... layLang=en
I just did a fresh install using my unattended CD with RVM v2.1.11 and update pack R13 to check what updates show on Windows Update.
Stimpy's list pretty much covers everything. There is just one other optional update (KB920342), but it requires WGA verification. I don't think those are integeratable, right...?
An updated release would be most appreciated indeed, if someone who can cook it could find the time to do it.
Thanks!
Stimpy's list pretty much covers everything. There is just one other optional update (KB920342), but it requires WGA verification. I don't think those are integeratable, right...?
An updated release would be most appreciated indeed, if someone who can cook it could find the time to do it.
Thanks!
That update is included in the Update Pack, TripleA.
Just be patient, everybody. The wheels are turning.
Just be patient, everybody. The wheels are turning.
- roirraWedorehT
- Posts: 763
- Joined: Sun Oct 15, 2006 2:25 pm
Re: WScript 5.7 Oddities
I haven't gotten this error on any of the 3+ machines (with floppies enabled) that I've integrated WScript 5.7 on.RogueSpear wrote:I've come across something a little strange when I integrate WScript 5.7 into my source. It took me quite a while to discover this because I don't do too many installs on units with a floppy drive enabled anymore.
@5eraph: only for knowledge:
NEW EDIT:
I've created the italian RVMUP and my changelog since code65536's addon R13 is:
KB932823 - Replaced KB938032
KB933729 - Replaced KB925623
KB935879 - Replaced KB927802
KB936071 - Replaced KB932597
KB936357 - Updated to v2
KB937357 - Replaced KN906866 (Obsolete KB924270)
KB939653 - Replaced KB937143
KB939786 - Replaced KB916595
KB941133 - Replaced KB925066
KB941183 - Replaced KB933579; Updated MSXML 6
KB941202 - Partially updated KB929123
KB941248 - Replaced kb941598
KB941603 - Partially updated KB925876
KB941715 - Replaced KB933876
KB941833 - Replaced KB936181; Updated MSXML 4
KB941837 - Partially updated KB884575
KB941880 - Replaced KB939884
September 25 Root Certificates Update
Stubbed the Malicious Software Removal Tool (version: 1.34)
I hope this will help you during creation of new pack.
NEW EDIT:
I've created the italian RVMUP and my changelog since code65536's addon R13 is:
KB932823 - Replaced KB938032
KB933729 - Replaced KB925623
KB935879 - Replaced KB927802
KB936071 - Replaced KB932597
KB936357 - Updated to v2
KB937357 - Replaced KN906866 (Obsolete KB924270)
KB939653 - Replaced KB937143
KB939786 - Replaced KB916595
KB941133 - Replaced KB925066
KB941183 - Replaced KB933579; Updated MSXML 6
KB941202 - Partially updated KB929123
KB941248 - Replaced kb941598
KB941603 - Partially updated KB925876
KB941715 - Replaced KB933876
KB941833 - Replaced KB936181; Updated MSXML 4
KB941837 - Partially updated KB884575
KB941880 - Replaced KB939884
September 25 Root Certificates Update
Stubbed the Malicious Software Removal Tool (version: 1.34)
I hope this will help you during creation of new pack.
Last edited by kontini on Sun Oct 28, 2007 4:05 am, edited 3 times in total.
- RogueSpear
- Posts: 1155
- Joined: Tue Nov 23, 2004 9:50 pm
- Location: Buffalo, NY
Re: WScript 5.7 Oddities
[quote="roirraW "edor""]
Are you running any scripts that query the floppy drive?
I haven't gotten this error on any of the 3+ machines (with floppies enabled) that I've integrated WScript 5.7 on.[/quote]RogueSpear wrote:I've come across something a little strange when I integrate WScript 5.7 into my source. It took me quite a while to discover this because I don't do too many installs on units with a floppy drive enabled anymore.
Are you running any scripts that query the floppy drive?
- roirraWedorehT
- Posts: 763
- Joined: Sun Oct 15, 2006 2:25 pm
Re: WScript 5.7 Oddities
False alarm I guessRogueSpear wrote:Are you running any scripts that query the floppy drive?


- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
Thanks kontini but sorry guys looks like were going to have to wait for code or ryan to come backkontini wrote:@5eraph: only for knowledge:
I've created the italian RVMUP and my changelog since code65536's addon R13 is:
KB931678 - Replaced KB938032
KB933729 - Replaced KB925623
KB939653 - Replaced KB937143
KB939786 - Replaced KB916595
KB941183 - Replaced KB933579; Updated MSXML 6
KB941202 - Partially updated KB929123
KB941248 - Replaced kb941598
KB941715 - Replaced KB933876
KB941833 - Replaced KB936181; Updated MSXML 4
KB941837 - Partially updated KB884575
KB941880 - Replaced KB939884
September 25 Root Certificates Update
Stubbed the Malicious Software Removal Tool (version: 1.34)
I hope this will help you during creation of new pack.
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
Try changing
To
Code: Select all
[Flash.Register]
11,Macromed\Flash,Flash9d.ocx,1
Code: Select all
[Flash.Register]
11,,regsvr32.exe,,,"/s %11%\Macromed\Flash\Flash9d.ocx"
-
- Posts: 12
- Joined: Tue Sep 25, 2007 1:32 pm
Yes.OuTman wrote:does Flash registration issue, when integrating with nLite, still occurs when integrating with latest nLite RC?
nuhi is aware of the issue so hopefully it will be fixed before nLite goes final.
nLite Forum
I wouldn't count on it! There are many outstanding bugs with nLite. about 10% of the reg tweeks dont work, and on a clean XP SP2 cd image, I get this extra account turn up after Windows finnishes setup, meaning that I have 2 user accounts, and have to delete it from within Windows after. Also every now and then, nLite spits out a CD Image that is slightly corrupt with a handful of missing files.
Please don't take this as me disrespecting Nuhi, as nLite is a fantasic idea, and Nuhi is a very talented guy, and i'm sure he will get on top of these things one day.
Please don't take this as me disrespecting Nuhi, as nLite is a fantasic idea, and Nuhi is a very talented guy, and i'm sure he will get on top of these things one day.
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
Thanks for the info Outbreaker. But that is not the account name, I think it is called private or user or something like that. It's been a month or 2 since I last tried nLite. But the error I got a month ago was the same as what I used to get intermittantly about 6 months ago using nLite, and this problem has been mentioned by others on the nLite forum, but most bugs that are mentioned over there seem to get ignored, or at least buried by other posts.
I will give it another try once the final 1.4 comes out. But it's been a long time since I have seen any of the bugs in the reg tweeks get addressed.
I will give it another try once the final 1.4 comes out. But it's been a long time since I have seen any of the bugs in the reg tweeks get addressed.
So it is...5eraph wrote:That update is included in the Update Pack, TripleA.
I wonder why it still shows on Windows Update for me, then...? We'll see.
Thanks.