Jump to content

Customing a digitally signed files of I383 folder


Recommended Posts

Posted

Hi there.

After some researches on the web, and by myself, I achieved what I was aiming at.

Customing a digitally signed files in I383 folder

When I tried to replace original WINLOGON.EX_ by the modified one, Every time copying error were prompting during the XP dos-setup ( unable to copy this files!)

I believe XP setup is checking for every modification made on the file, for each bits modified.It enable to recognizes the file header and pop an error message up!

[GUIDE] IT WORKS with XP HOME SP1

STEP 1

Find in I383 folder, the file you what to modify, then decompress the file (e.g WINLOGON.EX_) with "expand" command.

SYNTAX : expand C:\WINLOGON.EX_ C:\WINLOGON.EXE

Now you get your EXE-file

STEP 2

Custom your EXE-file as you wish, then is coming the big trick. USE UPX PACKER or whatever PAKERS(aspack,armadillo,etc...)

You can find these kind of PAKERS on google.(Don't Worry :hello: )

STEP 3

When your file is UPX-Packed, Just compress your file again with "makecab" command

SYNTAX : makecab C:\WINLOGON.EXE C:\WINLOGON.EX_

Now you get your EX_ file.

Replace with the one in I383 folder.

STEP 4

You mustn't change anything in txtsetup.sif, dosnet.inf, layout.inf files, It's working as well.

Build your bootable ISO then LOAD it in Virtual PC 2004 to test it

IT SHOULD BE WORKING!!!

EXTRA: I noticed some files are not protected, like wpa.dbl, SFC_OS.dll you can replace without following these steps.

If you have found a quicker way to do it, post it, Because I've been looking for it since days.

Regards Guys.

@xie


Posted
Customing a digitally signed files in I383 folder

it's i386 rather (intel 386, as in, the old pre-486 CPU), and winlogon.exe is NOT digitally signed! Also, there is no such thing as a fix for signed executables. You just couldn't re-sign them yourself as the original signer anyhow (that's the whole point of it)

When I tried to replace original WINLOGON.EX_ by the modified one, Every time copying error were prompting during the XP dos-setup ( unable to copy this files!)

That's merely because it checks a checksum in the PE header, to see if the file is corrupted or not. If you edit an executable and don't fix the checksum in the header, it'll give you those "unable to copy file" messages indeed, because it assumes it's corrupted.

Using UPX to compress it isn't so much a fix as a side effect. It just happens that UPX fixes the checksum in the header after writing the packed executable. The real fix is merely writing the proper checksum in the PE header, and it just happens that there's a few programs that do just that (I'll even share mine in a few days, open source and all). I wouldn't really want to run every file through an exe packer just for that.

BTW, why in the world would you use the ancient SP1?

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...