In article <1577.2169-28095-113804108-1170718413@seznam.cz>, =?us-ascii?Q?charlie=20chernohorsky?= <endlessoblivion@seznam.cz> writes:
ok, so: start fractint, pick any disk video mode (e.g. 320x200), let it render, wait for completion, then go to the <v> screen, change 320 to 32, submit it -> crash
This is a memory bug that is present in the original fractint, but just doesn't cause a crash there. It simply scribbles over memory it shouldn't. If you run the DOS fracting with debugflag=10000 and use 32x200 for a disk video size, you'll get lots of "out of bounds" messages. Once again I've reproduced the original DOS bug in the Win32 port... At the moment, I'm not sure how to fix this because I haven't spent time reverse engineering the disk video support to know where the bug is in that code. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>