Post by harkaz » Fri Sep 13, pm It failed The same error message appears Let's start from scratch I haven't used a kernel debugger so far For the moment, I'll work on the existing patch. I will try to fix this later. Post by bphlpt » Fri Sep 13, pm Isn't this the same kind of error that OnePiece mentions here?
Integration side effects not UpdatePack bugs : setuperr. Please note that in some rare configurations the integration of this addon could cause issues, so we don't suggest to use it. Post by harkaz » Sat Sep 14, pm Thanks for the tip, bphlpt, I'll check this later.
Is this normal? Currently working hard on the "Battery unsigned" problem. I'm making progress: I have been able to reproduce the problem I faced with the original patch with the new one I applied yesterday. I'm confident I'll find the solution. Can someone help me debug it to find its region in EXE? Note: This is the region which, if changed, causes all catalogs not to be recognised correctly. This seems to be independent of battery, however. Post by harkaz » Sun Sep 15, am Making progress: With a second patch, I managed to completely remove Messenger its catalog was manually removed by me in syssetup.
So it seems that this patch is required for some changes in syssetup. Now, the final step is removing the "Battery unsigned issue". Post by harkaz » Sun Sep 15, pm Fixed the "Battery unsigned" issue, will perfrom some additional checks before giving you the essential details. How to properly patch syssetup. Grab the original XP SP3 syssetup. Using a hex editor, like XVI32, open the dll file. Go to address offset 33B7B. Replace 74 with EB. Save changes to syssetup. Using modifype -c command or a similar tool fix the PE checksum.
To get rid of the "Battery unsigned" issue, you have to perform this additional step: Open the syssetup. Delete or comment the line with the battery. Save changes. Use the new syssetup. Known side-effects: Setuperr. In addition, SFC does not protect syssetup.
However, SFC does not report any problems after Windows installation. Waiting for your comments after testing the new patch. Time to return to my SP4 project. Post by Atarixl » Mon Sep 16, pm Thanks harkaz, nice to read your "adventures" every day. I still tested them with nLite and Dutch XP, but of course? Well, it kinda worked, but there were 2 errors. So I hope you'll tell us how we can build the SP4 when the time's right, from your last posts, I'm sure you will succeed! DLL patch steps Integrates with RyanVM Integrator 1.
Last edited by 5eraph on Tue Sep 17, am, edited 4 times in total. Post by harkaz » Tue Sep 17, am Thanks Atarixl. I'm working on MSN Explorer I haven't tested the removed Messenger yet. Is it working as it should? Post by 5eraph » Tue Sep 17, am Tested and working as intended following steps 7 and 8 of your patching guide.
Details added to my previous post. Post by harkaz » Tue Sep 17, pm A new challenge: While installing the service pack testing now this error message appears: Setup cannot copy the file syssetup. Let's see what's going on here Let's see if Gurgelmeyer has done sth on that The error GetCatVersion: Failed to retrieve version information from Probably patching it is not needed UPDATE 2: The error message: "A component's fil soes not match the information peresent in the verification manifest" seems to be related with update.
It is probably related with modified syssetup. Issue seems to have been fixed with a second patch I applied. Note that Gurgelmeyer's update. Messenger removed. The only thing I need to add for removal are the start menu messenger entries. After that, I'll test slipstreaming to SP3 installation media.
Is there an automated way to keep the update. Post by harkaz » Thu Sep 19, am Some instructions to create a self extracting executable. Extract the sfx from the KB for example package for the desired language: In the update package of the desired language, using a hex editor, search for MSCF string.
This the self-extracting "header for EXE file. The update. Any argument parsed to the sfx executable will be parsed to the update.
Using a hex editor, open the sp4. Go to the hex editor section. Change 20 to 60 and save changes. Optionally, add a manifest to require elevation each time the SP4 package is run. Post by tomasz86 » Thu Sep 19, pm harkaz Good luck with the project but I think you're spending a lot of time on things which have already been done Same instructions as the ones above were already posted by WildBill 3 years ago here , and here you can also find my automated version.
As for Gurgelmeyer and USP5 - he didn't modify any signed system files so no additional patching was necessary except for the installer. Post by harkaz » Thu Sep 19, pm Thanks! This was the source of theseinstructions, and thank you for mentioning it!
I posted it in this thread so that everything is one place. Now, I have an additional problem with update. No catalog file installs after SP4 installation completes.
Similar problems arise when slipstreaming the SP4 to installation media. I will try to create a new patch. Post by X » Fri Sep 20, pm Seeing if this will subscribe me to the thread. Interested in this project. Have nothing else to say except good luck.
Last edited by X on Sat Sep 21, pm, edited 1 time in total. Post by harkaz » Sat Sep 21, pm Thanks! Right now, I'm trying to fix some issues related with modified syssetup. If you know Assembly, I need your help here: After some examination of the svcpack.
This function fails with error code: 0xb No signature was present in the object. However, no "unsigned driver" dialog is displayed. This function is normally called before the SetupDiCallClassInstaller and sets the device installation parameters. Which flag of this function would cause such a behaviour? Class installers and co-installers must not display any UI if this flag is set.
Post by harkaz » Sat Sep 21, pm Changing the parameter to 0 changed absolutely nothing. Probably it requires some debugging. For the moment I'm working on the other errors I haven't checked. The GetCatVersion failure is a characteristic example. I don't know if it will solve the problem however. Post by harkaz » Sat Sep 21, pm It's very difficult to install all catalogs with a modified syssetup.
I'm abandoning the idea of using a patched syssetup. After all, a modified syssetup. I'm working on that. Post by harkaz » Sun Sep 22, am I put back the original syssetup.
That's very interesting Post by 5eraph » Sun Sep 22, am Are you getting any catalog files to install? Would it help to use a command line tool to install them, like SignTool?
Post by harkaz » Sun Sep 22, pm No catalogs are installed at all. I will test signtool. It seems that the issue is related with messenger removed INF files - the catalog nt5inf. Post by 5eraph » Sun Sep 22, pm You can find the latest known version of SignTool in an addon of mine. Post by 5eraph » Sun Sep 22, am. Post by harkaz » Sun Sep 22, pm.
Post by 5eraph » Sun Sep 22, pm. Post by harkaz » Mon Sep 23, pm. Post by ricktendo64 » Mon Sep 23, pm. Post by harkaz » Tue Sep 24, pm. Privacy Terms. Skip to content. Quick links. Last edited by harkaz on Thu Jan 13, pm, edited times in total. Post by harkaz » Tue Sep 10, pm Thanks for you support. I am organising the SP3 files and preparing to update them later. I have decided to remove MSN Messenger completely, because it's no more functional.
I will also replace MSN Explorer with its latest free release. The current version is Is this the latest free MSN Explorer version available? Post by harkaz » Wed Sep 11, pm Thanks for the tip.
I'll send them a PM later. Right now, I'm working on Windows Messenger removal. It's hard work after all. I have just finished modifying the update. Post by Kelsenellenelvian » Wed Sep 11, pm I have a "fixed" copy of sfxcab. Are you interested? It is what was used to build the usp5 for win2k. Please donate to Kelsenellenelvian. Post by harkaz » Wed Sep 11, pm Yes, why not? It may be useful Post by harkaz » Thu Sep 12, am I have a problem with editing syssetup.
It seems that the file is digitally signed. How do I patch the syssetup. Update: I tried copying the syssetup. I can't find a patched syssetup. Apply it to a Windows source, then pull the file from the source once patched. Post by harkaz » Thu Sep 12, pm Thanks for the link. I will retry on a real XP SP3 machine and update this post. But now Windows XP Setup shows messages about installing unsigned drivers. Is there something wrong I'm doing? Is there a way to avoid this? I also had this problem with a manual patch I did.
The only modification I've made is to comment out the msmsgs. To turn OFF the Digital signature do these steps:- 1. This will disable the Digital Signature. SIF and adding these lines is not a solution for a service pack, because it has to be as generic as possible. Kelsenellenelvian: It seems I have 3 options here: 1. Find a different patch for syssetup.
Don't modify syssetup. Abandon the project, as you did. I will start with number 1 to see if I can do something. A kernel debugger may be useful. Have you tried this before? I will start working on it. My goal right now is to understand how pSetupVerifyFile works and change its parameters, not to prevent calling it.
Code: Select all 1. The Setuapi. Post by bphlpt » Fri Sep 13, pm It's been a looooong time since I've done assembly work, and I could be totally wrong, but it seems like it might be easiest to just change the jz to a jmp, ie always jump, not just if zero.
Unless I'm missing something? Cheers and Regards. Post by harkaz » Fri Sep 13, pm I will try your suggestion bphlpt, this seems to be the solution. However, I have a practical problem: How do I get the hex code machine code after changing jz to jmp?
This is essential to know in order to patch the syssetup. Should I go trial and error? I'm testing it right now. Will report back soon. Post by bphlpt » Fri Sep 13, pm Of course if the file you patched is also digitally signed, then Good luck! Post by harkaz » Fri Sep 13, pm It failed The same error message appears Let's start from scratch I haven't used a kernel debugger so far For the moment, I'll work on the existing patch.
I will try to fix this later. Post by bphlpt » Fri Sep 13, pm Isn't this the same kind of error that OnePiece mentions here? Integration side effects not UpdatePack bugs : setuperr. Please note that in some rare configurations the integration of this addon could cause issues, so we don't suggest to use it. Post by harkaz » Sat Sep 14, pm Thanks for the tip, bphlpt, I'll check this later.
Is this normal? Currently working hard on the "Battery unsigned" problem. I'm making progress: I have been able to reproduce the problem I faced with the original patch with the new one I applied yesterday.
I'm confident I'll find the solution. Can someone help me debug it to find its region in EXE? Note: This is the region which, if changed, causes all catalogs not to be recognised correctly. This seems to be independent of battery, however. Post by harkaz » Sun Sep 15, am Making progress: With a second patch, I managed to completely remove Messenger its catalog was manually removed by me in syssetup.
So it seems that this patch is required for some changes in syssetup. Now, the final step is removing the "Battery unsigned issue". Post by harkaz » Sun Sep 15, pm Fixed the "Battery unsigned" issue, will perfrom some additional checks before giving you the essential details. How to properly patch syssetup. Grab the original XP SP3 syssetup. Using a hex editor, like XVI32, open the dll file. Go to address offset 33B7B. Replace 74 with EB.
Save changes to syssetup. Using modifype -c command or a similar tool fix the PE checksum. To get rid of the "Battery unsigned" issue, you have to perform this additional step: Open the syssetup. Delete or comment the line with the battery. Save changes. Use the new syssetup. Known side-effects: Setuperr. In addition, SFC does not protect syssetup. However, SFC does not report any problems after Windows installation. Waiting for your comments after testing the new patch.
Time to return to my SP4 project. Post by Atarixl » Mon Sep 16, pm Thanks harkaz, nice to read your "adventures" every day. I still tested them with nLite and Dutch XP, but of course?
Well, it kinda worked, but there were 2 errors. So I hope you'll tell us how we can build the SP4 when the time's right, from your last posts, I'm sure you will succeed! DLL patch steps Integrates with RyanVM Integrator 1.
Last edited by 5eraph on Tue Sep 17, am, edited 4 times in total. Post by harkaz » Tue Sep 17, am Thanks Atarixl. I'm working on MSN Explorer
0コメント