FAQs - Revision history

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

2020-06-10T21:10:40Z

Where are all the various log files?

← Older revision		Revision as of 21:10, 10 June 2020
Line 10:		Line 10:

	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 <b>File->Open log file</b>. It will open up in your text editor.		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 <b>File->Open log file</b>. 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.<br>		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.<br>

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

2018-09-20T21:41:08Z

How can I get the latest license certificate for my security token?

← Older revision		Revision as of 21:41, 20 September 2018
Line 64:		Line 64:
	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]]<br><br>		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]]<br><br>
	==How can I get the latest license certificate for my security token?==		==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~~.<br><br>	+	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.<br><br>
	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.<br>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.<br>		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.<br>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.<br>
	These methods work for parallel, USB, and virtual dongles.<br><br>		These methods work for parallel, USB, and virtual dongles.<br><br>

Barb: /* FAQs */

2018-09-20T19:15:00Z

FAQs

← Older revision		Revision as of 19:15, 20 September 2018
Line 34:		Line 34:
	==What ports are used by Signature Systems software?==		==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]]<br><br>		You can find a list of ports here [[http://wiki.signature.net/index.php/TCP/IP_Ports_used_by_Signature_Products]]<br><br>
		+
		+	==What options can be set in the #XAP file?==
		+
		+	CLOSE<br>
		+	The CLOSE command tells Comet to stop listening on the XAP gateway (in effect, resetting
		+	the gateway).
		+
		+	LOGFILE pathname[,cycle \| ,erase]<br>
		+	The cycle option keeps up to 7 generations of the log file.
		+
		+	LISTEN port-number<br>
		+	Specifies the port for XAP to listen on. Port 80 will be used by default.
		+
		+	USEWIN<br>
		+	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]<br>
		+	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<br>
		+	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?==		==I'm getting an error message that CometLib couldn't be registered. What should I do?==

Barb: /* FAQs */

2016-10-11T15:03:43Z

FAQs

← Older revision		Revision as of 15:03, 11 October 2016
Line 64:		Line 64:
	* 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]]		* 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.		* 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.

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

2016-08-16T17:41:53Z

Should I run Comet16 or Comet32?

← Older revision		Revision as of 17:41, 16 August 2016
Line 50:		Line 50:
	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.<br><Br>		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.<br><Br>
	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<br>		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<br>
-	~~Alternatively~~ you ~~can use~~ the ~~Force32~~ = 1 ~~option~~ in your ~~CosW~~.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]]~~<br>~~	+	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]]<br><br>
-	~~If you want to make sure all Comet clients on the network are running Comet32, just set Force32 = 1 in your CosWGlob.ini file~~ <br><br>	+
	Other things to consider:<br>		Other things to consider:<br>
	Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers.<br>		Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers.<br>

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

2016-08-16T17:36:55Z

Should I run Comet16 or Comet32?

← Older revision		Revision as of 17:36, 16 August 2016
Line 50:		Line 50:
	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.<br><Br>		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.<br><Br>
	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<br>		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<br>
-	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]]<br><br>	+	Alternatively you can use the Force32 = 1 option in your CosW.ini file [[http://wiki.signature.net/index.php/CosW.ini_settings]]<br>
		+	If you want to make sure all Comet clients on the network are running Comet32, just set Force32 = 1 in your CosWGlob.ini file <br><br>
	Other things to consider:<br>		Other things to consider:<br>
	Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers.<br>		Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers.<br>

Barb: /* FAQs */

2016-08-16T17:01:02Z

FAQs

← Older revision		Revision as of 17:01, 16 August 2016
Line 56:		Line 56:
	Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows]<br><br>		Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows]<br><br>
	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.		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.

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

2016-08-16T16:50:57Z

Should I run Comet16 or Comet32?

← Older revision		Revision as of 16:50, 16 August 2016
Line 48:		Line 48:

	==Should I run Comet16 or Comet32?==		==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.<br>	+	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.<br><Br>
	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<br>		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<br>
-	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]]<br>	+	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]]<br><br>
		+	Other things to consider:<br>
		+	Comet16 can run programs compiled for Comet16. It can also run programs compiled for Qantel computers.<br>
		+	Comet32 can run programs compiled for Comet16 and programs compiled for Comet32.<br><br>
		+	Check the Systems Requirements chart for [http://www.signature.net/signature/techdoc/general/systreq.htm Comet compatibility with the various versions of Windows]<br><br>
		+	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.

Barb: /* FAQs */

2016-08-16T16:39:19Z

FAQs

← Older revision		Revision as of 16:39, 16 August 2016
Line 46:		Line 46:
	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.<br>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.<br>		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.<br>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.<br>
	These methods work for parallel, USB, and virtual dongles.<br><br>		These methods work for parallel, USB, and virtual dongles.<br><br>
		+
		+	==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.<br>
		+	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<br>
		+	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]]<br>

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

2016-08-16T16:26:37Z

How can I get the latest license certificate for my security token?

← Older revision		Revision as of 16:26, 16 August 2016
Line 43:		Line 43:
	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]]<br><br>		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]]<br><br>
	==How can I get the latest license certificate for my security token?==		==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.<br>	+	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.<br><br>
-	If you can't run Comet at all, you can still get the latest license. ~~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.<br>	+	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.<br>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.<br>
	These methods work for parallel, USB, and virtual dongles.<br><br>		These methods work for parallel, USB, and virtual dongles.<br><br>