Mediator ZIV + OS4

[A1200Power]

Hello guys

Q : I take it that the mediator ziv suffers from the same probs as the mediator LT4 or not? When i let the amiga boot with OS4 it shows the mediator board including the attached devices, this is also in the early startupmenu visible.

I use a voodoo4 but i doesn't initialize when i select voodoo. Under os3.9 it works fine but i take it that OS4 has no support for the voodoo4 or do i need a voodoo3?

Thanks for the support.

[AMC258]

Ohhhh I hope I can use one of my Voodoo 5's... I really don't want to wait until I can find/afford a Voodoo 3 to use OS4 if it ever shows up.

[TetiSoft]

A1200Power wrote:
Q : I take it that the mediator ziv suffers from the same probs as the mediator LT4 or not?

No, the Mediator1200LT4 is not recognized by OS4 because it does not know its Zorro Vendor/Product ID combination yet.
The Zorro Vendor/Product ID combination of the Mediator Z-IV is known by OS4.

When i let the amiga boot with OS4 it shows the mediator board including the attached devices, this is also in the early startupmenu visible.

Yes, OS4 knows about the Z-IV.

I use a voodoo4 but i doesn't initialize when ik select voodoo. Under os3.9 it works fine but i take it that OS4 has no support for the voodoo4 or do i need a voodoo3?

OS4 should be able to recognize and use any Voodoo gfx board
with a PCI Vendor ID of 0x121a and a PCI Product ID of
3 or 5 or 9 which should describe a 3dfx Voodoo 3/4/5 AFAIK.
Which ID has your board?

[A1200Power]

@Tetisoft

Thanks for the info, i checked your data and came up with this

A ) The board has a product 9 id in the early menu
B ) OS4 shows a PCI Vendor ID of 0x121a

So the specs comply but there is no output on the monitor, even when os4 can display. The early startup menu should automaticly fwd the boot screen to any attached displaydevice that's recognized.

The mappings are 8 MB window on the ZIV mediator and the wait state is enabled.

Any other tips?

[TetiSoft]

A1200Power wrote:
@Tetisoft
Any other tips?

No, sorry, it should work but doesnt, strange.
Is any error reported? "DumpDebugBuffer RAM:bootlog.txt"
will create a file where you can search for possible error
messages.