Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: LordSpunky on June 18, 2011, 11:51:39 PM
-
So I've gotten around a few problems and I thought I would download and install the Picasso IV drivers from Aminet........I skipped through the install like I would any other program, even the bit when it said "Disable other drivers" and I pressed the "Whatever, get on with it" button and guess what? Now it doesn't work! Er.....so is there anyway to get into Workbench and see what is going on? I can't read the CF card on my Mac.....
Any help would be great, I am stuck without and pulling my hair out.
Regards and thanks for possible advice.
-
Use the Early Startup Menu by pressing both mouse buttons when booting and select "Boot with no startup sequence".
That will get you to a CLI prompt.
From there you can either manually check your Monitors directory under devs to see if you have anything other than the PIV monitor drivers or use "run :nil> LoadWB" (without quotes).
That will give you a basic Workbench with no drivers loaded and it's behind the CLI shell.
If not, just copy over your monitor drivers that work with your monitor, possibly PAL, from your Storage floppy.
Delete the PIV monitor driver in that DEVS/Monitors directory.
Reboot and you should at least get an error you can see and will be able to see your Workbench.
-
@wlemonds Thanks, that is much appreciated ! At least I can see Workbench now......although the command didn't work?
I typed in run :nil> LoadWB and it came up unknown command, so I thought I'll try simply, LoadWB and it did load.
In Devs: Monitors was the PicassoIV driver only, I double clicked it, black screen.
So back in I went and removed it. Reboot, working, then I copied across the Pal driver from Storage for a minute.
Is this a common problem? How do I get the Picasso drivers working any ideas?
I've just plugged back in the original owners HDD. In the Monitors folder is four! - HTSC, PAL, P4_Flickerfixer & PicassoIV........do I require them all? Tried putting them all in same problem.......also just uninstalled and reinstalled PicassoIV drivers......same problem, the only problem I can think is the scan rate of my monitor. It asks what it is, but I don't know, it selects 31kHz so I choose that, but I can't find any information regarding my monitor - Citizen Pro CM 14i [MultiScan]. Could that cause it?
-
or use "run :nil> LoadWB" (without quotes).
The correct command is:
run >nil: LoadWB
Drugs r bad. mmmkay? :D
-
If you install the Picasso96 package from Aminet it will do all the monitor stuff for you. After that you run the included Picasso tool to define your monitor's capabilities and you're all set.
-
If you install the Picasso96 package from Aminet it will do all the monitor stuff for you. After that you run the included Picasso tool to define your monitor's capabilities and you're all set.
I did install the package from Aminet, and followed the instructions this time. The only driver in Devs/Monitors was PicassoIV.
When the Amiga is turned on it loads into workbench and I have IDEFix installed, this loads and then the monitor goes black, that is all it does.
When I get into Workbench, and remove the PicassoIV file from Monitors the Amiga will load into Workbench. I'm not sure where the Picasso Tool is? There is Picasso96Mode in Prefs almost everything is greyed out.
-
Try this http://lilliput.amiga-projects.net/Picasso96.htm
-
When I get into Workbench, and remove the PicassoIV file from Monitors the Amiga will load into Workbench. I'm not sure where the Picasso Tool is? There is Picasso96Mode in Prefs almost everything is greyed out.
Village Tronic Soft & Manuals (http://www.sophisticated-development.de/software/index.php)
Give this link a chance :biglaugh:
-
Reading the docs might help. And keep the PAL or NTSC driver in Monitors. You need a working screen to do the necessary tricks to get Picasso modes to work - nothing works until you use the attach settings (to board xx) drop down menu in Picasso96mode if your board hasn't been recognized as intended by the installer.
-
I will be checking this out when I get five minutes, but last time I looked in Picasso96Mode the card was reconised on a list but wasn't on the drop down menu. I will check that though, and make sure NTSC and PAL monitor drivers are kept, I tried the docs I could only find revision notes
-
This might give something: boot via early startup without startup-sequence to workbench like written up there. Go to env: and delete screenmode.prefs which may have a Picasso mode as default which your monitor doesn't want to show. Then execute s:startup-sequence and you get your whole system running on PAL/NTSC screen. Go to screenmode and look if there are Picasso modes besides the PAL/NTSC ones. If there aren't any, go to Devs:Monitors and double click the PicassoIV monitor file. Look at screenmode again.
-
@Zipper: +1
Following Zipper's advice will get you to a point where you can see if the board is recognized while resetting your system to a useable state.
If you can see screen modes for the Picasso, DON'T USE THEM YET! It very well could be your monitor is unable to handle whatever the settings are and that is what the issue is. If there was an incorrect value put in, it can permanently damage your monitor.
If you successfully got this far and now have the fear of God in you, the best thing to do is find the specs. for your monitor. With these in hand, you can check to make sure the "monitor" modes you have to choose from will work; kinda work; not work at all; make you monitor go up in a mushroom cloud and then choose accordingly.
If you choose a setting that will cause the latter, please have a camera setup for all to enjoy. :roflmao:
On a more serious note, you NEED to find where the Picasso tools are located. They will help you fine tune your monitor modes as well as test them in a way that will not harm your monitor (as long as you don't do it over and over again). They really are the central nervous system for the board and how it is used.
-
I'll try this tonight if I'm not called out. The problem is I can't find any information about my monitor.....now I have the option of a more modern Sony multisync 17" but I need to pick it up from my mums. Got the part number somewhere........
-
Thanks for the help chaps - here is the update.
As stated before Google returns no results on my monitor. Citizen Pro CM 14i. The previous owner (who had not used it for many years) seemed to recall and rate of 30 / 31, it is installed to 31.
When typing in env: into shell I got no results, however I did get into Workbench and check the screenmode, no Picasso, so I double clicked the file in Monitors and instantly got a blank screen. I've been through the user guide and checked that all the required files are in the right places, at it seems there is 3 ways to config the card, one is 96mode and the other two seem to be editing files?........it has to be some setting as it all worked before on the old installation, I assume there would be no difference going from WB3.0 to 3.1?
-
If you install the Picasso96 package from Aminet it will do all the monitor stuff for you. After that you run the included Picasso tool to define your monitor's capabilities and you're all set.
@Mousehouse - please can you confirm the Picasso tool and where the installation puts it? Is it Picasso96Mode in Prefs? I can't find anything else.....
....additionally without the driver in Monitors the Picasso Debug states Picasso isn't running. I've just installed MUI because I tried to run a program called PVS and it was missing a file, I played about and still the same!
However I found this pic of the About screen from the old system not sure if it helps
-
Will connect and boot up the old lady this weekend... if your screen goes blank after starting the monitor then probably the Picasso is sending at an unsupported frequency, you need to use the mode tool to configure the card for this.
Do you have another monitor option available? Like a small TFT used for a desktop PC? I struggled with a crappy old monitor as well, and my $90 Acer TFT worked without too much hassle.
edit:
The screenshot shows CyberGraphX installed, the menu bar shows P96. Is this of your system or something you found online?
-
The screen shot is my A4000. But old install of 3.0
-
Just to clarify. The screen shot is NOT from your current setup in any way shape or form correct? Meaning, this picture is from a completely different install of the OS and what you are running now is from a fresh install on a wiped hard drive/ partition correct? I ask because things can get extremely odd if you try to run both CGX and P96 at the same time.
I really wish I still had my system with the Picasso IV in it because I can't for the life of me remember where the screen editor is put. I know it is in its own folder within the core AOS folders.
Example: "PREFS" folder -> "Picasso" folder -> Picasso programs.
Wait. You said you were looking at your screen and when you clicked on the Picasso Icon in "MONITORS" everything went black right? Does it flicker first or does it immediately go black?
Do you have your monitor hooked up to the standard video out on the A4000 via a converter or to the Picasso pass-through/flicker fixer? I don't want to offend you with such a simple question, but it sounds like it is working as far as immediately changing over to the other monitor.
And are there any indicator lights on the front of the monitor that blink or do otherwise when the monitor isn't getting a signal? Some even display a message of "NO SIGNAL" or something like that.
-
I'm never offended by simple questions, I am re-learning and really annoyed with this problem. Yes the picture is of the old setup, made by the old owner. And the monitor is connected directly to the Picasso card output. With PicassoIV in the Monitor folder you can view the Amiga loading (I have AExplorer in startup and you see that load and IDE Fixer) just before you get the Workbench desktop the monitor screen goes black and the green power indication flickers. When there is no PicassoIV in Monitors the Amiga loads as normal, but no Picasso in Screen mode, drop PicassoIV back in monitors and double click goes black. I do have a modern TFT, when just plugged in there is no picture and screen flickers black / grey lines. I would have to check what the TFT can handle.
Another thought is to plug in the old hard drive with orignal setup and see what settings are.
And this is my only spare monitor - Emprex LM-1904 (http://www.emprex.com/02_products_02.php?id=163)
-
Right well I have done some more playing and it still doesn't work.
I put in the original owners hard drive and had a look around, it doesn't use Picasso96Mode but Picasso TNG which was different there were some different .library files that I copied over. Then I downloaded nicholas's link which gives a more upto date Picasso96....low and behold it also contains TNG!
Uninstalled Picasso96, reinstalled Picasso96, same. Then I went a got my spare CRT (Sony Trinitron Multiscan 200ES). Works perfect on old setup, same results on new setup. I'm even thinking about filming this for all to see......I am so p*^sed off with this now!
-
This might give something: boot via early startup without startup-sequence to workbench like written up there. Go to env: and delete screenmode.prefs which may have a Picasso mode as default which your monitor doesn't want to show. Then execute s:startup-sequence and you get your whole system running on PAL/NTSC screen. Go to screenmode and look if there are Picasso modes besides the PAL/NTSC ones. If there aren't any, go to Devs:Monitors and double click the PicassoIV monitor file. Look at screenmode again.
Hi I am finding it hard to find Env and delete screenmode.prefs.....any ideas?
-
Hi I am finding it hard to find Env and delete screenmode.prefs.....any ideas?
If you are trying to delete with the "No Startup Sequence" method env: isn't assigned so you'll have to manually go to it.
In CLI, goto "sys : prefs/env-archive/sys" without quotes and remove the spaces between the colon.
Type DIR or LIST and you should see screenmode.prefs, either delete or rename it.
-
I'll give that a go....also got this which shows the start up jobby
(http://youtu.be/_1rolZrqCPI)http://youtu.be/_1rolZrqCPI
-
For everyone, I have fixed this problem - I don't know how to fix it for other people but it has worked for me.
I went through and copied every Picasso96 installed file from the previous owners setup and over wrote them on my new OS3.1 setup and it has worked!