home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Pier Shareware 6
/
The_Pier_Shareware_Number_6_(The_Pier_Exchange)_(1995).iso
/
035
/
zipct212.zip
/
README.1ST
< prev
next >
Wrap
Text File
|
1994-10-09
|
2KB
|
42 lines
RPF Zip Control(TM) Copyright 1993, 1994 RPF Software ALL RIGHTS RESERVED
README.1ST
If you plan to use an existing Zip Control (zipcntrl.exe) to unzip this
new delivery, you will see an error message at the point where it attempts
to unzip zipcntrl.exe. That is because your existing copy of zipcntrl.exe
is in use and OS/2 will not allow it to be "overwritten" by unzip.exe,
while it is in use.
We suggest that you unzip this new delivery to a new, temporary directory
(Zip Control will create this for you automatically). Once the delivery
has been unzipped successfully, fully exit Zip Control (so that zipcntrl.exe
will not be in use) and copy all the files from the new temporary directory
to your old/existing directory.
This way your existing zipcntrl.ini file (which contains your Registration
information and your other ZC customization) will still be used (will not
be overwritten).
NOTE: If you "test run" the new Zip Control in the temporary directory,
ZC creates a new ZipCntrl.ini file. This new ZipCntrl.ini file
will not contain your Registration Number nor any of your Zip
Control customizations. If you then wild card copy (*.*) the files
to your old Zip Control directory, the newly created ZipCntrl.ini
file will overwrite your old ZipCntrl.ini file, and your
Registration Number and customizations will be lost. You may want
to delete the ZipCntrl.ini file in the temporary directory (used for
the test run) before copying the new ZC files to your old ZC
directory.
Beginning with the Service Pak and continuing into the Personal OS/2 Beta,
IBM's E.EXE (the System Editor) opens underneath all open programs/windows.
This has been reported to IBM, and IBM has assigned it problem report number
PMR 2x535. However, IBM has reported that this will not be repaired since
it was re-designed to operate this way for OS/2 2.11 and therefore is "working
as designed." EPM.EXE and most (all?) other OS/2 programs do not seem to
operate the "new" way E.EXE does. If you feel E.EXE should be changed back
to the way it formerly worked, please contact IBM and reference PMR 2x535.