Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

How to make a IE ins Branding file?

- - - - -

  • Please log in to reply
7 replies to this topic

#1
seamanyin

seamanyin
  • Member
  • 9 posts
  • Joined 31-October 04
I want to branding IE with a ins file using [BRANDING] in WINNT.SIF.But I failed to use IEAK. :huh: ?Someone give me some suggestions or some thread to learn how to use IEAK.
er....Maybe some examples would be better.The reference with it is so difficult.
Thanks.


How to remove advertisement from MSFN

#2
rdalling

rdalling

    Member

  • Member
  • PipPip
  • 152 posts
  • Joined 29-March 04
the inf files need to exist in the root of $oem$


Winnt.sif
[Branding]
    BrandIEUsingUnattended=No
    IEBrandingFile=install.ins


R

#3
seamanyin

seamanyin
  • Member
  • 9 posts
  • Joined 31-October 04
O I think that I Know that.
The problem is how to make the install.ins?
Do you have a example?

#4
rdalling

rdalling

    Member

  • Member
  • PipPip
  • 152 posts
  • Joined 29-March 04
You need to download the IEAK administration kit from microsoft.

#5
seamanyin

seamanyin
  • Member
  • 9 posts
  • Joined 31-October 04
Should i use the profile manager or the wizard?

#6
keytotime

keytotime

    Advanced Member

  • Member
  • PipPipPip
  • 400 posts
  • Joined 05-October 04
The wizard

#7
seamanyin

seamanyin
  • Member
  • 9 posts
  • Joined 31-October 04
But in my concept,the wizard would make a IE install package.Don't we only need the install.ins file?

#8
keytotime

keytotime

    Advanced Member

  • Member
  • PipPipPip
  • 400 posts
  • Joined 05-October 04
it will create a install folder, inside the folder there will be two directories, one called ins. Browe that directory until you find the install.ins file. Copy the whole directory into $oem$.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users