There is hope for OS4 on the Classic.

@Catalist

Use an 8029 instead of 8139 card if you don't want to use PCMCIA. Its not like the 8139 ever went much faster than 10Mb/s in a Mediator 1200 anyway.

Nobody said that its impossible to get TV cards working under Mediator/OS4 either, its just that there are currently no native drivers for that. It might or might not work, at this point we don't know.

At least you actually can use network (8029), sound (terratec) and graphics (voodoo) in the mediator. Would you rather there was no support at all?

Besides, if you want, you can use the elbox 68k drivers. Just remove all OS4 native drivers for mediator cards and install them like on OS3.9, they even use the native Picasso96.

Theres no need to be so hostile about it, its not like hyperion owe you anything.

@rwo

Once the new SDK is out, there will be nothing stopping anyone interested from having a go at writing a SCSI driver, or any other driver for that matter.

@Catalist

(edit)

Deleted my post. No point in replying to this.

@Rogue

Perhaps you could write an article (Article section here on amigans) describing why certain hardware isn't supported, why dma doesn't work, what can be done to get around it, alternative cards to use and so on. That is, describe the technical reasons, economical reasons etc.

That way we can point people to that article.

@Chris

That's too bad :(

Both my AmigasPPC are fully supported. Great !!!

@Chris

Quote:
The 3c589 driver does not work.
The cnet.device driver works.
AFAIK it is unknown if the squirrel driver works, I'm not
aware that somebody tested it. Any betatester with BPPC
and Squirrel here?

@Catalist

The classic Amiga is over extended, it life span long passed it warranty period, personally don't think Hyperion should have spent this amount of time on supporting HW upgrades for some thing that where never designed to that expandable.

yes one can complain about HW support, personally think HW support list too long, and like you say at you end of comment, I agree whit you better to support new hardware, like Sam440, but we all know the issues whit that.

Personally I think Aminio (Amiga Inc nr. 1) / KMOS (Amiga Inc nr. 2) and ITec is one that making mess of the licensing and ownership.

@Catalist

Quote:
What about reading the comments in the compaibility list?
They say
Quote:
which IMHO perfectly explains that it is a hardware problem,
so please dont blame the software developers for that, thanks.

@orgin

Quote:

Of course I could do that, but what would it help? If you read Catalists posting, you see the typical rant. I don't think that any reasoning will reach him, more so since he apparently created this account just for the purpose of this rant.

The reasons are always the same, either no one actually was available for the driver, or the hardware doesn't support it. I don't think that people like Catalist could be reasoned with anyway.

@Rogue

OKey.

I've seen some people starting to claim that dma doesn't work and implying that it's because of os4 since it doesn't work on the A1's either.

So could be an idea to counter effect that and other misconceptions by making some kind of article.

@orgin

And those claiming this are who? Really I don't think that an article would help. Face it, those people will clame things like this no matter what. They could show AOS 4 runing with DMA working and they would still write those thing for whatever reason they have to write it.

So I think that they better continue their work and ignore comments like that.

@R-TEAM
Quote:
We don't suspend users just because they have a different opinion. Hit the report button and keep the troll pointing out of the public forums next time. Thanks.

Hi,

@ssolie

no problem ;)

but ..... who are the Report button ??
[AWeb 3.5.09 68k]

And -> i have nothing against different opinion ...
So long it is Amiga related [and not "other OS"] and
make sense in any way ..

Only to write [or copy from A.org] the same senseles
text make no discuss anyway ..

R-TEAM

@orgin

Quote:

DMA does work on the A1, otherwise there would be no DMA-capable IDE devices, or 100/1000 MB network drivers.

Personally, I don't think that these claims will stop with anything I write, but just in case, here's a cut-and-paste quote for everyone:

-- CUT HERE --
DMA PCI cards on the classic do not work because neither the Mediators nor the Prometheus support DMA. Some of them can do DMA between cards on the PCI bus, but that requires

a) special drivers that are specifically adapted to this "feature"
b) A bounce buffer in a PCI card, like a graphics card, so this does not work with e.g. AGA.
c) Adoptions in the graphics driver so that it reports less memory than it actually has.

Overall, this "solution" was rejected for the wide-ranging consequences it has. You may claim that the Articia fix was done on the A1 as well, but these kinds of fixes are local to the driver and do not require any changes in the DMA-driver AND the graphics card driver.

Needless to say, the graphics memory DMA hack only works on PCI graphics cards, i.e. if you have a CyberVisionPPC, or a BlizzardVisionPPC, a Picasso IV, AGA, or any other Zorro 2/3 graphics card, you would need to put in an extra (possibly unused) graphics card just to be able to use this "solution".
-- CUT HERE --

I hope this clears it up.

@Rogue

Ok thanks for the reply i'd like to make only two questions

1) is possible to use the old elbox driver to use the pci board like soundblaster and ethernet pci card ? If yes we have to use also the old graphic driver for voodoo ( mediator ) with the old soundblaster and ethernet driver or we can use the new graphic driver for the os4 with the old ?

2) As you said before, is possible to adapt the old driver to work on os4 or is a "big and trouble" work ?

Thanks

@nubechecorre

Quote:

Yes, this should be possible. It used to work, I haven't tried it in a while, and there is one potential pitfall. You would need to use either all AmigaOS 4.0-drivers or all-Elbox drivers.

The reaons for this are two-fold: One, you will need the Elbox graphics card driver since otherwise you do not get the additional memory buffer that is used as a bounce buffer for the DMA devices.

Two, the Elbox pci.library wants to retain the exclusive access to the Mediator hardware and more specifically, to the Mediator Offset Register. That means that the V52 expansion.library and pci.library might interfere with each other if both are trying to service "their" drivers. The result would invariably be trash.

The latter might also be an issue when you are using only Elbox drivers, but the code in expansion.library usually is dormant unless there is really something accessing PCI via the expansion.library.

Quote:

Not so much. In theory, you could even use a new feature of AmigaOS 4.0's rtg.library (pinned bitmaps) to create the bounce buffer without the need for a modified driver, but that would require that you know you are allocating a bitmap on the Voodoo 3, and that this Voodoo 3 is stuck into a Mediator. This is a bit shaky, but once you are use it would probably be relatively easy to adapt the drivers.

However, as I pointed out before, this requires a PCI Graphics card in the Mediator, it will not work with a Zorro card, or a BVisionPPC/CVisionPPC, or an AGA-only system.

@Rogue

I have a xsurf3 ethernet card and CV64/3D connected on a Zorro4 on my A1200PPC.

is the zorro4 busboard supported ?

@Rogue

There is a big difference in speed to use the native graphic library of amiga os 4.0 instead of Elbox library ?

Thanks

@Lio

No idea, really. If it appears as a "normal" Zorro II/III board, it might work, but I really can't tell.

@nubechecorre

Quote:

I suppose you will notice the difference, but I don't have any benchmarks that would illustrate it. I don't think that it will make a major difference, really.