|
NavSearch scans your files on
your local/network drivers, perform full text search according to
your searching criteria, then generates a temporary result file.
NavSearch then launches your web browser and loads this temporary
result file to the browser.
Before start searching, you must
tell NavSearch the location of your favourite web browser, and assign
a temporary file where searching results should be stored. You do
this by goto [Files | Setup Browser]
You may add the following
switches to NSACCESS.INI. (NSACCESS.INI is automatically
created when you register NavSearch. If you haven't registered yet,
please create this file using a text editor. e.g. NotePad)
[ADVANCE]
| SaveOnExit=0 |
Do
not save options at exit |
| Show_Lang=0 |
Hide
Language Selection Menu (NavSearch has English and French interface) |
| Show_Option=0 |
Hide
NavSearch [FILE] on the menu bar |
| Show_DirBtn=0 |
No
directory browse button |
| Show_FileType=0 |
No
selection of file type |
| Show_SubCheck=0 |
No
check box for 'Include Subdirectory' |
| Show_Adv=0 |
Hide
panel [Advance Options] |
| Modify_Dir=0 |
In
the [Limit to Directory] box, user may not input their own directory. |
| Can_Close=0 |
NavSearch
window cannot be closed |
| CloseOnExit=1 |
Close
NavSearch after search |
[APPINFO]
| INIPATH=D:\ini-directory\ |
Save
NAVSRH's preferences (NAVSRH.INI) in another directory,
instead of the same directory as NAVSRH.EXE. This switch is
particular
useful if NAVSRH.EXE is running from CD-ROM, or a network server.
e.g. INIPATH=C:\TEMP\ .or. INIPATH=A:\ |
| |
| How
to launch NavSearch within HTML pages |
If you are a CD-ROM publisher, or Intranet
developer, you might want to integrate NavSearch with your existing
HTML files. e.g. When an user is viewing HTML file on the Intranet
/ CD-ROM, he/she may start NavSearch by simply click on a hyperlink,
maybe something like 'Click here to search documents'.
You can do this easily by setting
up NavSearch as a helper application. e.g. Setup NavSearch
as a helper application for ".srh" extension. When user click
on <A HREF="temp.srh">Click here to search
documents</A>, NavSearch will be lauched by the browser
automatically.
In order to make the above example
working you need to create a file call "temp.srh'. However
it can be empty or just a dummy file, as its content is never used.
Netscape users can setup a helper
application by:
- Start Netscape
- Goto Options | General Options
| Helpers
MSIE users can setup a helper application
by:
- Goto View | Options
- Select the [Program] Tab
- Click on [File Types]
- Click on [New Type]
Now, you can define NavSearch as
the helper application for *.SRH document types.
| |
| How
to launch NavSearch within HTML Frames |
When you goto [Files | Setup Browser],
there is an optional field called "Frame File Name".
As mentioned above, NavSearch outputs
its results to a temporary result file. You can set your result
file name to whatever you like.
If - NO - FRAME file name
is set, NavSearch will tell your browser to load the "Result
File" everytime a search is completed.
If FRAME file name is set, NavSearch
will tell your browser to load the "Frame File" everytime
a search is completed.
If you do use a FRAME file, the frame
file must have a "frame src=temp.htm", where temp.htm refers to the
result file. So when NavSearch tells your browser to reload the
FRAME file, the results will be displayed with that frame.
e.g
- You want NavSearch to output its
results to "MYRESULT.HTM"
- You want this Result appear in
your FRAME file, "OPEN.HTM"
- You have a frame in OPEN.HTM which
loads "MYRESULT.HTM"
Your result file name is "MYRESULT.HTM"
Your frame file name is "OPEN.HTM"
- You must include the following
files:
- 16bit: NAVSRH.EXE & or
- 32bit: NAVSRH32.EXE &
- NSACCESS.INI - contains your
registration key and access control info.
- NAVSRH.INI - contains your
NAVSEARCH preferences (e.g. helper applications info, background
color, homepage location, etc).
- Useful dynamic variables for defining
homepage location, path list, and search paths:
%temp% - the Windows default temporary
directory, usually points to C:\TEMP
%exedir% - the directory of the program files
%exedriver% - the driver ID from which the program is running
from.
These 3 variables are very useful if you need to refer programs,
html files, path on your CDROM/Floppy/Network, but don't know
the driver ID where the user will run the program from.
e.g. if your user install your program under E:\DEMO\NAVSRH
- You can point the result file
to %TEMP%NSTEMP.HTM, or %EXEDIR%NSTEMP.HTM
- %temp%NSTEMP
= C:\TEMP\nstemp.htm
- %exedir%NSTEMP
= E:\DEMO\NAVSRH\nstemp.htm
- %exedriver%\NSTEMP
= E:\nstemp.htm
- If you distribute files on CD-ROM,
or a read-only floppy, you should stop user from saving their
preferences/boomarks to the same disk. You can do this by set
SaveOnExit=0. see above
| |
| Differences
between 16bit / 32bit versions |
|
Windows
Platform |
Support
Long Filenames? |
Auto
Detect Browser |
| 16bit |
All
Windows |
NO |
Supported,
but may call multiple instance of browser |
| 32bit |
Windows
95/98/NT |
YES |
Supported,
call only one instance of browser if DDE is supported |
Registration Info - REGINFO.HTM
Other Software From FAICO - SOFTWARE.HTM
Copyright © 1996-1998 FAICO Information Solutions (http://www.faico.net/)
If you have any question not answered here, please feel free to send
email to support@faico.net
|