Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: djkoelkast on May 30, 2013, 05:51:19 PM
-
I've reinstalled my A4000 because it wasn't really running ok.
Did a full 3.1 install, 3.9 upgrade, bb1, 2, 3 and 4, CyberGraphx V4 + 4.3 update.
After a lot of looking stuff up (new 68060 libraries, startup-sequence changes in bb3/4 and so on) I've got it fully working. Finally.
But when I switch to my CyberVision64 everything is distorted.
Please see attachment.
Is it broken? (the left/right mouse pre-boot menu says WORKING on everything) Or did I just do something wrong (I hope so ;) )
Thanks.
-
impossible to tell just by looking at the picture. I'd personally go for Picasso96 as imho its better. Do you have anything running in wbstart or startup/user that is new?
-
impossible to tell just by looking at the picture. I'd personally go for Picasso96 as imho its better. Do you have anything running in wbstart or startup/user that is new?
Since I'm unable to change my CyberVision into a Picasso I'll stick with this. I've had it for years, it worked for years, now I get this. This also happens when I change the Zorro slot it is in.
All WBStart items are standard items from either OS 3.9 or one of the 4 boing bags. I did not install any of them myself (yet). Just put the workbench refresh thing and the amidock away because I don't like them.
-
Picasso96 works well with CyberVision 64 of course.
-
@direktorn,
Yes it does. I use P96 on my A4000t with a Cybervision64.
Chris
-
Oh you mean like drivers? Where can I find them and how do I remove the CyberGraphx v4?
On the other hand: it did work before, but then again, that was a different installation.
Do I need these ones? http://lilliput.amiga-projects.net/Picasso96.htm
-
Ok just removed every trace of CyberGraphx, rebooted, installed Picasso from the link above.
When installing I get this error when it's 75% done:
COPYFILES: Couldn't copy file "Picasso96Mode" in line 4421.
DOS Error Type: Not enough memory for installation to continue.
Which surprises me, I have more than enough chip and fastmem available.
When skipping that part (possible when running install again and deselect it) the error comes again with another file (a .readme one).
Apart from that the installation seems to complete (when deselecting certain things), but now I can't get it booted.
It boots, don't see anything, reboots. This loops.
I'll try removing the stuff again through the emergency boot disk.
-
I know this doesn't help you, but I'm interested in the outcome.
I've never managed to get P96 drivers installed with my CV64 (machine in my sig.) . I've had the error you're getting (don't remember how I got around it) and then had my 'device not detected' or available. I sympathise with you.
BTW I've never seen an RTG screen like your original post. Weird.
-
I've had these glitches with CGX4 before so hopefully your card is ok, something is probably wrong in the tool types or something else installed causing compatibility issues.
Right now I'm using Picasso96 with my CV64/3D without any issues but CGX4 is definitely faster if you can get it working correctly. There are some updates you can download here:
http://phase5.a1k.org/index.php?cgx
-
The photo was taken with the original V4 cd + V4 RC5 installed
V6 was about MorphOS, which I don't use, so I left it at RC5.
-
Looks like faulty video RAM mate.
-
Looks like faulty video RAM mate.
... or bad contact into ram sockets. Maybe a simple cleaning will solve the problem.
-
igen az is lehet!
take the card out mate, grab it in your hands sideways. twist it to and fro slightly until you hear creaking and cracking. this will re seat the chips.
then try again.
-
I'll try to figure something out with the video ram. It is replacable, isn't it (in case it's gone forever?)
-
I've had these glitches with CGX4 before so hopefully your card is ok, something is probably wrong in the tool types or something else installed causing compatibility issues.
Right now I'm using Picasso96 with my CV64/3D without any issues but CGX4 is definitely faster if you can get it working correctly. There are some updates you can download here:
http://phase5.a1k.org/index.php?cgx
Starting with OS3.9 BoingBag 2, there are incompatibility problems with CyberGraphX unless you have these patches installed. Either make sure you have at least RC5 installed, or install over a plain OS3.1 installation, to determine whether you're dealing with a hardware or a software problem.
-
CGX 4 was a pain to get going on my A4000 with OS 3.9.
What I did was install the basic 3.1 Workbench, and then installed CGX 4 with patch 6. I knew then the hardware was ok as it worked.
One other thing: the Boing Bags. Boing Bags 3 and 4 are community efforts. I had some funny things happen with Boing Bag 3, so I just stuck with Boing Bag 2.
-
I've had it running before.
Also tried it with just bb2 and without the update, then there's that bug you can't select any screen modes but do get the boot logo. The boot logo was looking like crap too (green horizontal lines and so on)
-
Can you try just a stock WB 3.1 and CGX 4 install on a spare hard drive?
-
Start with just pushing in the video memory on the card.
Push very firmly and you will hear a click.
Mine comes unseated over time and trashes the pointer
Good luck.
-
Will try both tonight, thanks!
-
Very weird distortion.
I have my A4000 triple booting with OS3.1 with Cybergraphics, OS3.1 with Picasso 96 and OS3.9 BB2 with Cybergraphics 4 RC5 on a Cybervision64. No issues with installing any of them. I like Cybergraphics a little better than P96. Dragging screens is cool if essentially useless.
I definitely concur on trying to reseat the memory chips. And check the Zorro contacts as well.
There are a lot of parameters that can be changed in the CybergraphX commodity popup in the Prefs draw. I've had to change some of them to get things working smoothly and I would play around with them if reseating the memory doesn't work. You might have set some parameter in the installation that could cause this. I had some weird stuff but nothing this bad when I installed and unchecking one of the parameters fixed it. I don't remember which one, unfortunaltely.
-
Reseating the memory has worked. It has taken a while, my whole Amiga was refusing to boot. I bought myself a nice big towercase, built the Amiga in it and now everything works like a charm!