Product: Comet2006Workstation378.exe
Version: Comet 2006 Build 378
Date: January 26, 2007
1. The computer name can be used in place of the IP addr in the Server= statement of
the Comet.ini so the connection can still be made even if the ip address of the
server changes.
2. XAP errors will now go to the xap logfile if there is one rather than to the browser.
This change requires REL 7.02 or higher.
3. Changes were made to the way the eCometContext files are managed to prevent a situation
where a user might inherit another user's COMMON data. This change requires
REL 7.02 or higher. Here's a description of the process:
Xap always created files containing the user's common data in a folder
named temp under the users cos directory. These files are NOT comet
files. Each time a client launched the browser and connected to xap, a
new file was created. These files are a simple 6 digit sequential number
beginning with 000001 and incrementing for each new connection. A cookie
is placed in the client's browser named eCometContext.
The idea here is to supply common to a series of programs associated
with one client's browser session from the first xap page needed until
the browser is shut down.
A problem occurs when a user leaves his browser open and then comet and
xapmon is restarted. The browser then contains a cookie that is NOT
necessarily connected to the client. This would give multiple clients
access to the same common. Since Common data possibly contains user
identification information, this could cause much xap confusion.
The solution was made in both Comet and the XAPMON program. XAPMON will
erase all eCometContext files from cos\temp. It will extract the first 2
digits of the first file erased, increment this number and transmit it
to Comet. This is known as the XapID. This number will appear as the
first 2 digits of a new 8 digit file name in the temp directory.
If a browser presents Comet with a cookie which does not correspond to
an existing file, Common will be cleared, and a new file/cookie will be
established.
What happens with:
Old xapmon, old comet -- no change.
New xapmon, old Comet -- All files will be erased. New files look the
same as before.
Old xapmon, new Comet -- All files will begin with 99 always.
New xapmon, new Comet -- All files will be erased. New files have an
extra 2 leading digits that will increment each time comet is loaded.
The way an xap program can tell if comet was restarted is that common
will be cleared.
4. QENDITOR activity will no longer affect the contents of the eCometContext file.
5. Corrected a problem that could have erroneously caused a compile error 22 to be issued.
Changes in previous releases:
Build 377
1. Eliminated cosh crash if using xap logfile and file doesn't already exist.
2. QENDITOR no longer clobbers user common area if an XAP program aborts.
Build 376
1. Comet.exe will now copy FaxDriver.exe to the temp folder along with all the other
required Comet executables if it is found in the Comet folder.
Build 375
1. Corrected a problem that could have affected performance of XAP programs running
in partitions beyond P99.
2. A new #XAP command, USEWIN, has been introduced. This will direct XAP to
use direct Windows calls rather than going through the file server. The
default is to use the file server. Logging, however, always uses Windows
calls because of stack space limitations.
3. Server name in path for XAP merge file is no longer case-sensitive.
Build 374
1. The MID instruction now returns the unencrypted serial number of the dongle.
2. Corrected a problem using UNC names with the CopyFile mnemonic.
3. Corrected a problem transferring very large files with CopyFile (files that
would require longer than 30 seconds to transfer).
4. Enhanced CosP to be able to work with newer versions of pdfFactory.
Comet Explorer
1. Corrected a problem that produced an invalid qdir.i00 when creating a new directory.
2. Corrected problem doing KeyBuild using record #'s. Program would loop endlessly
if the file contained any deleted records.
Build 373
1. Corrected two problems that could have caused CosH to crash while running XAP
applications. One of the problems was caused by malformed requests from a
browser.
2. Corrected a problem that prevented GetDirAlias from working properly if the
target directory was a share.
CometLib
1. Corrected a problem in the data compression algorithm between CosC and CosW.
A possible buffer overrun may have occurred on very large buffers of non-repeating
characters.
Build 372
1. Corrected a problem that would cause files to be left open in CometServe
if a program got an error 66 (EXIT without ENTER). A symptom of this
problem is unexplained error 34s.
2. Corrected a problem introduced in .370 that would cause XAP applications
to error if the merge file exceeded 16K.
Comet Explorer
Added a progress bar to DirBuild during the initial scan of the qdir and
loading of the file information.
NOTE: We have discovered that DirBuild occasionally errors out when run
from a Comet Anywhere client. We are investigating this problem.
Build 371
1. The PRINT changes made in .370 have been taken out.
2. Corrected a problem in CosW so that when displaying a embedded child dialog
and clicking out of COSW to another application then clicking back onto COSW,
the focus will now return to the correct control.
3. The $(CATEMP) directory will now automatically added to the configuration
at startup if CFAM is in use.
Build 370
This is the first official release of Comet 2006
1. Copyfile and VerifyFile now go thru CFAM and the file server so users need not
have access to the Comet data folders to use these functions.
2. XAP is also now using CFAM and the file server for all except writes to the log
file. The pathname for the location of the logfile can be specified in the #XAP file.
3. A problem using (BM) with (CreateWindow) has been corrected.
4. A line feed is no longer generated by PRINT if the print line contains only special mnemonics.
5. A problem with VerifyFile has been fixed so the transfer is not done if the destination
file is already up to date and you request update only if necessary.
6. Comet Explorer
An icon for the "Find File" utility has been added to the toolbar.
DirBuild now defaults .csv files to "text" files.
The file size of files > 2gb is now displayed properly.
Build 369
1. Windows 2003 Server now properly identified in the Startup Details log.
2. Comet.exe and CosW.exe now surround Comet executable pathnames with quotes.
Previously, Comet may not have started if its pathname contained special characters.
3. Comet Explorer
An erroneous message indicating that the "SESSIONS" file could not be found has
been eliminated. This effected only Comet Anywhere sessions running Comet Explorer.
Build 368
1. Corrcted a problem that could have generated E80 if two or more files were open
with the same name on directories with the same name but different actual paths
(ie running data for more than one company on a system)
2. Corrected problems resulting from dynamic access of a directory by specifying its alias.
Build 367
1. The number of bytes from the last read or write to the WinSock gateway is now
returned by the STS function:
Layout of new STS function
2. Comet Anywhere Client Uninstall
Uninstalling Comet Anywhere no longer removes Microsoft .dlls used by other
applications.
3. Comet Explorer
Corrected a problem found when copying legacy files from one directory to another.
Added a button to the properties dialog for multi-keyed files to display the
attributes of the sub-keys.
Corrected a problem that may have prevented the utilities' results from being launched
to the browser on XP systems. This effected DeleteChain, FileList, KeyCheck, VerifyFile,
and WhoHas.
Build 366
1. Corrected problem that could have caused unpredictable results in programs
using EventSub when issing multiple commands. The cache was not being
flushed properly.
2. Corrected a problem that could have caused dialog-based IB programs to
receive notification of an event more than once. This could unpredictable
results.
CosP
1. Corrected a problem that could have caused problems if pdf documents were left
to accumulate in the default folder. When a new document was created, if a file
with its intended name already existed, an error would be generated.
Build 365
1. CLibNetServe
Corrected a problem that could have caused it to shutdown when server was very busy.
2. Comet Explorer
Corrected some problems found when copying a legacy file to a multi-keyed file.
Build 364
1. A problem that caused the CAID to change when daylight savings time began or ended
has been fixed.
2. Removed changes introduced in .362 that disallowed ACCESS from background partitions.
3. Corrected a problem that could cause GPF if ACTIVATE was attempted when no background
partitions were available.
4. The Comet Explorer Copy Utility has been enhanced to support multi-keyed files.
Build 363
1. Corrected a problem that could have crashed Comet if you got an error on an
ACTIVATE and an EXCP= error handler was coded.
2. Eliminated a crash when running CFAM and Enterlevel exceeded 99. Now an E78
will be issued instead.
3. Corrected a problem shutting down a DES program when abort is in progress
because the user closed the Comet window while generating a print document.
Symptoms of this problem were documents from remote clients being launched on
the host and/or GPF on the host computer.
4. A change has been made to the behavior of the /C startup parameter. The size
of the pathname used when loading Comet has been increased to 64 characters.
Also, only the REL folder will be accessed as this is all that is required
to run SYSGEN.
5. E54 is now issued if you have an html printer open and you attempt to open a
file with invalid keyname. Previously E75 was issued.
6. Eliminated a crash that could occur if you configured a CFAM directory that
did not exist.
Build 362
1. Comet can now be installed to run as a service.
2. Corrected a problem that could have crashed Comet if you got an error on an
ACTIVATE and an error handler was coded (ie ERRORTO or EXCP=).
3. Comet will no longer attempt to start if a connection to any of the configured
file servers fails.
4. Corrected a problem that could have resulted in negative user counts in the file
server dialog if an old version of CFAM attempted to connect.
5. REWRITE to an extended keyed file now always returns E32 if the record does not
already exist.
6. Background partitions can no longer perform DAB accesses. This was part of a move
to enhance security. An access statement executed in background will result in E37 --
CAN'T PERFORM GIVEN ACTION -- NO PERMISSION GRANTED. If you wish a background
partition to have access to particular DABs, just access them before the activate,
and those DABs will be copied to the target partition before the program is launched.
Build 361
1. Corrected a problem with the suppression of the initial formfeed for :RAW printers.
2. Corrected the way COSP determined the location of COSW.INI which could cause the
wrong fonts to get loaded.
3. CFAM will no longer crash if one or more servers was unavailable due to error.
4. A problem that was introduced in .360 that set TERM$ for all background partitions
to "T00" has been corrected. TERM$ for background partition is now always blank.
5. The WinSock gateway is now much faster. A system-enforced pause of 5 seconds was
able to be reduced to 1 tick. This will definitely speed up your WinSock applications
such as sending email from Comet.
6. Now you can develop and test XAP applications before you buy the license. You are
restricted to talking only to the local host at 127.0.0.1.
Build 360
1. New IB statements for use with the Multi-keyed File System for CFAM:
CreateKey FileName, KeyName, KeyLength, KeyPosition, Dir=DirectoryName, [excp=exception address]
Open (LUN) FileName, Key=KeyName[, Dir=DirectoryName][, excp=exception address]
KeyStatInfo$ = KeyStat (LUN) I0XNumber[, excp=exception address]
For more information, refer to the IB manual which is once again available online:
IB Manual
2. The FileList utility in Comet Explorer has been enhanced to support multi-keyed files.
The multi-keyed file system requires CFAM and CometServe0509 or higher.
