PRACC9309: Custom Setup Error: “Badly Formed File Description”
PSS ID Number: Q104824 Article last modified on 09-30-1993
1.10 WINDOWS
| The information in this article applies to: |
| - Microsoft Access Distribution Kit version 1.1 |
SYMPTOMS
The following error message “The INF file contains a badly formed file description line” occurs when you create a custom .INF file and insert spaces on either side of the equal sign (=), for example: [Single User] 1, ZMAIL.HL$, RENAME = ZMAIL.HLP, DEST = <math display="inline">(AppPath) 1, ZMAIL.IN</math>, RENAME = ZMAIL.INI, DEST = $(WindowsPath)
RESOLUTION
Remove all spaces before and after equal signs in the custom .INF file. The example given above would appear as follows: [Single User] 1, ZMAIL.HL<math display="inline">, RENAME=ZMAIL.HLP, DEST=</math>(AppPath) 1, ZMAIL.IN<math display="inline">, RENAME=ZMAIL.INI, DEST=</math>(WindowsPath)
STATUS
Microsoft has confirmed this to be a problem in the Microsoft Access Developer’s Kit version 1.1. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Additional reference words: 1.10 Setup ADK KBCategory: KBSubcategory: StpBlddsk StpProb Copyright Microsoft Corporation 1993.
