When you build the first version of an INF file for your device, the operating characteristics of the device are well known — even if you are building the INF file to test a hardware prototype on a Windows 95 machine.
For example. consider a fictitious piece of hardware, a SCSI Host Adapter which is built by Corporation X. The name of the device is the "CX2590 SCSI Adapter" and its Windows 95 device ID is *CX2590. There are no compatible device IDs for this device. All this information can be put into the INF file in a Manufacturer section.
The board has the following resource requirements:
All of this resource requirements information can be put into the INF file in one or more Log Config-type sections. Use the Infedit Log Config Sections folder to do this.
Corporation X is providing two files to support the device on one installation diskette:
All of the filename information and the source and destination information for copying the files can put into the INF file in one or more CopyFiles-type sections. Use the Infedit CopyFiles folder to do this.
Two entries must be made under the HKR key of the registry:
The information that causes these two registry entries to be made at installation time can all be put into the INF file in one or more Add Registry-type sections. Use the Infedit Add Registry Sections folder to do this.