home *** CD-ROM | disk | FTP | other *** search
- #
- # format for txtsetup.oem.
- #
- # General format:
- #
- # [section]
- # key = value1,value2,...
- #
- #
- # The hash ('#') introduces a comment.
- # Strings with embedded spaces, commas, or hashes should be double-quoted
- #
-
-
- [Disks]
-
- # Your driver distribution may include one disk or many disks.
- # This section lists the disks in the distribution set.
- #
- # <description> is a descriptive name for a disk, used when
- # prompting for the disk. This should be a quoted string,
- # like "Company XYZ Mouse Disk #1"
- #
- # <tagfile> is a file whose presence allows setup to recognize
- # that the disk is inserted. This should be a path from the root,
- # but may not include a drivespec. Example: \xyzmou1.tag
- #
- # <directory> is where the files are located on the disk. This should
- # be a path from the root but may not include a drivespec.
- # Example: \ (root directory)
-
- d1 = "NCR SDMS 53C400A SCSI Miniport -- HP400NT-3.00.02",\Sdms400a.tag,\
-
-
- [Defaults]
-
- # This section lists the default selection for each component
- # supported by this txtsetup.oem. If a line is not present for
- # a component, the default is the first item in the [<component_name>]
- # section (see below).
- #
- # <component_name> is one of computer, display, keyboard, mouse,
- # "keyboard layout", or scsi.
- #
- # <id> is a unique (within the component) string to be associated
- # with an option.
- #
- # Example:
- #
- # mouse = xyzmou1
- #
-
-
-
- [SCSI]
-
- # This section lists the options available for a particular component.
- #
- # <id> is the unique string for the option. For the computer component,
- # if this string ends in "_up", setup copies the uniprocessor kernel;
- # if this string ends in "_mp", setup copies the multiprocessor kernel;
- # if it ends in neither, the results are unspecified (you may
- # get either kernel).
- #
- # <description> is a text string, presented to the user in a menu.
- #
- # Example:
- #
- # [mouse]
- # xyzmou1 = "Company XYZ Mouse type 1"
-
- Sdms400A = "NCR SDMS 53C400A SCSI Miniport -- HP400NT-3.00.02"
-
-
-
- [Files.SCSI.Sdms400A]
-
- # This section lists the files that should be copied if the user
- # selects a particular component option.
- #
- # <file_type> is one of driver, port, class, dll, hal, inf, or detect.
- # (see descriptions below).
- #
- # <source_disk> identifies where the file is to be copied from, and must
- # match en entry in the [Disks] section.
- #
- # <filename> is the name of the file. This will be appended to the
- # directory specified for the disk in the [Disks] section to form the
- # full path of the file on the disk.
- #
- # <keyname> is the name of the key to be created in the registry services
- # list for this file, if the file is of type driver, port, or class.
- # This value will be used to form [Config.<keyname>] section names
- # (see below).
- #
- # Example:
- #
- # [Files.mouse.xyzmou1]
- # port = d1,xyzmou1p.sys,xyzmou1p
-
-
- driver = d1,Sdms400a.sys,Sdms400A
-
-
-
- [Config.Sdms400A]
-
- # This section specifies values to be set in the registry for
- # particular component options. Required values in the services\<keyname>
- # key are created automatically -- use this section to specify additional
- # keys and value to be created in services\<keyname>.
- #
- # <key_name> is relative to the services node for this device.
- # If it is empty (ie, ""), then it refers to the services node itself.
- # If specified, the key is created.
- #
- # <value_name> specifies the value to be set within the key.
- #
- # <value_type> is a string like REG_DWORD. See below.
- #
- # <value> specifies the actual value; its format depends on <value_type>
- # See below.
- #
- # Example:
- #
- # [Config.xyzmou1p]
- # value = "",MyValue,REG_DWORD,0
- # value = NewKey,NewValue,REG_SZ,"this is a value"
-
-
- #value = <key_name>,<value_name>,<value_type>,<value>...
-
-
-