[Rel] System File Patches >09/23/08<
Zacam thanks for updating these I am getting this AutoIt error on SFC, UXTHEME,XPRAID5 the TCPIP_100 seems to work fine. Here is the error message I am receiving
Line -1:
Error Array variable has incorrect number of subscripts or subscript dimension range exceeded
I am using Integrator 1.5 beta32 to add these.
Thanks,
dolivas
Line -1:
Error Array variable has incorrect number of subscripts or subscript dimension range exceeded
I am using Integrator 1.5 beta32 to add these.
Thanks,
dolivas
i also can confirm the error.
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
Yes you read that correctly could it be a problem with the Integrator beta32 ?
Should I report it to Siginet ?
I ran a test on SP2 to make sure it worked on it and was not just a SP3 problem and the error is still there the weird thing is sometime it works with one but not the other for instances I use the SFC it passes then I try to use the UXTheme and it fails with the error once you receive the error the source is now bad and all of them will now fail with that error? So the problem is with both SP2 and SP3 also the link for the Syssetup still does not work.
Thanks,
dolivas
Should I report it to Siginet ?
I ran a test on SP2 to make sure it worked on it and was not just a SP3 problem and the error is still there the weird thing is sometime it works with one but not the other for instances I use the SFC it passes then I try to use the UXTheme and it fails with the error once you receive the error the source is now bad and all of them will now fail with that error? So the problem is with both SP2 and SP3 also the link for the Syssetup still does not work.
Thanks,
dolivas
HI Zacam I found the problem it is with the UXTheme you have a colon where you should have a semicolon it is line 28 and should be this
;KB936929 - SP3
Blame it on the DAMN headache you had yesterday
I tested it with SP2 and SP3 and they all work now.
Thanks again for the updates and hard work.
I'll check back later to see if the Syssetup link is working.
;KB936929 - SP3
Blame it on the DAMN headache you had yesterday

Thanks again for the updates and hard work.
I'll check back later to see if the Syssetup link is working.
n e ways thx for the fast replies and the fast fixes.
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
Zacam quick question will the hivesys still work with SP3? Also I am getting these error in my setuperr.log should I be after using the patches?
Thanks,
dolivas
Thanks,
dolivas
Code: Select all
Error:
Setup detected that the system file named [c:\windows\system32\dmadmin.exe] is not signed properly
by Microsoft. This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.
***
Error:
Setup detected that the system file named [c:\windows\system32\drivers\dmboot.sys] is not signed properly
by Microsoft. This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.
***
Error:
Setup detected that the system file named [c:\windows\system32\dmconfig.dll] is not signed properly
by Microsoft. This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.
***
Error:
Setup detected that the system file named [c:\windows\system32\syssetup.dll] is not signed properly
by Microsoft. This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.
***
Error:
Setup detected that the system file named [c:\windows\system32\drivers\tcpip.sys] is not signed properly
by Microsoft. This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.
***
Error:
Setup detected that the system file named [c:\windows\system32\uxtheme.dll] is not signed properly
by Microsoft. This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.
***
I am using the SFC_OS patch and I don't think it is working with SP3 can anyone confirm they have it working. Here is a list of the patches applied should it be skipping the one SFC_OS.DLL ?
Thanks,
dolivas
Code: Select all
Hex Editing Files
17:43:54 - DMADMIN.EXE 2600.3264.503.0 Patched at offset 312.
17:43:55 - DMADMIN.EXE 2600.3264.503.0 Patched at offset 7216.
17:43:55 - DMBOOT.SYS 2600.3264.503.0 Patched at offset 304.
17:43:56 - DMBOOT.SYS 2600.3264.503.0 Patched at offset 69884.
17:43:56 - DMBOOT.SYS 2600.3264.503.0 Patched at offset 69911.
17:43:57 - DMCONFIG.DLL 2600.0.503.0 Patched at offset 144743.
17:43:57 - DMCONFIG.DLL 2600.0.503.0 Patched at offset 144770.
17:43:57 - SFC_OS.DLL 5.1.2600.3264 No match at offset . Patch skipped.
17:43:57 - SFC_OS.DLL 5.1.2600.3264 Patched at offset 320.
17:43:58 - SYSSETUP.DLL 5.1.2600.3264 Patched at offset 211753.
17:43:58 - SYSSETUP.DLL 5.1.2600.3264 Patched at offset 328.
17:43:59 - TCPIP.SYS 5.1.2600.3264 Patched at offset 304.
17:43:59 - TCPIP.SYS 5.1.2600.3264 Patched at offset 326214.
17:44:00 - UXTHEME.DLL 6.0.2900.3264 Patched at offset 104746.
17:44:00 - UXTHEME.DLL 6.0.2900.3264 Patched at offset 320.
dolivas
WTF? Checking now. 320 is the checksum, it should have patched the other offset. I find it interesting that it did not list the offset it skipped.
HIVESYS should still work in SP3, all the relevant sections have not changed.
*EDIT: Shanola. Now I know why SFC is not working.
Updating, will re-edit this once complete.
*EDIT: Update complete. Re-download and check hashes. SFC_OS Patch corrected. (frakking typo. *sighs*)
HIVESYS should still work in SP3, all the relevant sections have not changed.
*EDIT: Shanola. Now I know why SFC is not working.
Updating, will re-edit this once complete.
*EDIT: Update complete. Re-download and check hashes. SFC_OS Patch corrected. (frakking typo. *sighs*)
just to report another kind of potentialy problematic peripheral... yet anothers might exist for sure...
modifying the _general_ USB poll rate is really a bad idea, break too much things...
but the possibility to change only for determined peripherals will be very great... harder to implement than a simple hex hack I suppose, however keep up the good work
modifying the _general_ USB poll rate is really a bad idea, break too much things...
but the possibility to change only for determined peripherals will be very great... harder to implement than a simple hex hack I suppose, however keep up the good work

Which is what my new addon is aiming for. It's not a _general_ modification to the USB poll rate. It's a filter driver that attaches to the USBPort.sys file and then enumerates each connected device and what speed it is and allows you to set a manual speed for each (or leave it at the default speed).
Hi Zacam, I don't know what is causing this, but I just made a new XP build using your latest patches, that I just downloaded today, and have an error coming up during Windows Install complaining about SFC_OS.dll missing. When setup completes I get load of windows complaining about missing files, with the result of windows being un-usable.
I used the latest RC1 of the Integrator, on a clean XP disc.
I used the latest RC1 of the Integrator, on a clean XP disc.
Hi Zacam, I'm using a fresh SP2 CD, updated with Ryans latest Update Pack.
The Integrator does not report any problems, and says that it has patched the file fine. I even made a new CD, and run your patches last, just in case anything was some how corrupting the .dll, but that ended with the same result.
18:53:02 - Extracting PatchAddon_SFC_OS_v13f.7z
18:53:02 - MD5 Hash = 4ECBEB61C14EEE84317323163FCFA90B
18:53:08 - Processing Multi-Patch: SFC_OS.DLL v1.3f Build Date: 01/01/2008
18:53:11 - Hex Editing Files
18:53:11 - SFC_OS.DLL 5.1.2600.2180 Patched at offset 60644.
The Integrator does not report any problems, and says that it has patched the file fine. I even made a new CD, and run your patches last, just in case anything was some how corrupting the .dll, but that ended with the same result.
18:53:02 - Extracting PatchAddon_SFC_OS_v13f.7z
18:53:02 - MD5 Hash = 4ECBEB61C14EEE84317323163FCFA90B
18:53:08 - Processing Multi-Patch: SFC_OS.DLL v1.3f Build Date: 01/01/2008
18:53:11 - Hex Editing Files
18:53:11 - SFC_OS.DLL 5.1.2600.2180 Patched at offset 60644.
8:53:11 - SFC_OS.DLL 5.1.2600.2180
how come ure file is so old, if ure using ryans pack u should have a newer version.
how come ure file is so old, if ure using ryans pack u should have a newer version.
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
That, my friend, is a bloody good point! I wonder whats going on? I'm not new to using the Integrator, or Ryans packs, and this is the first time that I have run in to problems.bober101 wrote:8:53:11 - SFC_OS.DLL 5.1.2600.2180
how come ure file is so old, if ure using ryans pack u should have a newer version.
It's not really rocket science starting the Integrator, pointing it to a fresh XP CD, then telling it what update pack to use, then pressing the magic button! I can't see what i'm doing wrong here! lol
woops,my bad.the_guy wrote:There is no post-sp2 version of sfc_os.dll unless you use SP3.
XP theme source patcher
patches/overwrites ure default xp visual resources
patches/overwrites ure default xp visual resources
You fixed it Sigi!Siginet wrote:Try adding this to the patch:
I386\SFC_OS.DLL|5.1.2600.2180|320|555B02|E2E002
It seems to be missing. Allthough... pechecksum.exe should patch the checksum anyways. I'll do some extra testing. in the meantime that should fix your problem.
I applied your patch, and Windows installs perfect!
*** UPDATE ***
It seams that RC1 of the Integrator is having the same trouble with other addons that are missing this additional hex edit info. From what I can tell, it's messing up the checksum of any file it hex edits, when an addon that is missing simular information to Zacams patch.
These are the list of missing files that Windows setup complains about now...
dmconfig.dll
dmadmin.exe
dmboot.sys
Last edited by Stimpy on Wed Jan 09, 2008 3:38 am, edited 1 time in total.
These patches are missing checksums:
UXTheme:
I have a feeling something on Stimpy's computer is preventing PECHECKSUM.EXE from working correctly.
UXTheme:
Syssetup:;XP SP2
I386\UXTHEME.DLL|6.0.2900.2180|113178|83EC1C568D4DE4|33C0C9C2040090
;KB319740 - RVM 1.2.0 - 2.0.4
I386\UXTHEME.DLL|6.0.2900.2523|104714|83EC1C568D4DE4|33C0C9C2040090
TCPIP:;KB887816 - SP2QFE - RVM 1.2.0 - 1.2.1
I386\SYSSETUP.DLL|5.1.2600.2530|210500|73|72
;KB894871 - SP2QFE - RVM 1.2.2 - 1.3.1
I386\SYSSETUP.DLL|5.1.2600.2659|211108|73|72
Allthough I have been testing and it seems to me that the integrator is properly patching the checksums with or without them in the patch addons.;SP2
I386\TCPIP.SYS|5.1.2600.2180|324386|0A|64
;KB913446 SP2GDR
I386\TCPIP.SYS|5.1.2600.2827|325026|0A|64
;KB913446 SP2QFE - RVM 2.0.3 - 2.0.6
I386\TCPIP.SYS|5.1.2600.2827|325446|0A|64
;KB917953 SP2GDR
I386\TCPIP.SYS|5.1.2600.2892|325026|0A|64
;KB917953 SP2QFE - RVM 2.0.7 - 2.1.5
I386\TCPIP.SYS|5.1.2600.2892|325574|0A|64
;KB916852 SP2QFE - RVM 2.1.6 - 2.1.7
I386\TCPIP.SYS|5.1.2600.2956|325574|0A|64
I have a feeling something on Stimpy's computer is preventing PECHECKSUM.EXE from working correctly.
Does anybody have any ideas as to what can stop PEChecksum.exe from working?
I thought maybe my virus scanner, so I disabled it, and still the same result.
I have no other problems with the computer, so I just dont understand this at all.
To Zacam, I'm sorry if i'm pissing you off, it's not intentional.
I thought maybe my virus scanner, so I disabled it, and still the same result.
I have no other problems with the computer, so I just dont understand this at all.
To Zacam, I'm sorry if i'm pissing you off, it's not intentional.
I can confirm that I can install Windows without missing file errors if I use Beta32 of the Integrator.
I only get missing file errors relating to failed hex editing with RC1.
I can reproduce the results every time. I have tried replacing PEChesum.exe with version 3 when I use the RC1 version of the Integrator, still with the same missing file errors during Windows Setup.
I use the PEChecksum.exe that comes with Beta32. So it seems that PEChecksum is working ok, and that there must be something that has changed between Beta32 and RC1 of the RVMI, that is causing this.
I only get missing file errors relating to failed hex editing with RC1.
I can reproduce the results every time. I have tried replacing PEChesum.exe with version 3 when I use the RC1 version of the Integrator, still with the same missing file errors during Windows Setup.
I use the PEChecksum.exe that comes with Beta32. So it seems that PEChecksum is working ok, and that there must be something that has changed between Beta32 and RC1 of the RVMI, that is causing this.
Today I'am run Ryan latest beta update pack221b3 and TCPIP.SYS file is not patched,is this version of TCPIP.SYS not supported yet?
22:35:43 - Hex Editing Files
22:35:43 - SFC_OS.DLL 5.1.2600.2180 Patched at offset 320.
22:35:43 - SFC_OS.DLL 5.1.2600.2180 Patched at offset 60644.
22:35:44 - TCPIP.SYS 5.1.2600.3244 No match at offset 304. Patch skipped.
22:35:44 - TCPIP.SYS 5.1.2600.3244 No match at offset 325958. Patch skipped.
22:35:45 - UXTHEME.DLL 6.0.2900.2845 Patched at offset 104746.
22:35:45 - UXTHEME.DLL 6.0.2900.2845 Patched at offset
22:35:43 - Hex Editing Files
22:35:43 - SFC_OS.DLL 5.1.2600.2180 Patched at offset 320.
22:35:43 - SFC_OS.DLL 5.1.2600.2180 Patched at offset 60644.
22:35:44 - TCPIP.SYS 5.1.2600.3244 No match at offset 304. Patch skipped.
22:35:44 - TCPIP.SYS 5.1.2600.3244 No match at offset 325958. Patch skipped.
22:35:45 - UXTHEME.DLL 6.0.2900.2845 Patched at offset 104746.
22:35:45 - UXTHEME.DLL 6.0.2900.2845 Patched at offset
Yeah it's not supported, the offset is wrong. i've used this tool instead :
http://www.lvllord.de/download.php?url= ... 23d-en.zip
http://www.lvllord.de/download.php?url= ... 23d-en.zip