No CGX screen modes listed

[Piru]

Does anyone know what might cause this problem?

CGX had a buggy exec.library version compare (if version == 40) rather than if (version >= 40).

There are various ways to fix it: Update to the latest CGX, or if not possible (cgx3 perhaps), use the patcher included in my exec44 archive.

[Piru]

This is probably why I always seem to end up using Picasso96.

Hmm I don't quite follow. The problem is trivial to fix.

So how does this make you always use Picasso96?

[Piru]

A bug isn't always just a bug. Most of the time, a bug allows you to still use a product. But when a bug is so large that the product is defective right out of the box, kind of turns you off.

Sure. However this clearly isn't the case with CGX.

Especially when that product costs $40+. And in the past, you didn't have the access to developers like you do today. The support we get today for this stuff is incredible. Yesterday however seemed to be a different story.

Could be.

But again this wasn't the case with CGX. The fix to this problem was provided as soon as the problem was found (that is: When I wrote the exec44 patch and found out about the problem). The fix was already available for years when AmigaOS 3.9 BoingBag2 was released.

[Piru]

Thomas is right about this, with BB2 you'll need a newer cgxsystem.library if i remember correctly or CGX will not work at all with BB2.

The problem was that CGX tried to determine if the AmigaOS version is 3.0 or 3.1 prior patching the graphics.library (the graphics monitor related interfaces changed somewhat between 3.0 and 3.1). Unfortunately this check was flawed and checked explicitly against V40 (3.1). That is: Anything other than V40 (3.1) was considered AmigaOS 3.0. When BoingBag2 was introduced it included a new exec.library (V45). This threw off the OS version check of the CGX and it was unable to properly patch the graphics.library, resulting in no CGX modes available in the screenmodes list.

That is the only problem with CGX and BB2: Just a single mistake in a version check.

The problem can be worked around in at least 3 different ways:
1. Install the CGX V4 update.
2. Use the cgx44fixer from exec44 beta archive. This patch also works with CGX V3.
3. Downgrade back to exec V40 (disable exec.library via modifying the SetPatch cmdline, add SKIPROMUPDATES exec.library).

I hope this explanation is complete enough to leave no room of uncertainty. If you have any questions or think this explanation could be improved, just post a reply.