Posted by Jim Guerber on July 14, 2008 at 15:57:34:
In Reply to: cosw.ini Location posted by Mike Saunders on July 14, 2008 at 14:07:48:
I am also attempting to setup Comet on a vista workstation and here is what I have found.
The workstation is an HP Pavilion tx 2000 laptop purchased from Costco. It is using the pre-installed vista home edition with no modifications.
I am running comet.exe (C2008 Build 392). I have 2 vista users configured, one is admin and the other is a just a user (Jim). That does not matter since no matter which user runs, it does not have admin rights unless "run as administrator" is selected (right click).
1. If I set up Comet to launch from a network server, Comet.exe copies all executables to the temp dir correctly, but windows always asks permission to run before launching. (The Temp dir is "c:\users\Jim\appdata\local\temp").
2. If I set up the workstation so that all executables are on my C: drive, Windows does not ask permission to run. Perhaps a script could be used to run comet that copies all files from the network dir to the c:\comet\ directory and then launch comet.exe from there. I bet this would cause the UAC to accept the execution without presenting the dialog. In fact, I don't mind that extra click too much anyway.
3. Everything works except one thing: CometLib does not get registered. To fix this, I ran a cmd prompt as administrator and then navigated to "c:\users\jim\appdata\local\temp" and ran "regsvr32 cometlib.dll", just once. From then on cometlib works.
4. I do not see a problem with COSW.INI. It is created in "c:\users\All Users\Signature Systems". So, all users share the same COSW.INI. This was an automatic configuration. I did not try to specify where cosw.ini should go.
5. The problem with COSW.INI is that the CAFILES directory (and directory aliases that get automatically created under it) is created in the user's folder, making it difficult to run comet with more that one user on the same machine. If Comet were to be run only from one user, this would not be a problem. The way around this is to edit each dir alias and specify %userprofile% instead of "c:\users\jim" for example. A program could also be written to do the appropriate SetDirAlias mnemonics to accomplish this if necessary.
Mike, I don't know why you want multiple COSW.INI files on the same machine. Dir alias issues can be fixed like I said above. Are there other settings that should be kept separate from one user to another?
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.