"Paul Randall" <> wrote in message
news:%...
>
>>
>> There are probably simpler ways of doing this than the way I did it. I
>> converted the .chm file to a set of .html files (there are tools
>> available on the net for this eg 'chm decoder'), and then modified the
>> html links within them en masse to point to each other via script.
>>
>> CHM Decoder
>> http://www.gridinsoft.com/chm.php
>>
>> --
>> Jon
>
> I appreciate your responses, especially this one. A few years ago I
> disassembled the VBScript .chm to fix an error in a style that affected
> the readability of code samples on my computer, and reassembled it
> successfully. Did you reassemble your HTML into a single .CHM? Seems
> like I could manually compile a list of all the command line utilities and
> integrate all their .CHMs into a single large searchable CHM.
>
> -Paul Randall
>
I haven't done thus far, although it's a possibility. I've left it as a
folder full of html files - partly because I don't know how much I'll be
referrring to it, and partly because I'm lazy. There are tools available for
this purpose on the net if you want to try it, though, as I'm sure you're
already aware.
The Windows Server 2003 reference works a bit better under Vista. These are
the rough steps I took to extract the chm file...
Downloaded the 'Windows Server 2003 Administration Tools Pack' from
Windows Server 2003 Administration Tools Pack
http://www.microsoft.com/downloads/d...displaylang=en
After running the extractor, I then used the tool 'lessmsi' extract the
files from the .msi file
http://www.softpedia.com/get/Program...Ierables.shtml
(I had a version on hard disk already, but I believe that link is the same
one (?))
Made a shortcut to 'ntcmds.chm' amidst the extracted files.
--
Jon