🚀 go-pugleaf

I've just learned (the hard way - by trying it, and the harder way - by waiting
on hold to talk to a MS service engineer :-), that the Setup Toolkit's file
specification program (disklyt) does not preserve the directory structure of
the source files when it constructs the intermediate .LYT file. The inconcei-
vably short-sighted consequence of this flaw is that all files in a distri-
bution go into one directory on installation.

MS told me that there was no fix for this other than hand-coding the .LYT file
to prepend the appropriate path to each entry. Since I have ~250 files in this
distribution, I'm thinking that it's not worth the trouble, especially since
I will never be able to use the offending disklyt program to update my
installation since it'll wipe out all my work.

The question is: Is there some other workaround? Has someone written a layout
front-end that'll generate .LYT files that aren't brain dead?

This doesn't seem like a very hard problem to code. I'd really be happy to
dump MS's front-end anyway, since it's dog-slow (486/33 with 20MB RAM - is
Visual Basic this much of a pig??).

I find it hard to believe that MS put as much (apparent) work into the Setup
Toolkit only to distribute it with a brain-dead weak-link front-end processor.
If I don't get any workarounds and I do get enough encouragement to write one,
I'll tackle doing one myself.

Any ideas/opinions?
Jeff

 
---
         ___
        /  /          | Jeff Perry, HP Labs - Medical
HEWLETT/hp/PACKARD    | E-Mail: jeff@hpl4-d or jeff_perry@hplabs
      /__/            | Telnet: 415-857-6651



-- 

         ___
        /  /          | Jeff Perry, HP Labs - Medical
HEWLETT/hp/PACKARD    | E-Mail: jeff@hpl4-d or jeff_perry@hplabs