home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CD Direkt 1995 #1
/
Image.iso
/
cdd
/
winanw2
/
wnbrowse
/
readme.now
< prev
next >
Wrap
Text File
|
1994-01-06
|
5KB
|
112 lines
WnBrowse 3.5 Release Notes
--------------------------
Below are the changes made to WnBrowse since version 3.4. For full details
read the WNBROWSE.TXT file.
New Features
------------
1. Most of the options available from the 'Options' menu, plus some
new ones, have been moved to a new Preferences dialog accessed from
the Options menu.
2. OEM to ANSI Support
A new 'OEM to ANSI Translate' option has been added. When selected
any OEM characters in the file (such as IBM box drawing characters)
will be translated to their equivalent ANSI characters (this was
the default behaviour of earlier levels). When this option is not
selected, characters are not translated (useful to users in
countries where special characters are used, such as Umlauts).
3. Previously opened files available on File Menu
WnBrowse now remembers the last nine files that were opened from the
Open dialog. These files are listed on the File menu. Files that are
opened via Drag and Drop, or the File Manager extension are not saved.
4. File Launch Improvements
* WnBrowse now allows Windows EXE files being viewed to be launched.
* Text files without associated applications (via File Manager), can
be launched into an editor. The Editor to use can be set from the
new Preferences dialog.
* Files can now be launched from the File menu 'Launch Current File'
option.
* A Minimize-on-Launch option is now available from the Preferences
dialog.
5. WnBrowse now closes the file being browsed when it is minimized. The
file is re-opened when the WnBrowse window is restored.
6. The WnBrowse File Manager extension now supports the File Manager
status bar available under Windows for Workgoups.
7. When launching WnBrowse from the file manager extension, the extension
now expects WNBROWSE.EXE to be in the same directory as the extension
DLL (WBFXTEN.DLL). WNBROWSE.EXE is no longer required to be in a
directory contained in the DOS PATH environment variable.
8. WnBrowse will automatically install the File Manager extension when
run for the first time.
9. The information box now displays the Company Name for 16 bit
Windows EXE and DLL files, if available.
10. The DLL's imported by a Windows 16 bit or OS/2 1.X program are
now displayed in the file information dialog.
11. Minor change to Zip content display
* On the first display of the contents of a Zip file, the list
will be positioned to the first 'readme' file, if one is
present.
* On re-displaying the Zip list after viewing a Zipped file, the
list will be positioned to the file just viewed.
12. The TAB size can now be set via the Preferences dialog.
13. A description of a button's function can be displayed by clicking
the right mouse button over the button bar.
14. The 256 character per line limit for text files can now be changed
to any value between 80 and 1024 by adding a parameter to the
WNBROWSE.INI file (MaxLineLen=nnn).
Note : While you can view files that contain long lines in text mode
by scrolling, you will not be able to print such files (unless
you have a very wide printer !). It is my intention to add
word wrap printer support in a future release of WnBrowse.
Bugs Fixed
----------
1. On rare occasions, searching backwards in a hex file did not
find all matching strings.
2. Viewing a file contained with a ZIP file with no extension name
(.ZIP .EXE etc) failed.
4. WnBrowse now checks the data provided by Windows about fonts
for errors. WnBrowse will now cope with 'Problem' fonts rather
than falling over (with a zero divide exception).
Known Problems
--------------
1. GPF failure opening a Windows program for browsing.
On very rare occasions, WnBrowse will fail while opening a Windows
EXE file. The problem occurs when extracting the version information
from the file. I have only discovered one file that causes this
problem so far (the install program for Microsoft Access STFSETUP.EXE)
The bug is in a Windows support library VER.DLL and will be fixed by
Microsoft in due course (I hope).