Custom Query (31 matches)
Results (4 - 6 of 31)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7 | fixed | Change text .ini to .cfg files | ||
| Description |
The ini format doesn't allows for spaces left from the equal char. Therefore the .ini extension should not be used for these files. Esp. the Colors.ini file needs alignment to keep readability. Applies to: colors.ini, alias.ini, objects.ini. In order not to mess up user's config it's important to change it before an official release. |
|||
| #23 | fixed | Default values were not written to NEPMD.INI | ||
| Description |
After installation of NEPMD the EPM doesn't start with NEPMD settings. In contrast, the NEPMD program object 'Standard EPM' starts. Renaming myepmd\bin\NEPMD.INI is a workaround for that. A new one is created on the next EPM start. The malfunctioning NEPMD.INI contains the entry: RegDefaults -> \NEPMD\User\MovedUserFiles while the correct temporary entry would be: Install -> \NEPMD\User\MovedUserFiles That explains why the RegDefaults? application wasn't written. It already contains (wrong) data. As a result, EPM won't start. Additionally, that temporary entry is normally only written if the install script has copied previous files to a backup directory. The backup directory exists with the files etke603.dll and copydll.cmd. Normally they were deleted afterwards. It seems as if patching etke603.dll to apply the NEPMD colors has failed at the end. |
|||
| #32 | fixed | Encoding conversion from Unicode to others | ||
| Description |
The encoding from Windows UTF-16LE to ibm-850 with recode.exe works well. But the implementation in NEPMD reverts the file in binary (BIN) mode. The converted file is pure ASCII. On closing that and loading it again, the TEXT mode is assigned. Apparently it is tried to keep the previous mode. |
|||
