Print color bug (*solved*)
|
Print color bug (*solved*)
|
That's weird: the "system variable" core.SCREEN_ADDR is initialized with 16384, and core.SCREEN_ATTR_ADDR with 22528 respectively, and they are not modified anymore (in other words, all the instructions using these variables are read-only).
Are you sure that it's the PRINT routine? couldn't it be that a third party is corrupting that variable in some way? |
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Print color bug (*solved*) - by Darkstar - 10-03-2022, 08:18 PM
RE: Print color bug - by boriel - 10-04-2022, 06:54 AM
RE: Print color bug - by Darkstar - 10-04-2022, 09:44 AM
RE: Print color bug - by boriel - 10-04-2022, 10:53 AM
RE: Print color bug - by Darkstar - 10-05-2022, 12:44 AM
RE: Print color bug - by boriel - 10-05-2022, 07:01 AM
RE: Print color bug - by Darkstar - 10-05-2022, 07:59 AM
RE: Print color bug - by boriel - 10-11-2022, 06:15 PM
RE: Print color bug - by Darkstar - 10-11-2022, 06:57 PM
RE: Print color bug - by boriel - 10-05-2022, 10:27 AM
RE: Print color bug - by Darkstar - 10-07-2022, 01:09 AM
RE: Print color bug - by boriel - 10-07-2022, 10:53 PM
RE: Print color bug - by Darkstar - 10-08-2022, 01:36 AM
RE: Print color bug - by Darkstar - 10-08-2022, 03:11 AM
RE: Print color bug - by boriel - 10-08-2022, 08:04 AM
RE: Print color bug - by Darkstar - 10-08-2022, 08:37 AM
RE: Print color bug - by boriel - 10-09-2022, 06:30 PM
RE: Print color bug - by Darkstar - 10-09-2022, 08:27 PM
RE: Print color bug - by Darkstar - 10-10-2022, 04:20 AM
RE: Print color bug - by boriel - 01-19-2023, 10:56 PM
|
