[adding modified shell files to an installation CD (batchscript availab]

update:

i have created an neat batch file that replaces the 2k style icons with there XP equalivant.

included in the zip file:

input (copy your explorer.exe, shell32.dll, user32.dll and mydocs.dll inside this folder)

output (inside this folder you will find the resulting files after the patch)

output/i368 (same as above but packed as cab files so you can include them in windows setup folder)

source (the icon files itself are inside this folder)

make.bat (run this batch to patch the files inside input)

not included but needed:

ResHacker.exe (http://www.angusj.com/resourcehacker/)

modifyPE.exe (http://w-server.newram.wh.tu-darmstadt.de/freeware/windows/system-tools/xpisobuilder/modifyPE.exe)

GoRC.exe (http://www.jorgon.freeserve.co.uk/)

EDIT: woops still to big to upload here, ask me if you want it i will email it to you

[adding modified shell files to an installation CD (batchscript availab]

Do you think you can get alpha blending to work? This would be great for 2k.

no that is something only XP can do, the 2000 shell is just not up to the job (afaik)

should be something in explorer.exe or another system file but i dont think we can reshack or hexedit it.

i once tried the xp explorer.exe inside windows 2000 but it would need a lot of XP dlls 2k does not have.

but i agree it would be great

[adding modified shell files to an installation CD (batchscript availab]

How is it coming with your files?

im not at home today (visiting gramps).

when i get back i will slipstream sp5 and install on vmware (via RIS cos im lazy)

after that i will edit the system files again

all very easy but i think all those icons inside shell32.dll can be a pain in the a**

but that is nothing compaired how long it took to remove all XP alpha transparant versions of the icons

but (thank god) i still have the source files (i will zip them and add them to the topic maybe somone likes them)

btw: anyone knows some more dll's containing icons that i should replace with XP ones?

[adding modified shell files to an installation CD (batchscript availab]

hope u haven't used any other version of files,,

i think not, but since i still have to slipstream SP4 on the cd i need to re create the files anyway.

or uSP5 to be exact

ill post my results asap

[adding modified shell files to an installation CD (batchscript availab]

sth wrong with ntoskrnl.exe,,

be sure u have just changed the bitmap but not alter with version and HEX editing.

i only replaced bitmap 1 with reshack, i assume thats ok?

[adding modified shell files to an installation CD (batchscript availab]

It alters the checksum

modifyPE.exe

thanks

@echo off

modifype shell32.dll -c

modifype user32.dll -c

modifype mydocs.dll -c

modifype explore.exe -c

modifype ntoskrnl.exe -c

mkdir output

makecab shell32.dll output/shell32.dl_

makecab user32.dll output/user32.dl_

makecab mydocs.dll output/mydocs.dl_

makecab explorer.exe output/explorer.ex_

makecab ntoskrnl.exe output/ntoskrnl.ex_

pause

is this batch file up to the job?

[adding modified shell files to an installation CD (batchscript availab]

You did good. But after altering the dll's and before makcab you should run modifype

modifype shell32.dll -c

thanks i will try that!

but what exactly does modifype do?

EDIT: is this a tool included by windows? cos i dont think i have it

[adding modified shell files to an installation CD (batchscript availab]

hello everyone!

i have finaly managed to make a shell32.dll replacement for windows 2000 (it includes the XP icons without the alpha transparant versions) i did the same for user32.dll mydocs.dll and explorer.exe.

and next to that i have a modified bootscreen inside ntoskrnl.exe

for testing i copied them all trough the Recovery Console without any problems.

2000 looks pretty cool and modern now (without losing processor speed on window blinds and software like that)

ive tried to add those files to a windows setup directory.

using makecab and replaced the excisting shell32.dl_ user32.dl_..... files

at first it wont work (i needed to change the checksum of 2 of them) but after that the setup will copy them during the first stage of the windows setup.

but for some reason windows wont boot (it will freeze during the bootscreen).

so my question is what went wrong?

is there a better way of adding replacement system files?

is there more then only a checksum i should worry about?

oh and if anyone would like to have the modified files for there own use just tell me

ive added a screenshot of how it looks.

[Variables in setup.iss]

i was wondering if i can use these kind of variables in my InstallShield awnser file.

now i have this

[{76542EE3-5849-11D2-9C18-00609707C0FF}-SdAskDestPath-0]

szDir=C:\Program Files\ISS\BlackICE

can i do something like this?

[{76542EE3-5849-11D2-9C18-00609707C0FF}-SdAskDestPath-0]

szDir=%ProgramFiles%\ISS\BlackICE

some help please?

[Foxit batch installer the easy way :)]

ah thank you for the edit

[Foxit batch installer the easy way :)]

just found out how to use ftype.exe and assoc.exe.

they are a part of windows so everyone has them

@echo off
mkdir "%systemdrive%\Program Files\Foxit Reader\"
copy "Foxit Reader.exe" "%systemdrive%\Program Files\Foxit Reader\Foxit Reader.exe"

FTYPE FoxitReader.Document="%systemdrive%\Program Files\Foxit Reader\Foxit Reader.exe" "%1"
ASSOC .pdf=FoxitReader.Document

this will create a Foxit Reader folder in Program Files.

next it will copy the foxit exe to it.

and then it will use ftype.exe and assoc.exe to make it default for pdf files

[Running wihu After Installation.]

You should include a command line options like:

WIHU.exe /skipsettings /INI="install.ini"

or

[GUIRunOnce]

%Systemdrive%\install\wihu.exe /INI="install.ini"

if i do not set the ini path it will take install.ini lacated in the same folder (i tried)

Another Point,

Are the applications in the same folder of WIHU?

set the right variable at the ini file

the files are in a subfilder called Software like:

"X:\$OEM$\$1\install\Software"

i will set the paths in the ini file like this:

command=%WIHU%\Software\Winamp.msi

will this work or is there a better way?

[Running wihu After Installation.]

I want to make a Windows 2000 cd that has extra software on it.

Just to make sure is this going to work:

X:\I386\winnt.sif:

[Unattended]
OemPreinstall=Yes

[GUIRunOnce]
%Systemdrive%\install\wihu.exe

Wihu locations:

X:\$OEM$\$1\install\wihu.exe

X:\$OEM$\$1\install\install.ini

X:\$OEM$\$1\install\install.ini:

[settings]
skipsettings=1
(...)

should this work with only those few lines in winnt.sif?

if not what does a minimal winnt.sif need?