Jump to content

WinXP SP1.0a Czech setupapi.dll hack?


caps_buster

Recommended Posts

To be able modify the Windows install CD files, one need to hack the setupapi.dll file. There are well explained and documented where and what to modify for Windows 2000 SP4, Windows XP SP3 and Windows 2003 SP2, thanks to fdv: http://www.vorck.com/windows/edit-setupapi.html

However the guide cover only the there mentioned Windows versions, not the one I want to use. Searching for the "90 90 90 90 90 8B FF 55 8B EC 8B 45 2C 33 C9 3B C1" as Fred Vorck suggested turn out of no result in my version of the file.

So, what I need is some help how to do this. I cannot find the byte sequence for the XP SP3 version - 8B FF 55 8B EC - but I can found the byte sequences (4 cases of them) as for the Windows 2000 SP4 setupapi.dll file = 55 8B EC FF 75. When I changed the second one of them (as in Win2k SP4 version of the file), at the offset 4F17D (not same as for Win2k SP4 version of the file) it does not work at all. The install went file, but hand on on network components, at about 60% forever.

I did use the modifyPE -c on the file after I modified it to make the setup working...

When I pushed harder to make sure it is the modification fault, then I tried remove the "_X" that cause the setup to check the files:

Windows chokes on some modified INF files like LAYOUT is because it checks file sizes against the list in the LAYOUT.INF file of any file that has an _X in its line. In other words, if we open LAYOUT.INF and TXTSETUP.SIF, and find the line of that file, it reads:

layout.inf = 2,,244801,,,,_x,20,0,0

If you want to modify this file, delete the _X!

layout.inf = 2,,244801,,,,,20,0,0

...the setup immediatelly, after the first reboot, started to complaining about modified files that are "serious problem" and setup "cannot continue". That means the patch I made to the setupapi.dll is not working :( So, I asking if anyone know the correct byte sequence or have some ideas to try this version of the file. Thanks!

I got recommended this:

Search for pattern 68 34 09 00 00 (is only one) ... replace him with 33 C0 C2 30 00.

...however it only make the install crash. The install with the original file complained, when I used modified LAYOUT.INF, syssetup.inf, TXTSETUP.SIF and WINNT.SIF files. And did not continue. When I used the patched setupapi.dll file, then it just (at the moment when with the original setupapi.dll it just complained about the files - after the copy and the 1st reboot, in the nicer WinXP install GUI) crash. Sadly.

Anyone can help?

Link to comment
Share on other sites


Sometimes they return :w00t::

Caps (can I call you "Caps"? :unsure: )

have you actually checked the reply by dencorso in the above?

Just to try and keep everything as together as possible :angel :

jaclaz

Link to comment
Share on other sites

Here ya go to keep it even MORE together, seeing as how Caps mentioned WINNT.SIF ;)

I am working on providing a WONDERFUL response to your assertions over there. :yes:

You just LOVE to argue, don't you? (O-god, another one!)

Link to comment
Share on other sites

Sometimes they return :w00t::

Caps (can I call you "Caps"? :unsure: )

have you actually checked the reply by dencorso in the above?

And I've found it interesting that lately when "Caps" has asserted that something was either "wrong" or "doesn't work", it has often ended up that either his machine or his input was at fault. And then he "blamed" us for not catching "his" mistakes. I wonder why he's not getting much help. Hmmmm.

Cheers and Regards

Link to comment
Share on other sites

Of course there is a reason why I do prefer Win XP SP 1.0a - because they did not overrule the hosts files for M$ servery, for just one example out of many. However the problem is the impossibility to make a altered install CD.

And reading this thread make one wonder, why people that are asking are expected to know already the answer :) And when finding and pointing out the wrong suggestion they are bashed even more, lol...

PS. should be worth to mention, that I tried to fix the reboot during install with such modified DLL by modifyRE -e on the hacked dll, so it did not appear corrupted to the OS itself. But no luck. Perhaps better will be to combine both hacks...?

Edited by caps_buster
Link to comment
Share on other sites

Caps,

dencorso, who usually provides very correct advice :thumbup , replied you almost 4 (four years ago) here:

BTW, the reason you didn't find where to patch is because the SP1a file doesn't need to be patched... :whistle:

Besides NOT having the decency to reply AND thank him for the assistance he provided :realmad: (NO matter if useful or not) you simply CANNOT go on like this :no: .

dencorso provided you with a piece of info, which is either accurate (most probably :yes: ) or it is not. :ph34r:

Have you §@ç#ing TRIED following it? (simple try using the UNmodified SP1.0a .dll?)

WHAT were the results?

jaclaz

Link to comment
Share on other sites

He$$ NO, they didn't try it, no more than the ARGUING and IGNORING that was done HERE! "Doesn't work" and "I did it different because I didn't want what you gave but I only asked for and now such-and-such doesn't work" and so on and so on...

And WTH do you MEAN by

they did not overrule the hosts files for M$ server
Mine works fine. Googling this
"windows xp" hosts file not working

for an inkling of what you mean.

OHHHH! I mean AHAHHH! Google

"windows xp" hosts block WGA

You mean the "AntiWGA" MS BLOCKING "technique"! What, you have a BOGUS XP, i.e. Volume version using Blacklisted Key/Keygen? And the SP2 changed all of that? Gotcha! ;)

Caps, you're biting off more than you can chew. Indeed, you're biting on the WRONG THINGS after being SPECIFICALLY told what to bite on!

Link to comment
Share on other sites

I have no idea, what do you mean by the AntiWGA, however all that is not related at all of the original question, and that it - how to make the Win XP SP 1.0a czech version of setupapi.dll file work with modified install files. So either you have something to say about this, or you don't.

Link to comment
Share on other sites

ONE-MORE-TIME!!!! Your question has been.....

ANSWERED!

re - AntiWGA (maybe, maybe not)

they did not overrule the hosts files for M$ server
What do you MEAN by this? Other than AntiWGA, there's absolutely NO reason not to use SP3! Edited by submix8c
Link to comment
Share on other sites

Unfortunately, the answer (that the file not need patching) is likely to be a FALSE one.

When installing, it keep getting stuck on the message that the Win install file is wrong and it's signature is missing. It give this code of error: 800b0100 ...

So perhaps the file really does not need to be patched, but the install does not work when the files are modified :( So I presumed that they had to be patched in order to make it work... Especially that I did not find anything special (like a signature) in the end of the file LAYOUT.INF. In the file TXTSETUP.SIF, there is, at the very end, something that the Notepad2 "translate" as "SUB" - a one pace char with there letters and inverted... And even I copy and paste it exactly from the original file, it still come up with this error message and at it the whole install end. Or should I say get stuck?

That led me to believe that something shall be done with the setupapi.dll file.

This way it look:

TXTSETUP_SIF_end.png

Edited by caps_buster
Link to comment
Share on other sites

I hope to help matters by chiming in. Maybe.

Caps, you're going to get a LOT more mileage out of going to SP3. I mean, there's no way around the fact that your OS will be a lot less buggy.

I made that edit to the DLL years and years ago and I forget what routine I changed... God I can't even remember the decompiler I used on SP2's dll to find out the sequence.

if you want to do this, it's best to move to SP3, and if you are worried about Microsoft hard-coding themselves into the OS and overriding the HOSTS file, then edit dnsapi.dll to your liking. You'll block your own ability to reach microsoft.com for downloading updates if you do it wrong (you can always put them on a USB from another system) but the bottom line is that you will solve your problem, you'll be happier, you won't need to ask this anymore, you won't be fooling with a "dead" service pack anymore... there are only benefits. There is no solid reason not to switch, my friend. But even if you choose not to, it's been too long and I can't help, I don't have the tools anymore or the time to spare to do the same thing for SP1a.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...