Sonnet 7200 PCI programming

[Hedeon]

Originally Posted by Wrangler

I didn't think the TX was supported either? In fact, no A1200 Mediator is supported?

It is formally not supported. But version 17.13 can do some simple stuff on an A1200TX. Like QuakeWOS without sound.

[Jpor]

Originally Posted by Hedeon

Oh and if you have a TX then your jumper should be on 8MB, not 4MB.

Cheers

I set it 4MB for PCMCIA back when I had 3.1 ROMs.

Will try setting it to 8MB

[fitzsteve]

Originally Posted by Hedeon

It is formally not supported. But version 17.13 can do some simple stuff on an A1200TX. Like QuakeWOS without sound.

Mine works with AHI FM801 sound on QuakeWOS

[Jpor]

Originally Posted by fitzsteve

Mine works with AHI FM801 sound on QuakeWOS

Be interesting to see if a Soundblaster card will give the same.

[Hedeon]

Elbox removed most of the interrupt code out of their sound drivers, I think. It is interrupts that mess up things.

The 8 MB Z2 window of the TX is split up in 2x4 with one part always pointing to the gfx card.

Two errors can occur: one is e.g. a move.l (a0),(a1) where both addresses are in PCI memory but not in the same 4 MB.

The other is interrupt code not moving the window and getting non-sensical data. Mostly input.device getting into trouble while traversing lists.

And Jopr, your mediator will still not work with the 8MB set as it does not identify itself as a TX but an SX. The TX is the only mediator with a spilt window option.

[Jpor]

Originally Posted by Hedeon

Elbox removed most of the interrupt code out of their sound drivers, I think. It is interrupts that mess up things.

The 8 MB Z2 window of the TX is split up in 2x4 with one part always pointing to the gfx card.

Two errors can occur: one is e.g. a move.l (a0),(a1) where both addresses are in PCI memory but not in the same 4 MB.

The other is interrupt code not moving the window and getting non-sensical data. Mostly input.device getting into trouble while traversing lists.

And Jopr, your mediator will still not work with the 8MB set as it does not identify itself as a TX but an SX. The TX is the only mediator with a spilt window option.

Okay interesting. So are you saying Elbox have messed up with the new 2021 TX+ boards? And now identifying as SX boards?
I do also have a 2018 TX board in another test tower. So can check that as well.

[Timtheloon]

Originally Posted by Jpor

Hi Hadeon.



The board I have is definitely a Mediator 1200 TX+ 2021 model

Hi Jpor can you take a picture of your Mediator

Did you buy it direct from Elbox?

Wonder if Elbox have pulled a fast one to get rid of old stock by re-badging it and for us with the untrained eye wouldn’t notice or maybe there is a reason they have gone back to this configuration which would be interesting to find out.

[Jpor]

Originally Posted by Timtheloon

Hi Jpor can you take a picture of your Mediator

Did you buy it direct from Elbox?

Wonder if Elbox have pulled a fast one to get rid of old stock by re-badging it and for us with the untrained eye wouldn’t notice or maybe there is a reason they have gone back to this configuration which would be interesting to find out.

The 1200TX+ 2021 board I bought from Sordan.ie (Official Elbox reseller) and have registered this with Elbox in the hope they would send me pci.library 14.

The board is slightly different to a 1200 TX 2018 model as it now includes 2 x fan headers for the newer Elbox Black Mk II case. If memory serves me it shows REv 2.2 on the board and again is a black PCB.

Will try and get a picture up for you to see.

[Hedeon]

It does not matter. The firmware says it is an SX. There is no way for programs to detect it otherwise. Contact Elbox on why this is.

I think difference is split zorro window. PCI library itself checks for TX before setting that up. I resourced it :-)

[indigolemon]

Mine is a TX (ordered 2017) and definitely shows $3C and $BC - I wonder if they've made a mistake with this TX+ update making it report itself as an SX?

I did have limited success with a K1 and QuakeWOS back in late 2018 - even getting sound working with AHI and the FM801 sound-card, but it was not stable. After anything from 5 to 30 minutes the machine would lock up.

Still super impressive given the issues the 1200 Mediator presents!

[ Show youtube player ]

I've stashed my K1 for now, until I can get my hands on a big box machine

[Jpor]

Originally Posted by Hedeon

And Jopr, your mediator will still not work with the 8MB set as it does not identify itself as a TX but an SX. The TX is the only mediator with a spilt window option.

So have contacted Elbox support. Got a lightning response back from them

So because I have my Mediator with the 4MB jumper set the TX+ board becomes an SX board. To turn it into a TX board I have to set the jumper to 8MB.

Will give it a go and check again.

[Hedeon]

Originally Posted by Jpor

So have contacted Elbox support. Got a lightning response back from them

So because I have my Mediator with the 4MB jumper set the TX+ board becomes an SX board. To turn it into a TX board I have to set the jumper to 8MB.

Will give it a go and check again.

Oh. That makes sense, actually :-)

[Jpor]

So tried the 8MB jumper today. Unfortunately it now locks up both of my Builds. 3.9 hybrid with 3.1.4 as well as my fully 3.1.4.1 installation.

Both lockup before getting to workbench. Also tried Medconfig to say I’m using the 8MB jumper as well as NOT telling the configuration. Both the same experience.

So either something in my configs on both builds causing an issue. Or my setup and or TX+ problem.

Will try the K1 on my 2016 1200TX board with 8MB jumper to see if it happens as well.

Not plain sailing for me at the moment.

[Timtheloon]

PCI Card setup could also be your problem

Found my setup would do different things if I didn’t have them in a certain order, for me my killer is in the bottom PCI slot.

I’m not home at the moment but will be at the weekend and can flash up my tower and also look at my configuration and check all my settings for you and how my cards are setup.

Are you still trying to use two video cards? i.e using the ATI for memory and the voodoo has video? Try with just 1 video card for testing if you were.

I tried this but it was prone to lots of crashes i was also trying to use MMUlibs to config the memory ranges but this didn’t seem to help with a two graphics card config

[Jpor]

Yeah still using 2 graphics cards. Voodoo 4 as main RTG with Radeon giving me a further 128MB fast RAM. Just to add I’m using a Blizzard 1260 with MKIV SCSI card with 256MB FastRAM as well.
If you can let me know your PCI card assignments etc.. That would be great.

[Timtheloon]

So your setup is similar to mine

Only difference being the newer TX and I have a Voodoo 3

Try it without the ATI card

[Hedeon]

Originally Posted by Jpor

Yeah still using 2 graphics cards. Voodoo 4 as main RTG with Radeon giving me a further 128MB fast RAM.

.

Go measure the speed.... It's about the speed of chip ram.

[grelbfarlk]

Originally Posted by Hedeon

.

Go measure the speed.... It's about the speed of chip ram.

But number go up. R U saying number don't go up? 184,549,376 is a large number at top of Workbench. Much bigger than 37,748,736

[grelbfarlk]

Has anybody tried running CandyFactoryPro? This uses ppc.library.

[klx300r]

Originally Posted by Hedeon

Ok, I finally after some time (3 years?) have a working OS4 machine again.

nBlood WOS didn't work on it. So I updated ReWarp, and fixed the startup.o from WOS newlib and removed direct access to framebuffer when ReWarp is detected and now it seems to run on my OS4 machine.

CD music is disabled. You need the .WAVs as found on BSzili's site.
updated powerpc.library for OS4 (ReWarp) is included.

Let me know how it runs.

works amazing on my X1000 thanks