Graphics corruption

[delshay]

I am inclined to agree that it's a configuration (or power or both) issue simply because the chance that 3 successive bvision cards all suffer the same specific defect seems remote.

Make sure any overclocking tooltypes are disabled in the monitor driver (hint: 2AIDEMREPYMNONAFADELLATSNII, MELTDOWN)

If done correctly overclocking has nothing to do with this problem. I have finished the Ultra Bvision which is clocked 125Mhz and sets a new world record.

A Master Bvision is now also complete,but I am awaiting driver update for this card,but even without the driver update has set another world record with its Ultra Low Latency SGRAM (speed will never be revealed).

Both Bvision work on 37.5Mhz+ bus regardless if the PCI bus has jump ship.

[Karlos]

If done correctly overclocking has nothing to do with this problem. I have finished the Ultra Bvision which is clocked 125Mhz and sets a new world record.

Umkay, this helps the OP solve his display problem how, exactly?

[danbeaver]

"Umkay, this helps the OP solve his display problem how, exactly?"

Only use those modes that work without issues?

[freqmax]

It helps by showing that up to 125 MHz should work?

Pushing the D/A (or RAM) above certain bitrates can make them go gibberish.

Anyway if you lack programming skills paint some pictures with vertical lines of different base colors + white (R-G-B-White). Make a slide show of it if you can. Also open one picture in a window you can move horizontal and vertical to see what happends.

[danbeaver]

A Moire' effect is neither a programming failure nor the sign of the ill informed. DAC issues and clock rates can make a difference. Three boards with the same "issue" in only certain modes COULD be either a hardware (my vote) or software issue. If it is necessary to find out which, use P96 or pop it into an OS 4.1 system. Ergo different software. If the "issue" persists, it is hardware. Don't shoot the messenger; this is a forum -- you know where Caesar got stabbed to death? Be open to other ideas.

[delshay]

It helps by showing that up to 125 MHz should work?

Pushing the D/A (or RAM) above certain bitrates can make them go gibberish.

All true,but I don't think it will work on any other Bvision as my permedia 2 chip is different and has 250Mhz Ramdac as standard with 143Mhz SGRAM chipsets and does not go gibberish.

There is also timing parameters to take advantage of faster SGRAM,but none of this is available/or will not work on any other Bvision card in its current state.

Anyway all this does not matter as Master Bvision is working,and now sets the pace and i think it may get quicker.

[danbeaver]

Thank you for the input, it can now be established that you did not cause the problem and with your technical background don't care to help

[actung_bab]

yes ran mine from pc psu as well as the floppy connector but both toghter

you should not have to get 3 bvsion cards i never had bit trouble with mine

theres some pcb i seen on amigakit so not sure what this does was pictured with bvsion card

http://amigakit.leamancomputing.com/catalog/product_info.php?cPath=42&products_id=339

oh this is if you use certain ata fast ide card i just used standred buffered card

[rvo_nl]

thanks, Ive got 2 of those but they are not going to solve my trouble. I first need to rule out a software issue and for that I want to install OS4. No clue why this is not working though. Will report back when I made some progress there.

[rvo_nl]

well, I managed to install CGX4 (4.3 rc5) over a clean WB3.1 installation. Even with the default 56khz monitor, any resolution I tested had the same artifacts. Even in 8 bit. I guess I didnt spot the lines before, because of the few colours it uses. So every other screen except the workbench screen shows up garbled. Problem in certain memory range then? Must be Fastmem then, since all Bvisions have this problem?

Edit: seriously, please help me out. After spending some time with my machine I've noticed how much effort I put into it over the last few years. I really must get it working again and Im really eager to try out OS4.1 Classic. Any ideas are welcome. Anything on-topic, please..

[Damion]

I would also initially guess a software or power/contact issue, but it sounds like you've triple-checked all the basics. How about reducing the RAM on the BPPC to one stick, or trying a single different one? You might also end up trying another motherboard, or thoroughly checking yours for failing capacitors.

I had a similar problem once with a Picasso IV on an A2000, that had previously worked fine. Random garbage, that eventually progressed to lock-ups. After trying a million different things (and suspecting a dud PIV), it turned out to be something defective on the motherboard.

[freqmax]

Yeah try with another motherboard. And please upload some pictures of your hardware.

[Zac67]

Incidentally, have you made sure it's not the monitor? Those digital displays can develop pretty strange defects at times...

[rvo_nl]

I had a similar problem once with a Picasso IV on an A2000, that had previously worked fine. Random garbage, that eventually progressed to lock-ups. After trying a million different things (and suspecting a dud PIV), it turned out to be something defective on the motherboard.

@damion interesting. did you have such 'garbage' also under RTG graphics modes? Because that is the strange part, everything on my a1200 board doesnt SEEM related to my bvision output, but maybe Im wrong. Anyway tonight I will try swapping both simm's for one out of my blizz1230. If that doesnt help, its either ppc, or mainboard.

@freqmax Im hoping to find someone nearby with a machine I can test my hardware on

@Zac67 yes, I have 2 identical monitors and swapped them around more than once, to rule out things.

[delshay]

Check SGRAM on Bvision not coming into contact with something on motherboard.
Check Bvision(s) on another Blizzard card.
Check Blizzard card PCI connection for contact stray wire/poor solder contact.
Check thermal paste (if any) not in contact with soldering contacts.

[yssing]

Ive seen something similar to that on my old A4K wit CYB64/3D it turned out to be a short circuit problem with two of the pins on the virge chip. After I fixed it no more graphics problem.

So maybe look for a short circuit on your board.