Posted by Robert G Laurin on October 14, 2004 at 08:27:56:
More than once the topic of maintaining the COSW.INI file has been brought up on this forum.
Again, this morning I'm hit with a problem regarding the lack of accessibility of the COSW.INI.
On ALL of our workstations we have a customized section in COSW.INI called [OemToAnsi] that contains the translation table of extended characters (above 128) to allow the use of french accents. This is to retain compatibility with our 12+ years old huge database and is compounded with the fact that we are still using DOS based utility for some of our operations.
So everytime we set a new station, we have to run a little batch file that appends the customized portion of COSW.INI. But this morning as I was working remotely, I noticed that the station I was using did NOT have the [OemToAnsi] section in the COSW.INI thus preventing me to properly edit some data that was using french accents. I verified the Qtilities and found nothing to allow me the transfer the customized COSW.INI from our server.
So I found myself with no method of updating my local COSW.INI.
If there would be tools to update/maintain remotely the COSW.INI I could have fixed this problem easily. I could even have the QSTARTX verify the client's COSW.INI for the missing section.
The ability to update/maintain the COSW.INI would be very helpfull. It could also be used to add the Maximum Remote Sessions (MaxRemSessions?) on the guests machine. They are guest after all, so the host should have the authority to maintain the COSW.INI.