Welcome to the Picasso96 FAQ!

Note: newest entries first, to give you latest information first! If your problem is not covered here, it's probably in the documentation...

Please read the documentation, too!

  1. Q: I own a PicassoII(+) and the Picasso drivers of some applications do not work with Picasso96 but worked with the original software. What is wrong?
    A: Sorry, but some drivers for the old API are really buggy, e.g. the ADPro Saver and Display modules. There is no way to make them work properly as they did not even adhere to the original Picasso API.

  2. Q: I own a PicassoII and tried to use Picasso96 with it but Picasso96 refuses to find the board. The old software works. What's wrong?
    A: Your PicassoII is probably configured for segmented mode. This mode is not supported by Picasso96. You will have to change the appropriate jumper. Note: if you run the showconfig tool from your workbench, the PicassoII must show up as two devices with the product ids 11 and 12. If it shows as id 13, it is configured for segmented mode.

  3. Q: I have strangely distorted images or text on my Merlin. What can I do about it?
    A: Try to set the "NoPlanar2ChunkyBlits=Yes" tool type in the monitor driver icon. This should help.

  4. Q: What tool types are there to configure a Picasso96 board?
    A: There are:
    If you change the tool types you will have to reboot to get the changes activated.
    All other tool types are explicitly non-documented. Do not try them or you might be in real problems. Do not even ask anyone what they are for. They are only for our internal testing.

  5. Q: What Picasso96 ENV variables are there?
    A: There are:
    These environment variables can be changed any time and will take effect immediately.
    All other environment variables are explicitly non-documented. Do not try them or you might be in real problems. Do not even ask anyone what they are for. They are only for our internal testing.

  6. Q: I think that something is not working for me. Who is the right one to mail my report to?
    A: First, are you really sure that it is a Picasso96 problem? Did you read the documentation and you did not find enough information there?
    Ok, if you are sure you want to write a mail, choose the appropriate person to send it to:

  7. Q: I keep getting random crashes or currupted memory lists. What is wrong?
    A: Do you use FastIPrefs or do you still use the original IPrefs? The original IPrefs uses a far too small stack frame and gets in deep trouble when used with the v43 picture.datatype supplied with Picasso96. I suggest you switch to FastIPrefs and tell me if that "cured" your problems.

  8. Q: ShapeShifter is awfully slow in High- and TrueColor modes, it seems to use refresh modes. What can I do about it?
    A: The Macintosh can only use direct display memory access when using one of these modes: All other modes are refresh modes! And no, we can't do anything about it! Don't even bother to ask!

  9. Q: Since Picasso96 version 1.19 my mouse sprite is scrambled on the far right portion of the screen. What can I do about it?
    A: Since version 1.19, always 64 pixel hardware sprites are being used which need more time to fetch the sprite data during horizontal retrace. Please increment the horizontal total value of affected modes and move the mode to the left until this effect no longer occures.

  10. Q: Is there no way to get DPaint to work with non-planar Picasso96 modes?
    A: All those who want to use DPaint with Picasso96 should use ModePro and tell it to "force planar" screens.

  11. Q: I have problems getting a small mode like 320x200 to work with my CyberVision 64. What can I do?
    A: The default modes might be too small for your card. Try to increase the horizontal and vertical totals by a few percent.

  12. Q: It aint much but why is my mosepointer's colors being somekind of inverted when passing over colored areas of screens in almost any depth?
    A: That's a limitation of many VGA chips. They have only two real mouse colors and one inverting "color". On the PC, normally only two colors are needed so that's ok for them.
    You'll have to paint yourself a two colored mouse sprite, switch to software sprite or live with it. Sorry!

  13. Q: I have problems using IFF pictures with FastIPrefs, WBPattern or Multiview. What can I do about it?
    A: You can improve the situation by running CPUBlit. If you want to use CPUBlit, put it in your Sys:S/Startup- Sequence before the monitors are started. The line must look like that: 'CPUBlit -a -b'.

  14. Q: I already have a settings file for CyberGraphX or the old Village system which I want to use. What can I do?
    A: The PicassoModeTNG by Olaf Barthels can load those settings.

  15. Q: Why do some screens not respond to DisplayBeep()?
    A: Because Picasso96 currently does nothing when DisplayBeep() is called for a Hi- or TrueColor screen. The reason is that on screens that are not CLUT based, the standard way to do a DisplayBeep() does not work. Some replacement will be implemented later.

  16. Q: Why do all my icons flicker when moved around on a Picasso96 screens?
    A: With Picasso96 icons are not moved beamsyncronized. The icon is first cleared out at its current position and then redrawn at the new position.
    As a matter of fact, for a short amount of time the icon is not visible. This causes the flicker unless it happens in the vertical blanking period. Currently Picasso96 moves icons without waiting to be as fast as possible.

  17. Q: Why does PhotoGenics display only a strange black-and-white screen when trying to open a HiColor screen?
    A: That's because PhotoGenics incorrectly tries to open a screen with depth=0... use a screen promotor and tell it to open with depth=16... You can download some fixes for Photogenics from the Picasso96 home page.

  18. Q: I don't like the settings supplied with Picasso96 because they do not use the bandwidth my monitor likes or I would like to get better modes. What can I do?
    A: There are two alternatives:
    1. Use Picasso96Mode and either create new modes or alter the pixel clock of the existing ones, test the modes, save and reboot.
    2. Look at the Picasso96Settings web page and look if there is one for you...

  19. Q: Why is it that I can not use TrueColor modes with the CyberVision64?
    A: The cards supported by Picasso96 have different color formats:
    Cards and their supported color formats
    CardPlanarChunkyHiColor15 HiColor16TrueColorTrueAlpha
    So, the CyberVision can not use 24 bit TrueColor modes but has 32 bit modes with an (unused) alpha channel.

  20. Q: I defined my own display modes, but some of them seem to have problems with the hardware sprite (of my Cirrus based board). It either disappears at the right side of the display or there are some strange pixels when I move the mouse sprite to the top of the screen.
    A: The mode you created does not give the VGA chip enough time to fetch the sprite data during horizontal retrace. You will have to increase the horizontal totals by a few pixels and move the display to the left. You can check this in the edit and test screens of Picasso96Mode, too.

  21. Q: Some of my pictures and images are not rendered correctly.
    A: Maybe some of your datatypes might be incompatible. We currently have tested and can advise the use of:

  22. Q: The supplied v43 picture.datatype has a smaller revision number than the CyberGraphX picture.datatype. Which one should I use with Picasso96?
    A: The picture.datatype supplied with Picasso96 is completely different to the one supplied with CyberGraphX. The Picasso96 picture.datatype works with Picasso96 and CyberGraphX, but the CyberGraphX picture.datatype works only with CyberGraphX. So, you will have to use the Picasso96 picture.datatype.

  23. Q: Why is it, that NewIcons icons are rendered incorrect when I use the option RTG?
    A: This mode is not compatible with Picasso96 before version 1.19.

  24. Q: Why is there no screen dragging with Picasso96?
    A: Hmmm, the sad thing is: VGA chips do not have the features the Amiga Copper offers. There are too many restrictions:

  25. Q: Which programs are known not to work with Picasso96?
    A: Currently, these seem to be:
    Please tell me what to add... :-\

  26. Q: Will there be support for the Retina Z2?
    A: Support for the Retina Z2 is being worked on by external programmers, but there is nothing to test yet.
    Do not send any mail asking about specific dates or beta testing offerings, you will notice when the boards are supported!

  27. Q: How can I create new resolutions for Picasso96?
    A: You'll have to use Picasso96Mode. Here is how:

  28. Q: How can I copy resolutions or modes for Picasso96?
    A: You'll have to use Picasso96Mode. Here is how:

  29. Q: How can I delete resolutions or modes for Picasso96?
    A: You'll have to use Picasso96Mode. Here is how:

  30. Q: Picasso96Mode: how can I activate or deactivate a mode or resolution?
    A: Double click the list entry.

  31. Q: Some of my old Village drivers are behaving strangely or crash. Why?
    A: We really suggest that you get rid of them. The old Village API is a pile of ... :-(
    Please use the Picasso96 drivers or try the CyberGraphX ones!

  32. Q: Some (old) documentation says, KickStart 3.1 is needed for Picasso96. Why?
    A: NEW FEATURE: from Picasso96 1.17 on, 3.0 is sufficient. We have found the differences and added the necessary code to allow full 3.0 compatibility.

  33. Q: How can I tell the version of Picasso96 I currently have?
    A: In the root directory of the archive or disk you got is a file called version. From a shell window, do "version <path>Version" or simply "type" this file. This file does not exists on the November 96 demo disk, but on all later releases.

  34. Q: I installed Picasso96, but I don't get any screen modes. What's wrong?
    A: The settings files which are currently supplied assume a PicassoIV board. If you have another one, start Picasso96Mode, select the menu "Attach setting to" and choose your board (should be the last line of the menu. If your board does not appear, the monitor file has not been started or is misconfigured (check tool types of Sys:Devs/Monitors/<YourBoardName>).

  35. Q: Why are screens with up to 16 colors so slow on fast Amigas?
    A: Because on most cards, these screens are planar. If you want to speed them up, disable the planar modes with Picasso96Mode.

  36. Q: Why is the scrolling speed of the Picasso II, Piccolo or Spectrum less than under the old Picasso, CyberGraphX or EGS software?
    A: This is because the Picasso96 software normally respects the rastport and blit masks which requires multiple blits to be performed. If you want to speed up blitting, add a tool type "IgnoreMask=Yes" in your Devs:Monitors/PicassoII, Piccolo or Spectrum icon. Be warned though that this mode may result in incorrect rendering.

If you want me to add other items, send me suggestions. I would prefer to get them "ready for cut'n'paste"... :-)
tabt, February 11th, 1997