Category : Windows 3.X Files
Archive   : QDHELP30.ZIP

Output of file : WHATSNEW.WRI contained in archive : QDHELP30.ZIP
1¾«¹/aqqqqqrWelcome to QDHELP version 3.0

This file contains information on new features and fuctionality that
have been added to QDHELP. Also found here are any known problems
with backward compatibility.

New Fuctionality included in this release:

Rev 3.0
Added command, the /glossarytopic command has been added.
This command allows you to define a topic which will automatically
be placed in a glossary generated by QDHELP.

A new file XXXXX.DB can be generated when QDHELP is run. This
file contains a database of information on each topic in your help file.
It is an Ascii file and can be viewed using a editor. The real purpose
of the .DB file is to allow report generation.
A new pragma has been added to turn off the generation of the
database file. The command
/pragma nodatabase
will disable the generation of the .DB file.

Added program, a new program QDREPORT has been added to
the suite of tools for use with QDHELP. QDREPORT will
generate 3 different reports using the .DB file generated by
QDHELP. The reports generated are Topic Report which contains
informatoin about each topic you have defined, Browse Sequence
Report which shows the order or you browse sequences and Link
Topic Report which shows which topics link to and are linked from
a given topic.

QDSHELL has been given a total facelift. It now uses standard
MS Windows Menus and a toolbar for speedy access. You
can now access QDHELP helpfile from within QDSHELLs Help
menu. Also you can search for QDHELP information by cutting/
copying a keyword you want to search on into the clipboard then
selecting the Search for QDHELP On... menu option.

/link command has been augmented to allow ,line option as
final parameter. This takes care of the problem of the first
link item in a list of items being indented less than the other
links. The perfered way of generating a list of links is now

/link TOPICNAME,Text for jump,line
/link TOPICNAME,Text for jump,line
/link TOPICNAME,Text for jump,line

This will cause all the Text for jumps to line up correctly.

Rev 2.0.4

Bug fix, /keywords command can now be placed anywhere in a topic
without giving a false error message.

You can place a /keywords command anywhere in a topic now. When
the keywords defined in this command are searched for they will
jump to the first text after the /keywords command. The search
will not jump just to the start of a topic. In prior releases of
QDHELP an error message was given if the /keywords command was
found after the first /para command in a topic. QDHELP actually
would generate the correct RTF but the error message was misleading
and just plain incorrect.

Bug fix, full path of bitmap in /bitmap command was not working

Fixed code so that only the filename.bmp would be put into the
.RTF file generated by QDHELP. V2.0 thru 2.0.3 would not strip
off the drive and path information that was put into the .RTF
file causing any /bitmap command which contained drive:\path
information to work improperly.

Rev 2.0.3

No changes just clean up

Rev 2.0.2


add pragma vbheader:

The command
/pragma vbheader
will now output a file inputname.vb which can be included in the
Global.bas file for Visual Basic. This file contains Global Const
declarations of the context ids needed for context sensitive help.

Note: if you have VB 3.0 you can simply add the XXXX.VB file
to your project. This is due to the fact that not all global
declarations need to be in a single file in VB 3.0


Bug Fix, No space after link commands.

None of the link commands put a space after the text of the hyperlink.
This bug was introduced between 1.0 and 2.0.1 and is fixed here.
Just as a note if you want more than one space after some link text
do the following:

/link TOPIC,Topic Hypertext
\ Text which follows 6 spaces after hyperlink text

Use a backslash at the beginning of the next line of text.


Rev 2.0.1


output file name change:

The default for the output file name is no
longer out.rtf. If no output file name is given explicitly the
output file will have the same base name as the input file with the
extention .rtf added. For example, if the input file is myhelp.qdh
the default output file will now be myhelp.rtf.


color text commands:

Text can now be colored using the \cfXXX command
where XXX is an index between 0 and 15 which determines the color of
the text. The included Windows help file shows the colors.


auto generation of .hpj file: The .hpj file will use the same base name
as the input file with a extension .hpj . To suppress the output of the
.hpj file use the command /pragma nohpj


auto generation of include file for context sensitive help:

QDHELP will automatically generate a C header file with constants
for context sensitive help. The file will use the same base name as
the input file with a extension of .hhh. This file can be included
in the .hpj file (if you are generating a .hpj and a .hhh file the
include will automatically be put in your .hpj file). It can also be
included in your C source via the #include directive.


format type for whole document:

A new command /defformat will accept both paragraph and text
formatting commands. If this command is used
outside a topic this will be the base format for all text in the
document. All other formatting commands are applied after the default
format commands. If this command is found inside a topic all the
text in the topic will use this as its base formatting commands.
When the topic ends so does the use of the /defformat command found
inside the topic.


format type for whole para:

The \para command now allows formatting
commands for text to be included after it. This will cause all the
text in that paragraph to use those formatting properties.


support for buildtags:

The /topic command now allows arguments after the topic name.
They are buildtag names.

This sets build tags BUILD1,BUILD2 and BUILD3 for topic MYTOPIC. The use
of the build tags is described in the Help Compiler manual. If you are
using the -j flag and generating an .hpj file the build tags will
automatically be put into the .hpj file for you. Also the BUILD option
in the [OPTIONS] section will be set to the OR of all of the build tags
This will cause all of the topics in the file to be built. You can,
of course, change what will be built by changing the BUILD option.


force a newline: (HC3.1 WinHelp 3.1)

Microsoft fixed the Help Compiler so it understands the \line command
now. So to put newlines into the help file do the following:


line 1 \line
line 2 \line
line 3 \line
line 4 \line

This will only work with the new Help Compiler and anything compiled
with the new help compiler can only be used with the new version of


support macro links: (HC3.1 WinHelp 3.1)

The Windows 3.1 release has alot of new power in the help engine.
QDHELP supports the new macro links (i.e. links the instead of /* Phil, what the hell
jumping to a topic execute a macro command). The syntax is /* is this ??

/macrolink link text,macro

where link text is the text to press and macro is the macro to execute
when link text is pressed.


support topic macros: (HC3.1 WinHelp 3.1)

The Windows 3.1 release allows macros to be executed when a topic is
jumped to. This is supported via the /topicmacro command.

The /topicmacro command is grouped with the /keywords /browse /title
commands at the beginning of a topic. Its syntax is

/topicmacro macro

Where macro is a macro that you want executed when the topic you are
defining is jumped to.


support for .HPJ file inputs:

Since QDHELP 2.0 supports automatic generation of .HPJ files there is
a whole set of commands that allow you to add information to the .HPJ
file. These commands were added so that you do not have to manually
edit the .HPJ file. In this way you can keep all the information you
need for your help file in one place. The following commands were


These commands are the same as the sections of the .HPJ file under Windows
3.1. You can find more information on each of these commands in the
accompanying help file.


New help file layout:

The source for the help files for QDHELP and QDMENU have been broken into
multiple files. If you choose to work in this method using the /include
command to gather all the files together you may be interested in the new
browse capability added for Win 3.1 users. The command
/pragma debug
causes a new button to be added to the help window labeled Browse. If you
press browse, and you ran the help file from the directory which contains the
.QDH source, a notepad will pop up with the source file for the given topic
in it. It is a very nice way to check and edit your help file. Try it,
you will like it.


Be sure to check the help file included and the source for the help file
since there is much that is new and the best way to learn about it is by


Backward compatibility Issues:

None of the Win 3.1 additions to help will be able to be compiled under the
HC 3.0 Help Compiler. This is the compiler that is still being shipped with
the Professional Toolkit for BASIC. You will need the 3.1 Help Compiler
to take advantage of these features. But remember that help files compiled
with the 3.1 Help Compiler are not useable by the 3.0 WinHelp program.
Therefore if someone is still running Windows 3.0 and your help file is
for 3.1 there could be problems.


Keep making help the quick and dirty way!

Phil Allen
 WinHelp 3.1)

Microsoft fixed the Help Compiler so it understands t€¹/w¹/B€Ÿÿÿ¡ÿÿçÿÿ+ÿÿJÿÿLÿÿxÿÿzÿÿÃÿÿÌÿÿÿÿQÿÿ–ÿÿÄÿÿÆÿÿÿÿPÿÿ™ÿÿÉÿÿÿÿ%ÿÿ9ÿÿgÿÿiÿÿ¢ÿÿÛÿÿÿÿYÿÿ™ÿÿØÿÿÿÿ+ÿÿ-ÿÿmÿÿ¥ÿÿßÿÿÿÿ_ÿÿ“ÿÿ•ÿÿ•ÐÿÿÿÿPÿÿÿÿ‘ÿÿµÿÿÙÿÿýÿÿÿÿÿ= ÿÿ? ÿÿˆ ÿÿ“ ÿÿÜ ÿÿÞ ÿÿ
 ÿÿY ÿÿš ÿÿÜ ÿÿ! ÿÿ< ÿÿ> ÿÿ@ ÿÿ ÿÿ– ÿÿ˜ ÿÿØ ÿÿ
ÿÿÿÿÿÿXÿÿZÿÿtÿÿvÿÿ¿ÿÿÊÿÿÿÿÿÿ^ÿÿ`ÿÿvÿÿxÿÿ†ÿÿ˜ÿÿÛÿÿÿÿcÿÿeÿÿ£ÿÿãÿÿãÿÿÿÿbÿÿdÿÿŒÿÿŽÿÿÖÿÿÿÿ_ÿÿrÿÿtÿÿ{ÿÿ˜ÿÿÑÿÿÛÿÿÝÿÿÿÿÿÿcÿÿeÿÿe®ÿÿ¹ÿÿÿÿÿÿNÿÿPÿÿlÿÿnÿÿšÿÿÜÿÿ!ÿÿgÿÿ˜ÿÿšÿÿãÿÿåÿÿýÿÿÿÿÿ1ÿÿwÿÿw´ÿÿ¶ÿÿÿÿÿÿÿLÿÿ•ÿÿ¾ÿÿÀÿÿ ÿÿ ÿÿJÿÿLÿÿÿÿÔÿÿÿÿ]ÿÿ¤ÿÿÛÿÿÝÿÿßÿÿß(ÿÿ*ÿÿMÿÿOÿÿŽÿÿ½ÿÿÿÿHÿÿŒÿÿÎÿÿÿÿ'ÿÿ)ÿÿrÿÿtÿÿ’ÿÿ”ÿÿ½ÿÿÿÿ?ÿÿ?AÿÿŠÿÿŒÿÿ¦ÿÿ¨ÿÿéÿÿÿÿÿÿÿÿ4ÿÿÿÿÈÿÿ ÿÿUÿÿžÿÿ¦ÿÿÈÿÿ ÿÿR ÿÿU ÿÿU W ÿÿ  ÿÿ¢ ÿÿÉ ÿÿË ÿÿ!ÿÿQ!ÿÿS!ÿÿ\!ÿÿ^!ÿÿe!ÿÿt!ÿÿƒ!ÿÿ’!ÿÿ¡!ÿÿ«!ÿÿ­!ÿÿó!ÿÿ8"ÿÿB"ÿÿB"D"ÿÿ"ÿÿ"ÿÿ¹"ÿÿ»"ÿÿþ"ÿÿ\#ÿÿ¯#ÿÿ±#ÿÿÍ#ÿÿÏ#ÿÿ$ÿÿ3$ÿÿ5$ÿÿ$ÿÿ$ÿÿ¬$ÿÿ®$ÿÿô$ÿÿ0%ÿÿ0%2%ÿÿx%ÿÿ®%ÿÿ°%ÿÿÃ%ÿÿÅ%ÿÿ &ÿÿ#&ÿÿ%&ÿÿo&ÿÿq&ÿÿ&ÿÿ’&ÿÿÙ&ÿÿ 'ÿÿf'ÿÿ­'ÿÿñ'ÿÿù'ÿÿû'ÿÿû'(ÿÿ(ÿÿ(ÿÿ'(ÿÿ2(ÿÿ>(ÿÿI(ÿÿV(ÿÿc(ÿÿe(ÿÿg(ÿÿ³(ÿÿù(ÿÿ)ÿÿ)ÿÿ`)ÿÿb)ÿÿy)ÿÿ{)ÿÿÆ)ÿÿÆ)*ÿÿ[*ÿÿ”*ÿÿ¤*ÿÿð*ÿÿ?+ÿÿŒ+ÿÿÖ+ÿÿé+ÿÿë+ÿÿ7,ÿÿ9,ÿÿƒ,ÿÿÍ,ÿÿ×,ÿÿÙ,ÿÿ%-ÿÿ'-ÿÿG-ÿÿI-ÿÿI-–-ÿÿå-ÿÿ/.ÿÿ|.ÿÿÄ.ÿÿ
/ÿÿ//ÿÿ1/ÿÿ}/ÿÿ/ÿÿª/ÿÿ¬/ÿÿ¸/ÿÿ»/ÿÿ×,ÿÿÙ,ÿÿ%-ÿÿ'-ÿÿG-ÿÿI-ÿÿ Arial help files for QDHELP and QDMENU have been broken into
multiple files. If you choose to work in this method usin

  3 Responses to “Category : Windows 3.X Files
Archive   : QDHELP30.ZIP

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: