Posted by Mike Saunders on July 15, 2008 at 07:49:07:
In Reply to: Re: cosw.ini Location posted by Jim Guerber on July 14, 2008 at 15:57:34:
Jim,
1) Currently all my installs have the Comet files loaded locally. I am not using any network installs. Using Vista Business SP1.
2) Cometlib not registered. Test is trying to start Comet Explorer. Error is Class not registered.
Hmm. I am seeing this on this this new Vista PC I am working on, however I have two other vistas where I swear
I did not manually register the DLL, yet Comet Explorer works. Will need to keep an eye on this.
When does Comet Register the DLL? Only once when Comet is installed? Or each time a new version is put in the TEMP dir? On the system that works, I renamed the DLL in the TEMP dir and when Comet Started, comet put a new copy in place and Comet Explorer still worked. Then with Comet running I again renamed the DLL, started Comet Explorer and got the Class not Registered message. Renamed the file correctly, Started Comet Explorer and it worked.
3) Multiple COSW.ini
Currently I was only asking for this due to the CATEMP location.
I had not yet worked with %userprofile% or SetDirAlias.
I had read forum messages that indicated different COSW.ini were allowed.
I saw in the Command Line Doc that said /INI could be used to specify ini location.
Currently all my attempts to have Comet find the cosw.ini someplace other than the default have failed.
3a) That being said... From what I see the COSW.INI allows for settings that "could" be PER USER settings. (Fonts, Colors, CATEMP, default printer).
From recent program experience, and again, being only a neophyte, I have learned that "Client" applications these days are expected to have Default (not user editable) Application Settings, user configurable application settings(that would apply to all instances of the application), and User settings(that only apply to the particular user instance). Unfortunately, these three different sets of settings are to be kept in different locations. Which is a pain.
Additionally if these applications create user "documents" then these need be be kept in yet another location.
3b) That being said... I do not see (our) Comet users making use of such complexity. I do not see systems with multiple users (other than perhaps an admin/std user) set up on them or users using roaming profiles. Generally it will be a single user system with a single user logon.
4) Just making sure.. you mentioned your COSW.ini was going into "c:\users\All Users\Signature Systems"... On Vista you are seeing the cosw.ini going into "C:\programdata\signature systems" correct?
5) If the commandline /INI is supposed to work, please specify how to use it. I tried /INI=[path] and /INI:[path]
6) I guess my current solution is to allow the standard user to create the cosw.ini, which will cause the CATEMP to point to C:\users\[std username]\appdata\local\temp\cafiles\catemp. It looks like the admin user can use this okay. (I think I got a bit twisted around yesterday and thought it was not working)
Thanks
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.