<![CDATA[DriverPacks.net Forum - [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?id=1100 Sat, 06 Jan 2007 07:55:37 +0000 PunBB <![CDATA[Re: [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=7018#p7018 Solved now! wink

]]> Sat, 06 Jan 2007 07:55:37 +0000 http://forum.driverpacks.net/viewtopic.php?pid=7018#p7018 <![CDATA[Re: [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=7012#p7012 thanks!

]]> Fri, 05 Jan 2007 20:00:56 +0000 http://forum.driverpacks.net/viewtopic.php?pid=7012#p7012 <![CDATA[Re: [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=7008#p7008 zilexa wrote:

No it does not...
I am using the Dutch updatepack by MEULC: http://www.ryanvm.net/forum/viewtopic.p … 9d0bff8711

When I check the contents of his updatepack, I cannot find a file named RVMUPPCK either. I do find MEULCPCK.IN_
Could that be it?

Then that's the cause. MeulC always kept on using "RVMUPPCK.IN_", so he must have decided to change that in his most recent release.

Will be fixed in the next update.

]]> Fri, 05 Jan 2007 18:49:16 +0000 http://forum.driverpacks.net/viewtopic.php?pid=7008#p7008 <![CDATA[Re: [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=7007#p7007 No it does not...
I am using the Dutch updatepack by MEULC: http://www.ryanvm.net/forum/viewtopic.p … 9d0bff8711

When I check the contents of his updatepack, I cannot find a file named RVMUPPCK either. I do find MEULCPCK.IN_
Could that be it?

]]> Fri, 05 Jan 2007 17:57:43 +0000 http://forum.driverpacks.net/viewtopic.php?pid=7007#p7007 <![CDATA[Re: [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=7001#p7001 zilexa wrote:

Sorry I wasn't that clear, I slipstreamed Ryan's Update Pack NL, KB883667 NL and DirectX december Sereby's Update.

Huh? Then RyanVM's UpdatePack should definitely have been detected! Can you verify that the file I386/RVMUPPCK.IN_ exists?

]]> Fri, 05 Jan 2007 10:12:39 +0000 http://forum.driverpacks.net/viewtopic.php?pid=7001#p7001 <![CDATA[Re: [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=6999#p6999 Sorry I wasn't that clear, I slipstreamed Ryan's Update Pack NL, KB883667 NL and DirectX december Sereby's Update.

]]> Fri, 05 Jan 2007 02:13:23 +0000 http://forum.driverpacks.net/viewtopic.php?pid=6999#p6999 <![CDATA[Re: [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=6981#p6981 It is assumed that this hotfix is slipstreamed by the DriverPacks BASE unless a file is detected that identifies an UpdatePack, i.e. RyanVM's, Sereby's, hp38gusers's or the Russian (don't remember the creator, it was something like "PetyaV4Sechkin").
As a work-around you could create a RVMUPPCK.INF file in your I386 directory.

So how did you slipstream all these updates WITHOUT an UpdatePack?

]]> Wed, 03 Jan 2007 14:27:12 +0000 http://forum.driverpacks.net/viewtopic.php?pid=6981#p6981 <![CDATA[Re: [SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=6970#p6970 *BUMP*
Some help please...

]]> Tue, 02 Jan 2007 23:59:35 +0000 http://forum.driverpacks.net/viewtopic.php?pid=6970#p6970 <![CDATA[[SOLVED BUG #296] Dutch UpdatePack not detected, which leads to ...]]> http://forum.driverpacks.net/viewtopic.php?pid=6921#p6921 Heyy
Driverpack Base unslipstreams my precious Dutch KB883667!
I have NLD windows, and NLD KB883667, slipstreamed with nLite. Then I run base and...:

...
2006-12-30 20:08:53 : <GUI>  Saved settings!
2006-12-30 20:08:53 : <GUI>  Closed GUI.
2006-12-30 20:08:53 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2006-12-30 20:08:54 : <PREP> Removed all attributes from \I386.
2006-12-30 20:08:57 : <PREP> Cleaned up \I386\svcpack.inf.
[b]2006-12-30 20:08:57 : <PREP> Unslipstreamed KB883667.[/b]
2006-12-30 20:08:57 : <PREP> Created a backup of \I386\winnt.sif.
2006-12-30 20:08:57 : <PREP> Created a backup of \I386\txtsetup.sif.
2006-12-30 20:08:57 : <PREP> Created a backup of \I386\dosnet.inf.
2006-12-30 20:08:57 : <PREP> Created temporary working directory.
2006-12-30 20:08:57 : <SLIP> Created necessary directory structure for method 2.
2006-12-30 20:08:57 : <SLIP> Copied files necessary for method 2.
2006-12-30 20:08:57 : <SLIP> Extracted files necessary for method 2.
2006-12-30 20:08:58 : <SLIP> Created \I386\presetup.cmd file.
2006-12-30 20:08:58 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2006-12-30 20:08:58 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2006-12-30 20:09:49 : <SLIP> Copied DriverPacks to \OEM.
2006-12-30 20:09:52 : <SLIP> Extracted and deleted \I386\svcpack.in_.
2006-12-30 20:09:52 : <SLIP> Updated \I386\svcpack.inf file to support KB888111 and KB921401.
2006-12-30 20:09:54 : <SLIP> Updated \I386\txtsetup.sif file to support KB888111.
2006-12-30 20:09:57 : <SLIP> Updated \I386\dosnet.inf file to support KB888111.
2006-12-30 20:09:57 : <SLIP> Updated \I386\dosnet.inf file to support KB921401.
2006-12-30 20:09:57 : <SLIP> Updated \I386\winnt.sif to support method 2.
2006-12-30 20:09:57 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2006-12-30 20:09:57 : <SLIP> Slipstream finished in 1 minutes and 4 seconds.
2006-12-30 20:09:59 : <CLNP> Temporary working directory successfully deleted.
2006-12-30 20:09:59 : Program terminated.

The only problem with this KB is when people don't use the localized version.
Ooh and even worse, after using Base, there is no newdev.dl_ file anymore in the i386 folder! This means error during Windows Setup. I can choose to cancel setup or continue without the file sad

took some time but I read on this forum somewhere that newdev is not only on the original Winxp cd but also in this KB.
So Base checks if  I intergrated this KB and simply deletes the newdev file.
As a solution I extracted the newdev.dll file from the KB, cabbed it and copied it to my i386 folder... but I'm sure that's not the same thing as integrating the KB. So I 'll hope it will be fixed smile

]]> Sat, 30 Dec 2006 19:12:34 +0000 http://forum.driverpacks.net/viewtopic.php?pid=6921#p6921