31
Software / Re: whats the deal with OS9 and BW/16color modes?
« Last post by goodoldmacs on Yesterday at 11:13:02 AM » maybe i should have been more specific:
there are a fair number of games made for OS7 that won't work in OS9 on a standard GeForce MX 20, because when you try to run them they say in an error, "please set to 16 colors mode and try again"...but in the monitors panel, there's no option.
so that was the problem i was trying to understand if there is some solution.
anyway your explanation makes sense, it's just...ok so a program requires black and white mode, a specific resolution, and a framebuffer address....why is that impossible to work around after 20+ years of OS9/OS10?
also there are some programs that run in 16 colors, lower resolution, yet you can use these on OS9. they just run in a typical finder window in the middle of the screen.
i'm sure some programs do have advanced frame codes but isn't it also possible that some are just simply programmed to get the user to switch to 16 color mode not because it is technically required but just because...no real reason? except maybe it caused the game to run better at the time it was released?
like for example, classic 16 color sim city has this lock, but there is nothing so advanced or particular about its graphics.
so yes the point i was making is surely someone must have figured a workaround? either an extension that adds a framebuffer emulation like you say, or maybe a method using resedit to simply remove the check? after all, if it simply didnt have the check run at the beginning, then tried to run the game anyway, what's the worst that could happen? a crash and restart? at least then there would be a chance to play it.
there are a fair number of games made for OS7 that won't work in OS9 on a standard GeForce MX 20, because when you try to run them they say in an error, "please set to 16 colors mode and try again"...but in the monitors panel, there's no option.
so that was the problem i was trying to understand if there is some solution.
anyway your explanation makes sense, it's just...ok so a program requires black and white mode, a specific resolution, and a framebuffer address....why is that impossible to work around after 20+ years of OS9/OS10?
also there are some programs that run in 16 colors, lower resolution, yet you can use these on OS9. they just run in a typical finder window in the middle of the screen.
i'm sure some programs do have advanced frame codes but isn't it also possible that some are just simply programmed to get the user to switch to 16 color mode not because it is technically required but just because...no real reason? except maybe it caused the game to run better at the time it was released?
like for example, classic 16 color sim city has this lock, but there is nothing so advanced or particular about its graphics.
so yes the point i was making is surely someone must have figured a workaround? either an extension that adds a framebuffer emulation like you say, or maybe a method using resedit to simply remove the check? after all, if it simply didnt have the check run at the beginning, then tried to run the game anyway, what's the worst that could happen? a crash and restart? at least then there would be a chance to play it.