ini error (AREV Specific)
At 25 NOV 2003 10:32:27AM Janice Preston wrote:
One workstation, 2000 Pro, service pack 2, Instead of getting the normal opening screen showing the company name, this workstation gets The Advanced Revelation Address then an errorB238 'Error opening or reading from .INI file "COLO" when logging in.
All other workstations are 98 and do not have the problem. They have the All -Network-Driver 1.50 and the NT/2000 Service. All files=200 and they have REVPARAM in each subdirectory. If anyone can offer a suggestion as to what on this workstation could be causing the problem it would be appreciated. To my knowledge no other clients with a Windows 2000 workstation have had a similar problem.
Thank you
Janice Preston
At 25 NOV 2003 10:53AM Matt Sorrell wrote:
Janice,
There is an environment varialbe "AREV" that controls which INI file it looks for. I would look in the system environment variables and make sure that this is set appropriately. If you are not using custom INI files, then I would not have this set at all. My guess is that it is trying to find COLOR.INI, or some variant thereof, but that the environment variable on the system is set wrong.
At 25 NOV 2003 02:04PM Janice Preston wrote:
Thanks Matt: Yes, it is looking for the color_us.ini but as this workstation is using the same batch file as all the other workstations I don't see how the environment variables can be incorrect for one and not for all. Unless I am misunderstanding your suggestions.
Janice
At 26 NOV 2003 07:29AM Don Miller - C3 Inc. wrote:
Do you have enough memory space available for the MS-DOS environment. From your original post, it looks as though the environment string is corrupted or truncated. Is the PIF file for this station the same as the others?
Don M.
At 26 NOV 2003 03:09PM Gerald Lovel wrote:
Janice,
I encounter this problem frequently with Win 2000. If the AREV application is started through a batch file, and the AREV.BAT file includes a statement such as SET AREV=XX_USER.INI to establish the .INI file to use, then Win 2000 does NOT add the string to the environment. Consequently, AREV cannot determine what .INI to use, so you get the error.
Create a custom CONFIG.NT (or is it AUTOEXEC.NT?) for the application's session, and include the environment setting command there, and the problem will go away.
Gerald