(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.1 Other Dialog Packs
2.2 History
2.3 Current and future work
2.4 Credits
2.5 Legal comments and disclaimer
*** 1.0 Comment from the developer ***
==================================
Welcome to Dialog Enhancer. Please consider registering it with BMT Micro to help further the development work here.
If you wish to continue using the product after a trial period of a month, please see later in this document for information on how to register. Please read the included file history for the latest updates and changes made to the installer.
New to this release is an intelligent system which tracks previous choices on installation including registration information. This makes re-installation due to a service pack update a less time consuming task.
Dialog Enhancer now compresses all resources on compilation to reduce memory footprint. As a result, the compilation process will take longer to complete. Please be patient!
Regards
Richard Castle
Dialog Enhancer Development
*** 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. Unfortunatly, much of the system was left untouched, using the old System Proportional font, which gave the new interface an unfinished look to it. Dialog Enhancer picks up here, and completes the update to the system applications and dialogs with the new look.
Dialog Enhancer improves the look of the OS/2 desktop by modifying the dialog files held within the system. The aesthetical look and operation of the dialogs can be changed. Components that Dialog Enhancer can update are :
System font used - Dialog Enhancer changes this to the new OS/2 Warp 4.0 system font.
Positioning of list boxes etc. - Dialog Enhancer improves the positioning and size of these.
New icons and bitmaps - Dialog Enhancer adds new icon resources to the dialogs.
Extra text - Dialog Enhancer adds extra information to some dialogs to reduce confusion.
Window - Dialog Enhancer repairs windows with no border definitions.
Sizing - Dialog Enhancer reduces the screen footprint for all windows.
New system icons - Dialog Enhancer updates some of the system icon set with new icons.
Win OS/2 - Dialog Enhancer makes the Win-OS/2 support look & feel more like OS/2
3rd Party Apps - Dialog Enhancer can support applications other than those developed through IBM.
*** 1.2 System requirements ***
===========================
Dialog Enhancer is unlike any standard system addon, in that it does not have an executable running during system operation. This means that the system is under no more pressure than usual, CPU load and memory usage will not increase when Dialog Enhancer is operational, and there is no change in system stability. (If any case, memory requirements are reduced, as we have removed much unused data left behind from previous versions of OS/2) As a result of this, the software will comply with the IBM specifications for OS/2 Warp 4.0 . Dialog Enhancer makes use of high colour icons during its operation however, and it is recommended, although not essential, that the system should run in a video mode offering more that 256 colours.
Disk space requirements are varied, depending on the nature of the current system state. (Multimedia not installed etc.) - Expect a maximum of 20Mb to be required for the install, both on the boot drive, and the drive where the installer is executed from.
CSD Fixpacks are supported in this release, although, PLEASE observe the warning in section 1.3 before applying Fixpacks and display driver updates.
Dialog Enhancer only supports English language versions of OS/2 Warp 4.0 - Foreign systems can still use Dialog Enhancer with the dissadvantage of new dialogs being in the English language. Expect to see future versions with packs availabled in other languages.
*** 1.3 Installation ***
===================
Installation of Dialog Enhancer is straightforward. Please remember check the "Current Restrictions" section later 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 on the sort of dialog themes/styles they wish to see on their system.
Ensure there are NO applications running in the task list and ensure the folders used to install from contain only alphanumeric characters. Start the installer by double clicking on the INSTALL.EXE executable icon, and follow through the on screen prompts for a successful installation. Please consult the troubleshooting section if problems are encountered, if the error is recognised by the installer, then details of the problem will be displayed.
Finally, to complete the installation, a reboot is required, to initialise the rebuilt applications.
##############
####WARNING####
##############
You MUST remember however, to uninstall Dialog Enhancer before applying any system CSD packs (Commonly known to most as Fixpacks), display driver updates, tcpip patrches, and updates to any 3rd party applications supported by Dialog Enhancer. This will allow the installer to modify the new updated files applied during the system update. It is well advised to heed this advise, as unrecognised system crashes may become common due to mismatched system files. Please read the section on uninstallation before commencing an uninstall.
Techie Information : Dialog Enhancer makes use of the "first come first serve" style that OS/2 uses when interpreting the path statements in the LIBPATH statement in the CONFIG.SYS file. It places a pointer to it's DLL folder where the new, rebuilt files reside. If, for example, a service pack is applied to the system, it will update all the DLL files in the \OS2\DLL folder. These however are not in use if Dialog Enhancer is active. (The system is using the newer DLL's in the \OS2\DEPROG\DLL folder. You can imagine how this could cause problems with various updates to the system expecting to find compliant (fixed) DLL's and getting older ones.
##############
####WARNING####
##############
*** 1.4 Uninstallation ***
=====================
The system employed in this version and beyond, uses a script file generated on install to allow the uninstall program to do all the work. For uninstallation, simply start it from the icon in the Dialog Enhancer folder created on the desktop when the update was first installed, or if that has been deleted since then, re-run the INSTALL.EXE program from the DEPROG folder in your OS2 directory. The rest of the uninstall will be completed on the next reboot, where the OS/2 startup script STARTUP.CMD is used to remove the redundant file structure in the OS2 folder.
*** 1.5 Operation ***
==================
Following the system reboot, there is nothing left to be done except enjoy the new system look. Dialog Enhancer should now be automatically enabled and operational. Explore your new system and enjoy what has been changed!
*** 1.6 Registration ***
====================
After recieving your key code through BMT Micro, you must UNINSTALL Dialog Enhancer to initiate the key code. This is because every dialog is updated with registration details. The safest and most reliable method is to uninstall and re-install.
The success of Dialog Enhancer 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 one 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 registration has not been carried out.
*** 1.7 Common questions and answers ***
====================================
Below are some of the most common questions put to us during development :
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, filer window etc. Contained within the dialog are a common set of controls to ensure the operating system looks consistant, 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 the removal of the file open/save registration message and registration warning messages in system about boxes, and the fact that WIN-OS/2 support is disabled. We believe in uncripled shareware, as it is the best way of demonstrating the registered product with only subtle reminders. Failing to register Dialog Enhancer 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 installed a new application, and now Dialog Enhancer no longer updates any dialogs.
A. The application has re-arranged the LIBPATH statement during its install. Run the "Repair LIBPATH Statement" utility from the program icon in the Dialog Enhancer folder created during installation.
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 web site and let us know! Remember that the system must be in the form as used at the end of a standard install (ie no tweaking of the system). Dialog Enhancer cannot support small font patches or alternative system font selections etc.
Q. Why does XXXXX application not have new dialogs?
A. Dialog Enhancer will only update programs it recognises from a list of supported applications. As time goes by, support packages will be released, which fully support these applications. We will base our work on demand for program updates, so if you wish to see a certain application given a visual facelift, let us know.
Q. Is there a future for Dialog Enhancer?
A. The answer is simply up to the user. If we receive good response and registrations, we will be more likely to continue producing updates, than if no-one registers. There is plenty of further potential for update in the system, and Dialog Enhancer is fully capable of embracing these.
Q. How can I get support for my registered version of Dialog Enhancer?
A. We would be happy and encoraged to hear your comments and findings, with your help we can make Dialog Enhancer even better and suited to the users who need it. Use the E-Mail contact address at the top of the readme for correspondance and/or the comments form on the Dialog Enhancer home page.
Q. Does Dialog Enhancer require any special utilities for installation?
A. As of this release onwards, Dialog Enhancer carries all the data required for a complete install. All that is required is OS/2 REXX support (installed by default).
Q. Why does Dialog Enhancer insist on placing itself on my boot drive?
A. Dialog Enhancer 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 effected by drive letter changes etc. We understand that many people are have restricted space on their sytem 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 must be uninstalled, and a re-install started to register the software. This is because every about box dialog is updated with the registration details and the nag removed from the open dialog. This cannot be done without a de-install. We are sorry for this inconvenience, but there is no reliable alternative.
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 easilly be supported in furture updates of the system.
Q. My system langauge is (Insert langauge here....), when will it be supported?
A. German is our main priority as far as langauges go, we base our conversions on the number of requests for that language and assign a priority to the task. German language support is 99% on the main installer, so we are now working on the dialog updates.
Q. I want to see added functionality in some of the dialogs.
A. Check out the 'Feature Enhancer' project at the following address :
The Dialog Enhancer install routine is _VERY_ sensitive to system configurations. If it is not happy about anything, no matter how trivial, it will warn the user and produce and error. Serious system modifications are made and if this procedure is taken lightly, all manner of problems could occur if system checks as extensive as this aren't made.
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 unrecognised error, then please return your INSTALL.LOG file and any .ERR files created to the E-Mail address at the top of this file, complete with a system description and details of where the failure happened. We will then 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 reports that my system is not English, causing a missmatch with the dialog pack file, even though my system is English.
A. The installer checks the entry in the OS/2 INI files 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 without danger.
Q. I get a window in the base left hand corner of my system when I run the installer, and an error message after text has scrolled up the window.
A. This is caused by OBJECT REXX being enabled. Use the SWITCHRX utility from the command line to return the REXX state back to CLASSIC REXX.
Q. On uninstallation, I am told there is a locked file 'NETMSG.EXE' that can't be restored.
A. After exiting the failed install, bring up the window list, and select close from the menu popup for "Network Messaging". This will close the locked file, and allow the installer to restore the backed up version.
Q. I run the uninstaller and reboot the system. The folder DEPROG is still in my OS/2 directory.
A. This could be caused by STARTUP.CMD failing to run. Try running it from the boot drive root directory. If this does not work, contact technical support using one of the methods listed at the top of the document.
Q. On reboot after a successful install, I get a TRAP error with PMMERGE.DLL just before the desktop loads up.
A. This only seems to happen at random times on _VERY_ few systems (We have only had 4 reports of this.). To resolve the problem, simply remove the problematic PMMERGE.DLL from the \OS2\DEPROG\DLL folder by using the "Boot to command line" option on the OS/2 recovery choices screen. This will re-enable the backed up version of the DLL. It would appear to be a slight mismatch problem with the resources, and the compiler used. We would also like to hear from those who have experienced the problem, and that way, we can build up a database of problematic configurations.
Q. On reboot after a successful install, I get an Dialog Enhancer ERROR #19
A. This is simply due to OS/2 reloading all applications loaded before the system reset. The behaviour after a reboot can be controlled by modifying the CONFIG.SYS 'RESTARTOBJECTS' string. Check your electronic documentation for more information. Simply ignore the error, and exit the installer.
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 get a white OS/2 error box during installation with a SYS3175 error message.
A. This does not seem to be linked with the installer having a problem. The REXX interpreter on some systems, depending on fixpack version applied varies in stability. If this error persists, consider re-installing OS/2 REXX support or changing your fixpack revision.
Explanations for some of the more cryptic error codes :
Error #2 : And installation has already completed! Please reboot.
Explanation : The installer has detected that the folder \OS2\DEPROG is inactive (ie. 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 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 the CONFIG.SYS and the system rebooted. If more help is required, please contact the author.
Explanation : The installer has detected that the LIBPATH entry exists and points towards the non existant \DEPROG\DLL folder. If this remained, there is a possibility that files being copied into the DLL folder will get blocked, and cause the installer to fail.
Solution : Simply remove the LIBPATH entry manually and reboot.
Error #6 : Uninstallation phase one is already complete!
Explanation : The installer has detected that the folder \OS2\DEPROG is active (ie. The currently active LIBPATH is pointing towards \OS2\DEPROG\DLL and consequently, the DLL files contained within are in use.) The file UNINSTAL.OLD has been detected, which means that an uninstall has completed successfully and that a reboot is required.
Solution : Reboot the machine, if the problem persists, remove the LIBPATH entry from the CONFIG.SYS file and reboot the machine.
Error #8 : Inactive \OS2\DEPROG folder detected!
Explanation : The installer has detected that the folder \OS2\DEPROG is inactive (ie. 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 exists in the folder (Except for the file UNINSTALL.SCR). This is most likely due to STARTUP.CMD failing to run on the reboot, and consequently the redundant fiel structure still remains.
Solution : Delete the \OS2\DEPROG folder before attempting to re-install.
Error #18 Unable to locate file.
Explanation : The 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 UNINSTAL.SCR file. This will prevent the uninstaller from trying to restore the file.
Error #31 : Unable to detect OS/2 Boot drive.
Explanation : As part of the system checks, Dialog Enhancer needs to determine the system boot drive. This is done by checking for the existance of 4 files required for OS/2 to boot, and the existance of a locked PMSHELL.EXE to show an active desktop. The files the installer check for are : \OS2LOGO , \CONFIG.SYS , \OS2\DLL\PMMERGE.DLL , \OS2\PMSHELL.EXE.
Solution : Ensure all of these files exist on the boot drive, and that the standard PMSHELL is running and not any 3rd party OS/2 Shell. If this still does not solve the problem, there is a hidden switch to force DE to accept a drive. The following syntax is used :
/FORCEBOOT=X:
Where X is the name of the drive to force DE to use. This feature is not fully recomended and it is advised that it is used as a last resort. The install, will however, check for the presence of CONFIG.SYS, OS2LOGO and an OS2 folder on the drive.
*** 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 (usually given away by the silly thin border definitions). These unfortunatly cannot be updated by Dialog Enhancer and would require IBM to re-program the applications in question as the dialog data is hard coded into the EXE - (An area, for safety reasons, Dialog Enhancer 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.
Some software has problems, they are listed below, as well as a small description of the problem. We are working with the developers to provide a solution.
1.9.1 Star Office (faulty controls on open dialog box - Still works though, but difficult)
Note: This is something that can only be recitified by the developer. If you wish
to see it supported, contact them and ask nicely!
1.9.2 X-File (faulty controls on open dialog box - Still works though on some systems, but difficult to use.)
Note: The X-File fix for this is currently available. See the Dialog Enhancer download page for details.
1.9.3 PM Graph (faulty controls on open dialog box - Still works though, but difficult)
1.9.4 Dialog Enhancer Installer does not support IBM's Object REXX.
1.9.5 LX compressed DLL & EXE files are not supported on installation.
*** 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 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 download page that will give all of the dialog boxes an OS/2 style look.
*** 2.1 Other Dialog Packs ***
==========================
Work in the pipeline includes a dialog pack containing all current dialogs and icons, hand drawn by Andrea Resmini (There are some excellent examples of his work throughout the installer). This will be available as just another pack file soon.
*** 2.2 History ***
================
# 1.060 First alpha of PM installer.
# 1.061 First beta of PM installer.
COMMENT : No other problems were reported, so it was updated to beta level.
# 1.062 Feature update.
FIX : Problems with loose code on code to grab data from CD.
FIX : Installer doesn't clip on VGA systems now.
FIX : Changed background colour of splash logo on installer to grey.
FIX : New routine for creating desktop objects. New look!
COMMENT : Still a few niggly problems, and we disliked the system for removing Dialog Enhancer.
# 1.070 Second beta of PM installer.
UPDATE : Readme files re-organised
UPDATE : Better calibration of PM Installer with VGA
UPDATE : Install dialogs smartened up some more.
UPDATE : File names are a little less cryptic.
UPDATE : Removed the need for REMOVEDE.CMD and created PM Uninstall utility.
UPDATE : Extensive sniffer section was cut down and streamlined
FIX : Bootdrive detection still was a little inaccurate, hopefully now fixed for users with multiboot systems.
FIX : Some niggles with the install from the CD were corrected.
# 1.10 Gamma release of PM Installer for retail sale.
UPDATE : Readme files updated a little
UPDATE : More information added to the installer/uninstaller program.
UPDATE : Installer icons updated.
FIX : Bug with getting utilities from OS/2 CD causing a file lock.
FIX : Slight trouble with the uninstallation system and editing of the STARTUP.CMD file.
FIX : Installer failed if run from the root directory of a drive.
FIX : Major bug in unpack routine that could have caused install to fail due to certain system configurations.
FIX : Check for space available on install drive returned the wrong error code.
FIX : Slight problem with the bootdrive listing in the log file.
FIX : If no bootdrive could be found, software didn't trap problem properly.
# 1.29 Update to retail version
UPDATE : Many areas of code optimised and re-organised. A few bugs noticed and fixed.
UPDATE : 3rd Party support has been tested to beta level.
UPDATE : 4OS/2 now checked for.
UPDATE : LX Compressed EXE files now checked for.
UPDATE : IBM Compiler is checked for version level.
UPDATE : New style header on file UPDATE.DAT
UPDATE : Copyfile routine now deletes source after copy
UPDATE : FORCEBOOT parameter added for those who cannot get DE to recognise their bootdrive.
UPDATE : Updated uninstall message to help those wishing to register.
UPDATE : Removed need for init sequence to be re-run on changing of files
UPDATE : A few more graphics replaced in installer to ensure uniform styling. DE folder icon added.
UPDATE : Coding added to support WINOS2 updates.
UPDATE : BMT has given us our own E-Mail : dialogenhancer@bmtmicro.com
FIX : IBM Compiler is now directly addressed in it's folder location. Previously, the path was relied on.
FIX : Annoying 'drive not ready' error box does not come up any more when checking CD-ROM drives etc.
FIX : Can now only be uninstalled by .EXE that installed it.
FIX : DLLs didn't really need to be backed up, this is not done any more.
FIX : The IBM Registry editor wasn't restored on uninstall.
FIX : Installer is much more careful about locked files.
FIX : The automatic shutdown option dows not prompt the user to CAD anymore.
FIX : Slight bug in routine to write NETPROG files out caused DrREXX error.
FIX : Desktop folder has now been sized, thanks to a small routine that was overlooked.
# 1.35b Beta release containing Warp 3.0 & German language support
UPDATE : Dialog Enhancer now installs to Warp 3.0 systems
UPDATE : German language support implemented. (Not fully translated though)
UPDATE : OS/2 Windows optimised for Warp 3.0 systems with 8.Helv fonts at VGA
FIX : Bug with opening a file called RXL2 which is also REXX a function.. :o)
FIX : Desktop folder background now autosized to window.
FIX : Error code reference for 4OS/2 check was incorrect. (Gave error #19)
# 1.37b Beta fix containing Warp 3.0 & German language support
FIX : There are more versions of English other than UK english in the world... fixed! (Aus, US...)
FIX : Debug check was left from previous testing.
FIX : Installer now directly calls CMD.EXE in the hope of getting round problem with 4OS/2
FIX : Error #19 was confusing many users. This has been changed to help understanding.
FIX : Subsection to pull data from OS/2 CD was sharpened up further.
UPDATE : German code translation now complete.
UPDATE : Installer now checks to see if it is being run from the [bootdrive]\OS2\DEPROG folder.
UPDATE : Code to unpack DATA from OS/2 CD split up for each Warp version.
UPDATE : (Warp 3.0) Installer now uses UNPACK2.EXE - Things seem to be working better.
# 1.40b Beta release
UPDATE : Installer no longer requires OS/2 CD.
UPDATE : New format introduced in UPDATE.DAT (Again! :o) )
UPDATE : 3rd Party support testing completed and tweaked. Now has a search routine!
FIX : Installer should be much faster due to optimisation of some subroutines.
FIX : Warp 3.0 systems no longer produce any compiler errors with beta .DAT file.
FIX : OS/2 Attrib command no longer required.
# 1.41b Beta release
UPDATE : A bit more sound and visual confirmation added to the error and complete dialogs.
FIX: Potential bug in backup routines which would have caused a failure if there was duplicate DLL in
subdirectories. The old locked DSPRES.DLL etc. bug was a symptom.
FIX: Search routine no longer uses 'DETACH' and now uses a separate thread.
FIX: Search routine caused an error if the file could not be found on the system.
# 1.42g Gamma release
UPDATE : About boxes is no more informative about version of Dialog Enhancer installed.
UPDATE : Changed over to new file structure on .DAT file for everything.
FIX : More visual confirmation on completion as to whether things went well.
# 1.43g Gamma release (never was released - internal update)
UPDATE : Support added in text files for problems with country detection.
UPDATE : Added support for double-click on 3rd party list box.
UPDATE : Finally found the problem that caused CLIPOS2.EXE to loose it's icon. Fixed.
UPDATE : Country code check in INI file made more reliable.
UPDATE : Destination check on uninstall now added to prevent locked file error.
# 1.50b Beta/Gamma release
UPDATE : New header system added to dialog pack file. (80% of code updated)
UPDATE : Brand new routines replace old unpack, backup systems etc.
UPDATE : 20K of code removed due to new algorithms, optimisations and an internal file registry array.
UPDATE : Uninstaller exeutable is now renamed to UNINST.EXE to aid user understanding.
UPDATE : Installer now searches for the .DAT file and is not locked to the UPDATE.DAT convention.
UPDATE : German support almost finalised.
UPDATE : Options screen is now modular with file modules being displayed in a list box. Much better.
UPDATE : Coding arranged in such away to support 3rd party dialog pack files.
FIX : WIN-OS/2 about box dialogs did not show the same information as the OS/2 ones.
# 1.51b Beta/Gamma release
FIX : Tried installer with 4OS/2 and performed well. Removed check for this command interpreter.
# 1.52b Beta/Gamma release
UPDATE : Removed check for system font until we can do more testing on it.
# 1.53b Beta/Gamma release
UPDATE : Spanish translation added to the installer. Thanks to Xavier for the hard work and effort.
UPDATE : German support in the installer is also complete. Thanks also to Christian.
# 1.55b Beta/Gamma release
FIX : Country code #1 was ignored on the country check.
# 1.60 Beta/Gamma release
UPDATE : Support code added for small icons at high resolutions if user wishes. Registered users only.
# 1.62 Beta/Gamma release
UPDATE : Updates made to the uninstallation system to improve understanding of errors.
UPDATE : Further work done to 3rd party pack file support section.
# 1.65 Beta/Gamma release
NEW : Dialog Enhancer now logs registration data in the OS2.INI file to ease speed of re-install.
NEW : Dialog Enhancer also logs the 3rd party file locations on installation in the OS2.INI file for speeding up future installations.
FIX : Bug in CLEANUP caused TEMP folder to be ignored.
FIX : Bug in registration routine caused legal codes to fail.
# 1.70 Beta/Gamma release
NEW : All modified DLL's now carry a Dialog Enhancer icon to set them out from non modified versions.
NEW : Dialog Enhancer now compresses all resources and significantly reduces disk space/memory requirements.
NEW : Dialog Enhancer remembers check box settings in the options area and saves them to the OS2.INI file to ease speed of re-install.
FIX : Uninstallation status bar didn't update during replacement of files.
*** 2.3 Current and future work ***
==============================
Other work in progress :
Eric Slaats (Smalled and Smalled HTML Extensions) and I have begun a project to allow new functionality to be added to the file open dialog and possibly other parts of the shell. The package will be a part of Dialog Enhancer and will allow features to be added to the system dialogs as well as just smartening in them up. First to be updated will be the file open dialog, which will feature many new features (folder creation, file information etc.) look out for this addition to the Dialog Enhancer package later this year. (For those interesting in contributing ideas to the project can fill out a request form on the Dialog Enhancer home page)
Further work is being done on the .DAT pack series of dialog styles for Dialog Enhancer (currently the only pack available is the standard WarpSans update) - soon to be released pending a successful beta period will be be a new pack featuring new unseen images to complement many of the dialogs, drawn by Andrea Resmini.
The broad coverage of Dialog Enhancer in terms of the dialogs updated is also being extended, with the bundled IBM applications getting a facelift. Expect to see some more 3rd party applications supported also in the near future!
The Dialog Enhancer pack file is being extended to support WinOS/2 applications, and give them an OS/2 look. This will be an optional extra selectable on install for registered users. Keep an eye out later in the year for further updates!
Installer changes :
The installer is currently being re-written in OS/2's Delphi equivalent - hence the reduced changes made to the current refresh of the installer. The new installer promises to be faster and easier to use. It will no longer require OS/2 REXX to operate, which will eliminate the REXX crashes seen on some systems. Expect more information soon, and a Alpha test phase shortly afterwards. To date, the new installer is 50% complete.
*** 2.4 Credits ***
================
Below is a list of the hard working people who have helped me test Dialog Enhancer and improve it before it was released for public testing.
Thom Davis, Jim Hruska, Joe Sniffen, Ronny G. Pettersen, Chris McKillop, Clark Tompsett, Eric Blade, Paul Hodges, George Boles, Mark Mellin, Ion I. Moraru, John Constantinos Bacas, Christopher David McKillop, Duane A. Chamblee, Mark Hay, A. Glass, William Rothwell, Christopher B. Wright, Jim Hruska, Anders Gjerl, Alan Elias, George Boles, Mesterhazy Attila, Ljudevit Devide, Kevin Yank, David P. Cole, Sean Coughlin, Quentin Stephens, Antony Curtis, Price Sicard, Loren Bandiera, Greg Marx, D. Gilbert, Rainer Feuerstein, Andrea Resmini, Mark Thurman, Rodney Baker, Christian Hennecke.
A special thanks goes out to...
Andrea Resmini, Thom Davis, Sean Coughlin, Ingo Guenther, Eric Slaats, the guys at OS/2 e-Zine and BMT Micro.
And anyone else who we have omitted. (Sorry!)
*** 2.5 Legal comments and disclaimer ***
===================================
All work on the system Dialogs is copyright Richard Castle 1997/1998. Dialog enhancer 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 fuctionality is not effected.
All trademarks belong to their respecive 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.
