home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
h
/
hv210.zip
/
CUSTOM.TXT
next >
Wrap
Text File
|
1992-01-09
|
20KB
|
532 lines
Copyright 1991-1992 Hware Corporation.
Hviews Installation
Overview
The installation program is a Windows program. It will copy all the
programs and data from the installation diskette onto the user hard
disk. After all the copying is done the installation program will
build a new program group with the Hviews icon in it. This icon is the
Hviews icon.
After, the new group is installed then a second program (HVIEWSB.EXE)
will be loaded if the installation program doesn't detect Hviews
having been installed previously.
This program will build Hviews icon groups for every existing program
manager group and will build one group named "All icons" that will
contain all the icons from all the program manager groups. Also, at
this time a file (HVIEWS.HVI) containing icons for each of the
applications that are associated to document types is built.
Note that the Program Manager allows icons to exist in a group after
the corresponding programs and / or files have been deleted or moved.
Hviews Builder must have access to the program file to obtain it's
icon. If the program file isn't founded then a substitute icon will be
used. This default icon is a black circle with a red line drawn
through it.
Installation process
Place the Hviews disk in the appropriate diskette drive. From Program
Manager use the Run command and enter the diskette drive and program
name INSTALL (i.e. . A:INSTALL).
This will start the install program which will ask the User to verify
the directory that Windows is installed in. It is preferred that
Hviews be installed in the Windows directory (Note that all files
loaded will start with the letter H). The directory Hviews is
installed in must be in the PATH. If you decide to install Hviews in
another directory you must add the directory to the PATH if it isn't
already in the PATH.
Next the installation program will display a Copy progress dialog box
which indicates what files are being copied and the percent done.
After all the files are copied, the Hviews group is created for the
Program Manager. You may want to copy the Hviews icon to another
program group, such as the Windows Application group. Open the
Windows Application and Hviews groups and while holding the Ctrl key
down drag the Hviews icon to the Windows Application group.
Finally, if Hviews hasn't been previously installed, the Hviews
Builder program is executed, which will copy all the applications
installed in Program Manager's groups into Hviews's corresponding icon
groups.
If Hviews has been installed before, then the HVIEWS.WIN and
HVIEWS.INI files will not be copied to the harddisk and the Hviews
Build program will not be execute. This prevents overwriting the icon
group files used by Hviews.
Using Hviews Builder
Hviews Builder is used only for creation of the Hviews icon group
files and the creation of the icon file (HVIEWS.HVI) used to contain
the icons of all the associations.
If the [extension] section of the WIN.INI file has been changed then
the Hviews Builder program needs to be loaded and the menu item MODE,
Build Associations selected to update the HVIEWS.HVI file.
User Customization
The Command action override bar (i.e. the push buttons along the left
side of the File view) is controlled by the contents of the HVIEWS.WIN
file. The following figure shows the contents of the HVIEWS.WIN file
as distributed on the Hviews installation diskette.
$msg msg1
'No Compiler available for %ext'
$msg msg2
'Operation not allowed on directory'
$operation
Default F XLS 'DDE(EXCEL.EXE) EXEC(EXCEL SYSTEM [OPEN{"%CD%FNAME"}])'
Default F XLC 'DDE(EXCEL.EXE) EXEC(EXCEL SYSTEM [OPEN{"%CD%FNAME"}])'
Default F XLW 'DDE(EXCEL.EXE) EXEC(EXCEL SYSTEM [OPEN{"%CD%FNAME"}])'
Default F XLM 'DDE(EXCEL.EXE) EXEC(EXCEL SYSTEM [OPEN{"%CD%FNAME"}])'
Default F DOC 'DDE(WINWORD.EXE) EXEC(WINWORD SYSTEM [FILEOPEN{"%CD%FNAME"}])'
Default F DOT 'DDE(WINWORD.EXE) EXEC(WINWORD SYSTEM [FILEOPEN{"%CD%FNAME"}])'
Default F RTF 'DDE(WINWORD.EXE) EXEC(WINWORD SYSTEM [FILEOPEN{"%CD%FNAME"}])'
Default F EXE 'PGM(%FNAME)'
Default F COM 'PGM(%FNAME)'
Default F PIF 'PGM(%FNAME)'
Default F BAT 'CMD(%NAME) wait'
Default F PAS 'CMD(%NAME.L) wait'
Default F BAS 'CMD(BASIC %NAME)'
Default F * 'WIN'
Default D * 'INT(S)'
Browse F ZIP 'CMD(PKUNZIP -vn %fname) wait'
Browse F * 'PGM(hbrow.exe) PARM(%FNAME)'
Browse D * 'INT(S)'
Edit F * 'PGM(notepad.exe) PARM(%FNAME)'
Edit D * 'INT(S)'
Compile F C 'CMD(CC %NAME) WAIT'
Compile F RC 'CMD(RRCC %NAME) WAIT'
Compile F ASM 'CMD(ASM %NAME) wait'
Compile F BAS 'CMD(BASICA %NAME)'
Compile F * 'MSG(msg1)'
Compile D * 'INT(S)'
Delete F * 'INT(D %FNAME)'
Delete D * 'INT(RD %FNAME)'
Print F * 'DLL(HPRINT.DLL)'
Print D * 'INT(S)'
PKZip F * 'DLL(HPKZIP.DLL)'
PKZip D * 'INT(S)'
PKUnZip F * 'CMD(PKUNZIP %FNAME) wait'
PKUnZip D * 'INT(S)'
Hex F * 'CMD(HFDUMP %FNAME) wait'
Hex D * 'INT(S)'
$eof
Figure 25
The entries after the line containing $operation are used to control
what action is processed with a double- click on an entry in the File
List . Entries are made up of four fields. Each field is delimited by
at least one blank. The fourth field is the action field. The first
three fields must match before an action will be processed. If there
isn't a match, then nothing happens when the User double-clicks on a
file entry or directory entry.
The first field is the text that Hviews displays in the push button in
the Command action override bar. The first entry must be the word
"Default" which is the default action.
The second field may only have the character "F" or "D". This is used
to match a selected entry in the File list table. An entry with a "F"
will match a file. An entry with a "D" will match a directory entry.
The third field is used to match the file type. For example the
action might be to browse a file. This allows different browse
programs to be selected based upon the file type. The last entry for
a given action type can be an asterisk (*) which will match any file
type.
The fourth entry is the command to be executed. It must be enclosed
in single quotes. There are seven command types (DLL, DDE, PGM, CMD,
WIN, MSG, and INT). See the table below for an explanation of these
command types.
DDE
This command type indicates the application supports using
DDE to open document files.
PGM
This command type is for executing programs (i.e. file types
COM or EXE). This entry may have a PARM passed to the
program with the PARM() option.
CMD
This command type is for executing a program or batch file. The
command processor (i.e. COMMAND.COM) is loaded and the command passed
to the command processor. The CMD type may have the attribute WAIT
which will prevent the window from closing on the termination of the
program / batch file. The User will be prompt to press the Enter key
to continue.
WIN
This entry indicates to Hviews that the Windows extensions are
to be searched for a match.
MSG
This command type will display a message. The message
must be one of the messages in the file.
INT
This command type is used to execute a Hviews internal
command. Internal commands are "S" for selecting a
subdirectory; "D" to delete a file entry; and "RD" to remove a
directory.
DLL
This command type is used to execute an external action
provided by a DLL library. The HPRINT.DLL is an example of
this command type.
Substitution variables
For this explanation assume the selected entry is ABCDEFG.EXE and the
current directory is E:\WIN3.0.
There are four variables used for substituting the selected entry into
the command. The variable must be terminated with a blank ,a right
parentheses, or a period. If you use a period you can concatenate the
remaining text with the substitution variable (i.e. %NAME.L will
be substituted as ABCDEFGL).
%CD
The current drive and directory (i.e. E:\WIN3.0\).
%FNAME
Substitutes the full selected entry (i.e. ABCDEFG.EXE).
%NAME
The Name part of the entry(i.e. ABCDEFG).
%EXT
The extension part of the filename (i.e. EXE).
Overview of HVIEWS.WIN file
Following is a section of the operation part of the HVIEWS.WIN file.
Each entry has been numbered so it can be referenced. The numbers are
not part of the file and the first field must be left justified.
1: Default F XLS 'DDE(EXCEL.EXE) EXEC(EXCEL SYSTEM [OPEN{"%CD%FNAME"}])'
2: Default F XLC 'DDE(EXCEL.EXE) EXEC(EXCEL SYSTEM [OPEN{"%CD%FNAME"}])'
3: Default F XLW 'DDE(EXCEL.EXE) EXEC(EXCEL SYSTEM [OPEN{"%CD%FNAME"}])'
4: Default F XLM 'DDE(EXCEL.EXE) EXEC(EXCEL SYSTEM [OPEN{"%CD%FNAME"}])'
5: Default F DOC 'DDE(WINWORD.EXE) EXEC(WINWORD SYSTEM [FILEOPEN{"%CD%FNAME"}])'
6: Default F DOT 'DDE(WINWORD.EXE) EXEC(WINWORD SYSTEM [FILEOPEN{"%CD%FNAME"}])'
7: Default F RTF 'DDE(WINWORD.EXE) EXEC(WINWORD SYSTEM [FILEOPEN{"%CD%FNAME"}])'
8: Default F EXE 'PGM(%FNAME)'
9: Default F COM 'PGM(%FNAME)'
10: Default F PIF 'PGM(%FNAME)'
11: Default F BAT 'CMD(%NAME) wait'
12: Default F PAS 'CMD(%NAME.L) wait'
13: Default F BAS 'CMD(BASIC %NAME)'
14: Default F * 'WIN'
15: Default D * 'INT(S)'
16: Browse F ZIP 'CMD(PKUNZIP -vn %fname) wait'
17: Browse F * 'PGM(hbrow.exe) PARM(%FNAME)'
18; Browse D * 'INT(S)'
19: Edit F * 'PGM(notepad.exe) PARM(%FNAME)'
20: Edit D * 'INT(S)'
21: Compile F C 'CMD(CC %NAME) WAIT'
22: Compile F RC 'CMD(RRCC %NAME) WAIT'
23: Compile F ASM 'CMD(ASM %NAME) wait'
24: Compile F BAS 'CMD(BASICA %NAME)'
25: Compile F * 'MSG(msg1)'
26: Compile D * 'INT(S)'
27: Delete F * 'INT(D %FNAME)'
28: Delete D * 'INT(RD %FNAME)'
29: Print F * 'DLL(HPRINT.DLL)'
30: Print D * 'INT(S)'
31: PKZip F * 'DLL(HPKZIP.DLL)'
32: PKZip D * 'INT(S)'
33: PKUnZip F * 'CMD(PKUNZIP %FNAME) wait'
34: PKUnZip D * 'INT(S)'
35: Hex F * 'CMD(HFDUMP %FNAME) wait'
36: Hex D * 'INT(S)'
Figure 26
The first seven entries (1-7) provide the actions for starting
programs that support Dynamic Data Exchange (DDE). The example shows
entries for Microsoft Excel and Word for Windows. If the application
isn't running, then the program name within parenthesis following the
DDE keyword is used to start the application. The document file name
will be supplied by Hviews internally. If the application is loaded
and responding to DDE messages, then a DDE conversation will take
place using the first token within the EXEC(...) parameter as the
Application, the second token as the Topic, and the third token as the
execute command to be processed by the application. Note that the
command to be processed (i.e. within the square brackets) uses braces
where parenthesis are to be used. Hviews will translate braces to
parenthesis before passing the command to the application.
The next four entries (8-11), provide the actions for starting
programs that of files with the EXE, COM, PIF, and BAT file types
respectively.
The twelfth entry (12) allows for a double-click on a Pascal source
file which will execute a batch file with the letter L appended to it.
This batch file, for example, could link the application and execute
it in one operation.
The thirteenth (13) entry allows for starting BASIC programs with a
double-click on the ????????.BAS file type.
If the file type doesn't match the first thirteen entries, then the
fourteenth entry (14) informs Hviews to search the [Extensions]
section of the WIN.INI file for a Window application.
The fifteenth entry (15) is the default action for a double-click on a
directory selection. This invokes the internal action of selecting a
subdirectory for the new current directory.
So the first fifteen entries (1-15) covers the standard actions as
described in other parts of this manual.
The sixteenth (16) entry will execute program B.EXE with the selected
filename as a parm. This action will match any file type.
The seventeenth entry (17) provides for selecting the internal action
of selecting a subdirectory for the new current directory when the B
action is active.
The eighteenth (18) entry will execute the SPFPC program with the
selected filename as a parm. When SPFPC is invoked with a filename the
editor is entered directly.
The nineteenth entry (19) provides for selecting the internal action
of selecting a subdirectory for the new current directory when the E
action is active.
The entries twenty (20) through twenty-six (26) are used to invoke
different compilers. Depending on the file type the appropriate
compiler is executed. All these entries have the WAIT attribute which
will keep the last lines of compiler output displayed until the User
responds with the Enter key. The last entry twenty-six (26), will
display a message (MSG1) indicating no compiler available.
The twenty-seventh entry (27) provides for selecting the internal
action of selecting a subdirectory for the new current directory when
the C action is active.
The twenty-eight (28) and twenty-ninth (29) entries provide for
deleting files and removing directories.
The thirtieth (30) entry will copy any selected file to the printer.
Note that you could add additional entries to restrict what files
could be sent to the printer.
The thirty-first entry (31) provides for selecting the internal action
of selecting a subdirectory for the new current directory when the P
action is active.
The thirty-second entry (32) executes program FDUMP which will display
the file in hex.
The thirty-third and last entry (33) provides for selecting the
internal action of selecting a subdirectory for the new current
directory when the H action is active.
The B.EXE and FDUMP.EXE programs are provided with Hviews and are
installed during the installation process.
Running a Batch file from an Icon
A BATCH file is run as a non-Windows Application. It inherits the
current environment which isn't expandable. If the batch file has SET
commands in it, the set commands will be ignored. If the batch file
runs an application that requires the set variables there are two
choices:
1
Set the variables in the AUTOEXEC.BAT file.
2
Execute the COMMAND.COM program specifying an environment size
(see example below).
Following is an example using the command processor. Assume the batch
file's name is ABCDEF.BAT. Enter the following command as the Program
Path for an icon or enter it in the Run dialog box. The example
specifies an environment space of 512 bytes (See your DOS manual for
details).
COMMAND.COM /E:512 /C ABCDEF.BAT
This solves the environment space problem; but when you make the
application an icon the icon will be displayed with the name of
"COMMAND". This is OK if you only have one batch file running; but if
you have multiple batch files running and minimized they will all be
titled with "COMMAND". To solve this problem copy the COMMAND.COM
program naming it with a unique name. Such as COMMANDA.COM. Then use
the following command line:
COMMANDA.COM /E:512 /C ABCDEF.BAT
Finally, make a PIF for the COMMANDA.COM file (i.e. COMMANDA.PIF) and
specify the title of your choice. Running a Batch file from the File
List
When a batch file is executed from the file list (i.e. the default
action "*") the COMMAND.COM program is loaded automatically (i.e. The
CMD action is used) . If you minimize the application it will be
titled with "COMMAND". If you use an action that uses the CMD action
and has the WAIT parameter specified then the icon title will be
"HWAIT". For both cases the icon title can't be changed.
Hviews does allow the environment size to be specified for all CMD
actions. In the HVIEWS.INI file there is a keyword CommandEnvSize.
The default value as distributed is 512 bytes.
Overview of HVIEWS.INI
The following figure shows the contents of the HVIEWS.INI file as
distributed on the Hviews installation diskette. The User doesn't have
to change any entries within this file.
[Hviews]
ACTIVE=1
CommandEnvSize=512
LASTWINCOMMAND=154
AUTOWINARRANGE=1
SAVESTATEONEXIT=1
STARTFROMSAVEDSTATE=1
Search_Order=2
Search_Details=3
FONT=-12 0 400 0 1 2 1 1 Fixedsys
[DefaultIcons]
MISSING=c:\win3.1\hviews.exe 4
DOS1=c:\win3.1\hviews.exe 7
[IconGroups]
GROUP1=C:\win3.1\ALL.HVG All Icons
GROUP2=C:\win3.1\GAMES.HVG Games
GROUP3=C:\win3.1\ACCESSOR.HVG Accessories
GROUP4=C:\win3.1\HVIEW.HVG Hview
GROUP5=C:\win3.1\MAIN.HVG Main
GROUP6=C:\win3.1\WINAPPL.HVG Win Applications
GROUP7=C:\win3.1\STARTUP.HVG StartUp
GROUP8=C:\win3.1\EXCEL.HVG Excel
GROUP9=C:\win3.1\SDKTOOLS.HVG SDK Tools
Figure 26
Requirements
Listed below are the software and hardware requirements:
* Microsoft Windows 3.0 (or later)
* A mouse is recommended
* Personal computer using the 80286, 80386SX, 80386DX, or higher
* One 5.25" high-density (1.2MB) disk drive and a hard disk
* Color monitor is recommended
Hviews files
Listed below are the files supplied with Hviews
FILE Function Copied to Hard Disk
HVIEWS.EXE Hviews application Yes
HVIEWSB.EXE Hviews Builder application Yes
HVIEWS1.DLL DLL used by Hviews Yes
HVIEWS2.DLL DLL used by Hviews Yes
HVIEWS3.DLL DLL used by Hviews Yes
HVIEWS4.DLL DLL used by Hviews Yes
HVIEWS5.DLL DLL used by Hviews Yes
HVIEWS.INI Hviews control file Yes (If first time)
HVIEWS.WIN Hviews action control file Yes (If first time)
*.HVG Icon group files Created by HVIEWSB
HVIEWS.HVI Icon database of associations Created by HVIEWSB
HVIEWS.HLP Hviews help file Yes
HWAIT.EXE Used for wait function Yes
HBROW.EXE File browser Yes
HPKZIP.DLL Zip DLL Yes
HPKZIP.HLP Zip DLL help file Yes
HVIEWSB.HLP Hviews Builder help file Yes
HBROW.HLP HBROW help file Yes
COMMDLG.DLL COMMDLG.DLL Maybe
APPSETUP.INF Install control file NO
INSTALL.EXE Installation program NO
Figure 27
Error Messages
The following table of error numbers are caused by errors in the
HVIEWS.WIN file. If you can't find the problem, then replace it with
a backup copy or a copy from the distribution disk.
The message number will be displayed in a Message box. Hviews will
proceed with initialization; but the Command override bar may not
function properly.
# Error message
1 DOS eof found before $eof
2 Action character missing (Must be first character on line)
3 Action greater than 2 characters
4 2 nd field must be F or D
5 3 nd field must not be greater than 3 characters
6 4 th field must not be greater than 80 characters
7 Same as error 2
8 2 nd field missing
9 3 nd field missing
10 4 th field missing
11 Out of memory - Too many actions
12 No actions
Figure 28