Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: videofx on March 25, 2013, 03:56:59 PM
-
I have a Picasso IV in my 4000T. If I boot from the Install WB 3.1 floppy video from the Picasso IV is fine, When I boot from the Workbench 3.1 floppy my monitor displays out of range and no video. So for testing I have my 1084 monitor connected to the standard 23 pin video connector and video is displayed perfectly. So why can the install disk work and not workbench? I have tried all the different jumper settings on the Picasso IV and no change.
Thanks!
-
I have a Picasso IV in my 4000T. If I boot from the Install WB 3.1 floppy video from the Picasso IV is fine, When I boot from the Workbench 3.1 floppy my monitor displays out of range and no video. So for testing I have my 1084 monitor connected to the standard 23 pin video connector and video is displayed perfectly. So why can the install disk work and not workbench? I have tried all the different jumper settings on the Picasso IV and no change.
I wouldn't expect the Picasso to be outputting anything at all from a standard install or workbench floppy disk.
If it's just the AGA going through the flicker fixer on the Picasso then I imagine your workbench disk has a different monitor or mode selected than the install disk.
-
Make sure you have the latest (7.4) update flashed:
http://www.sophisticated-development.de/software/index.php?thisfile=.//P-IV§ion=P-IV
It also wouldn't hurt to reset the scandoubler settings in the PIV bootmenu.
-
I agree but can I fix it?
-
Thats the million dollar question. How to reset the flickerfixer settings. When I boot with left shift I get into the Picasso IV but there is nothing to set for my monitor only reset to defaults which has no effect.
-
Odd. Mine all did the same thing (signal out of range/no flifi output at times) but that ended with the 7.4 update. Only other thing I can thing of is to delete the PAL/NTSC modes with PicassoModeTNG (they should then show back up with default settings after a reboot), and IIRC there's a little something funky in the bootmenu, you might have two switch back and forth between the scandoubler settings before it will actually let you save (sorry I can't be more specific, it's been a while since I tinkered with the bootmenu).
-
The FliFi changes to default 50 Hz and back to the programmed setting in early startup by pressing afair.