My custom logonui.exe and ntoskrnl.exe

[jim-p]

Today I decided to give my UA xp cd my personal signature.

Here's what I did step by step (for ntoskrnl.exe):

Found ntoskrnl.ex_ in the I386 directory.

Extraxted ntoskrnl.exe from inside it using 7zip.

Opened it with Reshacker.

Moved to BITMAP ->1-> 1033 folder.Right click-> replace resource-> open file with new bitmap and browsed to my boot picture.

The picture already is a 640*480*8 (16 colors) bitmap made in PS.

Replaced it, showed up well in Reshacker so File ->Save.

Cmd prompt, modifype ntoskrnl.exe -c, checksum done (have a nice day message).

Then makecab ntoskrnl.exe so as to compress it.Made ntoskrnl.ex_ as output so I placed it back to the I386 folder.

Then made a bootable iso with Nero (as allways).

Started up my VPC ...text setup ...reboot ...AND THAT USELESS DEFAULT XP BOOTSCREEN POPS UP!!

WHYYYY!!?!?!?!?

Installed fine, but the bootscreen remains the default one,even after several reboots.

Same (or almost same) proccess goes for the logonui.exe.

And again NOTHING.BLANK.AS IF I HAVE NOT MODIFIED THE FILES.

Suggestions anyone?

ps. My custom winntbbu.dll works perfectly though!

[Ctrl-X]

Try the XP LogonUI & Boot Screens subforum.

[dirtwarrior]

There is an ntoskrnl.exe in driver cab too

[mazin]

If you use nLite on XP-SP2, there's ntoskrnl.exe in SP2.cab but not in Drivers.cab!

If you don't use nLite, ntoskrnl.exe exists in both CABs.

In addition to Drivers.cab and SP2.cab, if you have SP1.cab, there's ntoskrnl.exe; too!

And you, SAFELY, need to hack 4 files:

ntkrnlmp.exe

ntkrnlpa.exe

ntkrpamp.exe

ntoskrnl.exe

[rajesh.kumar]

this would not work out if u use the files from the distribution cd. first install xp and do all kind of updates and take the required files from xp dir in ur hdd and do the modifications, modifype them and makecab, replace the files in the xp distribution with these modified files. this way i have made it work before.

[jim-p]

Thank you all for your interest.

I had no idea that the same file is located inside driver.cab!!

That rises one more question though:WHY did setup reject my file and used its own?

Is it SFC related?

And why bother reshacking all 4 nt*.exe files since VPC uses only one?

[mazin]

Even if I turned SFC off, Setup leaves the hacked file in i386 and uses the one in Drivers.cab!

This is why I cleaned all the house.