![]() |
![]() |
Articles / TULARC / PC info / ARM / | ![]() |
|
![]() |
||||
![]() |
![]() |
|||
![]() |
![]() |
|||
![]() |
||||
|
|
||||
![]() |
![]() |
|||
![]() |
10.3) Why do Windows programs give me incorrect colours in a 256 colour mode? |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
|
|
||
![]() |
||
![]() |
![]() |
![]() |
![]() |
||
![]() |
||
This article is from the comp.sys.acorn FAQ, by Paul Vigay with numerous contributions by others.
This can happen if you forgot to put a 'p' after colour descriptor in your Windows mode definition string. For example to configure the emulator to give windows a 1024x768 screen mode at 256 colours with fully programmable colours your string should look like this:-
x1024y768c256p
Note the p at the end of the line.
 
Continue to:
![]() |
|
|