DOS vs Comet32


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Robert G Laurin on June 21, 2016 at 12:24:46:

Found a couple of (annoying) issues with Comet32...

--------------

ALIAS... The support for Alias is slightly incomplete. While $(CATEMP) might work, using $(COMET) will NOT if the shortcut points to a DFS Share (Windows Distributed File System akak Domain Shares). It does not work if using a DFS path. Get EXCP 27 - DOS Error

ex: Comet executables are located in \\MyDomain\Comet. So the $(COMET) alias also points to \\MyDomain\Comet

Both are unusable in a variety of Comet32 file commands.

Same is true for QCFIG and {myconfig}.INI which does not support DFS Shares.

------------

NoEXCP

Documentation claims that it works on most file commands. See: http://wiki.signature.net/index.php/IB_Statements/noexcp

however, not all works. InputFile does not in the form:
MyContent$ = InputFile(FullPath$, NoEXCP)

--------------

CometUserFiles.Dat

While this has the potential to be extremely useful, I found that it copies the files, with the Comet executables, to the %TEMP% folder which does not have an Directory Alias and is therefore unavailable to Comet. this process was added in response to the lack of QSTARTX in Comet32.

Note here: don't know why, but I have a VB app that a Launch from Comet in $(CATEMP)... Been working fine for months, but today it could not find the DLL that is in CometUserFiles.Dat and therefore in %TEMP%. Couldn't figure what was different today...


Tested on Comet32.499/16.00 on Windows 7 Pro


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]