Aciniupd Does Not Update Certain Characters Properly in .ini File (240449)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition SP4
- Microsoft Windows NT Server 4.0 Terminal Server Edition SP5
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q240449 This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location from which you downloaded the release. SYMPTOMS
When you attempt to add a non-alphanumeric character into an .ini file with the Aciniupd.exe tool, it may not work as you expect.
For example, the following sample file uses an .ini file named Test.ini and attempts to modify the [CashRegister] section of the .ini file. The problem in the example is that there is a dash (-)at the beginning of the string that needs to be changed.
Existing Line: parms=-i"c:\appl\prod\views\ini\costview"
Required Change: parms=-i"i:\views\ini\costview"
Using the following batch file, the dash does get entered, but with a space in front:
set V=" -I\"I:\views\ini\costview\"
aciniupd.exe /v /e "TEST.INI" "CashRegister" "parms" %V%%
CAUSE
Although the "\" escape character is used, it is not interpreted properly at the beginning of the string. If there is a space at the beginning of the string ("\-I\"I:\views4\ini\costview\"), Aciniupd adds the escape character as well. As used as in the above batch file, the string does get implemented, but with the space.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Major | Last Reviewed: | 10/27/2003 |
|---|
| Keywords: | kbfix kbprb KB240449 |
|---|
|