D I A L O G   E N H A N C E R  ' 9 9   P M   I N S T A L L E R   D O C U M E N T A T I O N

(Please note : This file is formatted for resolutions of 1024x768 and above!)

Readme Version :	2.00
Last Updated :		23rd October 2001
Installer Version 		3.00b
Dialog Enhancer Web :	http://www.dialogenhancer.com
Support/contact E-Mail :	dialogenhancer@bmtmicro.com
(Please label all mail clearly with "Dialog Enhancer [...]" in the message title)

*** CONTENTS ***
==============
1.0 Comment from the developer
1.1 Introduction
1.2 System requirements
1.3 Installation
1.4 Uninstallation
1.5 Operation
1.6 Registration
1.7 Common questions and answers
1.8 Troubleshooting
1.9 Current restrictions
2.0 Win-OS/2 Support
2.1a Colour Manager
2.1b MouseSmart
2.2 Other Dialog Packs
2.3 History
2.4 Current and future work
2.5 Credits
2.6 Legal comments and disclaimer


*** 1.0 Comment from the developer ***
=============================
Welcome to the latest generation of Dialog Enhancer '99, the award-winning desktop enhancement utility for 
the OS/2 Warp 4.0 operating system. Please consider registering it with BMT Micro to help fund further development 
work.  If you wish to continue using the product after a trial period of a month, information on how to register 
can be found later in this document.  A file history is included, providing comment on any changes, made to the 
installer, since the last release.

Its been a long time coming, but Dialog Enhancer is eCS ready! This is the first beta of a version that can now
specifically support Serenity System's eComStation product. eComStation includes, out of the box, Dialog Enhanced
files for the base system, networking etc allowing more emphasis to be placed on bonus components. 
This recent release is aware of this change and makes the changes required.

Regards,
Richard Castle
Dialog Enhancer Development
Loughborough, UK


*** 1.1 Introduction ***
=================
With the release of OS/2 Warp 4.0, IBM improved on much of the PM interface by including a new system font 
and new properties notebooks.  Unfortunately, much of the system was left untouched, using the old System 
Proportional font, which gave the new interface an unfinished look. Dialog Enhancer picks up here and completes 
the update by adding the new look to the system applications and dialogs.

Dialog Enhancer '99 improves the look of the OS/2 desktop by modifying the dialog files held within the system. 
The aesthetic look and operation of the dialogs can be changed.  Components that Dialog Enhancer '99 can update 
are:

System font used -		Changes this to the new OS/2 Warp 4.0 system font.
Control positioning -		Improves the positioning and size of these.
New icons and bitmaps -		Adds new icon resources to the dialogs.
Extra text -			Adds extra information to some dialogs to reduce confusion.
Window -			Repairs windows with no border definitions.
Sizing -				Reduces the screen footprint for all windows.
New system icons -		Updates some of the system icon set with new icons.
Win-OS/2 -			Makes the Win-OS/2 support look & feel more like OS/2
3rd Party Apps -			Support applications other than those developed through IBM.

In addition to enhancing the look of the desktop, Dialog Enhancer also provides the following additional features:

1. Small font option -		For registered users only, the installer gives the user the option to specify 
				a smaller 32x32 icon scheme for higher screen resolutions.
2. Increased memory -		The redesigned resources compiled into the system are now compressed. This 
				means that each program/DLL takes less space when loaded into memory.
3. Smooth horizontal scroll -	A small but useful feature which fixes the horizontal window "jump" movement 
				when dynamic window drag is enabled.
4. Colour Manager -		Users now have the ability to adjust the colours of the window controls to suit their 
				desktop schemes.

*** 1.2 System requirements ***
========================

Dialog Enhancer '99 will operate on hardware at minimum specification recommended by IBM for Warp 4.0.

The following specifications should be considered :

Colours :		Dialog Enhancer '99 makes use of high colour icons when enabled. It is recommended, 
			although not essential, that the system be run in a video mode providing more than 256 colours.
OS/2 Version :		Dialog Enhancer '99 currently runs on OS/2 Warp 4.0, eComStation and Warp Server for
			eBusiness.
Disk Space :		Requirements are varied, depending on the nature of the current system state. (Multimedia not 
			installed etc.) - Expect a maximum of 40Mb to be required for the install, both on the boot drive, 
			and the drive from which where the installer is executed.
Fix Packs :		CSD Fixpacks are supported in this release.  PLEASE observe the warning in section 1.3 before 
			applying Fixpacks and display driver updates.
Language :		Dialog Enhancer '99 only supports English language versions of OS/2 - Foreign 
			systems can still use Dialog Enhancer '99 with the disadvantage of new dialogs being in the 
			English language. Foreign language pack files are in the process of being ported over to the new 
			installer.
Compression :		LX Lite compressed executables are not supported. 
			Dialog Enhancer '99 does support this format, but the IBM Resource Compiler that is used during the
			modification process will not recognise the header structure used. 
			Also, LXLite uncompressed files will not work, virgin files must be used.

*** 1.3 Installation ***
================
Installation of Dialog Enhancer is straightforward. Please remember check the "Current Restrictions" section for possible 
incompatibilities. Check that you have downloaded a 'PACK' file from the home page, which contains the details of how 
the new dialogs should be generated. In future versions, different pack files will be available to give the user selections 
of the sorts of dialog themes/styles they wish to see on their system.

Start the installer by double clicking on the INSTALL.EXE executable icon and follow through the screen prompts for a 
successful installation. Please consult the troubleshooting section if problems are encountered. If the error is known to the 
installer, details of the problem will be displayed. Finally, to complete the installation, a reboot is required to properly 
set up the rebuilt applications.

###########################
####WARNING - Very Important !!!! ####
###########################
You MUST remember  to uninstall Dialog Enhancer '99 before applying any of the following:

* System CSD packs, commonly known to most as Fixpacks. (non eComStation Users as eCS Fixpacks are DE aware)
* Display driver updates
* Updates to any 3rd party applications supported by Dialog Enhancer. 

This will allow the installer to modify the newly updated files applied during the system update. Mismatched 
system files are quite likely to cause mysterious crashes, which may become common.  Please read the section on uninstallation 
before commencing an uninstall.

Techie Information: Dialog Enhancer '99 makes use of the "first come first served" style that OS/2 uses when interpreting the 
LIBPATH statement in the CONFIG.SYS file. It places a reference to its DLL folder where the new rebuilt files reside. Should, for 
example, a service pack be applied to the system, it will update all the DLL files in the \OS2\DLL folder. With Dialog Enhancer '99 
active, however, these are not in use. (The system is using the newer DLL's in the \OS2\DEPROG\DLL folder). This could cause
problems with various updates to the system expecting to find compliant (fixed) DLL's and getting older ones instead.

###########################

*** 1.4 Uninstallation ***
==================
The system employed in this version and beyond, uses a script file generated during install to allow the uninstall program to 
do all the work. For uninstallation, simply start it from the icon in the Dialog Enhancer '99 folder.

If you are uninstalling Dialog Enhancer '99 in order to install a more recent version or to register your purchase, a reboot is NO 
LONGER required until after the installation of the newer version.

*** 1.5 Operation ***
================
Following the system reboot, there is nothing remaining except to enjoy the new system look. Dialog Enhancer '99 will be 
automatically enabled and operational. Explore your new system and enjoy the new look and feel!

*** 1.6 Registration ***
=================
After receiving your key code through BMT Micro, you must UNINSTALL Dialog Enhancer '99 to enter the key code. This is 
because every dialog in the system is created with registration details entered during install, so the current version must be 
uninstalled and re-installed. Fortunately, the time-consuming reboot between an install and an uninstall is NO LONGER required.

The success of Dialog Enhancer '99 relies solely on user feedback and registration. The program has a great future ahead of it, 
with many new features and projects being considered. These can only proceed if people register and support our work. We 
have decided to have only one 'nag' message on the file open dialog, which should be enough to remind those who are only 
exploring the new system, that they have not registered. The update must be removed from the system after 30 days of trial 
use if you have not decided to register and entered your registration key.

*** 1.7 Common questions and answers ***
================================

Q.	What is a dialog?
A.	A dialog is the graphical presentation by the operating system of a program. A dialog could be an
	"about" box, properties notebook, file window etc. Contained within the dialog are a common set of
	controls to ensure the operating system looks consistent with all applications designed to run on it.

Q.	What is the difference between the registered version and the unregistered version?
A.	The unregistered version is no different from the registered program. The only changes made are as
	follows:
	1. Removal of the file open/save registration message.
	2. Inclusion of registered information on all Dialog Enhancer '99 modified 'About Boxes'.
	3. Enablement of some of the 'tweak' options for the desktop.
	4. Win-OS/2 Support is available as a 3rd party addition.

	We believe in uncrippled shareware, as it is the best way of demonstrating the registered product with
	only subtle reminders. Failing to register Dialog Enhancer '99 after 30 days of trial use will slow development
	of future updates. Please register if you plan to use it beyond this period! There are an exciting lineup
	of sub-projects in the pipeline; keep an eye out for announcements!

Q.	I am a user of one of the original Dialog Enhancer packages. What is so special about Dialog Enhancer '99 ?
A.	Dialog Enhancer '99 was born out of frustration with the older development package "Dr Dialog" which
	relied heavily on support from REXX. The compiled executables were slow, as commands still had to pass
	through the interpreter. Because of the size of the code-base, program execution had pushed REXX to its 
	limits. The new installer features items seen in one of the last beta tests of the old code-base, with the 
	addition of the Colour Manager utility.
	Dialog Enhancer '99 also features extended 3rd party application support and a better system for identifying
	installer errors. Installation times are significantly faster with the new code-base.
	The bottom line is that the installer is a complete rebuild, adding to previous ideas, and improving
	on the algorithms used.

Q.	I have encountered 'clipping' on text of the new dialogs, what can I do?
A.	Fill out the bug report HTML form on the Dialog Enhancer '99 web site and let us know! Remember that
	the system must start in the form found at the end of a standard install (i.e. no tweaking of the system).
	Dialog Enhancer '99 cannot support small font patches or alternative system font selections that are
	allowed by some video cards, etc.

Q.	Why does XXXXX application not have new dialogs?
A.	Dialog Enhancer '99 will only update programs it finds on its list of supported applications. As
	time goes by, support packages will be released, which may improve the support of these applications as
	well as add new applications to the supported list. We will base our work on demand for program updates
	from registered users, so if you wish to see a certain application given a visual facelift, let us know.

Q.	I completed installation of Dialog Enhancer '99 and rebooted, but I don't really see much of a difference.
A.	On the grounds that the installation completed with no errors, check out the following areas :
	1. Icon Editor application.
	2. PM Checkdisk & PM Format.
	3. DOS Properties notebook.
	4. All system question/information/error dialogs.
	The list goes on. The Dialog Enhancer changes are system-wide and changes will become obvious after some use.
	Should there be no change, please contact support immediately.

Q.	Is there a future for Dialog Enhancer?
A.	The answer is simply up to you. If we receive good response and registrations, we will be more
	likely to continue producing updates than if few register. There is plenty of further potential for
	additional updates in the system, and Dialog Enhancer '99 is fully capable of embracing this.

Q.	How can I get support for my registered version of Dialog Enhancer?
A.	We would be happy and encouraged to hear your comments and findings. With your help, we can
	make Dialog Enhancer '99 even better and more valuable for those who use it. Use the E-Mail contact
	address at the top of this text file for correspondence and/or the comments form on the Dialog
	Enhancer Home Page.

Q.	Does Dialog Enhancer '99 require any special utilities for installation?
A.	As of this release, Dialog Enhancer '99 carries all the data required for a complete install.
	REXX support is no longer required for the installation process.

Q.	Why does Dialog Enhancer '99 insist on placing itself on my boot drive?
A.	Dialog Enhancer '99 works a little differently from standard system enhancers, and therefore needs
	to be a little more careful about file placement, the software is a BASE system update, so naturally,
	it should belong within the OS2 structure on the boot drive, as it will be least likely to be affected by
	drive letter changes, etc. We understand that many people have restricted space on their system
	boot drives, but this decision has been made to prevent many system problems.

Q.	How do I register Dialog Enhancer? I can't find anywhere to put the key code in!
A.	Dialog Enhancer '99 must be uninstalled, and a re-install started to register the software. This is                     
	because every "About" dialog is updated with the registration details and the "nag" must be removed from
	the open dialog. This cannot be done without a re-install. We are sorry for this inconvenience, but
	there is no reliable alternative. However, it is no longer necessary to reboot between the uninstall and 
	the re-install where you enter your registration key.

Q.	I want to see XXXXXX application supported!
A.	Simply let us know, and if demand is great enough, we will consider supporting that application.
	There is support already in the installer and DAT file structure to handle this, so 3rd party applications
	can easily be supported in future updates of Dialog Enhancer '99.

Q.	My system language is not supported! Will you provide my langauge pack file?
A.	We have German and Spanish pack files being upgraded to the new installer, they will be more
	comprehensive than before and not suffer from English text in some areas. Other langauges may be
	ported if demand exists.

Q.	I have tried Colour Manager and the 3D effects in the window controls are poorly defined.
A.	This problem is due to the OS/2 palette's not being able to provide all of the required colours.
	Increasing the number of colours in the Workspace Shell will reduce this problem. 16 Million colours
	is the preferred setting to see the correct effect.

Q.	My Matrox/Sci Tech GRADD system has font clipping problems on most of my dialogs. What is wrong?
A.	The most common problem with users of Matrox systems is that they have already selected an alternative
	system font for use in all dialogs. The MGA driver then recomputes the system metrics to adjust the dialog
	sizes. This clashes with Dialog Enhancer '99 which also changes the size of the dialogs. In short,
	open up the MGA Settings notebook, and return the system font to the default "System Proportional.10 - Normal"

Q.	Is a full de-install and re-install necessary if I want to add some features (e.g., color manager, or 3rd party 
	support) after the initial install?  Or can I simply re-run the install program without deinstalling?
A.	Unfortunately, to try and add this support, would bloat the installer to an unacceptable size. Uninstalling and 
	re-installing is a painless task with only one reboot needed so there is little to gain.

Q.	Why doesn't Dialog Enhancer '99 create the program icon folder during installation?
A.	This is caused by the WPS loosing it's ID 'link' to the desktop folder. It commonly result in the user having to use the
	SET DESKTOP entry in the CONFIG.SYS to force the INI files to look in the correct location. As a result of this, and API
	call to create a folder on the desktop will fail because it will not be able to locate the desktop the official way. 
	This problem is not restricted to Dialog Enhancer users, all routines that use this API will fail. A simple thing to fix IBM?

	The following REXX program will correct the error. Make sure it is run from the TEMP desktop that commonly appears
	when the error has occured. (ie. - There is no "SET DESKTOP" parameter in use with the broken link active).

	/*REXX FixDesk Ver 1.0 - (C) Rich Wlash*/
	call RxFuncAdd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs'
	call SysLoadFuncs
	SAY ''
	SAY 'Please enter in the location of the DESKTOP folder'
	PULL DESKFLDR
	if SysSetObjectData(DESKFLDR,"OBJECTID=<WP_DESKTOP>")
	then say "Success"
	else say"Failure"
	/*CODE END*/

	Thanks to Rich Wlash for sparing my sanity and that of others with this useful program.

Q.	Why does CHECKINI complain of missing items in the WarpCenter?
A.	CHECKINI is wrongly looking in the OS2\DLL folder for the *.CFG files that the WarpCenter uses. It reads in the older
	files and stops with an error. To prevent this, place a small routine to copy the active *.CFG files located in the 
	DEPROG\DLL back to the OS2\DLL folder. For example :

	@XCOPY C:\OS2\DEPROG\DLL\*.CFG C:\OS2\DLL

*** 1.8 Troubleshooting ***
====================
The software has gone through an extensive period of testing, but there will always be a few exceptions and problems not 
encountered during the short test cycles. If the installer returns an unknown error, then please return your INSTALL.LOG file 
and any .LOG files created in the LOG folder, to the E-Mail address at the top of this text file, complete with a system description 
and details of where the failure happened. We will do our best to rectify the situation.
If you encounter a problem during the actual operation of the update, do not hesitate to contact the support address at the 
top of the file, and let us know what the problem is.

Some common problems during install:

Q.	Dialog Enhancer '99 reports that my system is not English, causing a mismatch with the dialog 
	pack file, even though my system is English.
A.	The installer checks the entry in the system for the country version of the machine. This is
	generally set by the country utility in the OS/2 system folder. It has been known to fail, or return
	unusual codes in some cases. If your system is English, then it will generally be fine to proceed.

Q.	My SLIPPM program doesn't get changed on my non-English system.
A.	The OS/2 compiler seems to reject some of the foreign versions of SLIPPM.EXE due to incompatibilities.
	There is however a standard version available on Hobbes, which could be placed as a substitute. Search for
	SLIPPM.

Q.	I accidentally deleted the Dialog Enhancer '99 folder. How do I uninstall / operate Colour Manager?
A.	Use the switch /I to recreate the folder and icons using the UNINST.EXE program in the X:\OS2\DEPROG
	folder, where X: is your boot-drive.

Explanations for some of the more cryptic error codes:

Error #2 :	An installation has already completed! Please reboot.
	The installer has detected that the folder \OS2\DEPROG is inactive (i.e. The currently
	active LIBPATH is not pointing towards \OS2\DEPROG\DLL and consequently, the DLL files contained
	within are not in use.) It has however detected the file UNINSTAL.SCR which is the script file 
	used to uninstall, exists in the folder. This is the standard situation if the installer has 
	completed, but the system hasn't been rebooted. Otherwise, the LIBPATH entry has been removed 
	and the folder is lying dormant after the resulting reboot.

	SOLUTION : In the standard case, a reboot is all that is required. If the problem is the second 
	of the two, the LIBPATH entry needs to be placed into CONFIG.SYS and the system rebooted. If 
	more help is required, please contact support.

Error #4 :	Dialog Enhancer '99 CONFIG.SYS LIBPATH entry detected!
	The installer has detected that the LIBPATH entry exists and points towards the non-existent
	\DEPROG\DLL folder. If this entry remains, there is a possibility that files being copied into 
	the DLL folder will get blocked, causing the installer to fail.

	SOLUTION : Simply remove the Dialog Enhancer LIBPATH entry manually from your X:\CONFIG.SYS 
	using a text editor and reboot. (Where X: is your boot drive)

Error #8 :	Inactive \OS2\DEPROG folder detected!
	The installer has detected that the folder \OS2\DEPROG is inactive (i.e. The currently active
	LIBPATH is not pointing towards \OS2\DEPROG\DLL and consequently, the DLL files contained within 
	are not in use).  It has, however, detected that files exist in the folder (Except for the file 
	UNINSTALL.SCR). This is most likely due to the uninstaller failing to clear the folder.

	SOLUTION : Delete the \OS2\DEPROG folder manually before attempting to re-install.

Error #18 :	Unable to locate file.
	The un-installer has tried to restore a file from the \DEPROG\BACKUP folder and cannot find the
	destination file it must replace.

	SOLUTION : If the file has been moved, then return it to its original location. Otherwise, 
	manually remove OR change the entry referencing the application in the UNINSTAL.SCR file. 
	This will prevent the uninstaller from trying to restore the file. You will get hints as 
	to the location from the LOG file created.

*** 1.9 Current restrictions ***
======================
Some of the dialogs in the system are hard-programmed into the executable. Common examples are the main interface
in FTP-PM and the main dialog in the system installer (this is usually given away by the ugly thin border definitions). 
These unfortunately cannot be updated by Dialog Enhancer '99 and would require IBM to reprogram the applications in 
question as the dialog data is hard-coded into the EXE - (An area which, for safety reasons, Dialog Enhancer '99 does 
not touch). Fortunately, there are only a few applications which have this problem when compared with the 5000 or so 
dialogs currently updated in this release of the software.

1. Installation from a network drive - Installation from non EA aware partitions may call Dialog Enhancer to fail.
2. Installation from read-only media. Dialog Enhancer must be installed from a R/W access drive.
3. Problems have been reported when users have attempted to install DE from a FAT32 Partition.


*** 2.0 WIN-OS/2 Support ***
======================
This release of the installer includes support for the modification of WIN-OS/2 applications. This feature of Dialog Enhancer '99 
is restricted to those who have registered, and will only be installed on presentation of a valid key. Work is ongoing, and 
only the file Open/Save, and About dialog boxes have been updated to date.
The main WIN-OS/2 controls (check boxes, scroll bars, window buttons) are next on the list, so it is at this stage, when 
you will be able to see WIN-OS/2 apps resembling OS/2 ones. For the time being, I would be interested in comments from 
those registered users who have tried it. For those interested in further enhancing Win-OS/2, there is a utility available on 
the Dialog Enhancer '99 download page that will give all of the Win-OS/2 dialog boxes an "OS/2-style" look.

*** 2.1a Colour Manager ***
=====================
Colour Manager is supported within Dialog Enhancer '99 to change the hard-coded colours used on the window controls 
(Maximise, Minimise, Close etc) and some dialog controls (Check boxes and  radio buttons). These cannot be changed by 
the OS/2 Scheme palette and this really limits the user to the boring grey imposed by the Desktop. (Remember that changing 
the dialog background does not change the control colour.)

The resources are hard-coded in PMMERGE.DLL which is responsible for controlling some aspects of how OS/2 looks. Dialog 
Enhancer Colour Manager removes these resources, modifies the colours used within them and then re-compiles them. On 
reboot, the controls will now display the selected colour.

The offset adjustment allows the user to specify the shadow and highlight colours of the control. There is a base colour and both 
a darker & lighter shade to denote the '3D' effect used. Users with higher colour modes will experience better, more-defined 3D 
effects.

To re-cap the process to operate Colour Manager correctly...

1. Enable Colour Manager in the install properties notebook.
2. Select the base colour for the controls. (The shadow & highlight colours will be calculated automatically).
3. Complete the install and reboot.

You should now find that the window controls have changed to the selected colour. 

4. Open up the Scheme Palette and modify the dialog background and button colours to suit the new scheme.
5. Drag the completed scheem with the ALT key depressed to the desktop to change the whole system.

The system colour change will now be complete. You can now enjoy a COMPLETE colour scheme other than grey.

Note : The is no support at the moment to modify the colours used in the rest of the system as this is already user-configurable 
through the Scheme Manager. We are looking into the possibility of creating a Dialog Enhancer scheme in the Scheme Palette, 
so after a colour choice is made, Dialog Enhancer would automatically propose a corresponding scheme for the system. It must 
also be remembered that this may clash with some system enhancers such as Smart Windows or Object Desktop.

Update : Due to a possible bug in the WPS, the creation of a WPSchemePalette object dedicated to Dialog Enhancer seems not 
to work. If any users can shed any light on the problem, please let us know.

*** 2.1b MouseSmart ***
===================
MouseSmart is a new utility which allows users to modify the tracking speeds of their mouse to above those provided with the 
basic mouse properties notebook. The setting can be save to a loader object in the startup folder, to ensure that your setting are 
retained on reboot.

MouseSmart is beta software, and we are still toying with the format, so if anyone has any suggestions to make this little gem any
better, please let us know through the comments page on the web site.

MouseSmart is based upon a text mode configuration program available on Hobbes. The original program was developed by Peter 
Fitzimmons, Andreas Just, David Eckman and Wolfgang Mast.

*** 2.2 Other Dialog Packs ***
======================
Dialog Enhancer '99 features support for other pack files. The ability is there to develop your own pack file and make it available 
to others to use. Documentation is currently being written to cover the subject.


*** 2.3 History ***
==============
(Beta history is available on request)

3.00b 	Beta Release - 22/10/2001
NEW - Dialog Enhancer now supports eComStation

*** 2.4 Current and future work ***
=========================
Requests for your favourite third party applications are welcomed. Some applications cannot me updated due to the 
resource format used, but we will have a look and report back on the possibility for conversion.

We are open to ideas and suggestions!


*** 2.5 Credits ***
==============
Below is a list of the hard-working people who have helped us test Dialog Enhancer '99 and improve it before it was released.

George Boles, Konstantin Zhilenko, Mark Mellin, Johan Sjostrom, Stephen D. Holden, Neville Cobb, Michael Rowe, 
Per Johansson, Ben Borden, Richard J. Martin, Gerrit Schoenmaker, Patrick G. Gaerlan, Frank Berke, Adam P. Roycraft, John Moore, 
Peter Lindeman, Alex Newman, Eugene Tucker.

Special thanks go out to...
Ronald Brill, Thomas Bradford, Eirik Overby, Andrea Resmini, Ingo Guenther, Eric Slaats, the guys at OS/2 e-Zine and BMT Micro.
And anyone else who we have omitted. (Sorry!)

And a final mention to the guys at Speedsoft. Dialog Enhancer '99 was programmed with Sibyl, OS/2's excellent Delphi 
equivalent. Sibyl provided us with an easy to use interface and an object based system which allowed rapid development 
of the new application. For anyone considering RAD development, there is no better alternative. Thanks guys for an excellent 
and enjoyable product. For more info see: http://www.speedsoft-online.de/

*** 2.6 Legal comments and disclaimer ***
==============================
All work on the system Dialogs is copyright Richard Castle 1997-2000. Dialog Enhancer '99 only patches the system dialogs 
and does not contain any code to recreate any OS/2 files for pirating purposes. The new dialogs have been created "from scratch" 
and only mirror the originals in look and operation.  No application code has been modified, so functionality will not be affected.

All trademarks belong to their respective owners.

This package is provided 'as is', without any guarantees whatsoever. We are not liable or responsible for any loss or damage of 
any kind whatsoever, including, but not limited to, losses of a financial, physical, psychic, emotional, marital, social, or mental 
nature that may result from the use or the purported use of anything in this package, for any purpose whatsoever.
