Hi again, Beagle and y'all
Well, time rolls on and we make some progress.
As far as midi-control (input keyboard > output keyboard/module) is concerned, I've 'discovered' a one-man (i.e. not big firm committee) software which some of you may already know of - OneManBand from
www.1manband.nl. It was created as an accompaniment software in the Yamaha style, but it has some extremely well-designed screens for playing and recording which I'm using simply as controllers while playing keyboard. In essence, one of them turns your computer keyboard into a 60+ one touch keypad for either single patches or what it calls 'multi-voices', which are assemblies of up to 4 patches with precision control of octave and effects.
So as far as control of my Yamaha K1 as output, I'm now a very happy bunny.
Next new horizon: I want to use a different software with a different synth (the Roland VSC soft-synth for the moment ) to play, in effect, backing tracks - nothing fancy - just those extra lines and parts that 8 fingers and 2 thumbs can't encompass live. I'm having some difficulty in persuading the particular software to access the synth's higher banks, despite having what (by provenance) should be a bona fide *.ins file for the synth.
So I'm trying to deepen my understanding of the whole *.ins 'thing', and - here comes the real question

- I'm a bit surprised how little tight information there is on precisely what the formatting rules for an *.ins are. It's such a widely used device, and it has the resouces of Sonar behind it (doesn't it ?), I'd expect to be able to find a definition file or sheet
for an *.ins file. I've found a couple of sites that look at the process, but in a curiously off-hand way - "this worked for me, but please don't come to me with your questions" kind of thing.
So, can any one point me at an authoritative summary of what must be included, in what order, with what formatting ? Please!