Hi

This is the way how to force windows setup to accept any modified dll

first let us take example UXTHEME.DLL

the orignal uxtheme

start from offset C3FE : EC81 EC80 0000 0056 578B

the modified uxtheme

at the same offset C3FE : EC33 F68B C6C9 C208 008B

that mean we are change the checksum and we have to correct it ( setup will not ask for digital sign during copying the files.Setup will ask for the checksum )

letus calculate :

( EC33 + F68B + C6C9 + C208 + 008B ) - ( EC81 + EC80 + 0000 + 0056 + 578B ) = 13B38

we want the checksum 4 digit long that mean the result will be = 3B39

you will find the checksum in dll file after this digits

0010000000020000050001000500010004000?000000000000?00?0000040000XXXX

? : this could be any digit

x : this the checksum of the file

the checksum in this file at offset : 130

and the checksum for orignal file is : 1633

the checksum for the modified file will be : ( 1633 + 3B39 ) = 516C

ok now change the checksum to the new value and compress it with any software that can make cab file ( I recommend WinACE or CapPack ) and replace it with the orignal file ...... good luck

is it good explain ? or ?

well it's good but it's been to long since i did that kind of math so I'm not sure I would be able to use it.

Hi

webmedic

You are talking to old rusty engine !

naw man used to know what is that hex but it's been so long and I have not used it for years.

It's not rusty it's just that you know some things that others dont.

maybe this will help http://www.delorie.com/store/hcalc/hcalc.zip

Hi

webmedic

I mean my head by rusty engine

I know. It's not so rusty if remember stuff like that.

believe me it's old and rusty and smoke comes from every where when I use it

Hi

This is the way how to force windows setup to accept any modified dll

<snip>

I'm still a little confused. Also I opened up the hacked SFC_OS.DL_ that you made and found that you stuck your name in at the end.

captdilly - Do you have to quote the whole ******* post just to make a one line comment?

Other than that, welcome to the forums.

And woot. Maybe now I can get Windows XP to properly copy my wpa.dbl file.

And woot. Maybe now I can get Windows XP to properly copy my wpa.dbl file.

some one trying to get around activtion here.

And woot. Maybe now I can get Windows XP to properly copy my wpa.dbl file.

some one trying to get around activtion here.

Not necessarily, wpa.dbl is an "already activated" file, and wouldn't work if it was copied to a system with different hardware. Copying this over saves having to activate again, as you are only given a number of times you are allowed to activate before phoning Microsoft Support for a telephone ID.

how many times is that?

i've activated it over 30 times

Don't know exactly but was sure it was below 8 or something. They must have changed it

It was my understanding that you could activate the same computer any number of times. It is only until you start changing hardware around that you run into a problem. There could be something I'm missing, though.