[MacLover]

discdude, on 27 November 2011 - 09:05 PM, said:

MacLover, on 27 November 2011 - 02:21 PM, said:

I didn't notice it before but VirtualBox needs two more APIs to install properly:
SETUPAPI.DLL -> SetupSetNonInteractiveMode
SETUPAPI.DLL -> SetupUninstallOEMInfW

As I said before, no rush on getting these in but it would be nice to have the ability to run VirtualBox 4.x on Windows 2000.

Again, keep up the great work!

Did you try BlackWingCat's setupapi.dll? I don't know if it supports those two functions, but it is probably worth a try.

http://blog.livedoor...ves/873798.html

BWC's SETUPAPI.DLL doesn't support SetupSetNonInteractiveMode, therefore I cannot install VirtualBox 4 even with a modified MSI to allow installation on Win2k. It does have SetupUninstallOEMInfW though.

[int0x13]

Hi folks,
I got a software which is broken under windows 2000 sp4 (french version), because of the function "TzSpecificLocalTimeToSystemTime" which is not into win2k kernel32.dll.
I've googled and i've seen this topic is talking about patch and is referencing this function name (TzSpecificLocalTimeToSystemTime). Do you think it's possible to patch kernel32.dll library to add this function? And then make my software compatible with windows 2000. Is it what you do with your custom patches?
Regards,

[tomasz86]

WildBill's patch already has this function (TzSpecificLocalTimeToSystemTime) added. If you want to use it then you'll have to apply the English patch to your French system.

[int0x13]

tomasz86, on 28 November 2011 - 06:08 AM, said:

WildBill's patch already has this function (TzSpecificLocalTimeToSystemTime) added. If you want to use it then you'll have to apply the English patch to your French system.

Isn't it risky to apply english patch onto another language windows? You talk about the patch MS11-011 right? The one that can be found on this page My link ?
Thanks for your help! I didnt think what i'd like to do someone else already did! Seems very hard work.

[tomasz86]

Yes, I mean MS11-011 (2393802) but you should download it from here as I haven't updated the RyanVM list yet. V6 is the current version.

I can't say for sure but I guess that Windows files for European languages should be interchangeable. In the past I already tried using English kernel32.dll in a Polish system and no problems occurred. Of course some system dialogs may change to English but in case of kernel files most of them will be the text which you see on BSODs, not the actual system GUI.

Here there's instruction how to change the update.inf file.

[WildBill]

I found that my implementation of DbgPrintEx in ntdll was incorrect and would corrupt the stack, so I've posted MS11-011 V7 with a fixed version. I've also added DbgPrintEx to ntoskrnl, et. al. and RtlCaptureContext to kernel32. The new master additions list for V7 is below:

ntoskrnl.exe/ntkrnlpa.exe/ntkrnlmp.exe/ntkrpamp.exe

KeAcquireInterruptSpinLock
KeReleaseInterruptSpinLock
InterlockedPushEntrySList
InterlockedPopEntrySList
RtlInt64ToUnicodeString
RtlIntegerToUnicode
RtlClearBit
RtlTestBit
RtlSetBit
ZwQueryInformationThread......already there, added it to the export table
IoForwardIrpSynchronously/IoForwardAndCatchIrp (same routine, has two different exported names)
PsRemoveLoadImageNotifyRoutine (had to completely redesign the set and call routines to make this work)
PsRemoveCreateThreadNotifyRoutine (had to completely redesign the set and call routines to make this work)
_vsnwprintf
_aulldvrm
RtlGetVersion
KeFlushQueuedDpcs
DbgPrintEx


ntdll.dll

RtlIpv4StringToAddressA
RtlIpv4StringToAddressW
RtlIpv4StringToAddressExA
RtlIpv4StringToAddressExW
RtlIpv4AddressToStringA
RtlIpv4AddressToStringW
RtlIpv4AddressToStringExA
RtlIpv4AddressToStringExW
RtlIpv6StringToAddressA
RtlIpv6StringToAddressW
RtlIpv6StringToAddressExA
RtlIpv6StringToAddressExW
RtlIpv6AddressToStringA
RtlIpv6AddressToStringW
RtlIpv6AddressToStringExA
RtlIpv6AddressToStringExW
RtlInitializeGenericTableAvl
RtlIsGenericTableEmptyAvl
RtlGetElementGenericTableAvl
RtlNumberGenericTableElementsAvl
RtlInsertElementGenericTableAvl
RtlDeleteElementGenericTableAvl
RtlEnumerateGenericTableLikeADirectory
RtlLookupElementGenericTableAvl
RtlEnumerateGenericTableWithoutSplayingAvl
RtlEnumerateGenericTableAvl
RtlEncodePointer (not a stub -- it's the real functionality and depends on changes to ntoskrnl.exe, etc.)
RtlDecodePointer (not a stub -- it's the real functionality and depends on changes to ntoskrnl.exe, etc.)
RtlInterlockedPushEntrySList
RtlInterlockedPopEntrySList
RtlInterlockedFlushSList
RtlQueryDepthSList
RtlInitializeSListHead
LdrLockLoaderLock
LdrUnlockLoaderLock
LdrAddRefDll
RtlComputePrivatizedDllName_U
RtlValidateUnicodeString
RtlDuplicateUnicodeString
RtlDowncaseUnicodeChar
RtlFindCharInUnicodeString
RtlpEnsureBufferSize
RtlMultiAppendUnicodeStringBuffer
RtlAppendPathElement
LdrEnumerateLoadedModules
RtlRandomEx
RtlUnhandledExceptionFilter2
RtlUnhandledExceptionFilter
RtlAddVectoredExceptionHandler (also involved updating LdrpInitializeProcess and RtlDispatchException and adding internal function RtlCallVectoredExceptionHandlers)
RtlRemoveAddVectoredExceptionHandler (also involved updating LdrpInitializeProcess and RtlDispatchException and adding internal function RtlCallVectoredExceptionHandlers)
RtlGetNtVersionNumbers
DbgPrintEx (Fixed version)
_vsnwprintf
_lfind
_aulldvrm
_alldvrm
RtlpNotOwnerCriticalSection
RtlpApplyLengthFunction
RtlCopyOutOfProcessMemoryStreamTo
RtlLockMemoryStreamRegion
RtlUnlockMemoryStreamRegion
RtlNtPathNameToDosPathName
RtlGetLengthWithoutLastFullDosOrNtPathElement
RtlCreateBootStatusDataFile
RtlComputeCrc32
RtlCaptureContext
RtlLockBootStatusData
RtlUnlockBootStatusData
RtlGetSetBootStatusData
RtlNtStatusToDosErrorNoTeb (already there, only had to add it to the export table)
RtlAddMemoryStream
RtlReleaseMemoryStream
RtlQueryInterfaceMemoryStream
RtlReadOutOfProcessMemoryStream
RtlRevertMemoryStream
RtlCloneMemoryStream
RtlCommitMemoryStream
RtlSetMemoryStreamSize
RtlWriteMemoryStream
RtlSeekMemoryStream
RtlCopyMemoryStreamTo
RtlReadMemoryStream
RtlStatMemoryStream
RtlInitMemoryStream
RtlFinalReleaseOutOfProcessMemoryStream
RtlInitOutOfProcessMemoryStream
RtlSetLastWin32ErrorAndNtStatusFromNtStatus
RtlSetLastWin32Error/RtlRestoreLastWin32Error (same routine, exported under two different names)


bootvid.dll

VidSetVgaPalette (used by the bootskin code)


kernel32.dll

DecodePointer (forwarded export to NTDLL.RtlDecodePointer)
EncodePointer (forwarded export to NTDLL.RtlEncodePointer)
InterlockedPushEntrySList (forwarded export to NTDLL.RtlInterlockedPushEntrySList)
InterlockedPopEntrySList (forwarded export to NTDLL.RtlInterlockedPopEntrySList)
InterlockedFlushSList (forwarded export to NTDLL.RtlInterlockedFlushSList)
QueryDepthSList (forwarded export to NTDLL.RtlQueryDepthSList)
InitializeSListHead (forwarded export to NTDLL.RtlInitializeSListHead)
GetModuleHandleExA
GetModuleHandleExW
IsWow64Process
IsWow64Message
GetProcessHandleCount
GetNativeSystemInfo (same as GetSystemInfo, simply added another export table entry)
SetDllDirectoryA
SetDllDirectoryW
GetDllDirectoryA
GetDllDirectoryW
AttachConsole
TzSpecificLocalTimeToSystemTime
SetClientTimeZoneInformation
IsValidUILanguage
GetSystemWow64DirectoryA
GetSystemWow64DirectoryW
SetHandleContext
GetProcessId
GetSystemTimes
CreateMemoryResourceNotification
QueryMemoryResourceNotification
AddVectoredExceptionHandler (forwarded export to NTDLL.RtlAddVectoredExceptionHandler)
RemoveVectoredExceptionHandler (forwarded export to NTDLL.RtlRemoveAddVectoredExceptionHandler)
RtlCaptureStackBackTrace
SetThreadUILanguage
LZStart
GetExpandedNameA
GetExpandedNameW
LZInit
LZDone
LZCreateFileW
LZOpenFileA
LZOpenFileW
LZSeek
LZRead
LZClose
LZCloseFile
LZCopy
CopyLZFile
GetVolumePathNamesForVolumeNameW
GetVolumePathNamesForVolumeNameA
GetHandleContext
GetCPFileNameFromRegistry
EnumerateLocalComputerNamesW
EnumerateLocalComputerNamesA
CreateSocketHandle
CreateNlsSecurityDescriptor
AddLocalAlternateComputerNameW
AddLocalAlternateComputerNameA
RemoveLocalAlternateComputerNameW
RemoveLocalAlternateComputerNameA
SetLocalPrimaryComputerNameW
SetLocalPrimaryComputerNameA
RtlCaptureContext

This post has been edited by WildBill: 28 November 2011 - 09:40 PM

[tomasz86]

Thank you, WildBill

[int0x13]

tomasz86, on 28 November 2011 - 09:23 AM, said:

Yes, I mean MS11-011 (2393802) but you should download it from here as I haven't updated the RyanVM list yet. V6 is the current version.

I can't say for sure but I guess that Windows files for European languages should be interchangeable. In the past I already tried using English kernel32.dll in a Polish system and no problems occurred. Of course some system dialogs may change to English but in case of kernel files most of them will be the text which you see on BSODs, not the actual system GUI.

Here there's instruction how to change the update.inf file.

Ok i managed to install MS11-011v7 (last one) on my french Win2K advanced server. I dont know if it's same for windows 2000 server or not.
After that i found that i got another dependency issue with iphlpapi.dll library. ("The procedure entry point GetIpErrorString could not be located in the dynamic link library iphlpapi.dll")
So i thought about installing version from win2k3 server (which has GetIpErrorString function). After that i had another depend with ws2_32.dll
(The procedure entry point freeaddrinfo could not be located in the dynamic link library WS2_32.dll). I search onto WildBill patches and found Windows2000-KB2508429-v3-x86-ENU.
But after reboot, i got services.exe crashing and 60 second autoreboot counter alert. Dont know what's wrong. I tried to boot into safemode and it works, but not in normal mode. Maybe it has to do with the iphlpapi.dll i directly copy from win2k3 to win2k server.

[tomasz86]

Do you get this GetIpErrorString problem when trying to launch the program you mentioned before? What's the name of it?

You should check the dependencies with Dependency Walker. You will be able to solve the dependency problems with BlackWingCat's KDW. I may help you but first you need to let us know what the name of the program you're trying to use is.

[int0x13]

Alright, i will try KDW, didnt know this tool. Also i'd like to know how to add a simple function from one dll into another one using "PE TOOL", is there any how to to do this?
The tool i'd like to run under win2k PRO (and 2k PRO server if possible) it's here: here
To test the tool , you have to install it under XP+ and then copy the install folder or unpack the installer.
Thank you for your help.

This post has been edited by int0x13: 29 November 2011 - 08:19 AM

[bristols]

WildBill, on 26 November 2011 - 10:42 AM, said:

bristols, on 25 November 2011 - 06:49 AM, said:

Hi WildBill,

Just a report about my experience after installing 2393802-v6 (for which, thank you).

So far, so relatively good (installed on a pre-existing system, not slipstreamed) except for one or two strange resource leak-type behaviours that I certainly haven't seen previously. A few hours' browsing with two browsers (Firefox and Opera) and multiple open tabs, Notepad++, Notepad2, xplorer2 Lite, and a handful of instances of Irfanview has been enough to trigger it.

I apologise for the vagueness. However I'm pretty sure that the behaviour is a consequence (somehow) of installing your patch.

Strange. As far as I know, the patch doesn't do anything with resources. I took a pass through kernel32, ntdll, and ntoskrnl to see if I could spot any Unicode strings that weren't being freed, but so far everything looks okay. Are you seeing high memory usage for certain apps after a long time? Are you seeing it on both UP and MP processors? I'd probably need a lot more info before I'd know where to look, much less know that the patch itself is causing it.

I have it installed here, so I'll keep an eye out for memory leaks, but to date I've had no problems.

I've been using 2393802-v7 since yesterday and haven't experienced any problems. Coupled with the fact that my earlier report was less than scientific (I wasn't monitoring apps for memory usage, but instead was just observing odd lags in GDI refreshes in those certain apps I mentioned), I have to say now that I would disregard my earlier post.

Actually, the behaviour was like some kind of hard drive write lag. I saw it on a multiprocessor system - Pentium D Presler, ATI Radeon Xpress 1100 Pro chipset. I'm still quite unfamiliar with the system, and as such I haven't fine-tuned it, in terms of performance, to any large degree.

This post has been edited by bristols: 30 November 2011 - 01:21 PM

[bristols]

@WildBill: I've sent you a PM.

[WildBill]

Thanks, it turned out to be easy to find with the info you sent me (I missed a LEAVE instruction on AttachConsoleInternal). A V8 will be out shortly...

[WildBill]

Due to a bug in one of the new kernel routines (thanks, Bristols for finding it), I've had to post MS11-011 V8. This one also adds a new version of win32k.sys: I had originally wanted to wait until I posted MS11-034 (KB2506223) to add routines to win32k.sys, but analysis is showing that there are quite a lot of changes in MS11-034 such that it will take a while to complete. I'd really like to see if people can get the ATI v11 drivers working, so this one includes win32k.sys with some functions added. As such, I've also added a requirement that MS11-012 (KB2479628) first be installed (which I'm not happy about...this is why I held off on adding win32k.sys until now). Hopefully this won't create a problem as there is no circular dependency and this hotfix will warn you to install KB2479628 if need be.

Anyhow, here's the new list of additions:


ntoskrnl.exe/ntkrnlpa.exe/ntkrnlmp.exe/ntkrpamp.exe

KeAcquireInterruptSpinLock
KeReleaseInterruptSpinLock
InterlockedPushEntrySList
InterlockedPopEntrySList
RtlInt64ToUnicodeString
RtlIntegerToUnicode
RtlClearBit
RtlTestBit
RtlSetBit
ZwQueryInformationThread......already there, added it to the export table
IoForwardIrpSynchronously/IoForwardAndCatchIrp (same routine, has two different exported names)
PsRemoveLoadImageNotifyRoutine (had to completely redesign the set and call routines to make this work)
PsRemoveCreateThreadNotifyRoutine (had to completely redesign the set and call routines to make this work)
_vsnwprintf
_aulldvrm
RtlGetVersion
KeFlushQueuedDpcs
DbgPrintEx


ntdll.dll

RtlIpv4StringToAddressA
RtlIpv4StringToAddressW
RtlIpv4StringToAddressExA
RtlIpv4StringToAddressExW
RtlIpv4AddressToStringA
RtlIpv4AddressToStringW
RtlIpv4AddressToStringExA
RtlIpv4AddressToStringExW
RtlIpv6StringToAddressA
RtlIpv6StringToAddressW
RtlIpv6StringToAddressExA
RtlIpv6StringToAddressExW
RtlIpv6AddressToStringA
RtlIpv6AddressToStringW
RtlIpv6AddressToStringExA
RtlIpv6AddressToStringExW
RtlInitializeGenericTableAvl
RtlIsGenericTableEmptyAvl
RtlGetElementGenericTableAvl
RtlNumberGenericTableElementsAvl
RtlInsertElementGenericTableAvl
RtlDeleteElementGenericTableAvl
RtlEnumerateGenericTableLikeADirectory
RtlLookupElementGenericTableAvl
RtlEnumerateGenericTableWithoutSplayingAvl
RtlEnumerateGenericTableAvl
RtlEncodePointer (not a stub -- it's the real functionality and depends on changes to ntoskrnl.exe, etc.)
RtlDecodePointer (not a stub -- it's the real functionality and depends on changes to ntoskrnl.exe, etc.)
RtlInterlockedPushEntrySList
RtlInterlockedPopEntrySList
RtlInterlockedFlushSList
RtlQueryDepthSList
RtlInitializeSListHead
LdrLockLoaderLock
LdrUnlockLoaderLock
LdrAddRefDll
RtlComputePrivatizedDllName_U
RtlValidateUnicodeString
RtlDuplicateUnicodeString
RtlDowncaseUnicodeChar
RtlFindCharInUnicodeString
RtlpEnsureBufferSize
RtlMultiAppendUnicodeStringBuffer
RtlAppendPathElement
LdrEnumerateLoadedModules
RtlRandomEx
RtlUnhandledExceptionFilter2
RtlUnhandledExceptionFilter
RtlAddVectoredExceptionHandler (also involved updating LdrpInitializeProcess and RtlDispatchException and adding internal function RtlCallVectoredExceptionHandlers)
RtlRemoveAddVectoredExceptionHandler (also involved updating LdrpInitializeProcess and RtlDispatchException and adding internal function RtlCallVectoredExceptionHandlers)
RtlGetNtVersionNumbers
DbgPrintEx (Fixed version)
_vsnwprintf
_lfind
_aulldvrm
_alldvrm
RtlpNotOwnerCriticalSection
RtlpApplyLengthFunction
RtlCopyOutOfProcessMemoryStreamTo
RtlLockMemoryStreamRegion
RtlUnlockMemoryStreamRegion
RtlNtPathNameToDosPathName
RtlGetLengthWithoutLastFullDosOrNtPathElement
RtlCreateBootStatusDataFile
RtlComputeCrc32
RtlCaptureContext
RtlLockBootStatusData
RtlUnlockBootStatusData
RtlGetSetBootStatusData
RtlNtStatusToDosErrorNoTeb (already there, only had to add it to the export table)
RtlAddMemoryStream
RtlReleaseMemoryStream
RtlQueryInterfaceMemoryStream
RtlReadOutOfProcessMemoryStream
RtlRevertMemoryStream
RtlCloneMemoryStream
RtlCommitMemoryStream
RtlSetMemoryStreamSize
RtlWriteMemoryStream
RtlSeekMemoryStream
RtlCopyMemoryStreamTo
RtlReadMemoryStream
RtlStatMemoryStream
RtlInitMemoryStream
RtlFinalReleaseOutOfProcessMemoryStream
RtlInitOutOfProcessMemoryStream
RtlSetLastWin32ErrorAndNtStatusFromNtStatus
RtlSetLastWin32Error/RtlRestoreLastWin32Error (same routine, exported under two different names)


bootvid.dll

VidSetVgaPalette (used by the bootskin code)


kernel32.dll

DecodePointer (forwarded export to NTDLL.RtlDecodePointer)
EncodePointer (forwarded export to NTDLL.RtlEncodePointer)
InterlockedPushEntrySList (forwarded export to NTDLL.RtlInterlockedPushEntrySList)
InterlockedPopEntrySList (forwarded export to NTDLL.RtlInterlockedPopEntrySList)
InterlockedFlushSList (forwarded export to NTDLL.RtlInterlockedFlushSList)
QueryDepthSList (forwarded export to NTDLL.RtlQueryDepthSList)
InitializeSListHead (forwarded export to NTDLL.RtlInitializeSListHead)
GetModuleHandleExA
GetModuleHandleExW
IsWow64Process
IsWow64Message
GetProcessHandleCount
GetNativeSystemInfo (same as GetSystemInfo, simply added another export table entry)
SetDllDirectoryA
SetDllDirectoryW
GetDllDirectoryA
GetDllDirectoryW
AttachConsole
TzSpecificLocalTimeToSystemTime
SetClientTimeZoneInformation
IsValidUILanguage
GetSystemWow64DirectoryA
GetSystemWow64DirectoryW
SetHandleContext
GetProcessId
GetSystemTimes
CreateMemoryResourceNotification
QueryMemoryResourceNotification
AddVectoredExceptionHandler (forwarded export to NTDLL.RtlAddVectoredExceptionHandler)
RemoveVectoredExceptionHandler (forwarded export to NTDLL.RtlRemoveAddVectoredExceptionHandler)
RtlCaptureStackBackTrace
SetThreadUILanguage
LZStart
GetExpandedNameA
GetExpandedNameW
LZInit
LZDone
LZCreateFileW
LZOpenFileA
LZOpenFileW
LZSeek
LZRead
LZClose
LZCloseFile
LZCopy
CopyLZFile
GetVolumePathNamesForVolumeNameW
GetVolumePathNamesForVolumeNameA
GetHandleContext
GetCPFileNameFromRegistry
EnumerateLocalComputerNamesW
EnumerateLocalComputerNamesA
CreateSocketHandle
CreateNlsSecurityDescriptor
AddLocalAlternateComputerNameW
AddLocalAlternateComputerNameA
RemoveLocalAlternateComputerNameW
RemoveLocalAlternateComputerNameA
SetLocalPrimaryComputerNameW
SetLocalPrimaryComputerNameA
RtlCaptureContext


win32k.sys

EngIsSemaphoreOwned
EngClearEvent
EngBugCheckEx (forwards to NTOSKRNL.KeBugCheckEx)
EngAllocSectionMem
EngFreeSectionMem
EngMapSection


I'm prepared to release a new version of MS11-012 that also contains the new win32k.sys just to be safe, but I'm not sure which version is best to use as a starting point: the last one I released or tomasz's updated version. Any recommendations?

This post has been edited by WildBill: 04 December 2011 - 02:12 AM

[WildBill]

Just to be ultra-safe I also just posted MS11-012 V7, which has the new win32k.sys that I added to MS11-011 V8. This probably still has the slipstreaming issues that V6a had, but at least there is now no possibility of overwriting the newer win32k.sys from MS11-011 V8 with an older one. Both hotfixes now contain win32k.sys 5.0.2195.7401.

This post has been edited by WildBill: 04 December 2011 - 02:20 AM

[tomasz86]

WildBill,

there is v9 of MS11-012 available already

Could you add the newest win32k.sys to it instead of making a v7?


EDIT

Now I saw your comment in the last line of #454. Well, it's up to you I guess because after all, it's your patch

In my opinion the best way to go is to have only one updated version for each update.

EDIT2

Actually, if I remember correctly, v6a should be almost exactly the same as v9... the only difference being that v9 adds also registry changes from 967715 & 2286198 (details).

This post has been edited by tomasz86: 04 December 2011 - 03:02 AM

[acus]

Hi WildBill,

may I ask you to change the version number of two files?

In your Windows2000-KB2508429-v5-x86-ENU.exe there are:

1. kerberos.dll -> v.5.0.2195.7056
2. samsrv.dll -> v.5.0.2195.7011

while in Windows2000-KB907868-x86-ENU.EXE there is:
1. kerberos.dll -> v.5.0.2195.7072

and in Windows2000-KB904765-x86-ENU.EXE there is:
2. samsrv.dll -> v.5.0.2195.7071

Regards

[WildBill]

Hmm. I just realized that my MS11-012 patch actually does require MS11-011; it just doesn't do so explicitly. I'm going to have to release *another* MS11-011 with the new win32k.sys removed (so to get the new win32k.sys functions people should upgrade MS11-012 instead if they haven't done so already). As for kerberos.dll and samsrv.dll, is there an HBR that has those other versions?

Ignore the scratched-out part...getting all these hotfixes mixed up in my head...

This post has been edited by WildBill: 04 December 2011 - 12:23 PM

[acus]

Hi WildBill,

yes, you are right, the hotfixes are HBR.
http://support.micro...px?kbnum=904765
http://support.micro...px?kbnum=907868

Regards.

[tomasz86]

WildBill, on 04 December 2011 - 12:13 PM, said:

Ignore the scratched-out part...getting all these hotfixes mixed up in my head...

There are almost 300 updates/hotfixes on bristols' page
It's hard NOT to get confused...


I prepared a script which you may find useful.

updatever.cmd

You can use it to create update.ver automatically. Files from root directory and (if exist) files from uniproc, wms & xpsp2_binarydrop are processed. Useless files (spmsg.dll, spuninst.exe, empty.cat) are ignored. Files without version are also properly listed (instead of A=B,C,D they go A=B,,D).


1. Place updatever.cmd in an empty folder & run it once. Two folders (HF & TOOLS) will be created.




2. Download, unpack & copy into TOOLS these two files: fciv.exe (download) and filever.exe (find & download). I haven't tested newer versions of filever.exe so I can't say whether they work or not. The one I use is 5.0.2134.1.




3. Unpack updates like this:




4. Run updatever.cmd.


This is an example created for 2393802-v8:

[SourceFileInfo]
bootvid.dll=93a240abe57c7fff70217094c6ef31da,00050000087C0003,11360
kernel32.dll=60959fe454a2d22d916b5ea7b2fa50cf,0005000008931BF2,764688
ntdll.dll=56edaaa97265f14f9831a0b85ef6180a,0005000008931BAB,531728
ntkrnlmp.exe=085676dc6cbf24978b6540d223ccd9d6,0005000008931CD5,1961024
ntkrnlpa.exe=d14dafcbf3d1b7ae4b78451217caee73,0005000008931CD5,1960096
ntkrpamp.exe=e2d0c621099d41b90fe342f942b65d90,0005000008931CD5,1982336
ntoskrnl.exe=ee0f8d6a9272446d4a08ae58aa9067cb,0005000008931CD5,1937376
win32k.sys=982892466636b2178dc978cfbad2dd10,0005000008931CE9,1670896
uniproc\kernel32.dll=2302eab80f89e66f13053b873b1c2d35,0005000008931BF2,764688
uniproc\ntdll.dll=56edaaa97265f14f9831a0b85ef6180a,0005000008931BAB,531728

This post has been edited by tomasz86: 04 December 2011 - 01:47 PM