CometWiki - User contributions [en]

The Comet Gateways

2020-12-02T21:31:30Z

Barb:

'''Comet Gateways'''
There are several gateways available in Comet98 and Comet2000. These gateways provide access to features that are external to Comet, such as a high-speed sorting function, Internet application-layer protocols and advanced Common Gateway Interface processing, ODBC data sources, the serial port on a PC, and an internal fax/modem.

There are two basic steps for using a gateway: configuration and programming. The configuration step is accomplished with the [GATEWAYS] section in the INI file (which is processed by the SYSGEN program). Each configured gateway is listed in sequence. For example:

'''[GATEWAYS]'''

Gateway = 2,0; Sort driver gateway (gateway G00)
Gateway = 3,0; Winsock gateway (gateway G01)
Gateway = 4,0; XAP gateway (eComet) (gateway G02)
Gateway = 5,0; ODBC gateway (gateway G03)
The ODBC Gateway was replaced by mySQL for Comet32
Gateway = 6,0; Serial gateway (gateway G04)
The Serial Gateway was not implemented for Comet32
Gateway = 7,0; Universal gateway (fax) (gateway G05)
The Universal Gateway (aka the FAX Gateway) was not implemented for Comet32

The programming step starts with opening a specific gateway device. For example, the following statement opens the Winsock gateway shown in the above [GATEWAYS] configuration:

OPEN (20) “G01” ! open Winsock gateway

Note: The Reporter automatically generates the IB code to open the sort gateway, and the eComet Extensions automatically open the XAP gateway and assign the logical unit numbers to it.

For the other types of gateways, here is a general-purpose IB routine that shows how to locate and open a specific type of gateway on LUN (1). In the following example, the program searches for a type 6 gateway (serial gateway), which is signified by the ‘@06@’ returned by the DSTAT function.

length 3.0 & local I
length 3 & local Ga teName$
Open.Gateway:
print(0) 'Opening Gateway . . .'
for I = 100 TO 199
GateName$ = 'G' + SUB(STRIP(STR(I)), 2, 2)
if SUB(DSTAT(GateName$, excp=Try.Next.Gateway), 4, 1) EQ '@06@'_
goto Found.Gateway
Try.Next.Gateway:
next I
print(0) 'Cannot Locate Gateway.'
goto Abort
Found.Gateway:
open(1) GateName$
print(0) 'Gateway found as ';GateName$
return

The following chart shows each type of gateway, whether it is available in Comet98 or Comet2000 (and whether it is included with the base level or available as a add-on product), and describes its basic features. There are also links to documentation and sample programs.
{| border="1"
|-

! Type
! Name
! Comet98
! Comet2000
! Comet32
! Description
|-
| 2
| Sort
gateway
| included
| included
| Not
Included
|The sort driver gateway provides an efficient sorting method for both the Reporter and your IB applications. If the data to be sorted takes up less than 64K bytes, the sort driver performs the sort function in memory, and offers the fastest sort available on a Comet system. For data greater than 64K, the sort driver performs it's sorting using temporary disk files (either RAM or hard disk).

You need to configure one sort driver gateway for each user performing sorting operations simultaneously. We suggest configuring one sort gateway for each Reporter user. Each configured sort driver gateway requires 64K of system memory above and beyond the other memory requirements of Comet. Additionally, if one or more sort driver gateways are configured, the number of partitions that can be configured for a Comet system is reduced by 1.

For information on using the sort gateway from within an IB program, see the sort gateway section in the MoreThanBasic documentation.

|-
| 3
| Winsock
gateway
|
| included
|
|The Winsock gateway provides a way for IB applications to communicate over the Internet using industry-standard application-layer protocols. Introduced with Comet 2005, the Comet Email Printer provides a simple method for sending email from your Comet app.

|-
| 4
| XAP
gateway
|
|add-on
|
|The XAP gateway provides advanced Common Gateway Interface processing, and offers a way to create interactive web pages and eComet applications. XAP technology is patent pending. The many features of the XAP gateway are described in the eComet tutorial.

|-
| 5
| ODBC
client
gateway
|
|add-on
|replaced by SQL device
|The ODBC client gateway provides a way for IB applications to interact with external data sources, including Microsoft Access databases, Excel spreadsheets, and other ODBC-compliant data sources. For more information, see the ODBC client gateway documentation
|-

| 6
| Serial
gateway
|
|add-on
|Not included
|The serial gateway allows an InternetBasic (IB) program to communicate with an external serial device connected to the COM port of the Comet system. For more information, see the serial gateway documentation
|-

| 7
| Universal

gateway
|
| included
| Not
Included
|The universal gateway allows generic communication between Comet and an external driver program. The fax driver is the first example that uses the universal gateway. For information about the fax driver, see the fax driver documentation.

|-
| 8
|Local
XAP
gateway
|
|included
|
|The local XAP gateway allows development of web applications without an XAP license. These applications are limited to pages served by the local host. It's a great way to develop and test your site before implementing a full XAP configuration. For more info on using Comet to host your web site, check out the XAP tutorials..

|-

.

The Comet Gateways

2020-12-02T21:30:57Z

Barb:

'''Comet Gateways'''
There are several gateways available in Comet98 and Comet2000. These gateways provide access to features that are external to Comet, such as a high-speed sorting function, Internet application-layer protocols and advanced Common Gateway Interface processing, ODBC data sources, the serial port on a PC, and an internal fax/modem.

There are two basic steps for using a gateway: configuration and programming. The configuration step is accomplished with the [GATEWAYS] section in the INI file (which is processed by the SYSGEN program). Each configured gateway is listed in sequence. For example:

'''[GATEWAYS]'''

Gateway = 2,0; Sort driver gateway (gateway G00)
Gateway = 3,0; Winsock gateway (gateway G01)
Gateway = 4,0; XAP gateway (eComet) (gateway G02)
Gateway = 5,0; ODBC gateway (gateway G03)
The ODBC Gateway was replaced by mySQL for Comet32
Gateway = 6,0; Serial gateway (gateway G04)
The Serial Gateway was not implemented for Comet32
Gateway = 7,0; Universal gateway (fax) (gateway G05)
The Universal Gateway (aka the FAX Gateway) was not implemented for Comet32

The programming step starts with opening a specific gateway device. For example, the following statement opens the Winsock gateway shown in the above [GATEWAYS] configuration:

OPEN (20) “G01” ! open Winsock gateway

Note: The Reporter automatically generates the IB code to open the sort gateway, and the eComet Extensions automatically open the XAP gateway and assign the logical unit numbers to it.

For the other types of gateways, here is a general-purpose IB routine that shows how to locate and open a specific type of gateway on LUN (1). In the following example, the program searches for a type 6 gateway (serial gateway), which is signified by the ‘@06@’ returned by the DSTAT function.

length 3.0 & local I
length 3 & local Ga teName$
Open.Gateway:
print(0) 'Opening Gateway . . .'
for I = 100 TO 199
GateName$ = 'G' + SUB(STRIP(STR(I)), 2, 2)
if SUB(DSTAT(GateName$, excp=Try.Next.Gateway), 4, 1) EQ '@06@'_
goto Found.Gateway
Try.Next.Gateway:
next I
print(0) 'Cannot Locate Gateway.'
goto Abort
Found.Gateway:
open(1) GateName$
print(0) 'Gateway found as ';GateName$
return

The following chart shows each type of gateway, whether it is available in Comet98 or Comet2000 (and whether it is included with the base level or available as a add-on product), and describes its basic features. There are also links to documentation and sample programs.
{| border="1"
|-

! Type
! Name
! Comet98
! Comet2000
! Comet32
! Description
|-
| 2
| Sort
gateway
| included
| included
| Not
Included
|The sort driver gateway provides an efficient sorting method for both the Reporter and your IB applications. If the data to be sorted takes up less than 64K bytes, the sort driver performs the sort function in memory, and offers the fastest sort available on a Comet system. For data greater than 64K, the sort driver performs it's sorting using temporary disk files (either RAM or hard disk).

You need to configure one sort driver gateway for each user performing sorting operations simultaneously. We suggest configuring one sort gateway for each Reporter user. Each configured sort driver gateway requires 64K of system memory above and beyond the other memory requirements of Comet. Additionally, if one or more sort driver gateways are configured, the number of partitions that can be configured for a Comet system is reduced by 1.

For information on using the sort gateway from within an IB program, see the sort gateway section in the MoreThanBasic documentation.

|-
| 3
| Winsock
gateway
|
| included
|
|The Winsock gateway provides a way for IB applications to communicate over the Internet using industry-standard application-layer protocols. Introduced with Comet 2005, the Comet Email Printer provides a simple method for sending email from your Comet app.

|-
| 4
| XAP
gateway
|
|add-on
|
|The XAP gateway provides advanced Common Gateway Interface processing, and offers a way to create interactive web pages and eComet applications. XAP technology is patent pending. The many features of the XAP gateway are described in the eComet tutorial.

|-
| 5
| ODBC
client
gateway
|
|add-on
|replaced by SQL
|The ODBC client gateway provides a way for IB applications to interact with external data sources, including Microsoft Access databases, Excel spreadsheets, and other ODBC-compliant data sources. For more information, see the ODBC client gateway documentation
|-

| 6
| Serial
gateway
|
|add-on
|Not included
|The serial gateway allows an InternetBasic (IB) program to communicate with an external serial device connected to the COM port of the Comet system. For more information, see the serial gateway documentation
|-

| 7
| Universal

gateway
|
| included
| Not
Included
|The universal gateway allows generic communication between Comet and an external driver program. The fax driver is the first example that uses the universal gateway. For information about the fax driver, see the fax driver documentation.

|-
| 8
|Local
XAP
gateway
|
|included
|
|The local XAP gateway allows development of web applications without an XAP license. These applications are limited to pages served by the local host. It's a great way to develop and test your site before implementing a full XAP configuration. For more info on using Comet to host your web site, check out the XAP tutorials..

|-

.

The Comet Gateways

2020-12-02T21:30:09Z

Barb:

'''Comet Gateways'''
There are several gateways available in Comet98 and Comet2000. These gateways provide access to features that are external to Comet, such as a high-speed sorting function, Internet application-layer protocols and advanced Common Gateway Interface processing, ODBC data sources, the serial port on a PC, and an internal fax/modem.

There are two basic steps for using a gateway: configuration and programming. The configuration step is accomplished with the [GATEWAYS] section in the INI file (which is processed by the SYSGEN program). Each configured gateway is listed in sequence. For example:

'''[GATEWAYS]'''

Gateway = 2,0; Sort driver gateway (gateway G00)
Gateway = 3,0; Winsock gateway (gateway G01)
Gateway = 4,0; XAP gateway (eComet) (gateway G02)
Gateway = 5,0; ODBC gateway (gateway G03)
The ODBC Gateway was replaced by mySQL for Comet32
Gateway = 6,0; Serial gateway (gateway G04)
The Serial Gateway was not implemented for Comet32
Gateway = 7,0; Universal gateway (fax) (gateway G05)
The Universal Gateway (aka the FAX Gateway) was not implemented for Comet32

The programming step starts with opening a specific gateway device. For example, the following statement opens the Winsock gateway shown in the above [GATEWAYS] configuration:

OPEN (20) “G01” ! open Winsock gateway

Note: The Reporter automatically generates the IB code to open the sort gateway, and the eComet Extensions automatically open the XAP gateway and assign the logical unit numbers to it.

For the other types of gateways, here is a general-purpose IB routine that shows how to locate and open a specific type of gateway on LUN (1). In the following example, the program searches for a type 6 gateway (serial gateway), which is signified by the ‘@06@’ returned by the DSTAT function.

length 3.0 & local I
length 3 & local Ga teName$
Open.Gateway:
print(0) 'Opening Gateway . . .'
for I = 100 TO 199
GateName$ = 'G' + SUB(STRIP(STR(I)), 2, 2)
if SUB(DSTAT(GateName$, excp=Try.Next.Gateway), 4, 1) EQ '@06@'_
goto Found.Gateway
Try.Next.Gateway:
next I
print(0) 'Cannot Locate Gateway.'
goto Abort
Found.Gateway:
open(1) GateName$
print(0) 'Gateway found as ';GateName$
return

The following chart shows each type of gateway, whether it is available in Comet98 or Comet2000 (and whether it is included with the base level or available as a add-on product), and describes its basic features. There are also links to documentation and sample programs.
{| border="1"
|-

! Type
! Name
! Comet98
! Comet2000
! Comet32
! Description
|-
| 2
| Sort
gateway
| included
| included
| Not
Included
|The sort driver gateway provides an efficient sorting method for both the Reporter and your IB applications. If the data to be sorted takes up less than 64K bytes, the sort driver performs the sort function in memory, and offers the fastest sort available on a Comet system. For data greater than 64K, the sort driver performs it's sorting using temporary disk files (either RAM or hard disk).

You need to configure one sort driver gateway for each user performing sorting operations simultaneously. We suggest configuring one sort gateway for each Reporter user. Each configured sort driver gateway requires 64K of system memory above and beyond the other memory requirements of Comet. Additionally, if one or more sort driver gateways are configured, the number of partitions that can be configured for a Comet system is reduced by 1.

For information on using the sort gateway from within an IB program, see the sort gateway section in the MoreThanBasic documentation.

|-
| 3
| Winsock
gateway
|
| included
|
|The Winsock gateway provides a way for IB applications to communicate over the Internet using industry-standard application-layer protocols. Introduced with Comet 2005, the Comet Email Printer provides a simple method for sending email from your Comet app.

|-
| 4
| XAP
gateway
|
|add-on
|
|The XAP gateway provides advanced Common Gateway Interface processing, and offers a way to create interactive web pages and eComet applications. XAP technology is patent pending. The many features of the XAP gateway are described in the eComet tutorial.

|-
| 5
| ODBC
client
gateway
|
|add-on
|
|The ODBC client gateway provides a way for IB applications to interact with external data sources, including Microsoft Access databases, Excel spreadsheets, and other ODBC-compliant data sources. For more information, see the ODBC client gateway documentation
|-

| 6
| Serial
gateway
|
|add-on
|Not included
|The serial gateway allows an InternetBasic (IB) program to communicate with an external serial device connected to the COM port of the Comet system. For more information, see the serial gateway documentation
|-

| 7
| Universal

gateway
|
| included
| Not
Included
|The universal gateway allows generic communication between Comet and an external driver program. The fax driver is the first example that uses the universal gateway. For information about the fax driver, see the fax driver documentation.

|-
| 8
|Local
XAP
gateway
|
|included
|
|The local XAP gateway allows development of web applications without an XAP license. These applications are limited to pages served by the local host. It's a great way to develop and test your site before implementing a full XAP configuration. For more info on using Comet to host your web site, check out the XAP tutorials..

|-

.

The Comet Gateways

2020-12-02T21:28:59Z

Barb:

'''Comet Gateways'''
There are several gateways available in Comet98 and Comet2000. These gateways provide access to features that are external to Comet, such as a high-speed sorting function, Internet application-layer protocols and advanced Common Gateway Interface processing, ODBC data sources, the serial port on a PC, and an internal fax/modem.

There are two basic steps for using a gateway: configuration and programming. The configuration step is accomplished with the [GATEWAYS] section in the INI file (which is processed by the SYSGEN program). Each configured gateway is listed in sequence. For example:

'''[GATEWAYS]'''

Gateway = 2,0; Sort driver gateway (gateway G00)
Gateway = 3,0; Winsock gateway (gateway G01)
Gateway = 4,0; XAP gateway (eComet) (gateway G02)
Gateway = 5,0; ODBC gateway (gateway G03)
The ODBC Gateway was replaced by mySQL for Comet32
Gateway = 6,0; Serial gateway (gateway G04)
The Serial Gateway was not implemented for Comet32
Gateway = 7,0; Universal gateway (fax) (gateway G05)
The Universal Gateway (aka the FAX Gateway) was not implemented for Comet32

The programming step starts with opening a specific gateway device. For example, the following statement opens the Winsock gateway shown in the above [GATEWAYS] configuration:

OPEN (20) “G01” ! open Winsock gateway

Note: The Reporter automatically generates the IB code to open the sort gateway, and the eComet Extensions automatically open the XAP gateway and assign the logical unit numbers to it.

For the other types of gateways, here is a general-purpose IB routine that shows how to locate and open a specific type of gateway on LUN (1). In the following example, the program searches for a type 6 gateway (serial gateway), which is signified by the ‘@06@’ returned by the DSTAT function.

length 3.0 & local I
length 3 & local Ga teName$
Open.Gateway:
print(0) 'Opening Gateway . . .'
for I = 100 TO 199
GateName$ = 'G' + SUB(STRIP(STR(I)), 2, 2)
if SUB(DSTAT(GateName$, excp=Try.Next.Gateway), 4, 1) EQ '@06@'_
goto Found.Gateway
Try.Next.Gateway:
next I
print(0) 'Cannot Locate Gateway.'
goto Abort
Found.Gateway:
open(1) GateName$
print(0) 'Gateway found as ';GateName$
return

The following chart shows each type of gateway, whether it is available in Comet98 or Comet2000 (and whether it is included with the base level or available as a add-on product), and describes its basic features. There are also links to documentation and sample programs.
{| border="1"
|-

! Type
! Name
! Comet98
! Comet2000
! Comet32
! Description
|-
| 2
| Sort
gateway
| included
| included
| Not
Included
|The sort driver gateway provides an efficient sorting method for both the Reporter and your IB applications. If the data to be sorted takes up less than 64K bytes, the sort driver performs the sort function in memory, and offers the fastest sort available on a Comet system. For data greater than 64K, the sort driver performs it's sorting using temporary disk files (either RAM or hard disk).

You need to configure one sort driver gateway for each user performing sorting operations simultaneously. We suggest configuring one sort gateway for each Reporter user. Each configured sort driver gateway requires 64K of system memory above and beyond the other memory requirements of Comet. Additionally, if one or more sort driver gateways are configured, the number of partitions that can be configured for a Comet system is reduced by 1.

For information on using the sort gateway from within an IB program, see the sort gateway section in the MoreThanBasic documentation.

|-
| 3
| Winsock
gateway
|
| included
|
|The Winsock gateway provides a way for IB applications to communicate over the Internet using industry-standard application-layer protocols. Introduced with Comet 2005, the Comet Email Printer provides a simple method for sending email from your Comet app.

|-
| 4
| XAP
gateway
|
|add-on
|
|The XAP gateway provides advanced Common Gateway Interface processing, and offers a way to create interactive web pages and eComet applications. XAP technology is patent pending. The many features of the XAP gateway are described in the eComet tutorial.

|-
| 5
| ODBC
client
gateway
|
|add-on
|
|The ODBC client gateway provides a way for IB applications to interact with external data sources, including Microsoft Access databases, Excel spreadsheets, and other ODBC-compliant data sources. For more information, see the ODBC client gateway documentation
|-

| 6
| Serial
gateway
|
|add-on
|
|The serial gateway allows an InternetBasic (IB) program to communicate with an external serial device connected to the COM port of the Comet system. For more information, see the serial gateway documentation
|-

| 7
| Universal

gateway
|
| included
| Not
Included
|The universal gateway allows generic communication between Comet and an external driver program. The fax driver is the first example that uses the universal gateway. For information about the fax driver, see the fax driver documentation.

|-
| 8
|Local
XAP
gateway
|
|included
|
|The local XAP gateway allows development of web applications without an XAP license. These applications are limited to pages served by the local host. It's a great way to develop and test your site before implementing a full XAP configuration. For more info on using Comet to host your web site, check out the XAP tutorials..

|-

.

The Comet Gateways

2020-12-01T19:34:33Z

Barb:

'''Comet Gateways'''
There are several gateways available in Comet98 and Comet2000. These gateways provide access to features that are external to Comet, such as a high-speed sorting function, Internet application-layer protocols and advanced Common Gateway Interface processing, ODBC data sources, the serial port on a PC, and an internal fax/modem.

There are two basic steps for using a gateway: configuration and programming. The configuration step is accomplished with the [GATEWAYS] section in the INI file (which is processed by the SYSGEN program). Each configured gateway is listed in sequence. For example:

'''[GATEWAYS]'''

Gateway = 2,0; Sort driver gateway (gateway G00)
Gateway = 3,0; Winsock gateway (gateway G01)
Gateway = 4,0; XAP gateway (eComet) (gateway G02)
Gateway = 5,0; ODBC gateway (gateway G03)
Gateway = 6,0; Serial gateway (gateway G04)
Gateway = 7,0; Universal gateway (fax) (gateway G05)
NOTE: The Universal Gateway (aka the FAX Gateway) was not implemented for Comet32

The programming step starts with opening a specific gateway device. For example, the following statement opens the Winsock gateway shown in the above [GATEWAYS] configuration:

OPEN (20) “G01” ! open Winsock gateway

Note: The Reporter automatically generates the IB code to open the sort gateway, and the eComet Extensions automatically open the XAP gateway and assign the logical unit numbers to it.

For the other types of gateways, here is a general-purpose IB routine that shows how to locate and open a specific type of gateway on LUN (1). In the following example, the program searches for a type 6 gateway (serial gateway), which is signified by the ‘@06@’ returned by the DSTAT function.

length 3.0 & local I
length 3 & local Ga teName$
Open.Gateway:
print(0) 'Opening Gateway . . .'
for I = 100 TO 199
GateName$ = 'G' + SUB(STRIP(STR(I)), 2, 2)
if SUB(DSTAT(GateName$, excp=Try.Next.Gateway), 4, 1) EQ '@06@'_
goto Found.Gateway
Try.Next.Gateway:
next I
print(0) 'Cannot Locate Gateway.'
goto Abort
Found.Gateway:
open(1) GateName$
print(0) 'Gateway found as ';GateName$
return

The following chart shows each type of gateway, whether it is available in Comet98 or Comet2000 (and whether it is included with the base level or available as a add-on product), and describes its basic features. There are also links to documentation and sample programs.
{| border="1"
|-

! Type
! Name
! Comet98
! Comet2000
! Comet32
! Description
|-
| 2
| Sort
gateway
| included
| included
| Not
Included
|The sort driver gateway provides an efficient sorting method for both the Reporter and your IB applications. If the data to be sorted takes up less than 64K bytes, the sort driver performs the sort function in memory, and offers the fastest sort available on a Comet system. For data greater than 64K, the sort driver performs it's sorting using temporary disk files (either RAM or hard disk).

You need to configure one sort driver gateway for each user performing sorting operations simultaneously. We suggest configuring one sort gateway for each Reporter user. Each configured sort driver gateway requires 64K of system memory above and beyond the other memory requirements of Comet. Additionally, if one or more sort driver gateways are configured, the number of partitions that can be configured for a Comet system is reduced by 1.

For information on using the sort gateway from within an IB program, see the sort gateway section in the MoreThanBasic documentation.

|-
| 3
| Winsock
gateway
|
| included
|
|The Winsock gateway provides a way for IB applications to communicate over the Internet using industry-standard application-layer protocols. Introduced with Comet 2005, the Comet Email Printer provides a simple method for sending email from your Comet app.

|-
| 4
| XAP
gateway
|
|add-on
|
|The XAP gateway provides advanced Common Gateway Interface processing, and offers a way to create interactive web pages and eComet applications. XAP technology is patent pending. The many features of the XAP gateway are described in the eComet tutorial.

|-
| 5
| ODBC
client
gateway
|
|add-on
|
|The ODBC client gateway provides a way for IB applications to interact with external data sources, including Microsoft Access databases, Excel spreadsheets, and other ODBC-compliant data sources. For more information, see the ODBC client gateway documentation
|-

| 6
| Serial
gateway
|
|add-on
|
|The serial gateway allows an InternetBasic (IB) program to communicate with an external serial device connected to the COM port of the Comet system. For more information, see the serial gateway documentation
|-

| 7
| Universal

gateway
|
| included
| Not
Included
|The universal gateway allows generic communication between Comet and an external driver program. The fax driver is the first example that uses the universal gateway. For information about the fax driver, see the fax driver documentation.

|-
| 8
|Local
XAP
gateway
|
|included
|
|The local XAP gateway allows development of web applications without an XAP license. These applications are limited to pages served by the local host. It's a great way to develop and test your site before implementing a full XAP configuration. For more info on using Comet to host your web site, check out the XAP tutorials..

|-

.

The Comet Gateways

2020-12-01T16:27:04Z

Barb:

'''Comet Gateways'''
There are several gateways available in Comet98 and Comet2000. These gateways provide access to features that are external to Comet, such as a high-speed sorting function, Internet application-layer protocols and advanced Common Gateway Interface processing, ODBC data sources, the serial port on a PC, and an internal fax/modem.

There are two basic steps for using a gateway: configuration and programming. The configuration step is accomplished with the [GATEWAYS] section in the INI file (which is processed by the SYSGEN program). Each configured gateway is listed in sequence. For example:

'''[GATEWAYS]'''

Gateway = 2,0; Sort driver gateway (gateway G00)
Gateway = 3,0; Winsock gateway (gateway G01)
Gateway = 4,0; XAP gateway (eComet) (gateway G02)
Gateway = 5,0; ODBC gateway (gateway G03)
Gateway = 6,0; Serial gateway (gateway G04)
Gateway = 7,0; Universal gateway (fax) (gateway G05)
NOTE: The Universal Gateway (aka the FAX Gateway) was not implemented for Comet32

The programming step starts with opening a specific gateway device. For example, the following statement opens the Winsock gateway shown in the above [GATEWAYS] configuration:

OPEN (20) “G01” ! open Winsock gateway

Note: The Reporter automatically generates the IB code to open the sort gateway, and the eComet Extensions automatically open the XAP gateway and assign the logical unit numbers to it.

For the other types of gateways, here is a general-purpose IB routine that shows how to locate and open a specific type of gateway on LUN (1). In the following example, the program searches for a type 6 gateway (serial gateway), which is signified by the ‘@06@’ returned by the DSTAT function.

length 3.0 & local I
length 3 & local Ga teName$
Open.Gateway:
print(0) 'Opening Gateway . . .'
for I = 100 TO 199
GateName$ = 'G' + SUB(STRIP(STR(I)), 2, 2)
if SUB(DSTAT(GateName$, excp=Try.Next.Gateway), 4, 1) EQ '@06@'_
goto Found.Gateway
Try.Next.Gateway:
next I
print(0) 'Cannot Locate Gateway.'
goto Abort
Found.Gateway:
open(1) GateName$
print(0) 'Gateway found as ';GateName$
return

The following chart shows each type of gateway, whether it is available in Comet98 or Comet2000 (and whether it is included with the base level or available as a add-on product), and describes its basic features. There are also links to documentation and sample programs.
{| border="1"
|-

! Type
! Name
! Comet98
! Comet2000
! Comet32
! Description
|-
| 2
| Sort
gateway
| included
| included
| Not
Included
|The sort driver gateway provides an efficient sorting method for both the Reporter and your IB applications. If the data to be sorted takes up less than 64K bytes, the sort driver performs the sort function in memory, and offers the fastest sort available on a Comet system. For data greater than 64K, the sort driver performs it's sorting using temporary disk files (either RAM or hard disk).

You need to configure one sort driver gateway for each user performing sorting operations simultaneously. We suggest configuring one sort gateway for each Reporter user. Each configured sort driver gateway requires 64K of system memory above and beyond the other memory requirements of Comet. Additionally, if one or more sort driver gateways are configured, the number of partitions that can be configured for a Comet system is reduced by 1.

For information on using the sort gateway from within an IB program, see the sort gateway section in the MoreThanBasic documentation.

|-
| 3
| Winsock
gateway
|
| included
|
|The Winsock gateway provides a way for IB applications to communicate over the Internet using industry-standard application-layer protocols. Introduced with Comet 2005, the Comet Email Printer provides a simple method for sending email from your Comet app.

|-
| 4
| XAP
gateway
|
|add-on
|
|The XAP gateway provides advanced Common Gateway Interface processing, and offers a way to create interactive web pages and eComet applications. XAP technology is patent pending. The many features of the XAP gateway are described in the eComet tutorial.

|-
| 5
| ODBC
client
gateway
|
|add-on
|
|The ODBC client gateway provides a way for IB applications to interact with external data sources, including Microsoft Access databases, Excel spreadsheets, and other ODBC-compliant data sources. For more information, see the ODBC client gateway documentation
|-

| 6
| Serial
gateway
|
|add-on
|
|The serial gateway allows an InternetBasic (IB) program to communicate with an external serial device connected to the COM port of the Comet system. For more information, see the serial gateway documentation
|-

| 7
| Universal

gateway
|
| included
|
|The universal gateway allows generic communication between Comet and an external driver program. The fax driver is the first example that uses the universal gateway. For information about the fax driver, see the fax driver documentation.

|-
| 8
|Local
XAP
gateway
|
|included
|
|The local XAP gateway allows development of web applications without an XAP license. These applications are limited to pages served by the local host. It's a great way to develop and test your site before implementing a full XAP configuration. For more info on using Comet to host your web site, check out the XAP tutorials..

|-

.

The Comet Gateways

2020-12-01T16:24:51Z

Barb:

'''Comet Gateways'''
There are several gateways available in Comet98 and Comet2000. These gateways provide access to features that are external to Comet, such as a high-speed sorting function, Internet application-layer protocols and advanced Common Gateway Interface processing, ODBC data sources, the serial port on a PC, and an internal fax/modem.

There are two basic steps for using a gateway: configuration and programming. The configuration step is accomplished with the [GATEWAYS] section in the INI file (which is processed by the SYSGEN program). Each configured gateway is listed in sequence. For example:

'''[GATEWAYS]'''

Gateway = 2,0; Sort driver gateway (gateway G00)
Gateway = 3,0; Winsock gateway (gateway G01)
Gateway = 4,0; XAP gateway (eComet) (gateway G02)
Gateway = 5,0; ODBC gateway (gateway G03)
Gateway = 6,0; Serial gateway (gateway G04)
Gateway = 7,0; Universal gateway (fax) (gateway G05) (The Universal Gateway (aka the FAX Gateway) was not implemented for Comet32)

The programming step starts with opening a specific gateway device. For example, the following statement opens the Winsock gateway shown in the above [GATEWAYS] configuration:

OPEN (20) “G01” ! open Winsock gateway

Note: The Reporter automatically generates the IB code to open the sort gateway, and the eComet Extensions automatically open the XAP gateway and assign the logical unit numbers to it.

For the other types of gateways, here is a general-purpose IB routine that shows how to locate and open a specific type of gateway on LUN (1). In the following example, the program searches for a type 6 gateway (serial gateway), which is signified by the ‘@06@’ returned by the DSTAT function.

length 3.0 & local I
length 3 & local Ga teName$
Open.Gateway:
print(0) 'Opening Gateway . . .'
for I = 100 TO 199
GateName$ = 'G' + SUB(STRIP(STR(I)), 2, 2)
if SUB(DSTAT(GateName$, excp=Try.Next.Gateway), 4, 1) EQ '@06@'_
goto Found.Gateway
Try.Next.Gateway:
next I
print(0) 'Cannot Locate Gateway.'
goto Abort
Found.Gateway:
open(1) GateName$
print(0) 'Gateway found as ';GateName$
return

The following chart shows each type of gateway, whether it is available in Comet98 or Comet2000 (and whether it is included with the base level or available as a add-on product), and describes its basic features. There are also links to documentation and sample programs.
{| border="1"
|-

! Type
! Name
! Comet98
! Comet2000
! Comet32
! Description
|-
| 2
| Sort
gateway
| included
| included
| Not
Included
|The sort driver gateway provides an efficient sorting method for both the Reporter and your IB applications. If the data to be sorted takes up less than 64K bytes, the sort driver performs the sort function in memory, and offers the fastest sort available on a Comet system. For data greater than 64K, the sort driver performs it's sorting using temporary disk files (either RAM or hard disk).

You need to configure one sort driver gateway for each user performing sorting operations simultaneously. We suggest configuring one sort gateway for each Reporter user. Each configured sort driver gateway requires 64K of system memory above and beyond the other memory requirements of Comet. Additionally, if one or more sort driver gateways are configured, the number of partitions that can be configured for a Comet system is reduced by 1.

For information on using the sort gateway from within an IB program, see the sort gateway section in the MoreThanBasic documentation.

|-
| 3
| Winsock
gateway
|
| included
|
|The Winsock gateway provides a way for IB applications to communicate over the Internet using industry-standard application-layer protocols. Introduced with Comet 2005, the Comet Email Printer provides a simple method for sending email from your Comet app.

|-
| 4
| XAP
gateway
|
|add-on
|
|The XAP gateway provides advanced Common Gateway Interface processing, and offers a way to create interactive web pages and eComet applications. XAP technology is patent pending. The many features of the XAP gateway are described in the eComet tutorial.

|-
| 5
| ODBC
client
gateway
|
|add-on
|
|The ODBC client gateway provides a way for IB applications to interact with external data sources, including Microsoft Access databases, Excel spreadsheets, and other ODBC-compliant data sources. For more information, see the ODBC client gateway documentation
|-

| 6
| Serial
gateway
|
|add-on
|
|The serial gateway allows an InternetBasic (IB) program to communicate with an external serial device connected to the COM port of the Comet system. For more information, see the serial gateway documentation
|-

| 7
| Universal

gateway
|
| included
|
|The universal gateway allows generic communication between Comet and an external driver program. The fax driver is the first example that uses the universal gateway. For information about the fax driver, see the fax driver documentation.

|-
| 8
|Local
XAP
gateway
|
|included
|
|The local XAP gateway allows development of web applications without an XAP license. These applications are limited to pages served by the local host. It's a great way to develop and test your site before implementing a full XAP configuration. For more info on using Comet to host your web site, check out the XAP tutorials..

|-

.

Virtual Dongle

2020-09-21T16:12:49Z

Barb: /* Comet Security Server Virtual Dongle Installation */

== Comet Security Server Virtual Dongle Installation ==

The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:

*A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [http://www.signature.net/download/End%20User%20License%20Agreement.pdf]

*You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
*The Comet Security Server must have a reliable internet connection. If you use Internet Security Software you'll need to set it up to allow 2-way traffic with dongle.signature.net (to port 80) and signature.net (to port 8080). Be aware that your use of a proxy server may interfere with this communication. Also we have had customers with problems when SonicWall was doing content filtering. It may need to be disabled.
*The Comet Security Server must be running as a service and have '''administrator privileges'''.
*A Virtual Dongle may be associated with one and only one computer. Once installed you may not move it to another computer.

 If you are replacing an existing USB or parallel dongle:

*Install Server Products vsn 18 or higher on your server and make sure all is well using the existing dongle.
*Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
*Stop the Comet Services then remove the old dongle.
*Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''
*Return the old dongle to Signature Systems so that the permanent certificate can be issued.

 If you are installing a new system:

*Make sure your internet connection is working on the server where the Comet Services will be installed.
*If you haven't already done so, we recommend you install the Microsoft Redistributables Package. Some of the .NET framework files are used by the Security Server. You can download vcredist_x86.exe here [http://www.signature.net/download/MailBoxes/]
*Create the Comet Services folder.
*Put the DRB.txt file into that folder.
*Install Server Products vsn 18 or higher on your server. When it asks for dongle type, choose USB. This is because the Security Server will attempt to find a USB dongle first and it needs the drivers to be able to do that. When it asks if you want to restart Windows, say '''"No"'''. Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''

 Notes:
The DRB.txt file is a single-use file for installing and registering your virtual dongle. It is unique for each dongle installed. Once the installation has been registered successfully with our server the DRB.txt file expires and cannot be reused. This file is different from the Comet License Certificate file. Virtual dongles use a license file just like USB or parallel port dongles. The license file will be updated each time your subscription is renewed or new products are purchased.

STL Container IB Reference

2020-07-14T23:37:01Z

Barb: /* Utility Functions */

===Core Functions===
These are the main functions you will use for each container.

====Vector====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the vector
'''stlPopBack( <container-name> )''' removes the element at the end of the vector
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the front of the vector
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the vector
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Similar to arrays, vectors are mostly used to access data based on a numeric index, thus stlGet and stlSet are going to be your bread and butter functions for this container. stlPushBack is a great way to programatically build a vector - it will append the specified data to the end of the vector, and increase its size by 1. If you want to remove the last element, you would use stlPopBack. Then the stlFront and stlBack functions have been included as shortcuts for accessing the first and last elements respectively.

====List====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the list
'''stlPopBack( <container-name> )''' removes the element at the end of the list
'''stlPushFront( <container-name>, <data> )''' adds an element to the beginning of the list
'''stlPopFront( <container-name> )''' removes the element at the beginning of the list
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the beginning of the list
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the list

Lists are designed to be accessed sequentially, that is each element is associated with the preceding and following elements in the container. As such, the core functions provided are used to add, remove, and get the elements at the front and back of the list. The real power of lists is utilized during iteration - they are the most efficient container for inserting and erasing elements in the middle of the container.

====Map====
'''stlGet( <container-name>, <key> [,EXCP=statement label])''' gets the element at the key specified
'''stlSet( <container-name> <key> <data>)''' sets the element at the key specified

Maps are used to relate an element to a key (string index). Similar to vectors, to access a value, the key must be specified.

====Stack/Queue====
'''stlPush( <container-name>, <data> )''' adds an element to the container
'''stlPop( <container-name> )''' removes the next element from the container
'''stlPeek( <container-name> [,EXCP=statement label])''' gets the next element from the container
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Both stacks and queues utilize the same set of functions, but perform differently depending on which container you have implemented. In general, the stlPush, stlPop, and stlPeek functions are going to be the most important of these functions. They perform the basic operations associated with these containers. For stacks, stlPush and stlPop adds and removes from the end of the container. For queues, stlPush adds to the end of the container, and stlPop removes from the front of the container. For both containers, stlPeek will get the "next" element in the container (i.e. the last element for stacks, the first element for queues).

Because these containers are implemented with deques internally, we also provide access via numeric indexes with the stlSet() and stlGet() operators. These functions behave similarly to the vector functions of the same name, by getting and setting the elements at the specified index.

===Iteration Functions===
These functions are used to iterate over the elements of a container.

General:
'''stlBegin( <container-name> )''' sets the iterator position at the beginning
'''stlEnd( <container-name> )''' sets the iterator position at the end
'''stlNext( <container-name> )''' moves the iterator position forward one element
'''stlPrev( <container-name> )''' moves the iterator position back one element
'''stlRead( <container-name> [,EXCP=statement label])''' gets the element at the current iterator position
'''stlWrite( <container-name>, <data> )''' - sets the element at the current iterator position

Maps only:
'''stlReadKey( <container-name> [,EXCP=statement label])''' gets the key at the current iterator position

Lists only:
'''stlInsert( <container-name>, <data> )''' inserts the element BEFORE the current iterator position
'''stlErase( <container-name> )''' erases the element at the current iterator position
(stlErase will subsequently move the iterator position to the next element)

===Utility Functions===
These are basic functions that return information about the specified container.

'''stlSize( <container-name> [,EXCP=statement label])''' returns the size of the container
'''stlEmpty( <container-name> [,EXCP=statement label])''' returns whether the container is empty
'''stlClear( <container-name> )''' empties the specified container
'''stlReset( <container-name> )''' resets the container to its initial values

===Meta Functions===
These functions perform some action either on all of the elements in the container, or using all the elements in the container.

STL Container IB Reference

2020-07-14T23:33:15Z

Barb: /* Iteration Functions */

===Core Functions===
These are the main functions you will use for each container.

====Vector====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the vector
'''stlPopBack( <container-name> )''' removes the element at the end of the vector
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the front of the vector
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the vector
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Similar to arrays, vectors are mostly used to access data based on a numeric index, thus stlGet and stlSet are going to be your bread and butter functions for this container. stlPushBack is a great way to programatically build a vector - it will append the specified data to the end of the vector, and increase its size by 1. If you want to remove the last element, you would use stlPopBack. Then the stlFront and stlBack functions have been included as shortcuts for accessing the first and last elements respectively.

====List====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the list
'''stlPopBack( <container-name> )''' removes the element at the end of the list
'''stlPushFront( <container-name>, <data> )''' adds an element to the beginning of the list
'''stlPopFront( <container-name> )''' removes the element at the beginning of the list
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the beginning of the list
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the list

Lists are designed to be accessed sequentially, that is each element is associated with the preceding and following elements in the container. As such, the core functions provided are used to add, remove, and get the elements at the front and back of the list. The real power of lists is utilized during iteration - they are the most efficient container for inserting and erasing elements in the middle of the container.

====Map====
'''stlGet( <container-name>, <key> [,EXCP=statement label])''' gets the element at the key specified
'''stlSet( <container-name> <key> <data>)''' sets the element at the key specified

Maps are used to relate an element to a key (string index). Similar to vectors, to access a value, the key must be specified.

====Stack/Queue====
'''stlPush( <container-name>, <data> )''' adds an element to the container
'''stlPop( <container-name> )''' removes the next element from the container
'''stlPeek( <container-name> [,EXCP=statement label])''' gets the next element from the container
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Both stacks and queues utilize the same set of functions, but perform differently depending on which container you have implemented. In general, the stlPush, stlPop, and stlPeek functions are going to be the most important of these functions. They perform the basic operations associated with these containers. For stacks, stlPush and stlPop adds and removes from the end of the container. For queues, stlPush adds to the end of the container, and stlPop removes from the front of the container. For both containers, stlPeek will get the "next" element in the container (i.e. the last element for stacks, the first element for queues).

Because these containers are implemented with deques internally, we also provide access via numeric indexes with the stlSet() and stlGet() operators. These functions behave similarly to the vector functions of the same name, by getting and setting the elements at the specified index.

===Iteration Functions===
These functions are used to iterate over the elements of a container.

General:
'''stlBegin( <container-name> )''' sets the iterator position at the beginning
'''stlEnd( <container-name> )''' sets the iterator position at the end
'''stlNext( <container-name> )''' moves the iterator position forward one element
'''stlPrev( <container-name> )''' moves the iterator position back one element
'''stlRead( <container-name> [,EXCP=statement label])''' gets the element at the current iterator position
'''stlWrite( <container-name>, <data> )''' - sets the element at the current iterator position

Maps only:
'''stlReadKey( <container-name> [,EXCP=statement label])''' gets the key at the current iterator position

Lists only:
'''stlInsert( <container-name>, <data> )''' inserts the element BEFORE the current iterator position
'''stlErase( <container-name> )''' erases the element at the current iterator position
(stlErase will subsequently move the iterator position to the next element)

===Utility Functions===
These are basic functions that return information about the specified container.

'''stlSize( <container-name> )''' returns the size of the container
'''stlEmpty( <container-name> )''' returns whether the container is empty
'''stlClear( <container-name> )''' empties the specified container
'''stlReset( <container-name> )''' resets the container to its initial values

===Meta Functions===
These functions perform some action either on all of the elements in the container, or using all the elements in the container.

STL Container IB Reference

2020-07-14T23:29:48Z

Barb: /* Iteration Functions */

===Core Functions===
These are the main functions you will use for each container.

====Vector====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the vector
'''stlPopBack( <container-name> )''' removes the element at the end of the vector
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the front of the vector
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the vector
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Similar to arrays, vectors are mostly used to access data based on a numeric index, thus stlGet and stlSet are going to be your bread and butter functions for this container. stlPushBack is a great way to programatically build a vector - it will append the specified data to the end of the vector, and increase its size by 1. If you want to remove the last element, you would use stlPopBack. Then the stlFront and stlBack functions have been included as shortcuts for accessing the first and last elements respectively.

====List====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the list
'''stlPopBack( <container-name> )''' removes the element at the end of the list
'''stlPushFront( <container-name>, <data> )''' adds an element to the beginning of the list
'''stlPopFront( <container-name> )''' removes the element at the beginning of the list
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the beginning of the list
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the list

Lists are designed to be accessed sequentially, that is each element is associated with the preceding and following elements in the container. As such, the core functions provided are used to add, remove, and get the elements at the front and back of the list. The real power of lists is utilized during iteration - they are the most efficient container for inserting and erasing elements in the middle of the container.

====Map====
'''stlGet( <container-name>, <key> [,EXCP=statement label])''' gets the element at the key specified
'''stlSet( <container-name> <key> <data>)''' sets the element at the key specified

Maps are used to relate an element to a key (string index). Similar to vectors, to access a value, the key must be specified.

====Stack/Queue====
'''stlPush( <container-name>, <data> )''' adds an element to the container
'''stlPop( <container-name> )''' removes the next element from the container
'''stlPeek( <container-name> [,EXCP=statement label])''' gets the next element from the container
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Both stacks and queues utilize the same set of functions, but perform differently depending on which container you have implemented. In general, the stlPush, stlPop, and stlPeek functions are going to be the most important of these functions. They perform the basic operations associated with these containers. For stacks, stlPush and stlPop adds and removes from the end of the container. For queues, stlPush adds to the end of the container, and stlPop removes from the front of the container. For both containers, stlPeek will get the "next" element in the container (i.e. the last element for stacks, the first element for queues).

Because these containers are implemented with deques internally, we also provide access via numeric indexes with the stlSet() and stlGet() operators. These functions behave similarly to the vector functions of the same name, by getting and setting the elements at the specified index.

===Iteration Functions===
These functions are used to iterate over the elements of a container.

General:
'''stlBegin( <container-name> )''' sets the iterator position at the beginning
'''stlEnd( <container-name> )''' sets the iterator position at the end
'''stlNext( <container-name> )''' moves the iterator position forward one element
'''stlPrev( <container-name> )''' moves the iterator position back one element
'''stlRead( <container-name> [,EXCP=statement label])''' gets the element at the current iterator position
'''stlWrite( <container-name>, <data> )''' - sets the element at the current iterator position

Maps only:
'''stlReadKey( <container-name> )''' gets the key at the current iterator position

Lists only:
'''stlInsert( <container-name>, <data> )''' inserts the element BEFORE the current iterator position
'''stlErase( <container-name> )''' erases the element at the current iterator position
(stlErase will subsequently move the iterator position to the next element)

===Utility Functions===
These are basic functions that return information about the specified container.

'''stlSize( <container-name> )''' returns the size of the container
'''stlEmpty( <container-name> )''' returns whether the container is empty
'''stlClear( <container-name> )''' empties the specified container
'''stlReset( <container-name> )''' resets the container to its initial values

===Meta Functions===
These functions perform some action either on all of the elements in the container, or using all the elements in the container.

STL Container IB Reference

2020-07-14T23:25:24Z

Barb: /* Stack/Queue */

===Core Functions===
These are the main functions you will use for each container.

====Vector====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the vector
'''stlPopBack( <container-name> )''' removes the element at the end of the vector
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the front of the vector
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the vector
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Similar to arrays, vectors are mostly used to access data based on a numeric index, thus stlGet and stlSet are going to be your bread and butter functions for this container. stlPushBack is a great way to programatically build a vector - it will append the specified data to the end of the vector, and increase its size by 1. If you want to remove the last element, you would use stlPopBack. Then the stlFront and stlBack functions have been included as shortcuts for accessing the first and last elements respectively.

====List====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the list
'''stlPopBack( <container-name> )''' removes the element at the end of the list
'''stlPushFront( <container-name>, <data> )''' adds an element to the beginning of the list
'''stlPopFront( <container-name> )''' removes the element at the beginning of the list
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the beginning of the list
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the list

Lists are designed to be accessed sequentially, that is each element is associated with the preceding and following elements in the container. As such, the core functions provided are used to add, remove, and get the elements at the front and back of the list. The real power of lists is utilized during iteration - they are the most efficient container for inserting and erasing elements in the middle of the container.

====Map====
'''stlGet( <container-name>, <key> [,EXCP=statement label])''' gets the element at the key specified
'''stlSet( <container-name> <key> <data>)''' sets the element at the key specified

Maps are used to relate an element to a key (string index). Similar to vectors, to access a value, the key must be specified.

====Stack/Queue====
'''stlPush( <container-name>, <data> )''' adds an element to the container
'''stlPop( <container-name> )''' removes the next element from the container
'''stlPeek( <container-name> [,EXCP=statement label])''' gets the next element from the container
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Both stacks and queues utilize the same set of functions, but perform differently depending on which container you have implemented. In general, the stlPush, stlPop, and stlPeek functions are going to be the most important of these functions. They perform the basic operations associated with these containers. For stacks, stlPush and stlPop adds and removes from the end of the container. For queues, stlPush adds to the end of the container, and stlPop removes from the front of the container. For both containers, stlPeek will get the "next" element in the container (i.e. the last element for stacks, the first element for queues).

Because these containers are implemented with deques internally, we also provide access via numeric indexes with the stlSet() and stlGet() operators. These functions behave similarly to the vector functions of the same name, by getting and setting the elements at the specified index.

===Iteration Functions===
These functions are used to iterate over the elements of a container.

General:
'''stlBegin( <container-name> )''' sets the iterator position at the beginning
'''stlEnd( <container-name> )''' sets the iterator position at the end
'''stlNext( <container-name> )''' moves the iterator position forward one element
'''stlPrev( <container-name> )''' moves the iterator position back one element
'''stlRead( <container-name> )''' gets the element at the current iterator position
'''stlWrite( <container-name>, <data> )''' - sets the element at the current iterator position

Maps only:
'''stlReadKey( <container-name> )''' gets the key at the current iterator position

Lists only:
'''stlInsert( <container-name>, <data> )''' inserts the element BEFORE the current iterator position
'''stlErase( <container-name> )''' erases the element at the current iterator position
(stlErase will subsequently move the iterator position to the next element)

===Utility Functions===
These are basic functions that return information about the specified container.

'''stlSize( <container-name> )''' returns the size of the container
'''stlEmpty( <container-name> )''' returns whether the container is empty
'''stlClear( <container-name> )''' empties the specified container
'''stlReset( <container-name> )''' resets the container to its initial values

===Meta Functions===
These functions perform some action either on all of the elements in the container, or using all the elements in the container.

STL Container IB Reference

2020-07-14T23:19:59Z

Barb: /* List */

===Core Functions===
These are the main functions you will use for each container.

====Vector====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the vector
'''stlPopBack( <container-name> )''' removes the element at the end of the vector
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the front of the vector
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the vector
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Similar to arrays, vectors are mostly used to access data based on a numeric index, thus stlGet and stlSet are going to be your bread and butter functions for this container. stlPushBack is a great way to programatically build a vector - it will append the specified data to the end of the vector, and increase its size by 1. If you want to remove the last element, you would use stlPopBack. Then the stlFront and stlBack functions have been included as shortcuts for accessing the first and last elements respectively.

====List====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the list
'''stlPopBack( <container-name> )''' removes the element at the end of the list
'''stlPushFront( <container-name>, <data> )''' adds an element to the beginning of the list
'''stlPopFront( <container-name> )''' removes the element at the beginning of the list
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the beginning of the list
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the list

Lists are designed to be accessed sequentially, that is each element is associated with the preceding and following elements in the container. As such, the core functions provided are used to add, remove, and get the elements at the front and back of the list. The real power of lists is utilized during iteration - they are the most efficient container for inserting and erasing elements in the middle of the container.

====Map====
'''stlGet( <container-name>, <key> [,EXCP=statement label])''' gets the element at the key specified
'''stlSet( <container-name> <key> <data>)''' sets the element at the key specified

Maps are used to relate an element to a key (string index). Similar to vectors, to access a value, the key must be specified.

====Stack/Queue====
'''stlPush( <container-name>, <data> )''' adds an element to the container
'''stlPop( <container-name> )''' removes the next element from the container
'''stlPeek( <container-name> )''' gets the next element from the container
'''stlGet( <container-name>, <index> )''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Both stacks and queues utilize the same set of functions, but perform differently depending on which container you have implemented. In general, the stlPush, stlPop, and stlPeek functions are going to be the most important of these functions. They perform the basic operations associated with these containers. For stacks, stlPush and stlPop adds and removes from the end of the container. For queues, stlPush adds to the end of the container, and stlPop removes from the front of the container. For both containers, stlPeek will get the "next" element in the container (i.e. the last element for stacks, the first element for queues).

Because these containers are implemented with deques internally, we also provide access via numeric indexes with the stlSet() and stlGet() operators. These functions behave similarly to the vector functions of the same name, by getting and setting the elements at the specified index.

===Iteration Functions===
These functions are used to iterate over the elements of a container.

General:
'''stlBegin( <container-name> )''' sets the iterator position at the beginning
'''stlEnd( <container-name> )''' sets the iterator position at the end
'''stlNext( <container-name> )''' moves the iterator position forward one element
'''stlPrev( <container-name> )''' moves the iterator position back one element
'''stlRead( <container-name> )''' gets the element at the current iterator position
'''stlWrite( <container-name>, <data> )''' - sets the element at the current iterator position

Maps only:
'''stlReadKey( <container-name> )''' gets the key at the current iterator position

Lists only:
'''stlInsert( <container-name>, <data> )''' inserts the element BEFORE the current iterator position
'''stlErase( <container-name> )''' erases the element at the current iterator position
(stlErase will subsequently move the iterator position to the next element)

===Utility Functions===
These are basic functions that return information about the specified container.

'''stlSize( <container-name> )''' returns the size of the container
'''stlEmpty( <container-name> )''' returns whether the container is empty
'''stlClear( <container-name> )''' empties the specified container
'''stlReset( <container-name> )''' resets the container to its initial values

===Meta Functions===
These functions perform some action either on all of the elements in the container, or using all the elements in the container.

STL Container IB Reference

2020-07-14T23:12:06Z

Barb: /* Map */

===Core Functions===
These are the main functions you will use for each container.

====Vector====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the vector
'''stlPopBack( <container-name> )''' removes the element at the end of the vector
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the front of the vector
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the vector
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Similar to arrays, vectors are mostly used to access data based on a numeric index, thus stlGet and stlSet are going to be your bread and butter functions for this container. stlPushBack is a great way to programatically build a vector - it will append the specified data to the end of the vector, and increase its size by 1. If you want to remove the last element, you would use stlPopBack. Then the stlFront and stlBack functions have been included as shortcuts for accessing the first and last elements respectively.

====List====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the list
'''stlPopBack( <container-name> )''' removes the element at the end of the list
'''stlPushFront( <container-name>, <data> )''' adds an element to the beginning of the list
'''stlPopFront( <container-name> )''' removes the element at the beginning of the list
'''stlFront( <container-name> )''' gets the element at the beginning of the list
'''stlBack( <container-name> )''' gets the element at the end of the list

Lists are designed to be accessed sequentially, that is each element is associated with the preceding and following elements in the container. As such, the core functions provided are used to add, remove, and get the elements at the front and back of the list. The real power of lists is utilized during iteration - they are the most efficient container for inserting and erasing elements in the middle of the container.

====Map====
'''stlGet( <container-name>, <key> [,EXCP=statement label])''' gets the element at the key specified
'''stlSet( <container-name> <key> <data>)''' sets the element at the key specified

Maps are used to relate an element to a key (string index). Similar to vectors, to access a value, the key must be specified.

====Stack/Queue====
'''stlPush( <container-name>, <data> )''' adds an element to the container
'''stlPop( <container-name> )''' removes the next element from the container
'''stlPeek( <container-name> )''' gets the next element from the container
'''stlGet( <container-name>, <index> )''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Both stacks and queues utilize the same set of functions, but perform differently depending on which container you have implemented. In general, the stlPush, stlPop, and stlPeek functions are going to be the most important of these functions. They perform the basic operations associated with these containers. For stacks, stlPush and stlPop adds and removes from the end of the container. For queues, stlPush adds to the end of the container, and stlPop removes from the front of the container. For both containers, stlPeek will get the "next" element in the container (i.e. the last element for stacks, the first element for queues).

Because these containers are implemented with deques internally, we also provide access via numeric indexes with the stlSet() and stlGet() operators. These functions behave similarly to the vector functions of the same name, by getting and setting the elements at the specified index.

===Iteration Functions===
These functions are used to iterate over the elements of a container.

General:
'''stlBegin( <container-name> )''' sets the iterator position at the beginning
'''stlEnd( <container-name> )''' sets the iterator position at the end
'''stlNext( <container-name> )''' moves the iterator position forward one element
'''stlPrev( <container-name> )''' moves the iterator position back one element
'''stlRead( <container-name> )''' gets the element at the current iterator position
'''stlWrite( <container-name>, <data> )''' - sets the element at the current iterator position

Maps only:
'''stlReadKey( <container-name> )''' gets the key at the current iterator position

Lists only:
'''stlInsert( <container-name>, <data> )''' inserts the element BEFORE the current iterator position
'''stlErase( <container-name> )''' erases the element at the current iterator position
(stlErase will subsequently move the iterator position to the next element)

===Utility Functions===
These are basic functions that return information about the specified container.

'''stlSize( <container-name> )''' returns the size of the container
'''stlEmpty( <container-name> )''' returns whether the container is empty
'''stlClear( <container-name> )''' empties the specified container
'''stlReset( <container-name> )''' resets the container to its initial values

===Meta Functions===
These functions perform some action either on all of the elements in the container, or using all the elements in the container.

STL Container IB Reference

2020-07-14T23:06:56Z

Barb: /* Vector */

===Core Functions===
These are the main functions you will use for each container.

====Vector====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the vector
'''stlPopBack( <container-name> )''' removes the element at the end of the vector
'''stlFront( <container-name> [,EXCP=statement label])''' gets the element at the front of the vector
'''stlBack( <container-name> [,EXCP=statement label])''' gets the element at the end of the vector
'''stlGet( <container-name>, <index> [,EXCP=statement label])''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Similar to arrays, vectors are mostly used to access data based on a numeric index, thus stlGet and stlSet are going to be your bread and butter functions for this container. stlPushBack is a great way to programatically build a vector - it will append the specified data to the end of the vector, and increase its size by 1. If you want to remove the last element, you would use stlPopBack. Then the stlFront and stlBack functions have been included as shortcuts for accessing the first and last elements respectively.

====List====
'''stlPushBack( <container-name>, <data> )''' adds an element to the end of the list
'''stlPopBack( <container-name> )''' removes the element at the end of the list
'''stlPushFront( <container-name>, <data> )''' adds an element to the beginning of the list
'''stlPopFront( <container-name> )''' removes the element at the beginning of the list
'''stlFront( <container-name> )''' gets the element at the beginning of the list
'''stlBack( <container-name> )''' gets the element at the end of the list

Lists are designed to be accessed sequentially, that is each element is associated with the preceding and following elements in the container. As such, the core functions provided are used to add, remove, and get the elements at the front and back of the list. The real power of lists is utilized during iteration - they are the most efficient container for inserting and erasing elements in the middle of the container.

====Map====
'''stlGet( <container-name>, <key> )''' gets the element at the key specified
'''stlSet( <container-name> <key> <data>)''' sets the element at the key specified

Maps are used to relate an element to a key (string index). Similar to vectors, to access a value, the key must be specified.

====Stack/Queue====
'''stlPush( <container-name>, <data> )''' adds an element to the container
'''stlPop( <container-name> )''' removes the next element from the container
'''stlPeek( <container-name> )''' gets the next element from the container
'''stlGet( <container-name>, <index> )''' gets the element at the index specified
'''stlSet( <container-name> <index> <data>)''' sets the element at the index specified

Both stacks and queues utilize the same set of functions, but perform differently depending on which container you have implemented. In general, the stlPush, stlPop, and stlPeek functions are going to be the most important of these functions. They perform the basic operations associated with these containers. For stacks, stlPush and stlPop adds and removes from the end of the container. For queues, stlPush adds to the end of the container, and stlPop removes from the front of the container. For both containers, stlPeek will get the "next" element in the container (i.e. the last element for stacks, the first element for queues).

Because these containers are implemented with deques internally, we also provide access via numeric indexes with the stlSet() and stlGet() operators. These functions behave similarly to the vector functions of the same name, by getting and setting the elements at the specified index.

===Iteration Functions===
These functions are used to iterate over the elements of a container.

General:
'''stlBegin( <container-name> )''' sets the iterator position at the beginning
'''stlEnd( <container-name> )''' sets the iterator position at the end
'''stlNext( <container-name> )''' moves the iterator position forward one element
'''stlPrev( <container-name> )''' moves the iterator position back one element
'''stlRead( <container-name> )''' gets the element at the current iterator position
'''stlWrite( <container-name>, <data> )''' - sets the element at the current iterator position

Maps only:
'''stlReadKey( <container-name> )''' gets the key at the current iterator position

Lists only:
'''stlInsert( <container-name>, <data> )''' inserts the element BEFORE the current iterator position
'''stlErase( <container-name> )''' erases the element at the current iterator position
(stlErase will subsequently move the iterator position to the next element)

===Utility Functions===
These are basic functions that return information about the specified container.

'''stlSize( <container-name> )''' returns the size of the container
'''stlEmpty( <container-name> )''' returns whether the container is empty
'''stlClear( <container-name> )''' empties the specified container
'''stlReset( <container-name> )''' resets the container to its initial values

===Meta Functions===
These functions perform some action either on all of the elements in the container, or using all the elements in the container.

FAQs

2020-06-10T21:10:40Z

Barb: /* Where are all the various log files? */

= FAQs =

==Where are all the various log files?==
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Below we'll tell you where the default locations of the files are. But you can control the location of the Comet logs by creating a %COMETDATA% environment variable. This does not apply to the Comet Services log files.

Here is a list of the log files and their default locations:

'''The Comet Log''' 
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

If you can't even run Comet and you need the log, click on the "Details" button at the bottom right corner of the splash screen when you attempt to run Comet. When the log display opens up, click on File->Open log file. It will open up in your text editor.

If you can't even do that, try looking in C:\Users\[username]\AppData\Local\Signature Systems\LOGS

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path. 

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

'''The CosP Log''' 
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well. 
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

'''The Comet Services Logs''' 
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder. 

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6. 

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance. 

'''The XAP Log''' 
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log. 

==Where can I find my CosW.ini file?==
If you can find your Comet.log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This is true even if you are using the %COMETDATA% environment variable. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[http://wiki.signature.net/index.php/CosW.ini_settings]] 

==What ports are used by Signature Systems software?==
You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]] 

==What options can be set in the #XAP file?==

CLOSE 
The CLOSE command tells Comet to stop listening on the XAP gateway (in effect, resetting
the gateway).

LOGFILE pathname[,cycle | ,erase] 
The cycle option keeps up to 7 generations of the log file.

LISTEN port-number 
Specifies the port for XAP to listen on. Port 80 will be used by default.

USEWIN 
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.

EXPIRE xT[,ProgramName] 
This is used to set the expiration date for an eComet Context cookie. x is number; T is M|D|H, (for example 5M for 5 minutes); optional ProgramName is program to run when a new cookie is created (for example a relogin program). Without ProgramName, the normal XAP program is run with ClearCommon. Previously cookies expired only when the browser was closed. Now the cookies are persistent. Without the EXPIRE command cookies will be session cookies as they were before this enhancement. You can delete a cookie by setting an expiration date in the past.

TRACE 
Turns on the Comet32 TRACE window you'd get if you said TRACE ON in your IB program.

==I'm getting an error message that CometLib couldn't be registered. What should I do?==
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try. 
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on. 
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll 

==Will the Comet Services run on a virtual server?==
Yes as long as the server is running a supported version of Windows [[http://www.signature.net/signature/techdoc/general/systreq.htm]]. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[http://wiki.signature.net/index.php/Virtual_Dongle]] 
==How can I get the latest license certificate for my security token?==
There are a couple of ways. First if you are able to run Comet you can use the SecSrv utility with Comet32. In addition to doing certificate retrieval, it will also list all currently connected users along with their local IP addresses and tell you how long they have been connected. For Comet16 users you can use the older utility, SecLic. This requires that you have configured a WinSock gateway. 
If you can't run Comet at all, you can still get the latest license. For Server versions prior to 16.00, stop the Comet Services. Erase the license.txt and any [plugnumber].txt files from your Comet Services folder. When you restart the Comet Services the Security Server will automatically connect to our server to get the license if one is not found in your folder. If you're running Comet Services 16.00 or later, it's even easier. From the Security Server console, click Edit->Update licenses. Now click the "Update Certificate" button. Your certificate will be retrieved and installed for you. 
These methods work for parallel, USB, and virtual dongles. 

==Should I run Comet16 or Comet32?==
Comet16 can only be run on 32-bit versions of Windows and it has been retired. No further work will be done on it. We recommend you run Comet32. 
If you are running a 64-bit version of Windows, Comet32 will run automatically. On 32-bit versions of Windows you can request Comet32 by including /32 on your Comet shortcut command line: c:\comet\comet.exe /pn=nodename /32 
If you want to make sure all Comet clients on the network are running Comet32, just set ForceC32 = 1 in your CosWGlob.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]] 
Other things to consider: 
Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers. 
Comet32 can run programs compiled for Comet16 and programs compiled for Comet32. 
Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows] 
Note: 64-bit CometAnywhere clients can run their Comet session from a Comet16 CA host. In an environment where factors are preventing deployment of Comet32 at this time, this is a way you can run Comet16 on computers that otherwise could only run Comet32.

==How can I tell if a program was compiled for Comet16 or Comet32?==
There are several ways.
* CometExplorer's TYPE column indicates the type of object file: C16 Program, C32 Program, or C32M Program (Comet Mobile)
* When you run a program in Comet32 a colored block on the window's status line indicates the type of program: purple for Comet16; green for Comet32
* From inside your program you can use FSTAT on an object file to determine if it was compiled for Comet16 or Comet32. Look in position 135 [[http://wiki.signature.net/index.php/IB_Statements/fstat]]
* PSTAT can also be used to check the type of a program that's currently running. Look in position 219 [[http://wiki.signature.net/index.php/IB_Statements/pstat]]
* If you attempt to run a Comet32 program in Comet16 you will get an Error 63.

==Can I use the Comet16 compiler on a 64-bit computer?==
No, you can only run the Comet16 compiler from a computer that can run Comet16. When compiling from UltraEdit, either the Comet16 compiler or the Comet32 compiler will be launched depending on the version of Comet currently running on the host computer. So, on a 32-bit computer you can compile with either the Comet16 compiler or the Comet32 compiler, but on a 64-bit computer you can only compile with the Comet32 compiler.

Virtual Dongle

2019-06-20T18:29:53Z

Barb: /* Comet Security Server Virtual Dongle Installation */

== Comet Security Server Virtual Dongle Installation ==

The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:

*A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [http://www.signature.net/download/End%20User%20License%20Agreement.pdf]

*You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
*The Comet Security Server must have a reliable internet connection. If you use Internet Security Software you'll need to set it up to allow 2-way traffic with dongle.signature.net (to port 80) and signature.net (to port 8080). Be aware that your use of a proxy server may interfere with this communication.
*The Comet Security Server must be running as a service and have '''administrator privileges'''.
*A Virtual Dongle may be associated with one and only one computer. Once installed you may not move it to another computer.

 If you are replacing an existing USB or parallel dongle:

*Install Server Products vsn 18 or higher on your server and make sure all is well using the existing dongle.
*Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
*Stop the Comet Services then remove the old dongle.
*Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''
*Return the old dongle to Signature Systems so that the permanent certificate can be issued.

 If you are installing a new system:

*Make sure your internet connection is working on the server where the Comet Services will be installed.
*If you haven't already done so, we recommend you install the Microsoft Redistributables Package. Some of the .NET framework files are used by the Security Server. You can download vcredist_x86.exe here [http://www.signature.net/download/MailBoxes/]
*Create the Comet Services folder.
*Put the DRB.txt file into that folder.
*Install Server Products vsn 18 or higher on your server. When it asks for dongle type, choose USB. This is because the Security Server will attempt to find a USB dongle first and it needs the drivers to be able to do that. When it asks if you want to restart Windows, say '''"No"'''. Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''

 Notes:
The DRB.txt file is a single-use file for installing and registering your virtual dongle. It is unique for each dongle installed. Once the installation has been registered successfully with our server the DRB.txt file expires and cannot be reused. This file is different from the Comet License Certificate file. Virtual dongles use a license file just like USB or parallel port dongles. The license file will be updated each time your subscription is renewed or new products are purchased.

Using the email printer

2019-01-03T23:48:48Z

Barb: /* Configuration */

==Email Printing with Comet==
© 2007 Signature System Inc.

Within a few minutes you can configure a "printer" that will automatically email any text, HTML, or PDF document produced using Comet's printer drivers.

==Understanding SMTP==
The Email Printer uses a DES program called EMAILPTR. It talks the SMTP protocol.
SMTP stands for '''S'''imple '''M'''ail '''T'''ransport '''P'''rotocol. It is the basic protocol used to send mail over the internet. SMTP mimics the process of sending a package or letter by snail mail or delivery service. When mailing a physical letter, you first write the letter itself (the body), then write the envelope and then take the envelope to the post office, giving delivery instructions.

===There are 3 sections of an SMTP email transaction.===

====1. The SMTP routing instructions:====
* The connection server and port (Connect)
* The introduction (Domain)
* Optional Authentication (User and Password)
* The Sender's ID (Mail from)
* The destination (rcpt to)
* Other SMTP Commands

====2. The "envelope" or Header====
* The date
* From
* To
* Subject
* Other Header elements

====3. The body of the mail====
* Possibly multiple parts, each a different format.

==Requirements==

There are a few requirements to make this feature work.

* A WinSock gateway configured. It is better to configure multiple WinSock Gateways.
* A COM license for CometLib.
* A connection to the Internet.
* A reachable SMTP server.
* The TMP directory for Comet must be configured as a CFAM directory and it must be configured in SYSGEN using the $(CATEMP) alias:
00 = c ,$(catemp);

==Configuration==

You can designate TEXT, HTML, and PDF printers as email printers. Here is a sample of a section of an INI file:

Printer = leh,h,n,,htm,EmailPtr; ; Data records are limited to 254 bytes
Printer = leh,h,n,,htm,EmlPtr32; ; For Comet32 users only: no restriction on length of data records written to the printer
Printer = lep,p,n,,pdfFactory,EmailPtr;
Printer = let,x,n,,txt,EmailPtr; ; Data records are limited to 254 bytes
Printer = let,x,n,,txt,EmlPtr32; ; For Comet32 users only: no restriction on length of data records written to the printer

We could have named the printers any device name beginning with an "L". What designates this as an email printer is the DES program "EmailPtr" or "EmlPtr32". These DES programs are released as part of the REL Directory.

===Doc Manager===
You can configure a printer as both an email printer and an archive printer.

Printer = LPI,p,x,SPL:invoices,Adobe PDF,EmailPtr;

Every document printed to that printer would be rendered in PDF by the Adobe Pdf driver, emailed, and placed into the INVOICES docmanager archive. With appropriate Email.ini settings (see below), no program changes would be required other than selecting 'LPI' as the printer.

==Mnemonics==

There are several mnemonics specifically related to the email printer. First, you need to specify the smtp server name and port to be used to send your email.

Print (lun) (Server='smtp.ourserver.net mail')

Look at the server settings in your email program for the correct setting for this. The word "mail" above is an alias for port 25. Thus, you could have written

Print (lun) (Server='smtp.ourserver.net 25')

and accomplished the same thing. You can use any port mandated by your ISP. Port 25 is the default. If you do not specify a port as part of the server name, the email printer will attempt to use port 25. Note: Beginning with Comet 2006 you are able to send email from smtp servers that require authentication.

If you wish, you may also specify a domain name.

Print (lun) (Domain='signature.net')

If it is not specified, the email printer will supply the same domain as designated in the server mnemonic.

To specify the sender's name you use the "From" mnemonic.

Print (lun) (From='"jim guerber"<jim@@signature.net>')

This is used both for SMTP routing (MAIL FROM:) and for the mail message header (From:). It should be set to a valid email address.

Use the "To" mnemonic to specify your recipients. This will be used for SMTP routing (RCPT TO:) and the header (To:).

Print (lun) (To = 'jim<jim@@signature.net>')
Print (lun) (To = 'gina@@signature.net')

You must specify at least one recipient. Use multiple instances of this mnemonic to send your email to more than one recipient. CC and BCC recipients may be specified in addition to or instead of TO recipients.

Print (lun) (CC = 'barbara@@signature.net')
Print (lun) (BCC = 'brian@@signature.net')

You must include a subject for your email, use the "Subject" mnemonic.

Print (lun) (Subject='The Subject of this email')

In addition to whatever is written to the email printer, you may want to include body text. Depending on your email client, for html printers body text will either appear in an attachment, since it is usual for HTML to appear as the main body of the email, or it will be appended following the html content. For PDF printers, this text will be the main body of the email and the PDF will appear as an attachment. For text printers, the body text will appear just before the printer output. To specify body text, use the "Text" mnemonic.

Print (lun) (Text='yada yada yada')

The email printer will optionally write to a log file, recording details about each email sent, including responses from the smtp server. The log file is a text file located on any directory to which the user has access. The email printer will append to this log file. The log file may optionally be erased before the print job is run. Otherwise, it is up to the administrator or outside program to erase this file periodically.

Print (lun) (Log='file','dir','erase')

If the log file name is not specified, a file named "email.log" will be used. If the email directory is not specified, "COS" will be used. By default, the file will not be erased. If there is no LOG statement at all, no log file will be generated.

If you wish to specify a name for an attachment to your email, use the (EmailDocument=) mnemonic.

Print (lun) (EmailDocument='file')
Without the (EmailDocument=) mnemonic, the attachment would carry the default name of the document.

==Formatting of email addresses==

In the examples above, we have shown a few different ways to specify an email address. Mail programs like addresses formatted in the following way: "FirstName LastName"<email@domain.tld> Any of the following should work:

Print (lun) (To = 'Jim Guerber<jim@@signature.net>') ! Best
Print (lun) (To = 'Jim<jim@@signature.net>') ! ok
Print (lun) (To = 'jim@@signature.net') ! worst

If there is no space character in the name the double quotes are not necessary. Most email programs will take some sort of shortened form of email address, even just the address with no <> such as email@domain.tld, but some spam detection programs may object to this simple form. Note the use of double @ characters as an escape convention of Internet Basic.

Email addresses used in the SMTP routing instructions "mail from" and "rcpt to" will have any name information (like "Jim Guerber" in the above example) stripped out. Microsoft Exchange Server doesn't tolerate anything other than the simple email address.

== A Note on Verifying Email Addresses==

If you're going to do email address validation, consider that VRFY and EXPN are blocked by most ISPs nowadays. Also, simulating VRFY by stacking RCPT TO: commands is something that spammers do. ISPs know this, and the smarter ones track how often you do this. You'll get blocked after some number of attempts. I wouldn't go looking for a lot of sympathy from ISPs when trying to get unblocked afterwards, as the ISPs consider this a very bad practice that good guys don't engage in.
==The email.ini file==

Several settings for email printers never (or rarely) change. These settings can be placed in an initialization file (INI File). The email printer will look for a file named email.ini which can contain those settings. The email.ini file is optional since all values may be supplied by mnemonics in the program, but it may be a more convenient way to supply some parameters such as the smtp server name. Lines beginning with an exclamation marks ! are treated as comments.

====Mnemonics vs the Email.ini file====
The information required for an email may be either specified by the use of mnemonics, or placed in a text file called email.ini or both. You may want to setup a standard email.ini file containing items that remain constant from one email to another such as server and domain, and specify the rest of the info using mnemonics, or you may want to write a new email.ini file in the temp directory containing all of the information required before initiating the email program.
* The email.ini file is not processed until the printer is closed. This means that any time during the execution of the print program, you may add items to the email.ini file.
* Each print of a mnemonic causes a new line to be generated in the document (the email body) unless Transparent mode is specified (TR).
* Use of the email.ini file allows general print programs to generate email with no change.

The email printer will look for an equal sign (=) as a delimiter between the parameter name and the value. If an equal sign is not found, the whole line will be treated as text. This is the same as using the "text=" parameter. Here's an example:

server = smtp.ourserver.net
from = OrderProcessing@OurCompany.com
bcc = AcctsReceivable@OurCompany.com
subject = Thank you for your order
Thank you for your recent order. The attached document contains your invoice and delivery schedule.

Using the preceding email.ini file, all that the program would need to supply is the recipient's email address (using the (To=) mnemonic) and write the unique details of the message to the email printer. Note that Accounts Receivable will automatically receive a copy (bcc) of each email.

Some mnemonics supplied by the program have precedence over the email.ini settings. In other cases both values from a mnemonic AND values from the email.ini file will be used. Those mnemonics which will super cede the equivalent setting in the email.ini file are Server, Domain, From, Subject, and Log. And, if you were to try to use more than one of any of those mnemonics for a given email, only the first one of each would be used. The other settings: To, CC, BCC, and Text, may have multiple occurrences. And, if you use these mnemonics and have equivalent settings in the email.ini, they will all be processed for your email.

==Attachments==

Before understanding attachments, It is good to know the order documents get placed in the email for various printers. For the sake of this document we will call any text specified by the (text=)mnemonic or in the email.ini file "body text". For all email print jobs there are three possible components that are transmitted. The order depends on the printer type.

For HTML printers, the email is composed of the HTML generated for the printer, followed by the body text, and then any attachments specified.

For Text printers, email is composed of the printer output followed by body text and then attachments.

For PDF printers, the email is composed of body text, followed by the printer output as an attachment and then followed by any other attachments specified.

To add an attachment to the email document, either use the (attachment=path) mnemonic or specify the attachment in the INI file. The path specified must be a valid windows path (use either drive letter or UNC conventions), and does not need to be a Comet file or reside in a Comet directory. Any number of attachment files may be specified. The Emailptr program attempts to determine the mime type of the file by reading the mime keyed file in the rel directory using the file extent ion as the key. If the mime type is not determine able, the default mime type of "application/octet-stream" is used.

==Return Receipts==

Occasionally you may want to know when the receiver of your email reads it. Some (not all) email programs support the "Return-Receipt-To:" command. You may specify (a single) return receipt address either in the ini file or by using the (rr=) mnemonic. Following the equal sign must be a valid email address.

==Silent Running==

The Emailptr will sometimes put up a message box if some component of the email such as the subject is missing. This will stop any program that is designed to produce a series of emails, and would crash if run from a background partition. For that reason, there is an extra instruction in the email.ini file to take care of this situation. If you do not want the emailptr to send any output to the screen, include the '''silent''' command in the email.ini file. If this command appears alone, the emailptr will simply close the email and continue. You may also optionally specify a program to be entered each time an error is encountered. In that case, # buffer will contain the error information (the text that would normally appear in the message box.

==Other SMTP commands and header lines==

You may want to supply other commands to the SMTP server or place additional commands in the header. There are 2 commands that allow you to do that.

'''SmtpCmd=text''' includes the text into the smtp routing instructions. I can't find any good examples of why you would want to send one of these things, but in the future, some Exchange server or something may require one of these.

'''Smtphdr=text''' includes the text in the envelope (the header). There are several interesting commands you could want to put here, but most of them are obsolete.

Examples are:

print (LUN)(SmtpHdr='X-Priority: 1') ! mark the email as urgent

==Reference==

For reference, here is a complete list of mnemonics and their corresponding email.ini file settings:
{| border="1" cellpadding="2"
|-
!width="225"| Mnemonic
!width="400"| Ini file
|-
| (log = log$)
| log = email.log,cos,cycle
|-
| (server = server$)
| server = smtp.ourserver.net
|-
| (domain= domain$)
| domain= smtp.ourserver.net
|-
| (user = user$)
| user = username
|-
| (password= pw$)
| password = MyPassword
|-
| (from = from$)
| from = OrderProcessing@OurCompany.com
|-
| (to = to$)
| to = youraddress@yourisp.net
|-
| (cc = cc$)
| cc = mylawyer@protectme.net
|-
| (rr= ReturnReceipt$)
| rr = returnReceipt@OurCompany.com
|-
| (bcc = bcc$)
| bcc = AcctsReceivable@OurCompany.com
|-
| (subject = Subject$)
| subject = Thank you for your order
|-
| (attachment = a$)
| attachment = c:\boilerplate\terms.pdf
|-
| (silent = 'myprog')
| silent = myprog
|-
| (SmtpCmd = 'help')
| SmtpCmd=help
|-
| (SmtpHdr=h$)
| SmtpHdr=X-Priority: 1
|-
|
| ssl=true
|-
|
| tls=true
|}

==Notes==
Here is an interesting article aimed at writers of smtp servers with techniques for filtering spam. It is useful to us so that we can better format our emails to avoid being labeled as "ratware".

[http://slett.net/spam-filtering-for-mx/ Spam Filtering for Mail Exchangers]

Subscription Benefits

2018-12-07T19:40:17Z

Barb: /* Benefits of being a Comet Subscriber */

Even if you are not a current subscriber to the Comet Software, most of your core applications will continue to work. However, Signature Systems continually improves its software and adds new features to the Comet System. These features are mainly available to current Comet Subscribers only.
=Benefits of being a Comet Subscriber=

*Entitled to all updates made to existing products during the subscription year
*Free COM license for each Comet license. This license is required for:
**CometExplorer
**(CopyFile) mnemonic through the file server. Without a COM license CopyFile is done directly with Windows calls which requires the client to have Windows access to the source and destination folders. This could require you to purchase additional Client Access Licenses from Microsoft.
**(Document=) mnemonic. This mnemonic is used by features of the email printer, the pdf printer, and DocMgr.
**The DataExpress version of the Reporter.
**CB, the CometAnywhere File Transfer Utility
*Protection against the loss of Comet access because of theft or verifiable loss of the security module. We will replace the usb plug and Comet licenses immediately, at no charge to the subscriber. Comet users who are not subscribers must rely on their business insurance to replace their system by completely repurchasing Comet at current prices. The expense and delay could far outweigh the cost of the subscription.
*Priority access to the technical support staff.
*The convenience of being able to apply CometAnywhere licenses to any version of the CometAnywhere host. This can be especially useful at subscription time. When new CometAnywhere licenses are issued you may continue to run an older version of Comet on the host until it is convenient for you to install the upgrade.
*Free ODBC/mySQL licenses for each Comet license.

==These benefits expire at the end of the subscription period.==

The SYSGEN configuration utility/Printers

2018-11-19T20:26:23Z

Barb:

'''[PRINTERS]'''

Minimum Requirements:
.
This group is not required.
.
Refer to the minimal INI file to see the minimum requirements to configure Comet.

The PRINTERS group contains information about the configured printers. The following segment title defines each printer:

'''''Printer = printer-name,printer-type,spool-type,spool-name|printer-name,
device-name|#[:RAW],driver-event-server-name,owning-node;'''''

'''Examples:'''

[PRINTERS]

Printer = LP1,W,N,,//NTServer/HP Laserjet IIP,,;
; Printer-name LP1
; Printer-type W (Windows printer)
; Spool-type N (non-spooling)
; Spool-name none
; Printer-name //NTServer/HP Laserjet IIP
; DES-name none
; Owning-node none (printer not network sharable)

Printer = LP1,W,N,,HP Laserjet IIP,,;
; Printer-name LP1
; Printer-type W (Windows printer)
; Spool-type N (non-spooling)
; Spool-name none
; Printer-name HP Laserjet IIP
; DES-name none
; Owning-node none (printer not network sharable)

Printer = LP2,W,N,,Epson MX80:RAW,,;
; Printer-name LP2
; Printer-type W (Windows printer)
; Spool-type N (non-spooling)
; Spool-name none
; Printer-name Epson MX80 in RAW mode
; DES-name none
; Owning-node none (printer not network sharable)

Printer = LP3,L,N,,LPT1,,;
; Printer-name LP3
; Printer-type L (local printer)
; Spool-type N (non-spooling)
; Spool-name none
; Printer-name Use parallel port 1 (LPT1)
; DES-name none
; Owning-node none (printer not network sharable)

Printer = LP4,L,A,SP3,*,LPTDRV,SALES;
; Printer-name LP4
; Printer-type L (local printer)
; Spool-type A (Auto spool)
; Spool-name SP3
; Printer-name Use default printer port (LPT1)
; DES-name LPTDRV.DLL
; Owning-node SALES

Printer = L99,L,N,,C:\COMET\PRINTER\OUTPUT.TXT,,;
; Printer-name L99
; Printer-type L (local printer)
; Spool-type N (non-spooling)
; Spool-name none
; Printer-name Text file (C:\COMET\PRINTER\OUTPUT.TXT)
; DES-name none
; Owning-node none

Printer = LPH,H,N,,HTM,HTMLPTR,;
; Printer-name LPH
; Printer-type H (HTML printer)
; Spool-type N (non-spooling)
; Spool-name none
; Printer-name HTM (HTML printer)
; DES-name HTMLPTR
; Owning-node none

Printer = LPT,X,N,,TXT,EXTPTR,;
; Printer-name LPT
; Printer-type X (text printer)
; Spool-type N (non-spooling)
; Spool-name none
; Printer-name TXT (text printer)
; DES-name EXTPTR
; Owning-node none

'''Segment Title'''

Printer = printer-name,printer-type,spool-type,spool-name|printer-name,
device-name|#[:RAW],driver-event-server-name,owning-node;

'''printer-name'''
Required.

The printer device name in the form “Lxx” (where xx can be any alphanumeric character). Printer names must begin with the letter “L”.

printer-type

Required.

The type of printer that’s being configured.

{| Border=1
|-
|Type
|Description
|-
|L
|Local printer.<br/p>
A printer that is connected directly to the Comet node and assigned one of the following ports:<br/p>
LPT1, LPT2, LPT3, PRN, CON, COM1, COM2, COM3, COM4.
|-
|W
|Windows printer (Windows95 or higher).
|-
|H
|HTML printer (Comet2000 Build 291 and higher). See below for more information.
|-
|X
|Text printer (Comet2000 Build 291 and higher). See below for more information.
|-
|P
|PDF printer (Comet2005 and higher). See below for more information.
|-
|}

'''Note:''' Previous versions of Comet supported remote, network, and fax printers.<br/p>
These printer types are no longer supported.

'''spool-type'''

Required.

Defines the spooling characteristics for the printer that’s being configured.

{| Border=1
|-
|Type
|Description
|-
|N
|Non-spooling. The system will not create Comet spool files under any circumstances.
|-
|E
|Exception spooling.<br/p>
The system will create Comet spool files if the printer is off-line or not available.<br/p>
These spool files may be viewed and printed using Comet’s QSPOOL utility program.
|-
|A
|Auto-spooling.<br/p>
The system will create a Comet spool file every time this printer is selected for output.<br/p>
These spool files may be viewed and printed using Comet’s QSPOOL utility program.
|-
|X
|Document Archive (Comet 2005 and higher).<br/p>
The system will create a Comet archive file every time this printer is selected for output.<br/p>
These documents may be viewed using Comet’s DocMgr program. Archives are only available for pdf, htm, and txt printers.
|-
|}

'''spool-name | printer-name'''

Optional if the printer is non-spooling (N).

Required if the printer is exception (E), auto (A) spooling, or archive (X).

For archives, this parameter takes the form of Dir:Archive. Dir is the CFAM directory where the archive will be created. Archive is the name of the file that will be created to catalog the jobs in the archive. For example:

Printer = LP5,P,X,SPL:INVOICES,pdfFactory,,;

This specifies a pdf printer that creates its archive in INVOICES on SPL.

For legacy configurations, this parameter defines the spool-name or printer-name that will be used if this printer is configured for exception or auto spooling. (If the printer is configured for non-spooling, use a comma and leave this parameter blank.)

Spool-names are in the form “Sxx” (where xx can be any alphanumeric character).
.
Printer-names are in the form “Lxx” (where xx can be any alphanumeric character).

See below for information about Cascading Printers.

'''device-name | # [:RAW]'''

Required.

Defines the device-name where output will be sent.

· If this is a local printer, the device name matches the port where the printer is connected
(e.g., LPT1, LPT2, COM1, etc.), or use an asterisk (*) to specify the default host printer.
.
· If this is a Windows printer, enter the printer name such as “HP Laserjet IIP”.
Make sure that you use the exact name of the printer as it appears in the Control Panel.
.
· If this is a printer on a CometAnywhere system,
use a pound sign (#) to set the default Windows printer on the remote system.
The printing itself is managed by the COSP program on the remote CometAnywhere system.
.
· If this is a type H printer, enter HTM as the device name.

If this is a type X printer, enter TXT as the device name.

Type H and X printers are available with Comet2000 Build 291 and higher. See below for more information about HTML and text printers.

· To send output to a text file (without launching the text file), use the path name of the file. For example:

'''C:\COMET\PRINTER\OUTPUT.TXT'''

In this case, all output that is directed to this printer will be sent to the text file named OUTPUT.TXT in the C:\COMET\PRINTER directory. If this file does not exist, Comet creates it. If the file exists, the output is appended to the end of the file. (Note: Comet does not erase this file.)

To operate the printer in RAW mode, append “:RAW” to the printer name. For example:

'''HP Laserjet IIP:RAW'''

See below for information about RAW mode.

'''driver-event-server-name'''

Optional.

(Required if a driver event server is being configured.)

Defines the driver event server (DES) program that is to be used with the printer being configured.

If this is a type H or type X printer (available with Comet2000 Build 291 and higher), specify the appropriate DES progr

{| Border=1
|-
|Printer type
|DES program
|-
|H
|HTMLPTR
|-
|X
|EXTPTR
|-
|}

See below for more information about DES programs.

'''owning-node'''

Optional.

(Required if the printer is to be network sharable.)

Defines the owning node name if the printer is used in a network.

Do not declare this parameter is any of the following is true:

· The printer is not physically attached to a given node
.
· The printer is declared as auto spool
.
· You do not have a networked system
.
· You do not want the printer to be network sharable

'''"Raw" vs. "Cooked" Mode Printers'''

Comet offers two modes of printer support for MTB applications. Which mode you use at any given installation depends on the level of compatibility you desire with the DOS version of Comet. The primary difference between a "raw" mode printer and a "cooked" mode printer is the addition of the control word ":RAW" to the Windows printer name for a raw mode printer. A raw mode printer is required for fully 100 percent Comet/DOS compatible printer operation.

The features for each print mode are as follows:

'''Raw Mode:'''

{| Border=1
|-
|Advantages
|Disadvantages
|-
|· Provides 100% compatibility with existing MTB applications.

· The application may use printer-specific control codes to modify the printer's behavior.
|· Requires direct knowledge of specific printer codes by MTB applications to perform special operations (compressed print, etc.).

· The application may not use any Windows-oriented printer controls such as font selection, line drawing etc.
|-
|}

'''Cooked Mode:'''

{| Border=1
|-
|Advantages
|Disadvantages
|-
|· Provides an MTB application with access to the Windows Graphical Device Interface (GDI), providing enhanced features allowing custom forms to be printed directly under MTB program control.

· Provides limited compatibility for those legacy applications that use standard sized printer forms. Different sized forms may be used if the printer itself has knowledge of the form size when performing a form-feed (note that this is usually NOT the case).

· Printer font type/size may be modified by specifying Windows fonts.

· Knowledge of the specific kind of printer or its control codes is not required by the MTB application to use enhanced features.
|· Legacy programs that rely on line counting to print non-standard sized forms may not function properly.
|-
|}

'''Discussion'''

Many applications, specifically those that use standard form length (11 inches in the U.S.), can function properly when printing to a cooked mode printer by choosing an appropriate Windows font that is compatible with the printer. To eliminate MTB program modification, "System" fonts can be set to choose a font that will initially be used for a specific printer. System fonts are specified in the COSW.INI file (located in the WINDOWS directory). These settings affect Comet cooked mode printers only. Entries in the COSW.INI file must conform to the following example:

'''[Printer Fonts]'''

printer name Font-n = font, height, chars per inch, weight

where:

printer name is the name of a Windows printer. If omitted, this entry represents the default for all printers not listed.

n is a number to represent the font. The current standard for font usage is:

0 represents a normal size font
1 represents a compressed or narrow font
2 represents a expanded or wide font

font is the name of an existing Windows font

height is the character height specified in points

chars per inch is the desired number of chars per inch

weight is the heaviness of the font (range=0-1000, normal=400)

'''Examples:'''

; for printers not listed separately
Font-0 = Courier New, 12, 10, 400
Font-1 = Courier New, 12, 17, 400
Font-2 = Courier New, 12, 6, 400

; for HP LaserJet 4 only
HP LaserJet 4 Font-0 = Courier, 12, 10, 400

Some printers may not give the desired results with any of the available Windows fonts. If this should be the case, there are two options available:

Configure the Windows printer using the supplied "Generic" printer driver available when setting up your printer. Because generic printers are "text only" printers, Windows will not attempt to load any fonts to the printer, resulting in the printer using whatever font (or other settings) set by the factory or the front panel.
Use the raw mode described earlier in this document.

'''Driver Event Servers (DES)'''

When using a Comet printer that is configured to operate in "cooked" mode, the printer can be enabled to generate pre-printed pages for an existing MTB application. Specifying a Driver Event Server program in the configuration enables this feature.

A Driver Event Server (DES) is nothing more than an MTB subprogram that is "entered" transparently to the user program. Once in control, the DES program can access the printer and perform various operations to prepare a page for printing by the user application.

As is implied by its name, a DES is entered only in response to certain printer events. Currently those events supported are: Initialization (just after the printer has been opened), NewPage (before a form feed), and Shutdown (just before the printer is closed).

The following example shows how a DES can be included in your Comet .INI configuration file:

Printer = LPW, W, N, , HP LaserJet 4, PWMARK,;

The DES program in this example is named PWMARK.OBJ. Note that the .OBJ extension is not specified in the configuration syntax. Sample DES programs can be found in the Comet demonstration directory for Windows (DMW), which is available, along with the required WDL directory, at the Signature Systems web site.

The following sample DES programs are currently available:

PWMARK (source #PWMARK) draws a water mark on each page
PFORM (source #PFORM) generates a sample invoice form
PFONT N/C/E (source #PTRFNT)
.
Each selects one of the system fonts as follows:
.
N = System font 0 (normal print)
C = System font 1 (compressed [narrow] print)
E = System font 2 (expanded [wide] print)

See below for information about the HTMLPTR and EXTPRE driver event servers.

'''Form feeds and "raw" printers'''

Here a "workaround" solution to a problem that can happen when you print to "raw" printers under Comet98 and Comet2000. The problem has to do with the suppression of initial form feeds and the assumptions made by some existing MTB applications. Here's some background information.

When you print to a regular (non-raw) printer, there is no form feed problem because Windows ejects a job when it's done, even if your program does not include a final form feed. However, when you print to a "raw" printer, there can be a problem. The WINPRINT.DDL required by all type "W" printers suppresses the initial form feed. For programs that don't include a final form feed, his can cause multiple print jobs to run together (i.e., the second job prints on the final page of the first job, etc.).

Signature Systems solved the problem by writing a small Driver Event Server (DES) program that you can include in the configuration for your raw printers. The DES program is named FFCLOSE.OBJ and it simply issues a form feed every time it detects a non-trivial close of a printer. To configure this option, place the DES program name in the field following the Windows printer name in the configuration .INI file, as shown in this example:

Printer = LP1, W, N, , HP Laserjet 4:RAW, FFCLOSE,;

The FFCLOSE.OBJ program is included in the REL directory starting with release 99.01.

'''Cascading Printers'''

'''Note:''' Beginning with Comet release .344, cascading printers are no longer required to handle an unavailble printer (E31) configured as type "W", "H", "T", or "P".

Here is a useful method for configuring Windows printers in Comet. The method allows a user to open a printer and, if that printer is not available, have Comet automatically redirect the output to another configured printer. If you configure a number of printers this way, the user's request can "cascade" from one printer to the next until Comet finds an available printer.

The third parameter in the PRINTER= segment title defines the spooling characteristics of the printer. If you choose E (exception) and then attempt to print to a printer that's either busy or unavailable, your job will be redirected to the spooler or printer listed in the fourth parameter.

'''For example:'''

Printer = LP1,W,E,LP2,HP LASERJET 4:RAW,,;

If a user gets an open exception on LP1, their job is redirected to LP2.

This type of configuration lets you create a "bank" of printers that can cascade from one to the next if necessary. This is a great way to configure CometAnywhere printers. Let's say you have a single printer configured for your remote users, as follows:

Printer = L10,W,N,,#:RAW,,;

As you can see, the printer named L10 is a non-spooling printer. The # symbol indicates that output will be sent to the remote user's printer.

But, what happens if more than one remote user tries to open L10 at the same time? Because it's a non-spooling printer, the additional users would have a problem.

Here's how to solve that problem. Configure a series of cascading printers beginning with L10:

Printer = L10,W,E,L11,#:RAW,,;
Printer = L11,W,E,L12,#:RAW,,;
Printer = L12,W,E,L13,#:RAW,,;
Printer = L13,W,E,L14,#:RAW,,;
Printer = L14,W,E,L15,#:RAW,,;
Printer = L15,W,E,L16,#:RAW,,;
Printer = L16,W,E,L17,#:RAW,,;
Printer = L17,W,E,L18,#:RAW,,;
Printer = L18,W,E,L19,#:RAW,,;
Printer = L19,W,E,L20,#:RAW,,;
Printer = L20,W,N, ,#:RAW,,;

All of the CometAnywhere users could specify L10, and the system would print to the first available printer on the above list. If all CometAnywhere users tried to use L10 at the same time, each user's output would be redirected to the next available printer on the cascade list.

For planning purposes, you should configure the same number of cascading printers as the number of simultaneous CometAnywhere remote users. That way, you won't run out of available printers.

'''HTML and Text Printers'''

Starting with Comet2000 Build 291 and REL version 01.04, you can configure HTML and text printers. When an MTB program prints to one of these virtual printers, the output is written to a temporary file in the $(catemp) directory and that file is then launched. If it’s an HTML file, the output is displayed in your default web browser (e.g., Explorer, Navigator). If it’s a text file, the output is displayed in your default text editor (e.g., Notepad).

'''Notes'''

HTML and text printers support text output, including the (CR), (LF) and (FF) mnemonics, but do not support the Windows enhanced printing features (e.g., text and font functions, graphics and drawing functions).

When printing to an HTML or text printer from a Comet node, you can print from a foreground or background partition. However, when printing to an HTML or text printer from a CometAnywhere remote system, you can only print from a foreground partition (namely, your own session).

'''Configuration information'''

· To configure an HTML printer, specify the printer type as H, the spool-type as N, the device name as HTM, and the DES program as HTMLPTR.

For example, suppose you want to configure an HTML printer named LPH. Here’s the printer configuration command:

Printer = LPH,H,N,,HTM,HTMLPTR,;

· To configure a text printer, specify the printer type as X, the spool-type as N, the device name as TXT, and the DES program as EXTPTR.

For example, suppose you want to configure a text printer named LPT. Here’s the printer configuration command:

Printer = LPT,X,N,,TXT,EXTPTR,;

'''Implementation Notes'''

HTML and text printers rely on the interaction between the specified DES program and the Comet2000 printer driver. In order to create a valid HTML document, a minimal number of HTML tags must be added to the output. These additions happen (1) before the user’s program outputs any data, (2) each time the user’s program issues a form feed, and (3) when the user’s program closes the printer. Here are the tags that are added by HTMLPTR driver event server program.

Before the user’s program outputs any data

<HTML>

<HEAD>

<TITLE>

Output from program-name,directory – Comet 2000 version HTMLPTR version

</TITLE>

</HEAD>

<BODY>

<PRE>

Each time the user’s program issues a form feed

<HR WIDTH=100%>

When the user’s program closes the printer

</PRE>

</BODY>

</HTML>

'''Important note'''

If your printed output contains imbedded HTML commands, or characters that are reserved characters in HTML (such as the < and > symbols), these characters are interpreted by the browser the same as all other HTML documents (i.e., the Comet printer driver does not filter imbedded HTML characters). For example, if you print an MTB source program to an HMTL printer, and that source program contains in-line HTML commands (e.g., an eComet source program), the browser will interpret the HTML commands. To avoid this problem when printing Comet output that contains imbedded HTML, use a text printer and the EXTPTR driver event server.

When printing to a text printer, the EXTPTR driver event server adds a line of dashes each time the user’s program issues a form feed. Nothing else is added to the output.

The Comet Utility Source Subset library (XTL directory, starting with version 01.01) contains the source code for HTMLPTR and EXTPTR. If you want to customize your HTML printer output (by adding a background color or image to the <BODY> tag, for example), you can modify and recompile the appropriate DES program.

When an HTML or text printer is closed, the DES program launches the temporary document.

Prior to Comet 2005, each time you print to a type H or type X printer, Comet created a temporary file in the $(catemp) directory. If you want to save one of these temporary files to a more permanent location, you could use the “Save As” feature in your browser or text editor. Beginning in Comet 2005, you may use the (Document = FileName$, Dir$) mnemonic to specify the name and location of the file.

PDF Printers

Beginning with Comet 2005 you can output to a pdf printer. You will need to have a pdf printer driver, either Adobe Acrobat or pdfFactory, installed on your system.

You configure your pdf printer as a type "P" printer:

Printer = LP5,P,N,,pdfFactory,,;

This printer is non-spooling and output will be directed to the pdfFactory printer.

By default, the document will be assigned a name and created in the folder specified in the printer's properties. Optionally, you can assign the document's name and the Comet directory in which it will be created by using the (Document = FileName$, Dir$) mnemonic. When this mnemonic is used, the document is first created in the folder specified in the printer's properties. Then, when the printer is closed, the document is copied to the Comet directory. You may send this mnemonic multiple times to create several uniquely named copies of the document.

Depending on whether you are using pdfFactory or Adobe Acrobat, Comet requires specific printer settings. From the Control Panel, select the printer's properties, then "Printing Preferences". For Adobe Acrobat, be sure the check box for "prompt for pdf filename" is unchecked. If you wish documents to launch automatically when printed, you may check the "view Adobe pdf results" check box. We have also found that checking "Enable advanced printing features" on the "Advanced" tab of the "Properties" dialog speeds up the document generation process considerably. For pdfFactory, be sure the radio button for "save the file in the AutoSave folder" is selected. When using pdfFactory, documents must be launched manually or you may associate the DES program, ViewDoc, with the printer. This will cause the document to launch when the printer is closed.

Introduction to the Comet Security System

2018-09-27T13:37:24Z

Barb:

'''Introduction to the Comet Security System'''

The Comet Security System provides password sign-on security for Comet systems. These features are implemented through the standard QMONITOR program included with Comet Version 502 and above, and through the SECURITY utility program contained in the UTL directory of a standard Comet release.

This documentation is intended for system managers who will be installing and maintaining the Comet security system. We have tried to keep the information in this document as clear as possible, but if you should have questions about any information in this document, we recommend calling your authorized Signature Systems dealer before proceeding.

The standard QMONITOR program included with Comet release contains password security options. The security options are activated simply by running the SECURITY utility program. The following chart lists the differences between the security and non-security implementations of QMONITOR.

{| border="1"
|Non-security implementation
|Security implementation
|-
|No password required at sign-on
|Password required at sign-on
|-
|Automatic access to all Comet directories
|Restricted access to directories (controlled by directory list in individual's password record)
|-
|Ability to use the ACCESS command at the READY prompt
|Optional ability to use the ACCESS command at the READY prompt (controlled by flag in individual's password record)
|-
|System always runs QMONITOR
|System runs QMONITOR or specific user program (if program name is contained in individual's password record)
|}

The security options in QMONITOR make use of a system password file. Each record in this file contains the user's name, password, directory list, program-to-run, and ACCESS command flag.

When a user signs on to a password-secured Comet system, they enter their assigned password and QMONITOR reads the information from their password record to create their list of accessed Comet directories. Thus, each person's password may contain an individual list of up to 50 directories, one of the best ways to prohibit access to security-sensitive files and programs.

If the user's password record contains the name of a program to be run, the user will be taken immediately to that program (an application menu, for example) and they will not see the familiar READY prompt of the QMONITOR program. And, in the course of using the Comet system, that user will always be returned to the program listed in their password record, not to the QMONITOR READY prompt. (Note, however, that if no program name is listed in the user's password record, they will proceed to the QMONITOR program all the time.)

Another option in the user's password is a flag indicating whether or not the person will be allowed to use the ACCESS command at the READY prompt of QMONITOR. If the flag is turned on, the user will be permitted to access additional Comet directories from the READY prompt. If the flag is turned off, the user will not be permitted to access other Comet directories.

The system password file is created and maintained with the SECURITY program. This program provides options for naming the system password file; adding, changing, deleting,and printing password records; and renaming the system password file.

Note: Since the name of the system password file is itself contained in a data file, the filename can be changed at any time without having to change the QMONITOR program. In fact, the QMONITOR program never needs to be re-compiled in order to implement the Comet security system.

The following file is created by the Comet security system:

{| border="1"
|Filename
|Directory
|Description
|-
|QSTART2
|COS
|Contains the name of the system password file and a list of the users currently signed onto the system
|}

In addition, a user-defined password file name is created on a Comet directory specified by the user. This file is named (or renamed) via the SECURITY program.

Introduction to the Comet Security System

2018-09-27T13:34:41Z

Barb:

'''Introduction to the Comet Security System'''

The Comet Security System provides password sign-on security for Comet systems. These features are implemented through the standard QMONITOR program included with Comet Version 502 and above, and through the SECURITY utility program contained in the UTL directory of a standard Comet release.

This documentation is intended for system managers who will be installing and maintaining the Comet security system. We have tried to keep the information in this document as clear as possible, but if you should have questions about any information in this document, we recommend calling your authorized Signature Systems dealer before proceeding.

The standard QMONITOR program included with Comet release contains password security options. The security options are activated simply by running the SECURITY utility program. The following chart lists the differences between the security and non-security implementations of QMONITOR.

{| border="1"
|Non-security implementation
|Security implementation
|-
|No password required at sign-on
|Password required at sign-on
|-
|Automatic access to all Comet directories
|Restricted access to directories (controlled by directory list in individual's password record)
|-
|Ability to use the ACCESS command at the READY prompt
|Optional ability to use the ACCESS command at the READY prompt (controlled by flag in individual's password record)
|-
|System always runs QMONITOR
|System runs QMONITOR or specific user program (if program name is contained in individual's password record)
|}

The security options in QMONITOR make use of a system password file. Each record in this file contains the user's name, password, directory list, program-to-run, and ACCESS command flag.

When a user signs on to a password-secured Comet system, they enter their assigned password and QMONITOR reads the information from their password record to create their list of accessed Comet directories. Thus, each person's password may contain an individual list of directories, one of the best ways to prohibit access to security-sensitive files and programs.

If the user's password record contains the name of a program to be run, the user will be taken immediately to that program (an application menu, for example) and they will not see the familiar READY prompt of the QMONITOR program. And, in the course of using the Comet system, that user will always be returned to the program listed in their password record, not to the QMONITOR READY prompt. (Note, however, that if no program name is listed in the user's password record, they will proceed to the QMONITOR program all the time.)

Another option in the user's password is a flag indicating whether or not the person will be allowed to use the ACCESS command at the READY prompt of QMONITOR. If the flag is turned on, the user will be permitted to access additional Comet directories from the READY prompt. If the flag is turned off, the user will not be permitted to access other Comet directories.

The system password file is created and maintained with the SECURITY program. This program provides options for naming the system password file; adding, changing, deleting,and printing password records; and renaming the system password file.

Note: Since the name of the system password file is itself contained in a data file, the filename can be changed at any time without having to change the QMONITOR program. In fact, the QMONITOR program never needs to be re-compiled in order to implement the Comet security system.

The following file is created by the Comet security system:

{| border="1"
|Filename
|Directory
|Description
|-
|QSTART2
|COS
|Contains the name of the system password file and a list of the users currently signed onto the system
|}

In addition, a user-defined password file name is created on a Comet directory specified by the user. This file is named (or renamed) via the SECURITY program.

Introduction to the Comet Security System

2018-09-27T13:33:39Z

Barb:

'''Introduction to the Comet Security System'''

The Comet Security System provides password sign-on security for Comet systems. These features are implemented through the standard QMONITOR program included with Comet Version 502 and above, and through the SECURITY utility program contained in the UTL directory of a standard Comet release.

This documentation is intended for system managers who will be installing and maintaining the Comet security system. We have tried to keep the information in this document as clear as possible, but if you should have questions about any information in this document, we recommend calling your authorized Signature Systems dealer before proceeding.

The standard QMONITOR program included with Comet release contains password security options. The security options are activated simply by running the SECURITY utility program. The following chart lists the differences between the security and non-security implementations of QMONITOR.

{| border="1"
|Non-security implementation
|Security implementation
|-
|No password required at sign-on
|Password required at sign-on
|-
|Automatic access to all Comet directories
|Restricted access to directories (controlled by directory list in individual's password record)
|-
|Ability to use the ACCESS command at the READY prompt
|Optional ability to use the ACCESS command at the READY prompt (controlled by flag in individual's password record)
|-
|System always runs QMONITOR
|System runs QMONITOR or specific user program (if program name is contained in individual's password record)
|}

The security options in QMONITOR make use of a system password file. Each record in this file contains the user's name, password, directory list, program-to-run, and ACCESS command flag.

When a user signs on to a password-secured Comet system, they enter their assigned password and QMONITOR reads the information from their password record to create their list of accessed Comet directories. Thus, each person's password may contain an individual list of directories, one of the best ways to prohibit access to security-sensitive files and programs.

If the user's password record contains the name of a program to be run, the user will be taken immediately to that program (an application menu, for example) and they will not see the familiar READY prompt of the QMONITOR program. And, in the course of using the Comet system, that user will always be returned to the program listed in their password record, not to the QMONITOR READY prompt. (Note, however, that if no program name is listed in the user's password record, they will proceed to the QMONITOR program all the time.)

Another option in the user's password is a flag indicating whether or not the person will be allowed to use the ACCESS command at the READY prompt of QMONITOR. If the flag is turned on, the user will be permitted to access additional Comet directories from the READY prompt. If the flag is turned off, the user will not be permitted to access other Comet directories.

The system password file is created and maintained with the SECURITY program. This program provides options for naming the system password file; adding, changing, deleting,and printing password records; and renaming the system password file.

Note: Since the name of the system password file is itself contained in a data file, the filename can be changed at any time without having to change the QMONITOR program. In fact, the QMONITOR program never needs to be re-compiled in order to implement the Comet security system.

An additional utility program is included with the release. This program lets you convert a password file from Qantel format to Comet format. The program name is SECQ2C.

The following file is created by the Comet security system:

{| border="1"
|Filename
|Directory
|Description
|-
|QSTART2
|COS
|Contains the name of the system password file and a list of the users currently signed onto the system
|}

In addition, a user-defined password file name is created on a Comet directory specified by the user. This file is named (or renamed) via the SECURITY program.

FAQs

2018-09-20T21:41:08Z

Barb: /* How can I get the latest license certificate for my security token? */

= FAQs =

==Where are all the various log files?==
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Below we'll tell you where the default locations of the files are. But you can control the location of the Comet logs by creating a %COMETDATA% environment variable. This does not apply to the Comet Services log files.

Here is a list of the log files and their default locations:

'''The Comet Log''' 
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

If you can't even run Comet and you need the log, click on the "Details" button at the bottom right corner of the splash screen when you attempt to run Comet. When the log display opens up, click on File->Open log file. It will open up in your text editor.

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path. 

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

'''The CosP Log''' 
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well. 
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

'''The Comet Services Logs''' 
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder. 

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6. 

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance. 

'''The XAP Log''' 
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log. 

==Where can I find my CosW.ini file?==
If you can find your Comet.log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This is true even if you are using the %COMETDATA% environment variable. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[http://wiki.signature.net/index.php/CosW.ini_settings]] 

==What ports are used by Signature Systems software?==
You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]] 

==What options can be set in the #XAP file?==

CLOSE 
The CLOSE command tells Comet to stop listening on the XAP gateway (in effect, resetting
the gateway).

LOGFILE pathname[,cycle | ,erase] 
The cycle option keeps up to 7 generations of the log file.

LISTEN port-number 
Specifies the port for XAP to listen on. Port 80 will be used by default.

USEWIN 
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.

EXPIRE xT[,ProgramName] 
This is used to set the expiration date for an eComet Context cookie. x is number; T is M|D|H, (for example 5M for 5 minutes); optional ProgramName is program to run when a new cookie is created (for example a relogin program). Without ProgramName, the normal XAP program is run with ClearCommon. Previously cookies expired only when the browser was closed. Now the cookies are persistent. Without the EXPIRE command cookies will be session cookies as they were before this enhancement. You can delete a cookie by setting an expiration date in the past.

TRACE 
Turns on the Comet32 TRACE window you'd get if you said TRACE ON in your IB program.

==I'm getting an error message that CometLib couldn't be registered. What should I do?==
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try. 
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on. 
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll 

==Will the Comet Services run on a virtual server?==
Yes as long as the server is running a supported version of Windows [[http://www.signature.net/signature/techdoc/general/systreq.htm]]. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[http://wiki.signature.net/index.php/Virtual_Dongle]] 
==How can I get the latest license certificate for my security token?==
There are a couple of ways. First if you are able to run Comet you can use the SecSrv utility with Comet32. In addition to doing certificate retrieval, it will also list all currently connected users along with their local IP addresses and tell you how long they have been connected. For Comet16 users you can use the older utility, SecLic. This requires that you have configured a WinSock gateway. 
If you can't run Comet at all, you can still get the latest license. For Server versions prior to 16.00, stop the Comet Services. Erase the license.txt and any [plugnumber].txt files from your Comet Services folder. When you restart the Comet Services the Security Server will automatically connect to our server to get the license if one is not found in your folder. If you're running Comet Services 16.00 or later, it's even easier. From the Security Server console, click Edit->Update licenses. Now click the "Update Certificate" button. Your certificate will be retrieved and installed for you. 
These methods work for parallel, USB, and virtual dongles. 

==Should I run Comet16 or Comet32?==
Comet16 can only be run on 32-bit versions of Windows and it has been retired. No further work will be done on it. We recommend you run Comet32. 
If you are running a 64-bit version of Windows, Comet32 will run automatically. On 32-bit versions of Windows you can request Comet32 by including /32 on your Comet shortcut command line: c:\comet\comet.exe /pn=nodename /32 
If you want to make sure all Comet clients on the network are running Comet32, just set ForceC32 = 1 in your CosWGlob.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]] 
Other things to consider: 
Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers. 
Comet32 can run programs compiled for Comet16 and programs compiled for Comet32. 
Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows] 
Note: 64-bit CometAnywhere clients can run their Comet session from a Comet16 CA host. In an environment where factors are preventing deployment of Comet32 at this time, this is a way you can run Comet16 on computers that otherwise could only run Comet32.

==How can I tell if a program was compiled for Comet16 or Comet32?==
There are several ways.
* CometExplorer's TYPE column indicates the type of object file: C16 Program, C32 Program, or C32M Program (Comet Mobile)
* When you run a program in Comet32 a colored block on the window's status line indicates the type of program: purple for Comet16; green for Comet32
* From inside your program you can use FSTAT on an object file to determine if it was compiled for Comet16 or Comet32. Look in position 135 [[http://wiki.signature.net/index.php/IB_Statements/fstat]]
* PSTAT can also be used to check the type of a program that's currently running. Look in position 219 [[http://wiki.signature.net/index.php/IB_Statements/pstat]]
* If you attempt to run a Comet32 program in Comet16 you will get an Error 63.

==Can I use the Comet16 compiler on a 64-bit computer?==
No, you can only run the Comet16 compiler from a computer that can run Comet16. When compiling from UltraEdit, either the Comet16 compiler or the Comet32 compiler will be launched depending on the version of Comet currently running on the host computer. So, on a 32-bit computer you can compile with either the Comet16 compiler or the Comet32 compiler, but on a 64-bit computer you can only compile with the Comet32 compiler.

FAQs

2018-09-20T19:15:00Z

Barb: /* FAQs */

= FAQs =

==Where are all the various log files?==
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Below we'll tell you where the default locations of the files are. But you can control the location of the Comet logs by creating a %COMETDATA% environment variable. This does not apply to the Comet Services log files.

Here is a list of the log files and their default locations:

'''The Comet Log''' 
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

If you can't even run Comet and you need the log, click on the "Details" button at the bottom right corner of the splash screen when you attempt to run Comet. When the log display opens up, click on File->Open log file. It will open up in your text editor.

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path. 

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

'''The CosP Log''' 
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well. 
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

'''The Comet Services Logs''' 
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder. 

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6. 

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance. 

'''The XAP Log''' 
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log. 

==Where can I find my CosW.ini file?==
If you can find your Comet.log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This is true even if you are using the %COMETDATA% environment variable. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[http://wiki.signature.net/index.php/CosW.ini_settings]] 

==What ports are used by Signature Systems software?==
You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]] 

==What options can be set in the #XAP file?==

CLOSE 
The CLOSE command tells Comet to stop listening on the XAP gateway (in effect, resetting
the gateway).

LOGFILE pathname[,cycle | ,erase] 
The cycle option keeps up to 7 generations of the log file.

LISTEN port-number 
Specifies the port for XAP to listen on. Port 80 will be used by default.

USEWIN 
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.

EXPIRE xT[,ProgramName] 
This is used to set the expiration date for an eComet Context cookie. x is number; T is M|D|H, (for example 5M for 5 minutes); optional ProgramName is program to run when a new cookie is created (for example a relogin program). Without ProgramName, the normal XAP program is run with ClearCommon. Previously cookies expired only when the browser was closed. Now the cookies are persistent. Without the EXPIRE command cookies will be session cookies as they were before this enhancement. You can delete a cookie by setting an expiration date in the past.

TRACE 
Turns on the Comet32 TRACE window you'd get if you said TRACE ON in your IB program.

==I'm getting an error message that CometLib couldn't be registered. What should I do?==
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try. 
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on. 
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll 

==Will the Comet Services run on a virtual server?==
Yes as long as the server is running a supported version of Windows [[http://www.signature.net/signature/techdoc/general/systreq.htm]]. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[http://wiki.signature.net/index.php/Virtual_Dongle]] 
==How can I get the latest license certificate for my security token?==
There are a couple of ways. First if you are able to run Comet you can use the SecLic utility. This requires a WinSock gateway in your configuration. If you are running Comet32, SecLic has been replaced by SecSrv. The WinSock gateway is automatically configured for you in Comet32. 
If you can't run Comet at all, you can still get the latest license. For Server versions prior to 16.00, stop the Comet Services. Erase the license.txt and any [plugnumber].txt files from your Comet Services folder. When you restart the Comet Services the Security Server will automatically connect to our server to get the license if one is not found in your folder. If you're running Comet Services 16.00 or later, it's even easier. From the Security Server console, click Edit->Update licenses. Now click the "Update Certificate" button. Your certificate will be retrieved and installed for you. 
These methods work for parallel, USB, and virtual dongles. 

==Should I run Comet16 or Comet32?==
Comet16 can only be run on 32-bit versions of Windows and it has been retired. No further work will be done on it. We recommend you run Comet32. 
If you are running a 64-bit version of Windows, Comet32 will run automatically. On 32-bit versions of Windows you can request Comet32 by including /32 on your Comet shortcut command line: c:\comet\comet.exe /pn=nodename /32 
If you want to make sure all Comet clients on the network are running Comet32, just set ForceC32 = 1 in your CosWGlob.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]] 
Other things to consider: 
Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers. 
Comet32 can run programs compiled for Comet16 and programs compiled for Comet32. 
Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows] 
Note: 64-bit CometAnywhere clients can run their Comet session from a Comet16 CA host. In an environment where factors are preventing deployment of Comet32 at this time, this is a way you can run Comet16 on computers that otherwise could only run Comet32.

==How can I tell if a program was compiled for Comet16 or Comet32?==
There are several ways.
* CometExplorer's TYPE column indicates the type of object file: C16 Program, C32 Program, or C32M Program (Comet Mobile)
* When you run a program in Comet32 a colored block on the window's status line indicates the type of program: purple for Comet16; green for Comet32
* From inside your program you can use FSTAT on an object file to determine if it was compiled for Comet16 or Comet32. Look in position 135 [[http://wiki.signature.net/index.php/IB_Statements/fstat]]
* PSTAT can also be used to check the type of a program that's currently running. Look in position 219 [[http://wiki.signature.net/index.php/IB_Statements/pstat]]
* If you attempt to run a Comet32 program in Comet16 you will get an Error 63.

==Can I use the Comet16 compiler on a 64-bit computer?==
No, you can only run the Comet16 compiler from a computer that can run Comet16. When compiling from UltraEdit, either the Comet16 compiler or the Comet32 compiler will be launched depending on the version of Comet currently running on the host computer. So, on a 32-bit computer you can compile with either the Comet16 compiler or the Comet32 compiler, but on a 64-bit computer you can only compile with the Comet32 compiler.

Main Page

2018-09-20T19:11:50Z

Barb: /* Comet by Signature Systems, Inc. */

='''Comet by Signature Systems, Inc.'''=

* [[Getting Started With Comet]]

* [[Subscription Benefits]]

* [[Virtual Dongle]]

* [[FAQs]]

* [[CFILES - the replacement for DbMgr]]

* [[Comet Meetings]]

* [[Configuration and Installation]]

* [[Programming]]

* [[Comet32]]

* [[STL Containers]]

* [[Xap and Comet32]]

* [[CometAnywhere Mobile]]

* [[Products]]

* [[Utilities]]

* [[Comet Tips]]

* [http://support.signature.net/ Support - Users Forum]

* [[How to edit this Wiki]]

* '''[http://cc.signature.net/guest/adduser Request ability to edit pages on this Wiki]'''

*[[Comet And RDP]]

A hint from the old guy. The Wiki's text size is based on the browser's settings. In '''Firefox''' I set the minimum font size to 16.

Tools >> Options >> Content >> Advanced. Minimum font size.

Subscription Benefits

2018-08-08T13:43:24Z

Barb: /* Benefits of being a Comet Subscriber */

Even if you are not a current subscriber to the Comet Software, most of your core applications will continue to work. However, Signature Systems continually improves its software and adds new features to the Comet System. These features are mainly available to current Comet Subscribers only.
=Benefits of being a Comet Subscriber=

*Entitled to all updates made to existing products during the subscription year
*Free COM license for each Comet license. This license is required for:
**CometExplorer
**(CopyFile) mnemonic through the file server. Without a COM license CopyFile is done directly with Windows calls which requires the client to have Windows access to the source and destination folders. This could require you to purchase additional Client Access Licenses from Microsoft.
**(Document=) mnemonic. This mnemonic is used by features of the email printer, the pdf printer, and DocMgr.
**The DataExpress version of the Reporter.
**CB, the CometAnywhere File Transfer Utility
*Protection against the loss of Comet access because of theft or verifiable loss of the security module. We will replace the usb plug and Comet licenses immediately, at no charge to the subscriber. Comet users who are not subscribers must rely on their business insurance to replace their system by completely repurchasing Comet at current prices. The expense and delay could far outweigh the cost of the subscription.
*Priority access to the technical support staff.
*The convenience of being able to apply CometAnywhere licenses to any version of the CometAnywhere host. This can be especially useful at subscription time. When new CometAnywhere licenses are issued you may continue to run an older version of Comet on the host until it is convenient for you to install the upgrade.
*Free ODBC/mySQL licenses for each Comet license.
*Use of the CometAnywhere Mobile API for developing IB programs that run on the Apple iPad and iPhone.

==These benefits expire at the end of the subscription period.==

Glossary of Terms

2018-05-01T21:30:42Z

Barb:

'''Glossary of Files and Terms'''

'''CapiServ.dll''' - A library of support routines for communication with external applications

'''CasMonitor.exe''' - Provides a mechanism to configure the "CometAsService" service startup parameters. It also monitors the state of the service and allows the user to start and/or stop the service.

'''CAUPD.exe''' - A self-extracting zip file containing CosUpd.exe, CosW.exe, CosP.exe, DIBAPI32.dll, and Update.dat to update software used by Comet Anywhere clients. This has been replaced by CAUpdate.exe beginning with Comet 2005.

'''CAUpdate.exe''' - A self-extracting zip file containing Comet.exe, CosW.exe, CosP.exe, CometLib.dll, and DIBAPI32.dll to update software used by Comet Anywhere clients. This has been replaced by the recommendation to run a full Comet install for your CometAnywhere clients.

'''CbSetup.exe''' - An installation program for the drivers required to locate your USB dongle. You need not run this program directly. It will be run automatically for you by CometServerProducts.exe.

'''CbUSB.exe''' - A diagnostic utility to test for the presence and validity of your USB dongle

'''CFAM.exe''' - The module which handles communications between your Comet application and its file server, whether local or remote

'''CFAMNetServe.exe''' - The Comet client/server communication manager. It provides remote connectivity to CFileSrv for CFAM clients.

'''CFileSrv.exe''' - The Comet file server for Windows operating systems

'''CLibNetServe.exe''' - Provides remote access for CometLib at the Comet Anywhere host computer.

'''CNS''' - see CFAMNetServe.exe

'''COM product''' - A COM-compliant DLL available to Comet applications allowing them to access Comet files from programs written in languages other than Internet Basic, such as Visual Basic, VBScript, JScript, and C++.

'''Comet.exe''' - The program used to startup Comet and insure that the user is running the most up to date version of Comet available on the network

'''CometKMD.sys''' - The driver used to communicate with your parallel security dongle

'''CometNTService.exe''' - The program which performs the (un)installation and execution of the Comet file server programs as services.

'''CometLib.dll''' - The library of Comet file system functions available to COM-compliant programming languages.

'''CometPV.dll''' - The library of functions required for use with the Comet OleDbLite product.

'''CometServerProducts.exe''' - The program used to install a Comet file and/or security server with all required files and libraries.

'''CometSrv.NLM''' - The Comet file server for NetWare operating systems.

'''CometWorkstation.exe''' - The program used to install a Comet workstation with all required files and libraries.

'''Cos32.exe''' - The Comet32 runtime kernel

'''CosC.exe''' - The Comet sessions manager

'''CosD.exe''' - The Comet16 debugger for Internet Basic programs

'''CosH.exe''' - The Comet runtime kernel

'''CosHdll.dll''' - OBSOLETE: a test version of the Comet32 runtime kernel

'''CosHipc.dll''' - A library of supporting routines used by CosH.exe

'''CosM32.exe''' - The Comet32 Internet Basic compiler

'''CosP.exe''' - The Comet printer driver for Windows printers

'''CosW.exe''' - The Comet session; the window in which Comet runs

'''Crt.ddl''' - The definition of mnemonic extensions to the Internet Basic language for use with terminal I/O

'''Crt32.ddl''' - The definition of mnemonic extensions to the Internet Basic language for Comet32 terminal I/O

'''CSAdmin.exe''' - A program used to install the security dongle drivers and setup the server executables to run as a service. This program was replaced by CometServerProducts.exe beginning in Comet 2004 and by ServerInstall.exe for older systems.

'''CSecSrv.exe''' - The Comet Security Server for Windows operating systems

'''DDL''' - An abbreviation for data definition language, a database language that describes its data structures

'''DLL''' - An abbreviation for dynamic link library, a file containing a collection of executable routines designed to perform specific functions

'''DIBAPI32.dll''' - A 32-bit device-independent bitmap (DIB) library used by CosW.exe and CosP.exe for rendering bitmap objects

'''FaxDriver.exe''' - The Comet fax driver

'''InstallHelper.dll''' - A component of InstallShield™ used in the installation of Comet software products.

'''ODBC''' - An abbreviation for Open DataBase Connectivity - A Microsoft standard for accessing different database systems.

'''ODBCd.dll''' - A library of functions used by the COMET16 ODBC facility

'''ODBCDrv.exe''' - A library of functions used by the COMET16 ODBC facility

'''OleDbLite''' - The Comet product allowing use of Crystal Reports™ to access to your Comet data

'''ServerInstall.exe''' - A program used to install the security dongle drivers and setup the server executables to run as a service. This program was replaced by CometServerProducts.exe beginning in Comet 2004.

'''System.ddl''' - The definition of mnemonic extensions to the Internet Basic language for use with the kernel

'''System32.ddl''' - The definition of mnemonic extensions to the Internet Basic language for use with the Comet32 kernel

'''UniDrv.dll''' - A universal driver used by the Comet fax application

'''WinPrint.ddl''' - The definition of mnemonic extensions to the Internet Basic language for use with printer output.

'''WPrint32.ddl''' - The definition of mnemonic extensions to the Internet Basic language for use with Comet32 printer output.

'''Ws32.ddl''' - The definition of mnemonic extensions to the Internet Basic language for use with Comet32 WinSock applications.

--------------------------------------------------------------------------------
Copyright © 1995 - 2013 Signature Systems, Inc.

Comet Error Codes

2018-05-01T16:16:43Z

Barb: /* Internet Basic Compiler Error Messages */

== Comet Exception Messages ==

(QERCOMET file)
EXCP Meaning
=================================================================
00 No Exception Reported
01 Not in Current Use
02 End of File
03 Unable to Allocate Space for File
04 Keyed File Write Without Index
05 Create Without Directory Label
06 Directory Not Found on ACCESS
07 File Unavailable--Lock/Unlock Error
08 Not in Current Use
09 Not in Current Use
10 Not in Current Use
11 File Not Found
12 File Already Exists
13 Text file exists on CREATE
14 Not in Current Use
15 Unhandled math error
16 Number too large for variable
17 Numeric overflow
18 Not in Current Use
19 Attempt to divide by zero
20 Math library ran out of memory
21 Math library internal error
22 Not in Current Use
23 Not in Current Use
24 Unable to Rename Disk to Disk
25 Invalid DOS Call
26 Invalid Message Call
27 DOS Returned an Error
28 Invalid Priority Call
29 Not in Current Use
30 Device Inoperative
31 Device or Directory Unavailable
32 Key Not Found
33 Record Unavailable--Extract Error
34 Logical Unit # Unavailable for Open
35 File Not Open for Read or Write
36 Can't Perform Function on Open File
37 Not in Current Use
38 Device or Target File System Unable to Perform Function
39 Not in Current Use
3D KDOS Function Error
40 Invalid Window Specified
41 Edit Mask Length Incorrect
42 Not in Current Use
43 Not in Current Use
44 I/O Buffer Overflow
45 Invalid Parameter
46 Non-Numeric Input in a Numeric Field
47 Parameter Too Large
48 Invalid Key or Record Size: CREATE
49 Invalid Logical Unit Number
50 Array Subscript Out of Range
51 Not in Current Use
52 Not in Current Use
53 Invalid File Access
54 Invalid Function for Named File
55 Not in Current Use
56 Record Already Exists for INSERT
59 Not in Current Use
60 Cannot IPL while other Users Active
61 Program Not Found
62 Not in Current Use
63 Cannot Run Non-Object File
64 Invalid Partition Name
65 Partition Busy, Program Running
66 Performed an EXIT when ENTERLEVEL value was 0
67 Partition Busy, Normal Termination
68 Terminate Complete, Task Wasn't Idle
69 Activate Unsuccessful/Task had Error Pending
70 ESCAPETO/SUB not active for INTERRUPT
71 DOS Failed to Transfer Read Data
72 IRQ 3 Failure from Comet Board
73 Illegal Jump to Location Zero
74 Not in Current Use
75 Resources Left Allocated After Call
76 File Size Limit Reached in Demo Mode
77 Attempted Write with Zero Length
78 Error Performing ENTER/EXIT Program
79 Key Block Offset Too Large
7A Attempt to EXTRACT Keyed Only File
7B Maximum File Size Exceeded
80 Maximum I/O Buffer Size Exceeded
81 Spool File Error
82 Top Key Sector not in Delete Stack
83 DOS Disc Error
84 Key Sector Search Level Impossible
85 ES NOT POINTING TO DATA_SEG IN DOS CALL
86 File Descriptor List Overflow
87 Unexpected EOF from DOS
88 Keys but NO Records in File
89 Unsupported Reference
8A Network Buffer Overflow
8E Node Lock Timed Out
90 Disk Full -- DOS Wrote Less Than Expected
91 Invalid/Unsupported System Call
92 GOSUB Stack Underflow
93 GOSUB Stack Overflow
94 Directory Entry Unavailable / CLOSE
95 Next Key Unavailable for Deletion
96 New Key Found during INSERT
97 New First Key found during INSERT
98 Extracted Record not found in Table
99 Error Received from DOS

== Internet Basic Compiler Error Messages ==

Number Error Message
===================================================================
00 System error - Reload and restart
01 Missing keyword, punctuation
02 Cannot redefine symbolic constant at execution time
03 Variable referenced is incorrect type or undefined
04 Variable has been previously defined
05 Out of range parameter (constant)
06 Array too large (9999 bytes maximum)
07 Unnecessary characters following a statement
08 Statement number previously declared
09 Invalid syntax for hex field
10 Non-numeric FOR/NEXT parameter
11 Invalid loop statement
12 Invalid string constant termination
13 Nested FOR/NEXT loop using same control variable
14 Invalid conditional statement
15 FOR/NEXT nesting error
16 No matching FOR statement
17 Statement number required
18 FORMAT number not declared
19 Argument/subscript error
20 Incorrect number of expression operands
21 Precision will overflow accumulator
22 No path to this statement
23 No space to evaluate expression
24 Precision conflict (FOR/NEXT)
25 We've only got one string accumulator
26 String length not declared
27 BREAK or CONTINUE found, no FOR/DO
28 Integer out of range
29 Operand/operator type disagreement
30 Unbalanced parentheses
31 Numeric expression required
32 Logical expression required
33 Expression operator not allowed
34 No DO loop conditional clause
35 String expression required
36 Fraction, where integer required
37 Integer/symbolic constant required
38 -reserved for future use-
39 Invalid usefile parameter
40 LOOP statement has no preceding "DO"
41 SELECT/CASE sequence error
42 CASE: "FROM" with no "TO" or "THRU"
43 "CASE ELSE" no last "CASE"
44 MTB51 read\write error
45 .ELSE without .IF (Comet16 only)
46 Unrecognizable compiler directive (Comet16 only)
47 not used
48 not used
49 not used
50 not used
51 Program exceeds 64K (Comet16 only)
52 Too many conditional statements (internal label count) 64K (Comet16 only)
53 Array element not allowed for SELECT CASE expression

== Windows Sockets Error Codes, Values, and Meanings ==

Last reviewed: November 17, 1997
Article ID: Q150537
The information in this article applies to:
Microsoft Windows NT Workstation versions 3.5 and 3.51
Microsoft Windows NT Server versions 3.5 and 3.51
Microsoft LAN Manager version 2.2c
Microsoft TCP/IP-32 for Windows for Workgroups, versions 3.11, 3.11a, and 3.11b
Microsoft Windows 95
Microsoft Network Client version 3.0 for MS-DOS

'''SUMMARY'''

This article describes the Windows Sockets error codes.

'''MORE INFORMATION'''
The following table is a list of possible error codes returned by the WSAGetLastError() call, along with their explanations.

Windows Sockets code Error Description
------------------------------------------------------------------------
WSAEINTR 10004 Interrupted system call.
WSAEBADF 10009 Bad file number.
WSEACCES 10013 Permission denied.
WSAEFAULT 10014 Bad address.
WSAEINVAL 10022 Invalid argument.
WSAEMFILE 10024 Too many open files.
WSAEWOULDBLOCK 10035 Operation would block.
WSAEINPROGRESS 10036 Operation now in progress. This error is
returned if any Windows Sockets API
function is called while a blocking
function is in progress.
WSAEALREADY 10037 Operation already in progress.
WSAENOTSOCK 10038 Socket operation on nonsocket.
WSAEDESTADDRREQ 10039 Destination address required.
WSAEMSGSIZE 10040 Message too long.
WSAEPROTOTYPE 10041 Protocol wrong type for socket.
WSAENOPROTOOPT 10042 Protocol not available.
WSAEPROTONOSUPPORT 10043 Protocol not supported.
WSAESOCKTNOSUPPORT 10044 Socket type not supported.
WSAEOPNOTSUPP 10045 Operation not supported on socket.
WSAEPFNOSUPPORT 10046 Protocol family not supported.
WSAEAFNOSUPPORT 10047 Address family not supported by protocol
family.
WSAEADDRINUSE 10048 Address already in use.
WSAEADDRNOTAVAIL 10049 Cannot assign requested address.
WSAENETDOWN 10050 Network is down. This error may be
reported at any time if the Windows
Sockets implementation detects an
underlying failure.
WSAENETUNREACH 10051 Network is unreachable.
WSAENETRESET 10052 Network dropped connection on reset.
WSAECONNABORTED 10053 Software caused connection abort.
WSAECONNRESET 10054 Connection reset by peer.
WSAENOBUFS 10055 No buffer space available.
WSAEISCONN 10056 Socket is already connected.
WSAENOTCONN 10057 Socket is not connected.
WSAESHUTDOWN 10058 Cannot send after socket shutdown.
WSAETOOMANYREFS 10059 Too many references: cannot splice.
WSAETIMEDOUT 10060 Connection timed out.
WSAECONNREFUSED 10061 Connection refused.
WSAELOOP 10062 Too many levels of symbolic links.
WSAENAMETOOLONG 10063 File name too long.
WSAEHOSTDOWN 10064 Host is down.
WSAEHOSTUNREACH 10065 No route to host.
WSASYSNOTREADY 10091 Returned by WSAStartup(), indicating that
the network subsystem is unusable.
WSAVERNOTSUPPORTED 10092 Returned by WSAStartup(), indicating that
the Windows Sockets DLL cannot support
this application.
WSANOTINITIALISED 10093 Winsock not initialized. This message is
returned by any function except
WSAStartup(), indicating that a
successful WSAStartup() has not yet been
performed.
WSAEDISCON 10101 Disconnect.
WSAHOST_NOT_FOUND 11001 Host not found. This message indicates
that the key (name, address, and so on)
was not found.
WSATRY_AGAIN 11002 Nonauthoritative host not found. This
error may suggest that the name service
itself is not functioning.
WSANO_RECOVERY 11003 Nonrecoverable error. This error may
suggest that the name service itself is
not functioning.
WSANO_DATA 11004 Valid name, no data record of requested
type. This error indicates that the key
(name, address, and so on) was not found.

'''NOTE:''' This table does not include all of the error codes defined in
Winsock

== CopyFileErrors: ==
'''Function Error Routine/Apply Descriptions'''

'''select case FuncError'''
{| Border=1
|-
| Heading 1
| Heading 2
| Heading3
|-
| case 0
| Funcerror$ = 'Function not supported'
|
|-
| case 1
| Funcerror$ = 'Success -- update performed'
|
|-
| case 2
| Funcerror$ = 'CometAnywhere required'
|
|-
| case 3
| Funcerror$ = 'Source file error (see suberrors)'
|
|-
| case 4
| Funcerror$ = 'Aborted by user'
|
|-
| case 5
| Funcerror$ = 'Function in progress'
|
|-
| case 20
| Funcerror$ = 'Success -- update not required'
|
|-
| case 21
| Funcerror$ = 'Success -- update required'
|
|-
| case 22
| Funcerror$ = 'Destination file error (see suberrors)'
|
|-
| case else & Funcerror$ = 'Unknown'
| endselect
|
|-
|}
'''select case FileError'''
case 0
FileError$ = 'Success'
case 2
FileError$ = 'File not found'
case 3
FileError$ = 'Path not found'
case 5
FileError$ = 'Access denied'
case 12
FileError$ = 'Invalid access'
case 15
FileError$ = 'Invalid drive'
case 16
FileError$ = 'An error has occurred in the current directory'
case 18
FileError$ = 'No more files'
case 32
FileError$ = 'Sharing violation'
case 33
FileError$ = 'Lock violation'
case 80
FileError$ = 'File exists'
case 123
FileError$ = 'The Filename, Directory Name, or Volume Label Syntax Is Incorrect'
case 161
FileError$ = 'Bad pathname'
case else
FileError$ = 'Unknown'
endselect
return

'''GetDirAliasErrors:'''
select case FuncError
case 0
Funcerror$ = 'Function not supported'
case 1
Funcerror$ = 'Success'
case 2
Funcerror$ = 'CometAnywhere required'
case 3
Funcerror$ = 'Source file error (see suberrors)'
case 4
Funcerror$ = 'Aborted by user'
case 5
Funcerror$ = 'Function in progress'
case else & Funcerror$ = 'Unknown'
endselect

'''select case FileError'''
case 0
FileError$ = 'Success'
case 2
FileError$ = 'File not found'
case 3
FileError$ = 'Path not found'
case 5
FileError$ = 'Access denied'
case 12
FileError$ = 'Invalid access'
case 15
FileError$ = 'Invalid drive'
case 16
FileError$ = 'An error has occurred in the current directory'
case 18
FileError$ = 'No more files'
case 32
FileError$ = 'Sharing violation'
case 33
FileError$ = 'Lock violation'
case 80
FileError$ = 'File exists'
case 123
FileError$ = 'The Filename, Directory Name, or Volume Label Syntax Is Incorrect'
case 161
FileError$ = 'Bad pathname'
case else
FileError$ = 'Unknown'
endselect
return

== These are spare headings for any other tables of error codes ==
== Actually I just couldn't be bothered to check the help to see how to force this T.O.C. ==

CometAnywhere Mobile

2018-04-25T18:24:25Z

Barb: /* Demo programs */

== CometAnywhere Mobile (Alpha testing) ==

Click here for the [[CometAnywhere Mobile Changelog]]

== READ ME FIRST ==

You MUST send your UDID number to justin@signature.net in order to be included in the alpha testing for CometAnywhere Mobile!

To get your UDID, go to your iPad device under iTunes, and click "Serial Number." "Identifier (UDID)" should then show up with a long hex code next to it - this is your UDID. We are currently building your UDID numbers into our releases so that ONLY the iPads with the included UDIDs can run the mobile app.

Alternatively you can download a program (like http://itunes.apple.com/us/app/udid/id458358726?mt=8) and use it to email a summary of your device to justin@signature.net

== Disclaimer ==

This product is VERY alpha. We hope that you will join us in developing this product, but be aware that it is and will be constantly in flux. By getting in at the ground floor, you will be able to follow our development, see new features become available, as well as recommend new features as you become familiar with the mobile devices.

That being said, there is absolutely no guarantee that as we release new versions of the app, that old programs will continue to run (or even be stable). We are trying to provide you with the best product we can, which means that at this stage functions/procs could change overnight, and redesigns of the app will be commonplace - especially if you see improvements we can make!

We hope you will help us test this new and exciting product.

== Licensing ==

CometAnywhere Mobile currently uses up a regular CometAnywhere license. You must have a CometAnywhere host running with available client licenses.

== Installation ==

The CometAnywhere Mobile App requires the latest REL (12.07) be installed on the CometAnywhere host. Due to the special nature of mobile devices, we are running a special MMonitor program to interface with the iPad.

Once you've received the CometAnywhere Mobile app, you must install it on your iPad. To do this, import the .ipa file into itunes (usually by double clicking). Then sync the app to your iPad by going to your iPad (under devices in itunes), then the "Apps" tab. Check "Sync Apps" and sync the CometAnywhere app.

When it's synced, you should be able to run the app from your iPad and connect to a CometAnywhere mobile-enabled server.

== Running the app ==

When the app first opens, you must push the "Connect" button in order to connect to a CometAnywhere host. Currently, you must connect via a globally visible IP address (i.e. myserver.mydomain.com, or xxx.xxx.xxx.xxx). Once connected you will be prompted to enter a program to run. Use this to run any mobile programs you have compiled.

== Demo programs ==

Demo programs are hosted on cc32.signature.net under the username "mobile" and password "mobile". Connect and log in, then enter the demo program name that you would like to run.

== Mobile.inc ==

Currently, mobile programs are written using procs to simulate mnemonics/functions that interact with the iPad. You can find the file [http://www.signature.net/download/MailBoxes/mobile.inc here]. Use these procs as demonstrated in the demo programs.

== KBC Demo App ==

Info on how to download and install the KBC invoicing demo app, source included [[http://wiki.signature.net/index.php/KBC_demo_app]].

Virtual Dongle

2018-02-27T18:39:48Z

Barb: /* Comet Security Server Virtual Dongle Installation */

== Comet Security Server Virtual Dongle Installation ==

The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:

*A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [http://www.signature.net/download/End%20User%20License%20Agreement.pdf]

*You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
*The Comet Security Server must have a reliable internet connection. If you use Internet Security Software you'll need to set it up to allow 2-way traffic with dongle.signature.net (to port 80) and signature.net (to port 8080). Be aware that your use of a proxy server may interfere with this communication.
*The Comet Security Server must be running as a service and have '''administrator privileges'''.
*A Virtual Dongle may be associated with one and only one computer. Once installed you may not move it to another computer.

 If you are replacing an existing USB or parallel dongle:

*Install Server Products vsn 18 or higher on your server and make sure all is well using the existing dongle.
*Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
*Stop the Comet Services then remove the old dongle.
*Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''
*Return the old dongle to Signature Systems so that the permanent certificate can be issued.

 If you are installing a new system:

*Make sure your internet connection is working on the server where the Comet Services will be installed.
*If you haven't already done so, we recommend you install the Microsoft Redistributables Package. Some of the .NET framework files are used by the Security Server. You can download vcredist_x86.exe here [http://www.signature.net/download/MailBoxes/]
*Create the Comet Services folder.
*Put the DRB.txt file into that folder.
*Install Server Products vsn 18 or higher on your server. When it asks for dongle type, choose USB. This is because the Security Server will attempt to find a USB dongle first and it needs the drivers to be able to do that. When it asks if you want to restart Windows, say '''"No"'''. Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''

Virtual Dongle

2018-02-27T18:39:35Z

Barb: /* Comet Security Server Virtual Dongle Installation */

== Comet Security Server Virtual Dongle Installation ==

The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:

*A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [http://www.signature.net/download/End%20User%20License%20Agreement.pdf]

*You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
*The Comet Security Server must have a reliable internet connection. If you use Internet Security Software you'll need to set it up to allow 2-way traffic with dongle.signature.net (to port 80) and signature.net (to port 8080). Be aware that your use of a proxy server may interfere with this communication.
*The Comet Security Server must be running as a service and have '''administrator privileges'''.
*A Virtual Dongle may be associated with one and only one computer. Once installed you may not move it to another computer.

 If you are replacing an existing USB or parallel dongle:

*Install Server Products vsn 16 or higher on your server and make sure all is well using the existing dongle.
*Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
*Stop the Comet Services then remove the old dongle.
*Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''
*Return the old dongle to Signature Systems so that the permanent certificate can be issued.

 If you are installing a new system:

*Make sure your internet connection is working on the server where the Comet Services will be installed.
*If you haven't already done so, we recommend you install the Microsoft Redistributables Package. Some of the .NET framework files are used by the Security Server. You can download vcredist_x86.exe here [http://www.signature.net/download/MailBoxes/]
*Create the Comet Services folder.
*Put the DRB.txt file into that folder.
*Install Server Products vsn 18 or higher on your server. When it asks for dongle type, choose USB. This is because the Security Server will attempt to find a USB dongle first and it needs the drivers to be able to do that. When it asks if you want to restart Windows, say '''"No"'''. Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''

Subscription Benefits

2018-01-31T21:21:27Z

Barb: /* Benefits of being a Comet Subscriber */

Even if you are not a current subscriber to the Comet Software, most of your core applications will continue to work. However, Signature Systems continually improves its software and adds new features to the Comet System. These features are mainly available to current Comet Subscribers only.
=Benefits of being a Comet Subscriber=

*Entitled to all updates made to existing products during the subscription year
*Free COM license for each Comet license. This license is required for:
**CometExplorer
**(CopyFile) mnemonic through the file server. Without a COM license CopyFile is done directly with Windows calls which requires the client to have Windows access to the source and destination folders. This could require you to purchase additional Client Access Licenses from Microsoft.
**(Document=) mnemonic. This mnemonic is used by features of the email printer, the pdf printer, and DocMgr.
**The DataExpress version of the Reporter.
*Protection against the loss of Comet access because of theft or verifiable loss of the security module. We will replace the usb plug and Comet licenses immediately, at no charge to the subscriber. Comet users who are not subscribers must rely on their business insurance to replace their system by completely repurchasing Comet at current prices. The expense and delay could far outweigh the cost of the subscription.
*Priority access to the technical support staff.
*The convenience of being able to apply CometAnywhere licenses to any version of the CometAnywhere host. This can be especially useful at subscription time. When new CometAnywhere licenses are issued you may continue to run an older version of Comet on the host until it is convenient for you to install the upgrade.
*Free ODBC/mySQL licenses for each Comet license.
*Use of the CometAnywhere Mobile API for developing IB programs that run on the Apple iPad and iPhone.

==These benefits expire at the end of the subscription period.==

Subscription Benefits

2018-01-31T21:20:51Z

Barb: /* Benefits of being a Comet Subscriber */

Even if you are not a current subscriber to the Comet Software, most of your core applications will continue to work. However, Signature Systems continually improves its software and adds new features to the Comet System. These features are mainly available to current Comet Subscribers only.
=Benefits of being a Comet Subscriber=

*Entitled to all updates made to existing products during the subscription year
*Free COM license for each Comet license. This license is required for:
**CometExplorer
**(CopyFile) mnemonic through the file server. Without a COM license CopyFile is done directly with Windows calls which requires the client to have Windows access to the source and destination folders. This could require you to purchase additional Client Access Licenses from Microsoft.
**(Document=) mnemonic. This mnemonic is used by features of the email printer, the pdf printer, and DocMgr.
**The DataExpress version of the Reporter.
*Protection against the loss of Comet access because of theft or verifiable loss of the security module. We will replace the plug/usb and Comet licenses immediately, at no charge to the subscriber. Comet users who are not subscribers must rely on their business insurance to replace their system by completely repurchasing Comet at current prices. The expense and delay could far outweigh the cost of the subscription.
*Priority access to the technical support staff.
*The convenience of being able to apply CometAnywhere licenses to any version of the CometAnywhere host. This can be especially useful at subscription time. When new CometAnywhere licenses are issued you may continue to run an older version of Comet on the host until it is convenient for you to install the upgrade.
*Free ODBC/mySQL licenses for each Comet license.
*Use of the CometAnywhere Mobile API for developing IB programs that run on the Apple iPad and iPhone.

==These benefits expire at the end of the subscription period.==

Subscription Benefits

2018-01-31T20:01:32Z

Barb:

Even if you are not a current subscriber to the Comet Software, most of your core applications will continue to work. However, Signature Systems continually improves its software and adds new features to the Comet System. These features are mainly available to current Comet Subscribers only.
=Benefits of being a Comet Subscriber=

*Entitled to all updates made to existing products during the subscription year
*Free COM license for each Comet license. This license is required for:
**CometExplorer
**(CopyFile) mnemonic through the file server. Without a COM license CopyFile is done directly with Windows calls which requires the client to have Windows access to the source and destination folders. This could require you to purchase additional Client Access Licenses from Microsoft.
**(Document=) mnemonic. This mnemonic is used by features of the email printer, the pdf printer, and DocMgr.
**The DataExpress version of the Reporter.
*Protection against the loss of Comet access because of theft or verifiable loss of the security module. We will replace the plug/usb and Comet licenses immediately, at no charge to the subscriber. Comet users who are not subscribers must rely on their business insurance to replace their system by completely repurchasing Comet at current prices. The expense and delay far outweigh the cost of the subscription.
*Priority access to the technical support staff.
*The convenience of being able to apply CometAnywhere licenses to any version of the CometAnywhere host. This can be especially useful at subscription time. When new CometAnywhere licenses are issued you may continue to run an older version of Comet on the host until it is convenient for you to install the upgrade.
*Free ODBC/mySQL licenses for each Comet license.
*Use of the CometAnywhere Mobile API for developing IB programs that run on the Apple iPad and iPhone.

==These benefits expire at the end of the subscription period.==

IB enhancements for Comet32

2017-12-05T22:49:47Z

Barb:

[[IB_Statements/SearchFile|'''Search File - C32''']]

[[IB_Statements/InputFile_and_PrintFile|'''InputFile and PrintFile - C32''']]

[[IB_Statements/GetFormat|'''GetFormat and SetFormat - C32''']]

[[IB_Statements/UserDefinedProcs|'''User Defined Procedures''']]

Comet32 Numeric Processing
* Comet32 provides much enhanced numeric handling over Comet16.
* Numeric variables can be as long as 32 decimal places. This is twice the length of Comet16.
* Expression results are calculated to length 64.32 so that partial results of expressions are preserved.
* The following Comet16 Functionality is supported::
Add, z = x + y
Subtract, z = x - y
Multiply, z = x * y
Divide, z = x / y
Negate, z = - x
Abs, z = abs(x) -- Return the absolute value of x
Int, z = int(x) -- Return the integer portion of x
Fpt, z = fpt(x) -- Return the fractional portion of x
Sgn, z = sgn(x) -- Return the sign of x (-1,0,+1)
Num, z = num(a$,err) -- Return the string a$ converted to a number.
Asc, z = asc(a$) -- Return the ascii equivalent of the first character in a$.
Len, z = len(a$) -- Return the length of string a$.
BitwiseAnd, z = x and y
BitwiseOr, z = x or y
BitwiseXor, z = x xor y
BitwiseNot, z = not(x)
Mod, z = x mod y -- Divides int(x) by int(y) and return the remainder
Sqrt, z = sqrt(x) -- Return the Square Root of x
Rnd, z = rnd() -- Return a "random number" between 0 and 1
Many additional math functions are supported in Comet32:
Cbrt, z = cbrt(x) -- Return the Cube Root of x
Log, z = log(x) -- Return the base-e logarithm of x, so x==exp(z)
Log10, z = log10(x) -- Return the base-10 logarithm of x, so x==pow(10,z)
Exp, z = exp(x) -- Return e raised to the power x, so x==log(z)
Pow, z = pow(x,y) -- Return x raised to the power y
Sin, z = sin(x) -- Return the sine of x, with x in radians
Cos, z = cos(x) -- Return the cosine of x, with x in radians
Tan, z = tan(x) -- Return the tangent of x, with x in radians
Asin, z = asin(x) -- Return the inverse sine of x, in radians
Acos, z = acos(x) -- Return the inverse cosine of x, in radians
Atan, z = atan(x) -- Return the inverse tangent of x, in radians
Atan2, z = atan2(y,x) -- Return the 4 quadrant inverse tangent of y/x
Sinh, z = sinh(x) -- Return the hyperbolic sine of x
Cosh, z = cosh(x) -- Return the hyperbolic cosine of x
Tanh, z = tanh(x) -- Return the hyperbolic tangent of x
Asinh, z = asinh(x) -- Return the inverse hyperbolic sine of x
Acosh, z = acosh(x) -- Return the inverse hyperbolic cosine of x
Atanh, z = atanh(x) -- Return the inverse hyperbolic tangent of x
Factorial, z = factorial(x)-- Return the factorial of x
Floor, z = floor(x) -- Return the floor (next lowest integer value) of x.
Ceil, z = ceil(x) -- Return the ceil (next highest integer value) of x.
Gcd, z = gcd(x,y) -- Return the GCD (greatest common divisor) of x, y.
Lcm, z = lcm(x,y) -- Return the LCM (least common multiple) of x, y.

Beware! The following code will not work the same for Comet32 as it did for Comet16:
For I = 0 to 99
A$ = "T" + sub(str(i+100),15,2)
Next i

Because the result of the addition is in the accumulator which has changed.

The following code will ALWAYS work for both Comet16 and Comet32:
For I = 0 to 99
A$ = `T' + sub(strip(str(i+100)),2,2)
Next I

Internet Basic Compiler Error Messages

2017-11-22T15:27:02Z

Barb: /* Internet Basic Compiler Error Messages */

== Internet Basic Compiler Error Messages ==

Number Error Message
===================================================================
00 System error - Reload and restart
01 Missing keyword, punctuation
02 Cannot redefine symbolic constant at execution time
03 Variable referenced is incorrect type or undefined
04 Variable has been previously defined
05 Out of range parameter (constant)
06 Array too large (9999 bytes maximum)
07 Unnecessary characters following a statement
08 Statement number previously declared
09 Invalid syntax for hex field
10 Non-numeric FOR/NEXT parameter
11 Invalid loop statement
12 Invalid string constant termination
13 Nested FOR/NEXT loop using same control variable
14 Invalid conditional statement
15 FOR/NEXT nesting error
16 No matching FOR statement
17 Statement number required
18 FORMAT number not declared
19 Argument/subscript error
20 Incorrect number of expression operands
21 Precision will overflow accumulator
22 No path to this statement
23 No space to evaluate expression
24 Precision conflict (FOR/NEXT)
25 We've only got one string accumulator
26 String length not declared
27 BREAK or CONTINUE found, no FOR/DO
28 Integer out of range
29 Operand/operator type disagreement
30 Unbalanced parentheses
31 Numeric expression required
32 Logical expression required
33 Expression operator not allowed
34 No DO loop conditional clause
35 String expression required
36 Fraction, where integer required
37 Integer/symbolic constant required
38 -reserved for future use-
39 Invalid usefile parameter
40 LOOP statement has no preceding "DO"
41 SELECT/CASE sequence error
42 CASE: "FROM" with no "TO" or "THRU"
43 "CASE ELSE" no last "CASE"
44 MTB51 read\write error
45 .ELSE without .IF
46 Unrecognizable compiler directive
47 - reserved -
48 - reserved -
49 - reserved -
50 - reserved -
51 Program exceeds 64K
52 Too many internal statements
53 Array element not allowed for SELECT CASE expression

IB Statements/move

2017-11-10T16:17:17Z

Barb:

'''MOVE statement'''

'''Syntax:''' MOVE (string-argument-1, string-argument-2, starting-position, length)

'''Discussion:''' The MOVE statement moves a specified number of characters from one string into another string, starting at a specified location in the second string.

String-argument-1 may be a string constant, a single element string variable, a string array element, a string expression or a string function.

String-argument-2 must be a string variable.

The starting position and length are numeric values. They may be numeric constants or single element numeric variables. The starting position is the position in the second string argument into which the characters from the first string argument are to be moved. The length is the number of characters to be moved.

'''Example:''' MOVE(A$,B$,2,3)

If A$ = "ABCDEFG" and B$ = "123456789", after the move operation, A$ will be "ABCDEFG" and B$ will be "1ABC56789".

Virtual Dongle

2017-09-20T16:17:05Z

Barb: /* Comet Security Server Virtual Dongle Installation */

== Comet Security Server Virtual Dongle Installation ==

The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:

*A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [http://www.signature.net/download/End%20User%20License%20Agreement.pdf]

*You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
*The Comet Security Server must have a reliable internet connection. If you use Internet Security Software you'll need to set it up to allow 2-way traffic with dongle.signature.net (to port 80) and signature.net (to port 8080). Be aware that your use of a proxy server may interfere with this communication.
*The Comet Security Server must be running as a service and have '''administrator privileges'''.
*A Virtual Dongle may be associated with one and only one computer. Once installed you may not move it to another computer.

 If you are replacing an existing USB or parallel dongle:

*Install Server Products vsn 16 or higher on your server and make sure all is well using the existing dongle.
*Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
*Stop the Comet Services then remove the old dongle.
*Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''
*Return the old dongle to Signature Systems so that the permanent certificate can be issued.

 If you are installing a new system:

*Make sure your internet connection is working on the server where the Comet Services will be installed.
*If you haven't already done so, we recommend you install the Microsoft Redistributables Package. Some of the .NET framework files are used by the Security Server. You can download vcredist_x86.exe here [http://www.signature.net/download/MailBoxes/]
*Create the Comet Services folder.
*Put the DRB.txt file into that folder.
*Install Server Products vsn 16 or higher on your server. When it asks for dongle type, choose USB. This is because the Security Server will attempt to find a USB dongle first and it needs the drivers to be able to do that. When it asks if you want to restart Windows, say '''"No"'''. Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''

Virtual Dongle

2017-03-02T16:55:34Z

Barb: /* Comet Security Server Virtual Dongle Installation */

== Comet Security Server Virtual Dongle Installation ==

The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:

*A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [http://www.signature.net/download/End%20User%20License%20Agreement.pdf]

*You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
*The Comet Security Server must have a reliable internet connection. If you use Internet Security Software you'll need to set it up to allow 2-way traffic with dongle.signature.net (port 80) and signature.net (port 8080).
*The Comet Security Server must be running as a service and have '''administrator privileges'''.
*A Virtual Dongle may be associated with one and only one computer. Once installed you may not move it to another computer.

 If you are replacing an existing USB or parallel dongle:

*Install Server Products vsn 16 or higher on your server and make sure all is well using the existing dongle.
*Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
*Stop the Comet Services then remove the old dongle.
*Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''
*Return the old dongle to Signature Systems so that the permanent certificate can be issued.

 If you are installing a new system:

*Make sure your internet connection is working on the server where the Comet Services will be installed.
*If you haven't already done so, we recommend you install the Microsoft Redistributables Package. Some of the .NET framework files are used by the Security Server. You can download vcredist_x86.exe here [http://www.signature.net/download/MailBoxes/]
*Create the Comet Services folder.
*Put the DRB.txt file into that folder.
*Install Server Products vsn 16 or higher on your server. When it asks for dongle type, choose USB. This is because the Security Server will attempt to find a USB dongle first and it needs the drivers to be able to do that. When it asks if you want to restart Windows, say '''"No"'''. Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''

Virtual Dongle

2017-03-02T16:54:58Z

Barb: /* Comet Security Server Virtual Dongle Installation */

== Comet Security Server Virtual Dongle Installation ==

The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:

*A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [http://www.signature.net/download/End%20User%20License%20Agreement.pdf]

*You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
*The Comet Security Server must have a reliable internet connection. If you use Internet Security Software you'll need to set it up to allow 2-way traffic with dongle.signature.net (port 80) and signature.net (port 8080).
*The Comet Security Server must be running as a service and have '''administrator privileges'''.
*A Virtual Dongle may be associated with one and only one computer. Once installed you may not move it to another computer.

 If you are replacing an existing USB or parallel dongle:

*Install Server Products vsn 16 or higher on your server and make sure all is well using the existing dongle.
*Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
*Stop the Comet Services then remove the old dongle.
*Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''
*Return the old dongle to Signature Systems so that the permanent certificate can be issued.

 If you are installing a new system:

*Make sure your internet connection is working on the server where the Comet Services will be installed.
*If you haven't already done so, we recommend you install the Microsoft Redistributables Package. Some of the .NET framework files are used by the Security Server. You can download vcredist_x86.exe here [http://www.signature.net/download/MailBoxes/]
*Create the Comet Services folder.
*Put the DRB.txt file into that folder.
*Install Server Products vsn 13 or higher on your server. When it asks for dongle type, choose USB. This is because the Security Server will attempt to find a USB dongle first and it needs the drivers to be able to do that. When it asks if you want to restart Windows, say '''"No"'''. Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.'''

Subscription Benefits

2017-02-21T22:16:04Z

Barb: /* Benefits of being a Comet Subscriber */

Even if you are not a current subscriber to the Comet Software, most of your core applications will continue to work. However, Signature Systems continually improves its software and adds new features to the Comet System. These features are mainly available to current Comet Subscribers only.
=Benefits of being a Comet Subscriber=

*Entitled to all updates made to existing products during the subscription year
*Free COM license for each Comet license. This license is required for:
**CometExplorer
**(CopyFile) mnemonic through the file server. Without a COM license CopyFile is done directly with Windows calls which requires the client to have Windows access to the source and destination folders. This could require you to purchase additional Client Access Licenses from Microsoft.
**(Document=) mnemonic. This mnemonic is used by features of the email printer, the pdf printer, and DocMgr.
**The DataExpress version of the Reporter.
*Protection against the loss of Comet access because of theft or verifiable loss of the security module. We will replace the plug/usb and Comet licenses immediately, at no charge to the subscriber. Comet users who are not subscribers must rely on their business insurance to replace their system by completely repurchasing Comet at current prices. The expense and delay far outweigh the cost of the subscription.
*Priority access to the technical support staff.
*The convenience of being able to apply CometAnywhere licenses to any version of the CometAnywhere host. This can be especially useful at subscription time. When new CometAnywhere licenses are issued you may continue to run an older version of Comet on the host until it is convenient for you to install the upgrade.
*Free ODBC/mySQL licenses for each Comet license.

==These benefits expire at the end of the subscription period.==

Main Page

2017-02-10T17:07:20Z

Barb: /* Comet by Signature Systems, Inc. */

='''Comet by Signature Systems, Inc.'''=

* [[Getting Started With Comet]]

* [[Subscription Benefits]]

* [[Virtual Dongle]]

* Get your questions answered with [[FAQs]]

* [[CFILES - the replacement for DbMgr]]

* [[Comet Meetings]]

* [[Configuration and Installation]]

* [[Programming]]

* [[Comet32]]

* [[STL Containers]]

* [[Xap and Comet32]]

* [[CometAnywhere Mobile]]

* [[Products]]

* [[Utilities]]

* [[Comet Tips]]

* [http://support.signature.net/ Support - Users Forum]

* [[How to edit this Wiki]]

* '''[http://cc.signature.net/guest/adduser Request ability to edit pages on this Wiki]'''

*[[Comet And RDP]]

A hint from the old guy. The Wiki's text size is based on the browser's settings. In '''Firefox''' I set the minimum font size to 16.

Tools >> Options >> Content >> Advanced. Minimum font size.

Subscription Benefits

2016-12-13T17:57:46Z

Barb: /* Benefits of being a Comet Subscriber */

Even if you are not a current subscriber to the Comet Software, most of your core applications will continue to work. However, Signature Systems continually improves its software and adds new features to the Comet System. These features are mainly available to current Comet Subscribers only.
=Benefits of being a Comet Subscriber=

*Entitled to all updates made to existing products during the subscription year
*Free COM license for each Comet license. This license is required for:
**CometExplorer
**(CopyFile) mnemonic through the file server. Without a COM license CopyFile is done directly with Windows calls which requires the client to have Windows access to the source and destination folders. This could require you to purchase additional Client Access Licenses from Microsoft.
**(Document=) mnemonic. This mnemonic is used by features of the email printer, the pdf printer, and DocMgr.
**The DataExpress version of the Reporter.
*Protection against the loss of Comet access because of theft or verifiable loss of the security module. We will replace the plug/usb and Comet licenses immediately, at no charge to the subscriber. Comet users who are not subscribers must rely on their business insurance to replace their system by completely repurchasing Comet at current prices. The expense and delay far outweigh the cost of the subscription.
*Priority access to the technical support staff.
*The convenience of being able to apply CometAnywhere licenses to any version of the CometAnywhere host. This can be especially useful at subscription time. When new CometAnywhere licenses are issued you may continue to run an older version of Comet on the host until it is convenient for you to install the upgrade.
*Free ODBC/mySQL licenses for each Comet license.
*Free OleDbLite license for each Comet license (required for interface to Crystal Reports. Note: We can only interface to version 8.x of Crystal Reports.).

==These benefits expire at the end of the subscription period.==

FAQs

2016-10-11T15:03:43Z

Barb: /* FAQs */

= FAQs =

==Where are all the various log files?==
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Below we'll tell you where the default locations of the files are. But you can control the location of the Comet logs by creating a %COMETDATA% environment variable. This does not apply to the Comet Services log files.

Here is a list of the log files and their default locations:

'''The Comet Log''' 
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

If you can't even run Comet and you need the log, click on the "Details" button at the bottom right corner of the splash screen when you attempt to run Comet. When the log display opens up, click on File->Open log file. It will open up in your text editor.

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path. 

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

'''The CosP Log''' 
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well. 
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

'''The Comet Services Logs''' 
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder. 

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6. 

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance. 

'''The XAP Log''' 
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log. 

==Where can I find my CosW.ini file?==
If you can find your Comet.log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This is true even if you are using the %COMETDATA% environment variable. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[http://wiki.signature.net/index.php/CosW.ini_settings]] 

==What ports are used by Signature Systems software?==
You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]] 

==I'm getting an error message that CometLib couldn't be registered. What should I do?==
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try. 
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on. 
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll 

==Will the Comet Services run on a virtual server?==
Yes as long as the server is running a supported version of Windows [[http://www.signature.net/signature/techdoc/general/systreq.htm]]. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[http://wiki.signature.net/index.php/Virtual_Dongle]] 
==How can I get the latest license certificate for my security token?==
There are a couple of ways. First if you are able to run Comet you can use the SecLic utility. This requires a WinSock gateway in your configuration. If you are running Comet32, SecLic has been replaced by SecSrv. The WinSock gateway is automatically configured for you in Comet32. 
If you can't run Comet at all, you can still get the latest license. For Server versions prior to 16.00, stop the Comet Services. Erase the license.txt and any [plugnumber].txt files from your Comet Services folder. When you restart the Comet Services the Security Server will automatically connect to our server to get the license if one is not found in your folder. If you're running Comet Services 16.00 or later, it's even easier. From the Security Server console, click Edit->Update licenses. Now click the "Update Certificate" button. Your certificate will be retrieved and installed for you. 
These methods work for parallel, USB, and virtual dongles. 

==Should I run Comet16 or Comet32?==
Comet16 can only be run on 32-bit versions of Windows and it has been retired. No further work will be done on it. We recommend you run Comet32. 
If you are running a 64-bit version of Windows, Comet32 will run automatically. On 32-bit versions of Windows you can request Comet32 by including /32 on your Comet shortcut command line: c:\comet\comet.exe /pn=nodename /32 
If you want to make sure all Comet clients on the network are running Comet32, just set ForceC32 = 1 in your CosWGlob.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]] 
Other things to consider: 
Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers. 
Comet32 can run programs compiled for Comet16 and programs compiled for Comet32. 
Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows] 
Note: 64-bit CometAnywhere clients can run their Comet session from a Comet16 CA host. In an environment where factors are preventing deployment of Comet32 at this time, this is a way you can run Comet16 on computers that otherwise could only run Comet32.

==How can I tell if a program was compiled for Comet16 or Comet32?==
There are several ways.
* CometExplorer's TYPE column indicates the type of object file: C16 Program, C32 Program, or C32M Program (Comet Mobile)
* When you run a program in Comet32 a colored block on the window's status line indicates the type of program: purple for Comet16; green for Comet32
* From inside your program you can use FSTAT on an object file to determine if it was compiled for Comet16 or Comet32. Look in position 135 [[http://wiki.signature.net/index.php/IB_Statements/fstat]]
* PSTAT can also be used to check the type of a program that's currently running. Look in position 219 [[http://wiki.signature.net/index.php/IB_Statements/pstat]]
* If you attempt to run a Comet32 program in Comet16 you will get an Error 63.

==Can I use the Comet16 compiler on a 64-bit computer?==
No, you can only run the Comet16 compiler from a computer that can run Comet16. When compiling from UltraEdit, either the Comet16 compiler or the Comet32 compiler will be launched depending on the version of Comet currently running on the host computer. So, on a 32-bit computer you can compile with either the Comet16 compiler or the Comet32 compiler, but on a 64-bit computer you can only compile with the Comet32 compiler.

Getting Started With Comet

2016-08-17T18:45:29Z

Barb:

Comet is a versatile computing environment developed by Signature Systems for business and web applications running on Microsoft Windows. It includes a multi-tasking runtime component and a high-speed database engine. It can run as a standalone system, in a local area network, in a wide area network, and on the Internet. One of Comet’s notable strengths is its remote application processing, which is accomplished with CometAnywhere and/or eComet. Application programming is primarily done in Signature's Internet Basic compiled language. There is also an option to access the Comet File Server from COM-compliant languages such as Visual Basic and C++. 

'''Installation''' 
If you are running in a network environment you should install your server first. Once it is all setup, you can install your workstations. Download the Server Install Program, CometServerProductsxxxx.exe, where xxxx is the version number from http://www.signature.net/download/CometServer%20Products%20%28Windows%29/ While you may install it in whatever folder you choose, we recommend C:\Comet Services as you will see references to this folder name elsewhere in our documentation. By default the installation will setup both the Security Server (using a USB Security Token) and the File Server to run as a Windows service. Note the USB Security Token should be installed onto the server and the Comet License file placed in the C:\Comet Services folder. 

Download the Comet client software from http://signature.net/download/Comet2016/ While you may install it in whatever folder you choose, we recommend C:\Comet on your server as you will see references to this folder name elsewhere in our documentation. The clients will be setup to load the Comet executables from the server. 

Download the supporting utilities from http://signature.net/download/REL/ and http://www.signature.net/download/UTL/ Unzip the REL folder into server folder C:\Comet\REL and the UTL folder into C:\Comet\UTL. 

Comet uses a .ini file to define its configuration. You must establish this file before attempting to run Comet for the first time. You can find the layout of this file here: http://wiki.signature.net/index.php/The_SYSGEN_configuration_utility It is recommended that you keep this file in server folder C:\Comet. When you run Comet for the first time it should recognize that the .ini file needs to be processed. It will run SYSGEN. Once this runs successfully, restart Comet and you should see the default start program, QMONITOR. 

Access to particular folders and some convenience options may be specifed using the optional QMONITOR Security System. Here is a link to some documentation on how to set that up: http://www.signature.net/signature/techdoc/security/ 

'''File System and Programming''' 

While the Comet File System handles several file types, the most common data file is the keyed file. Here is some info on Comet Keyed Files: http://wiki.signature.net/index.php/Intro_to_Multi-Keyed_Files 

'''Internet Basic''' (IB) will be your primary programming language for Comet. Here's a link to a statement summary: http://signature.net/ib/stmtsum.htm In addition, several enhancements have been added to our current generation product, Comet32, including user-defined procs: http://wiki.signature.net/index.php/IB_Statements/UserDefinedProcs
IB source files may be any Comet data file type however we strongly recommend using a text file with a ".ibs" (for IB source) extension. This file type can be recognized by the recommended text editor, UltraEdit from IDM Computer Solutions http://www.ultraedit.com/ You should purchase the editor directly from IDM. After it is installed, run CometUESetup.exe to add the Comet extensions to UltraEdit. You'll find CometUESetup.exe in your Comet executables folder, C:\Comet. 

To write Windows dialog programs for Comet you'll use the optional '''Comet Windows API'''. You can download that here: http://www.signature.net/download/WinDev/ There are 2 components to this library, WDL (the API code library) and DLG (sample programs). You'll need to install Wdl1401.zip into folder C:\Comet\WDL and Dlg1401.zip into C:\Comet\DLG. There's also a third folder of sample programs for some special purpose IB instructions. For this, install DMW1402.zip into C:\Comet\DMW. 

'''Utilities''' 

'''The Report Generator''' script language can be used for quick reporting on your data. Here's a link to an introduction to its capabilites: http://signature.net/signature/techdoc/rpg/ The Report Generator programs are included in the UTL folder installed above. 

'''Comet Explorer''' provides a collection of data file management utilites: http://www.signature.net/2005/cometex.html You can run it by clicking on the "Comet Explorer" hyperlink on the QMONITOR screen or by running CometEx. 

There is also a set of older utilites accessible by clicking the '''"Utilities" hyperlink''' in QMONITOR. Note that these utilities have been replaced by Comet Explorer and may not support all the newest Comet features and file types. 

'''XAP for eComet Web Applications''' 

XAP is an optional add-on to your Comet system that provides the capability to write interactive web-based applications that have access to the Comet file system. Here's a link to a tutorial and demo applications: http://www.signature.net/ecomet/index.html 

'''mySQL''' 

Comet provides a SQL device that allows you to connect to a MySQL database (remote or local) from within an IB application. It is designed to provide a simple way to access your mySQL data for use within Comet. Here's more info on how to use this device: http://wiki.signature.net/index.php/SQL_Driver 

'''COM-compliant access to the File Server''' 

Although most all of your Comet development will be done in IB, there may be an occasion where it is more convenient to write your Comet application in another language such as Visual Basic or C++. The CometLib API provides this capability. You'll find documentation and programming examples here: http://wiki.signature.net/index.php/CometLib 

'''Links for more help''' 

The '''Site Map''' page is a good place to start a search for additional documentation http://www.signature.net/sitemap.htm . For example it's here you'll find information about the Comet PDF and Email Printers, Comet startup-options, and CometAnywhere for remote clients. 

We have also started a '''wiki''' which may provide additional help: http://wiki.signature.net/index.php/Main_Page 

And of course there's our '''Support Forum''' http://support.signature.net/ This is supported by the Signature Systems staff and members of the Comet user community. It's a great resource for getting answers to your questions.

Main Page

2016-08-16T17:47:20Z

Barb: /* Comet by Signature Systems, Inc. */

='''Comet by Signature Systems, Inc.'''=

* [[Getting Started With Comet]]

* [[Subscription Benefits]]

* Get your questions answered with [[FAQs]]

* [[CFILES - the replacement for DbMgr]]

* [[Comet Meetings]]

* [[Configuration and Installation]]

* [[Programming]]

* [[Comet32]]

* [[STL Containers]]

* [[Xap and Comet32]]

* [[CometAnywhere Mobile]]

* [[Products]]

* [[Utilities]]

* [[Comet Tips]]

* [http://support.signature.net/ Support - Users Forum]

* [[How to edit this Wiki]]

* '''[http://cc.signature.net/guest/adduser Request ability to edit pages on this Wiki]'''

*[[Comet And RDP]]

A hint from the old guy. The Wiki's text size is based on the browser's settings. In '''Firefox''' I set the minimum font size to 16.

Tools >> Options >> Content >> Advanced. Minimum font size.

FAQs

2016-08-16T17:41:53Z

Barb: /* Should I run Comet16 or Comet32? */

= FAQs =

==Where are all the various log files?==
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Below we'll tell you where the default locations of the files are. But you can control the location of the Comet logs by creating a %COMETDATA% environment variable. This does not apply to the Comet Services log files.

Here is a list of the log files and their default locations:

'''The Comet Log''' 
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

If you can't even run Comet and you need the log, click on the "Details" button at the bottom right corner of the splash screen when you attempt to run Comet. When the log display opens up, click on File->Open log file. It will open up in your text editor.

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path. 

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

'''The CosP Log''' 
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well. 
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

'''The Comet Services Logs''' 
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder. 

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6. 

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance. 

'''The XAP Log''' 
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log. 

==Where can I find my CosW.ini file?==
If you can find your Comet.log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This is true even if you are using the %COMETDATA% environment variable. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[http://wiki.signature.net/index.php/CosW.ini_settings]] 

==What ports are used by Signature Systems software?==
You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]] 

==I'm getting an error message that CometLib couldn't be registered. What should I do?==
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try. 
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on. 
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll 

==Will the Comet Services run on a virtual server?==
Yes as long as the server is running a supported version of Windows [[http://www.signature.net/signature/techdoc/general/systreq.htm]]. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[http://wiki.signature.net/index.php/Virtual_Dongle]] 
==How can I get the latest license certificate for my security token?==
There are a couple of ways. First if you are able to run Comet you can use the SecLic utility. This requires a WinSock gateway in your configuration. If you are running Comet32, SecLic has been replaced by SecSrv. The WinSock gateway is automatically configured for you in Comet32. 
If you can't run Comet at all, you can still get the latest license. For Server versions prior to 16.00, stop the Comet Services. Erase the license.txt and any [plugnumber].txt files from your Comet Services folder. When you restart the Comet Services the Security Server will automatically connect to our server to get the license if one is not found in your folder. If you're running Comet Services 16.00 or later, it's even easier. From the Security Server console, click Edit->Update licenses. Now click the "Update Certificate" button. Your certificate will be retrieved and installed for you. 
These methods work for parallel, USB, and virtual dongles. 

==Should I run Comet16 or Comet32?==
Comet16 can only be run on 32-bit versions of Windows and it has been retired. No further work will be done on it. We recommend you run Comet32. 
If you are running a 64-bit version of Windows, Comet32 will run automatically. On 32-bit versions of Windows you can request Comet32 by including /32 on your Comet shortcut command line: c:\comet\comet.exe /pn=nodename /32 
If you want to make sure all Comet clients on the network are running Comet32, just set ForceC32 = 1 in your CosWGlob.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]] 
Other things to consider: 
Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers. 
Comet32 can run programs compiled for Comet16 and programs compiled for Comet32. 
Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows] 
Note: 64-bit CometAnywhere clients can run their Comet session from a Comet16 CA host. In an environment where factors are preventing deployment of Comet32 at this time, this is a way you can run Comet16 on computers that otherwise could only run Comet32.

==How can I tell if a program was compiled for Comet16 or Comet32?==
There are several ways.
* CometExplorer's TYPE column indicates the type of object file: C16 Program, C32 Program, or C32M Program (Comet Mobile)
* When you run a program in Comet32 a colored block on the window's status line indicates the type of program: purple for Comet16; green for Comet32
* From inside your program you can use FSTAT on an object file to determine if it was compiled for Comet16 or Comet32. Look in position 135 [[http://wiki.signature.net/index.php/IB_Statements/fstat]]
* PSTAT can also be used to check the type of a program that's currently running. Look in position 219 [[http://wiki.signature.net/index.php/IB_Statements/pstat]]
* If you attempt to run a Comet32 program in Comet16 you will get an Error 63.

FAQs

2016-08-16T17:36:55Z

Barb: /* Should I run Comet16 or Comet32? */

= FAQs =

==Where are all the various log files?==
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Below we'll tell you where the default locations of the files are. But you can control the location of the Comet logs by creating a %COMETDATA% environment variable. This does not apply to the Comet Services log files.

Here is a list of the log files and their default locations:

'''The Comet Log''' 
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

If you can't even run Comet and you need the log, click on the "Details" button at the bottom right corner of the splash screen when you attempt to run Comet. When the log display opens up, click on File->Open log file. It will open up in your text editor.

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path. 

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

'''The CosP Log''' 
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well. 
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

'''The Comet Services Logs''' 
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder. 

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6. 

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance. 

'''The XAP Log''' 
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log. 

==Where can I find my CosW.ini file?==
If you can find your Comet.log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This is true even if you are using the %COMETDATA% environment variable. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[http://wiki.signature.net/index.php/CosW.ini_settings]] 

==What ports are used by Signature Systems software?==
You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]] 

==I'm getting an error message that CometLib couldn't be registered. What should I do?==
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try. 
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on. 
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll 

==Will the Comet Services run on a virtual server?==
Yes as long as the server is running a supported version of Windows [[http://www.signature.net/signature/techdoc/general/systreq.htm]]. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[http://wiki.signature.net/index.php/Virtual_Dongle]] 
==How can I get the latest license certificate for my security token?==
There are a couple of ways. First if you are able to run Comet you can use the SecLic utility. This requires a WinSock gateway in your configuration. If you are running Comet32, SecLic has been replaced by SecSrv. The WinSock gateway is automatically configured for you in Comet32. 
If you can't run Comet at all, you can still get the latest license. For Server versions prior to 16.00, stop the Comet Services. Erase the license.txt and any [plugnumber].txt files from your Comet Services folder. When you restart the Comet Services the Security Server will automatically connect to our server to get the license if one is not found in your folder. If you're running Comet Services 16.00 or later, it's even easier. From the Security Server console, click Edit->Update licenses. Now click the "Update Certificate" button. Your certificate will be retrieved and installed for you. 
These methods work for parallel, USB, and virtual dongles. 

==Should I run Comet16 or Comet32?==
Comet16 can only be run on 32-bit versions of Windows and it has been retired. No further work will be done on it. We recommend you run Comet32. 
If you are running a 64-bit version of Windows, Comet32 will run automatically. On 32-bit versions of Windows you can request Comet32 by including /32 on your Comet shortcut command line: c:\comet\comet.exe /pn=nodename /32 
Alternatively you can use the Force32 = 1 option in your CosW.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]] 
If you want to make sure all Comet clients on the network are running Comet32, just set Force32 = 1 in your CosWGlob.ini file 
Other things to consider: 
Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers. 
Comet32 can run programs compiled for Comet16 and programs compiled for Comet32. 
Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows] 
Note: 64-bit CometAnywhere clients can run their Comet session from a Comet16 CA host. In an environment where factors are preventing deployment of Comet32 at this time, this is a way you can run Comet16 on computers that otherwise could only run Comet32.

==How can I tell if a program was compiled for Comet16 or Comet32?==
There are several ways.
* CometExplorer's TYPE column indicates the type of object file: C16 Program, C32 Program, or C32M Program (Comet Mobile)
* When you run a program in Comet32 a colored block on the window's status line indicates the type of program: purple for Comet16; green for Comet32
* From inside your program you can use FSTAT on an object file to determine if it was compiled for Comet16 or Comet32. Look in position 135 [[http://wiki.signature.net/index.php/IB_Statements/fstat]]
* PSTAT can also be used to check the type of a program that's currently running. Look in position 219 [[http://wiki.signature.net/index.php/IB_Statements/pstat]]
* If you attempt to run a Comet32 program in Comet16 you will get an Error 63.

FAQs

2016-08-16T17:01:02Z

Barb: /* FAQs */

= FAQs =

==Where are all the various log files?==
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Below we'll tell you where the default locations of the files are. But you can control the location of the Comet logs by creating a %COMETDATA% environment variable. This does not apply to the Comet Services log files.

Here is a list of the log files and their default locations:

'''The Comet Log''' 
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

If you can't even run Comet and you need the log, click on the "Details" button at the bottom right corner of the splash screen when you attempt to run Comet. When the log display opens up, click on File->Open log file. It will open up in your text editor.

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path. 

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

'''The CosP Log''' 
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well. 
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

'''The Comet Services Logs''' 
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder. 

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6. 

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance. 

'''The XAP Log''' 
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log. 

==Where can I find my CosW.ini file?==
If you can find your Comet.log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This is true even if you are using the %COMETDATA% environment variable. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[http://wiki.signature.net/index.php/CosW.ini_settings]] 

==What ports are used by Signature Systems software?==
You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]] 

==I'm getting an error message that CometLib couldn't be registered. What should I do?==
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try. 
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on. 
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll 

==Will the Comet Services run on a virtual server?==
Yes as long as the server is running a supported version of Windows [[http://www.signature.net/signature/techdoc/general/systreq.htm]]. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[http://wiki.signature.net/index.php/Virtual_Dongle]] 
==How can I get the latest license certificate for my security token?==
There are a couple of ways. First if you are able to run Comet you can use the SecLic utility. This requires a WinSock gateway in your configuration. If you are running Comet32, SecLic has been replaced by SecSrv. The WinSock gateway is automatically configured for you in Comet32. 
If you can't run Comet at all, you can still get the latest license. For Server versions prior to 16.00, stop the Comet Services. Erase the license.txt and any [plugnumber].txt files from your Comet Services folder. When you restart the Comet Services the Security Server will automatically connect to our server to get the license if one is not found in your folder. If you're running Comet Services 16.00 or later, it's even easier. From the Security Server console, click Edit->Update licenses. Now click the "Update Certificate" button. Your certificate will be retrieved and installed for you. 
These methods work for parallel, USB, and virtual dongles. 

==Should I run Comet16 or Comet32?==
Comet16 can only be run on 32-bit versions of Windows and it has been retired. No further work will be done on it. We recommend you run Comet32. 
If you are running a 64-bit version of Windows, Comet32 will run automatically. On 32-bit versions of Windows you can request Comet32 by including /32 on your Comet shortcut command line: c:\comet\comet.exe /pn=nodename /32 
If you want to make sure all Comet clients on the network are running Comet32, instead of /32 on each client set Force32 = 1 in your CosWGlob.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]] 
Other things to consider: 
Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers. 
Comet32 can run programs compiled for Comet16 and programs compiled for Comet32. 
Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows] 
Note: 64-bit CometAnywhere clients can run their Comet session from a Comet16 CA host. In an environment where factors are preventing deployment of Comet32 at this time, this is a way you can run Comet16 on computers that otherwise could only run Comet32.

==How can I tell if a program was compiled for Comet16 or Comet32?==
There are several ways.
* CometExplorer's TYPE column indicates the type of object file: C16 Program, C32 Program, or C32M Program (Comet Mobile)
* When you run a program in Comet32 a colored block on the window's status line indicates the type of program: purple for Comet16; green for Comet32
* From inside your program you can use FSTAT on an object file to determine if it was compiled for Comet16 or Comet32. Look in position 135 [[http://wiki.signature.net/index.php/IB_Statements/fstat]]
* PSTAT can also be used to check the type of a program that's currently running. Look in position 219 [[http://wiki.signature.net/index.php/IB_Statements/pstat]]
* If you attempt to run a Comet32 program in Comet16 you will get an Error 63.

FAQs

2016-08-16T16:50:57Z

Barb: /* Should I run Comet16 or Comet32? */

= FAQs =

==Where are all the various log files?==
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Below we'll tell you where the default locations of the files are. But you can control the location of the Comet logs by creating a %COMETDATA% environment variable. This does not apply to the Comet Services log files.

Here is a list of the log files and their default locations:

'''The Comet Log''' 
Normally the easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).

If you can't even run Comet and you need the log, click on the "Details" button at the bottom right corner of the splash screen when you attempt to run Comet. When the log display opens up, click on File->Open log file. It will open up in your text editor.

Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path. 

If you are using the /log command line argument on your Comet shortcut then the Comet log will be in the user's temp folder (%temp%). It'll be called [profile].log, where [profile] is the Comet profile name matching the /PN= command line argument.

'''The CosP Log''' 
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In some error situations you will see a message to find additional information in CosPErr.log. Follow the path in the error message to retrieve that file as well. 
In order to get the printing logs you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.

'''The Comet Services Logs''' 
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder. 

The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6. 

The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. (If the dialog is disabled, you'll need to restart the console using "Run as administrator".) Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance. 

'''The XAP Log''' 
An XAP log is only generated if you have a LOGFILE statement in your #XAP file. The LOGFILE specifies where to find the log. 

==Where can I find my CosW.ini file?==
If you can find your Comet.log file, finding CosW.ini is really easy. Navigate one folder up from the folder containing the Comet.log file. You'll find CosW.ini there. This is true even if you are using the %COMETDATA% environment variable. This file contains important settings for how your Comet session and printing will be handled. You can find out about those settings here [[http://wiki.signature.net/index.php/CosW.ini_settings]] 

==What ports are used by Signature Systems software?==
You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]] 

==I'm getting an error message that CometLib couldn't be registered. What should I do?==
The CometLib dll should register automatically when you start Comet. If not, there are a couple of things to try. 
First, right-click your Comet shortcut and select "Run as administrator". If CometLib registers successfully, you can run Comet normally from now on. 
If that was unsuccessful then you can try to register it manually. It needs to be registered for the user's temp folder. To do that, get to the Windows command prompt by running cmd.exe. Change to the temp folder by typing cd %temp%. Now you can register CometLib by typing regsvr32 cometlib.dll 

==Will the Comet Services run on a virtual server?==
Yes as long as the server is running a supported version of Windows [[http://www.signature.net/signature/techdoc/general/systreq.htm]]. You will probably want to consider using a virtual dongle for your Comet security. Here's a link to info about the virtual dongle: [[http://wiki.signature.net/index.php/Virtual_Dongle]] 
==How can I get the latest license certificate for my security token?==
There are a couple of ways. First if you are able to run Comet you can use the SecLic utility. This requires a WinSock gateway in your configuration. If you are running Comet32, SecLic has been replaced by SecSrv. The WinSock gateway is automatically configured for you in Comet32. 
If you can't run Comet at all, you can still get the latest license. For Server versions prior to 16.00, stop the Comet Services. Erase the license.txt and any [plugnumber].txt files from your Comet Services folder. When you restart the Comet Services the Security Server will automatically connect to our server to get the license if one is not found in your folder. If you're running Comet Services 16.00 or later, it's even easier. From the Security Server console, click Edit->Update licenses. Now click the "Update Certificate" button. Your certificate will be retrieved and installed for you. 
These methods work for parallel, USB, and virtual dongles. 

==Should I run Comet16 or Comet32?==
Comet16 can only be run on 32-bit versions of Windows and it has been retired. No further work will be done on it. We recommend you run Comet32. 
If you are running a 64-bit version of Windows, Comet32 will run automatically. On 32-bit versions of Windows you can request Comet32 by including /32 on your Comet shortcut command line: c:\comet\comet.exe /pn=nodename /32 
If you want to make sure all Comet clients on the network are running Comet32, instead of /32 on each client set Force32 = 1 in your CosWGlob.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]] 
Other things to consider: 
Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers. 
Comet32 can run programs compiled for Comet16 and programs compiled for Comet32. 
Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows] 
Note: 64-bit CometAnywhere clients can run their Comet session from a Comet16 CA host. In an environment where factors are preventing deployment of Comet32 at this time, this is a way you can run Comet16 on computers that otherwise could only run Comet32.