Custom Query (80 matches)

It is known that there are two system encodings in Windows: the ANSI encoding (used all over in the GUI APIs) and the OEM encoding (used for compatibility with DOS applications and in particular in the command line sessions for file and console output). For God knows what reasons, in some locales, these two encodings differ. For example, in .ru, we have cp1251 (windows-1251) for ANSI and IBM-866 for OEM (this is the same as in OS/2 and MS/PC DOS).

I found out that at least one UI function, MessageBox?(), expects two encodings at the same time for two its different arguments: the window title bar should be in IBM866 while the message text itself -- in windows-1251. I guess this happened to be like that because message text is drawn by Odin on its own (and hence the ANSI encoding is expected) while the title bar is drawn by the system (using the OS/2 encoding which is the same as OEM). This is completely wrong and needs to be fixed. According to Win32 docs, ANSI should be supplied in both cases.

e:\svn-code\odin32[0]svn up . svn: Can't check path 'testapp/encodings/.cmd': SYS0123: A file name or volume label contains an incorrect character. It does not show from the copy and paste but between the / after encodings and the .cmd there are four arrows that point to the right. From the web interface I see the file as: тЅст.cmd

e:\svn-code\odin32[1]help sys0123

SYS0123: A file name or volume label contains an incorrect character.

EXPLANATION: The system does not accept characters displayed using the keyboard combination ALT plus 0-32 or the following characters:

\ / [ ] : | < > + ; = . ? * "

ACTION: Correct the file name or volume label and retry the command.

Problem is, KEIL does not work cause it can not read it's tools.ini file. Hermann Ulrichskoetter found out where this fails and made a build about 3 years ago with this one line commented out. For me his build worked for years now. But we do not understand if there are any problems with this change.

Here is the original post from Herman from 18.11.2007 at the odin.user group

This weekend I had some time to get deeper into this problem. I found that at line 725 in src\kernel32\mmap.cpp

(fdwAccess & FILE_MAP_READ) && !(mProtFlags & (PAGE_READWRITE|PAGE_READONLY))

becomes true and generates an error because fdwAccess==FILE_MAP_READ and mProtFlags==PAGE_WRITECOPY.

I just commented that line and now TOOLS.INI can be read without problems. I have no idea wether this modification can make problems because I don't understand what mProtFlags==PAGE_WRITECOPY means :-(

Anyway, now I can run KEIL 6.5 with PEC. That is not a problem because I don't use the IDE.

Hermann