Yes so I have just found out, normally we would use RTF but I don't think its a big deal, We'll just format it in a different way. Writing an RTF interpreter is PITA I know I had to do it once, took me almost a month!
Anyways something that I have moved on to is appending to the value returned by the VSTPluginsPath registry key. I need it to install to a folder under VSTPluginsPath. We don't "own" the VSTPluginsPath so there is other company's plugins that are installed there. What is generally done is you install your app to a folder under VSTPluginsPath and most DAWs(Digital Audio Workstation) include adding plugins found in subfolders of VSTPluginsPath.
Sorry to have to lean on you for stuff like this but I gotta get this thing out (note in my 12th hour, or so of development today). Its really late in the game for us to be changing install technology, but Inno has this recurring problem that we just can't get to work and there is no work around. I should rephrase that, its not actually Inno's fault, and its not actually MS's fault, MS says that it is up to Install developers to ensure this condition does not exist, and Inno says something about MS set the guidelines. The problem is the,-1 icon index issue (well documented) in the uninstall registry setting if you have an invalid icon index, it causes a gazillion lines in the add remove programs applet. I had this fixed once before by chicken wire and duct tape, and, I built our final install only to find out that its back. So thats why I am changing install technology, Its hard enough what I'm doing let alone not having confidence in the install technology, or having to go to a freaking news group for support. We release a lot of freeware so there is no funds for commercial install builders.