Mediator + BVision configuration problems

[Boot_WB]

Well, I'm really confused now.

The installations in both partitions are screwed.  Kept getting ramlib failure on bootup in the end.
I've tried reinstalling, but on a fresh installation my bvision display is all blacked out (I can see borders, but no cursor, text, graphics).
I think the bvppc patch changes something in either cgx, the permedia driver or the bvision monitor settings.  I don't know.  Either way it sacaded onto the new emergency disk I created and from there to the fresh OS3.9 installation.

OS3.0 works fine, the installation of OS3.9 goes fine.  

Am trying a fresh install from scratch, but without using any previous monitor drivers, etc.

@Kas1e - I'll give that a try :-)  Thanks

At the moment I'll settle for a working installation with ANY graphics driver.  Have installed 3.9 many times before and never had this trouble... :-(

Just done a fresh installation with no graphics driver and no cd drivers copied during installation.

Ramlib failure    :madashell:
What the phuckibnhfdshfjkshfkjdhkas
gkj;hklgfjalk!!!?!??!?!?!?!?!?

I'm going to try installing idefix on 3.0, THEN installing 3.9 from an installation which can't possible be affected by all of this.  This is driving me nuts.  More so...

[kas1e]

ramlib failure can be in fact of :

1. bad envs for WarpOS
2. bad hardware contact (too much time was for me somethink like it)

Basically i do always somtehink like this:
by BPPCfix patch, i remove old ppc.library from ppc. It's one a buggy, and WarpOs must be works without this library. Basically i can said, that BPPCFix must be in any case.
Load OS, and do manually (if i want warp-os) : loadlib powerpc.library.

PS. Also i was have problems with installation of Bvision drivers. CGX 3 just do not works, but cgx v4 works just fine. What i do:
Install CGX4. Reboot, can't load. Black screen. Reboot without startup, erase cgxsystem.library, install last bvision updates, reboot - all works.


Ps. Full install for me was looks like this:

setup 2 partitions. do full install for voodoo3/mediator on first. with ppc, warpos, warp3d and so on.

After it just copy all files from 1st partition to the second, and second called system_bvision. Change startup-sequnce and user-startup for system_bvision path,
and install CGX v4 drivers as i said uppear. After it i am remove old warp3d and install new one for bvision, and just change data in env:powerpc/gfxaddr (of course env of bvision partiion ), and all works ok.

[doctorq]

Sounds more to me like the 680#0 libraries are either corrupted or out of date.

As for installing a BVision, don't use the installer on the CyberGraphX v4 CD, but unpack the latest update, unarc it, and use the installer in this one. Get an update from this page for instance.

[Boot_WB]

doctorq wrote:
Sounds more to me like the 680#0 libraries are either corrupted or out of date.

Latest flashrom update compatible with BVision installed.  Not 0x0 libraries.  Even reflashed to be sure.

As for installing a BVision, don't use the installer on the CyberGraphX v4 CD, but unpack the latest update, unarc it, and use the installer in this one. Get an update from this page for instance.

This is the one I'm using (or trying to).

Kas1e wrote:
  ramlib failure can be in fact of :

1. bad envs for WarpOS
2. bad hardware contact (too much time was for me somethink like it)

I'd not even got around to installing warpOS yet, this was just a fresh OS3.9 install.

I've already cleaned the edge-connector contacts with a pencil eraser today, as I've suffered this problem before.
I would think it might be my 4-way adapter, but I haven't touched it at all.

At the moment I'm just trying to install OS 3.9 again.  Once I've done that, and backed up the installation (to a CD) I'll maybe think about cgx/p96 partitions.

Reminds me of when I first got OS3.9, all this malarky.  What a farce.

Thanks for your advice folks.

If I was paid minimum wage for the work I do on my Amiga I'd be pretty rich.  

[Framiga]

"Just done a fresh installation with no graphics driver and no cd drivers copied during installation.

Ramlib failure
What the phuckibnhfdshfjkshfkjdhkas
gkj;hklgfjalk!!!?!??!?!?!?!?!?"

fresh 3.9 install?

http://www.gregdonner.org/os39faq/os39faq.html

down ATM (look at Installation tips)

[doctorq]

Latest flashrom update compatible with BVision installed. Not 0x0 libraries. Even reflashed to be sure.

And you haven't even bothered to try to install the software libraries? I'd still suggest you to try it out, but it's of course your choice.

Even though it should be on the flash rom of the BPPC, I have never been able to get a stable installation without installing the software libraries, so I would suggest you to at least try it out. At least you can rule that out afterwards.

A very recent experience (two days ago); I couldn't get my CVPPC working on my CSMK3 with latest pre G-Rex flash. After installing latest software libraries, the CVPPC were fully functioning, and have been since.

[Boot_WB]

@All

I've FINALLY found the problem (I think), after a cascade of failures, initally started during this thread - which has probably cost me around 100 hours (and around £30) work to find the root of.

Started with the problems described above.

For a while the Amiga would crash during bootup when trying to install IDEfix.

Most times most of the PCI cards would not be recognised, although strangely the Voodoo card always was recognised.
This was the biggast clue, as I'd had this symptom before when I had a loose Earth wire in one of my Molex connectors.

Very rarely I'd get a red screen on boot, sometimes no boot at all.

I replaced EVERYTHING piece by piece:

Tried a new 4-way adapter, and just a 44-40pin adapter.
Tried a different Mediator.
Replaced the IDE and floppy cables
Removed the Tower LED connector form the motherboard.
Tried removing each PCI card in turn
Bought a new 550W ATX PSU
Tried a different keyboard adapter
Installed onto a new Hard drive.
Tried removing the floppy drive (haven't got a spare one of those  :-P )
Tried a different accelerator (Apollo 1240)
Different RAM
Different motherboard (Rev 1b)

Occasionally after removing something, or changing something the problems would all disappear - I'd think I'd solved it only for the problems to reappear next time I rebooted.

Having reinstalled several times I was certain this was not a software issue, but the only thing left which was in the original configuration is the physical mass of the Power Tower.

Although not visible, it seems that the tower was bowing the motherboard ever so slightly.  Although it looks fine, I've tried bending the interior plate of the tower slightly inwards, and at the moment (touches wood) all the problems have disappeared.

Just thought I'd post this lengthy description in case someone else has similar, seemingly random, sporadic, untraceable issues.

It's working again  :-)  :-)  :-)  :-)  :-)  :-)  :-)  :-)  :-)

[humppa]

Sorry for digging out this old thread, but could you please tell me if this whole solution (BVision *and* Mediator) was easy to fit?
I wonder if there is enough space under the Mediator so that the BVision fits without having any contact with the circuit board or heating up too much.

Thanks!

[Boot_WB]

Hi, the majority of the Bvision is not under the mediator so you can still attach a haetsink and/or fan with no obstruction.  The hole in the bvision is large enough that you can still access the floppy power and led headers through it with the mediator pass-through connector in place.

I added a small rubber stopper onto one of the chips of the motherboard to support the bvision, thus preventing it from touching the motherboard - though this is probably not necessary if your BPPC is supported properly.

There is (further back in this thread) a utility called BVPPCfix which, like the BPPCfix utility, removes resident libraries on startup - in this case deactivating the BVision.  This could be useful if you have a dual-boot setup where 1 partition is for BVision, and 1 is for Mediator.  iirc there are some problems reported (although I can't remember noticing any difference) of the bvision/mediator combination slowing down performance when both PPC and Mediator are in use.  

Mechanically, there were no problems.  Performance wise I'm sure it works, i just had other problems which all came to light.  I've not yet gotten around to reassembling everything.

Regards



Rich

[humppa]

Thanks for your post and the detailed descriptions.
I'll give it a try tomorrow. I am planning to use Mediator and Voodoo3 solely for OS 3.9 while using the BVision for a separate MOS PUP installation on a second SCSI-harddisk.
Thanks for the tip with BVPPCfix, I might use that for the OS 3.9 partition.