Bob,

After a little trial and error, and several "can't open the .col file" complaints. I changed the first section of a dave.col which was a copy of the msdnvs6a.col to:

<TitleString value="MSDN Library Visual Studio 6.0"/>
<FolderOrder value=0/>
<Folder>
<TitleString value="Dave Welcome to the MSDN Library"/>
<FolderOrder value=1/>
<Folder>
<TitleString value="=foxhelp"/>
<FolderOrder value=1/>
<LangId value=1033/>
</Folder>
<Folder>
<TitleString value="=dshelp"/>
<FolderOrder value=2/>
<LangId value=1033/>
</Folder>
<Folder>
<TitleString value="=inet98"/>
<FolderOrder value=3/>
<LangId value=1033/>
</Folder>

Created a new shortcut to use my .col file and started it up. It puts VFP at the top and added the inet98 to the file. It worked. It also took a long time to genereate a dave.chw file the first time I clicked on the inet98 topic. I was unsucessful at ever getting it to try and add a .htm file into the structure. So it may require only chm files in there. I also couldn't get it to add the WAB.CHM file so it may require a CHM generated by a later complier version too?

Make sure you set the FolderOrder properly.

>>Bob,
>>
>>Nothing official here, but try renaming the MSDNVS6A.CHS file to zMSDNVS6A.CHS, then edit the MSDNVS6A.COL file and restart MSDN it accepted my changes to some of the titles and regenerated the CHS file.
>>
>
>You're right... it does generate a new CHS, but, the topic/folder I added still doesn't show up.
>
>BOb