archive
/
windows-server-2003
mirror of https://github.com/selfrender/Windows-Server-2003
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3 Commits
1 Branch
0 Tags
1.5 GiB
 
 
 
 
 
 
Tree: 827363a95b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '827363a95b'
${ noResults }
windows-server-2003/inetsrv/iis/setup/imh6
Shaswata Das 827363a95b
Create LICENSE 		4 years ago
..
dirmake.txt commiting as it is 4 years ago
empty.txt commiting as it is 4 years ago
hardcode.lst commiting as it is 4 years ago
header.ddf commiting as it is 4 years ago
iisend.inx commiting as it is 4 years ago
iistop.inx commiting as it is 4 years ago
infutil.csv commiting as it is 4 years ago
makefile commiting as it is 4 years ago
makefile.inc commiting as it is 4 years ago
readme.txt commiting as it is 4 years ago
sources commiting as it is 4 years ago

readme.txt 

info on things to watch out for when adding a file to iis

---------------------------------------------------------



Adding a binary file to iis



1. You have to change iisend.inx

   as well as iismid_*.inx

   as well as iisend_*.inx to make the file install



2. you'll have to change nt\inetsrv\iis\placefil.txt to make the file binplace to the binaries dir

   or nt\inetsrv\iis\placefil5.txt if it's for the iis51 built only binaries



3. you'll have to add the file to hardcode.lst

   (so that postbuild info on this file is created and so that localization knows that it must localizes this file)

   localization looks in this file to determine which files it needs to localize that are outside of the cabs...



4. You'll have to modify nt\mergedcomponents\setupinfs\layout.inx

   and make sure that the file gets downloaded during winnt32.exe for the right SKU (and only for those sku's!)



5. if the file is in regard to inetmgr, then adminpak needs to get notifed of any changes!



6. if the file is another counter then, have to investigate if it's a ia64 counter that needs to be installed in the syswow64 directory on ia64 machines!