A4000 + Mediator 4000Di + Classic Workbench.

[ElectroBlaster]

Is it possible for me to use this lot together?

A4000 + Mediator 4000Di + Classic Workbench ADVSP

Bearing in mind I have never even tried a mediator and I am aware of the fussy nature of these things.

I was hoping I could go with ClassicWB and then introduce the mediator, installing it etc.

Tia

 

[fitzsteve]

No is the short answer because the ADVSP pack has some enhancements that conflict with Picasso 96.

Good news however, you can use the Classic WB P96 pack which as the same icon pack and as the name suggests supports Picasso 96, it also has a lot of additional software installed to take advantage of the higher resolutions.

To install this setup in WinUAE, remove the UAEGFX monitor driver, set a native screen mode > on the Amiga install MMCD then Picasso 96 for Mediator.

Alternatively the Classic Workbench 3.9 pack also lends itself well to the Mediator

 

[cloverskull]

+1 for Classic Workbench 3.9 for this setup.

I've recently done similar in an A1200 Mediator configuration but using OS 3.2.2. I wish it were simple to "upgrade" ClassicWB 3.9 with 3.2.2 but alas I couldn't figure out how to do it cleanly, so I used a "virgin" 3.2.2 setup and am piecing together my OS now.

 

[ElectroBlaster]

Thanks

Looks like it may be best to build my own from scratch.

EDIT: Will give ClassicWB 3.9 a go

 

[cloverskull]

ClassicWB3.9 is a good bet

 

[Boing-ball]

No is the short answer because the ADVSP pack has some enhancements that conflict with Picasso 96.

Good news however, you can use the Classic WB P96 pack which as the same icon pack and as the name suggests supports Picasso 96, it also has a lot of additional software installed to take advantage of the higher resolutions.

To install this setup in WinUAE, remove the UAEGFX monitor driver, set a native screen mode > on the Amiga install MMCD then Picasso 96 for Mediator.

Alternatively the Classic Workbench 3.9 pack also lends itself well to the Mediator

Personally I would reverse the install. P96 then MMCD. Why? The MMCD installation installs the Voodoo and Radeon drivers into LIBSicasso96. If you haven't installed P96 first it won’t install properly, I.e. P96 installation creates the folders LIBSicasso96 etc. One of the many pitfalls for Mediator installations. Also look to install MMCUPD2.6 then finally pci.library 3.14 for 68060 and or pci.library 3.15 For 68040. There is also updates also not found on MMCDUP2.6 like a newer Voodoo.driver. Make sure you run MedConfig after each MMCD and MMCDUPD2.6 as this also sets up the configuration for Graphics RAM etc..
All can be found on Elbox.com.

As for OS3.9 and 3.2.2.1. I do it this way. Install OS3.9. Update with BB1&2. I also use the 2018 version of BB4 for all the extras. Once happy it works, then update to 3.2. Etc.. Remember that each update puts on a new Startup-Sequence.

 

[fitzsteve]

It's a long time since I done the setup manually, you'd think Elbox would've made it simpler by now with a new installer that gets the job done all in one go lol.

I'm so grateful to have all my backups lol. If I had to start again from scratch today I might end up throwing the lot out the window.

I had some fun this last week setting up my PiStorm32 with the Mediator, lacking the MMU it doesn't support Warp3D but otherwise it's incredibly fast and seems pretty stable!

 

[Boing-ball]

It's a long time since I done the setup manually, you'd think Elbox would've made it simpler by now with a new installer that gets the job done all in one go lol.

I'm so grateful to have all my backups lol. If I had to start again from scratch today I might end up throwing the lot out the window.

I had some fun this last week setting up my PiStorm32 with the Mediator, lacking the MMU it doesn't support Warp3D but otherwise it's incredibly fast and seems pretty stable!

Have played around with both A1200 and A4000 Mediator setups that many times. I feel as though I could set one up in my sleep now
Also have Setup a Mediator and PiStorm with Pi4B last year in a Checkmate case which replaced a Blizzard 040/PPC and GREX setup. I’m currently using a July 2023 EMU68 build as it’s the only one I’ve found that was stable and works with a Mediator SX board With a Voodoo3, Spider-II USB and 8139 Realtek NIC. Anything after that has been released has caused chaos and lockups.

 

[specfreak]

Interesting read in relation to PiStorm32. I've just got my A1200 1D.4 board back from being recapped. Sadly my BPPC 060@50Mhz/PPC603e@240MHz+256MB RAM gave up the ghost (was working for a week or so then not :-(, a few months back).
So, I got a PiStorm32 (with rpi3a) after deliberating between things like a TF1232, TF1260, but decided PiStorm32 to start due to cost (simple as that for now).

I've got a Mediator SX with Voodoo3 3000 16MB, 8139 Realtek NIC and SB128 sound card.

I did a new OS 3.1 and OS 3.9 install and then my MMC 1.26 CD, even tried others, but once I get to the MedConfig part my machine just freezes.
I've tried to see what the system is doing in snoopdos, but it just shows it checking the ENV settings and then vendors.txt.... just hangs.
I'm using EMU build 1.0.2. I presumed it was to do with the lack of MMU, but @Boing-ball says above it may be an issue with the EMU68 build.
I've got my OS on a CF card and also got the Pi's SD partition types 76 to show up.

I bought 2x 32GB microSD cards to play with, so will try the July 2023 build and see what that does.

It's been a while since I've used my A1200 Power Tower, I had it at work for a while until I had to bring it home and it's been sat in a box in the corner of a room for about 7 years, until now. I found a cosy spot in my computer cupboard, but it has to go sideways.

Anyway, a lot of fun and hair pulling to get a system up, probably grab CaffineOS as wel.

 

[Boing-ball]

Interesting read in relation to PiStorm32. I've just got my A1200 1D.4 board back from being recapped. Sadly my BPPC 060@50Mhz/PPC603e@240MHz+256MB RAM gave up the ghost (was working for a week or so then not :-(, a few months back).
So, I got a PiStorm32 (with rpi3a) after deliberating between things like a TF1232, TF1260, but decided PiStorm32 to start due to cost (simple as that for now).

I've got a Mediator SX with Voodoo3 3000 16MB, 8139 Realtek NIC and SB128 sound card.

I did a new OS 3.1 and OS 3.9 install and then my MMC 1.26 CD, even tried others, but once I get to the MedConfig part my machine just freezes.
I've tried to see what the system is doing in snoopdos, but it just shows it checking the ENV settings and then vendors.txt.... just hangs.
I'm using EMU build 1.0.2. I presumed it was to do with the lack of MMU, but @Boing-ball says above it may be an issue with the EMU68 build.
I've got my OS on a CF card and also got the Pi's SD partition types 76 to show up.

I bought 2x 32GB microSD cards to play with, so will try the July 2023 build and see what that does.

It's been a while since I've used my A1200 Power Tower, I had it at work for a while until I had to bring it home and it's been sat in a box in the corner of a room for about 7 years, until now. I found a cosy spot in my computer cupboard, but it has to go sideways.

Anyway, a lot of fun and hair pulling to get a system up, probably grab CaffineOS as wel.

Hi,

Not got around with my setup for a few months due to playing around with A4K setups. I believe the Mediator and EMU68 maybe down to the Mediator needing specific DMA settings for the Voodoo or RTG board of choice to work correctly. It maybe an address conflict?
When I get around to it, will try and have another play around with a TX board to see….

Don’t forget that MMCDUP2.6 will not have the latest pci.library (V3.14 & 3.15) or the Voodoo RTG drivers

 

[fitzsteve]

I got my Mediator/Voodoo/Emu68/1200sx working together the only thing I couldn't get going was Warp3D which will be due to lack of MMU. I was lucky I guess with the nightly build I grabbed!

 

[fitzsteve]

Here's my thread:

Post in thread 'A1200 Black Box Tower Project' https://www.amibay.com/threads/a1200-black-box-tower-project.112250/post-2491453

 

[specfreak]

Cheers @fitzsteve , I'll check out the linked thread.

 

[fitzsteve]

Posted by mistake

 

[specfreak]

Hi,

Not got around with my setup for a few months due to playing around with A4K setups. I believe the Mediator and EMU68 maybe down to the Mediator needing specific DMA settings for the Voodoo or RTG board of choice to work correctly. It maybe an address conflict?
When I get around to it, will try and have another play around with a TX board to see….

Don’t forget that MMCDUP2.6 will not have the latest pci.library (V3.14 & 3.15) or the Voodoo RTG drivers

I'll have a play around, see if I can spot anything. I had been testing later pci.library before my BPPC gave up. I have the CF backup and an almost identical setup in WinUAE so
can look at when my MedConfig settings are. Maybe I can just tweak my ENV settings, but I'll also setup the July PiStorm32 Lite build and see if that helps.

It was probably working fine with old drivers at the time, I was just trying to get my NIC card working, which worked fine in OS4.1 FE Classic.

I think issuing the Pciinfo command also hangs the system. It's the beginning of the usual Miggy fun.

 

[Boing-ball]

I'll have a play around, see if I can spot anything. I had been testing later pci.library before my BPPC gave up. I have the CF backup and an almost identical setup in WinUAE so
can look at when my MedConfig settings are. Maybe I can just tweak my ENV settings, but I'll also setup the July PiStorm32 Lite build and see if that helps.

It was probably working fine with old drivers at the time, I was just trying to get my NIC card working, which worked fine in OS4.1 FE Classic.

I think issuing the Pciinfo command also hangs the system. It's the beginning of the usual Miggy fun.

Check the jumpers on the mediator. I seem to recall I have this set to the 4MB window due to using PCMCIA and a Squirrell SCSI adapter. Try the config jumper on and off to see if that helps.

 

[specfreak]

@Boing-ball . I started over using the July 23 PiStorm32 build as suggested, and indeed it doesn't hang now.
I forgot what a faff on is it starting over. I can get my Voodoo 3/3000 16MB screens to display (using P96 21.c > e), but for some reason my screenmode prefs aren't saving, so when I reboot they revert to a normal PAL 4 colour WB? Even though I have the DEVS:Monitors/Voodoo setup.

Pciinfo shows all my cards, but when I installed the Internet software form my OS3.9 CD it seems to be missing a load of mcc's, so I've got a lot of notes to make to get back to how it was.

I have my Mediator SX jumper set to 8MB Window, I didn't change anything on it (yet). I don't use PCMCIA these days. I have had a Squirrell SCSI before but I think I sold that when I got the Mediator and used a NIC card. I had used a PCMCIA NIC adaptor before, but that was like eons ago now.

I tend to use the Gotek and CF cards to get stuff into my miggy.... oh and regular floppies.

Booting into my previous 3.9 O60/BPPC just results in a MMU error with pci.library, so that will be legacy until or if I ever get my BPPC fixed or get a TF1260.
At least I can still access all my CF and previous builds via WinUAE. Of course for 3.9 it needs to be non JIT to work, but I figured that out.

Thanks for the info guys, really appreciate it. It's just gonna take me time to reacquaint with the quirks of my setup.

 

[specfreak]

Oddly, I was able to resolve my Voodoo screen problem by creating a WinUAE config similar to the PiStorm32.
Opened a screen mode with the Voodoo which made WinUAE go full screen black.
However, when I took this back into my real A1200T then it magically worked..... then it worked in WinUAE too?

It's took all day, but now my NIC card works as well, but not my Sound card (SB128)

The problem is after all this, is that I probably couldn't re-trace my steps to resolving it. I just made a system backup.

Sorry if I'm hi-jacking the thread. I'll stop and maybe make a new one if that's more appropriate.