i already have a spider as i have a mediator too but it works really bad, it's very slow and not compatible, moreover Spider uses DMA which is not allowed by AmigaOS 4.1FE (only the on board SCSI of the PPC), but i guessed that a Zorro III card doesn't suffer the same problem as on the official...
I Have a PPC Amiga 4000 not an AmigaNG, so i just will plug it on the zorro Slot. I arranged my system with an IDE Sd adapter with the SD slot in the frontal part of the tower and i installed different version of AmigaOS on some industrial SD cards, i installed AmigaOS 4.1.FE too and sometimes...
i tested it with AmigaAMP 2.25 too but no luck, i cannot understand what i do wrong.
I upgraded the Delfina.library and put the mhimdev.library in libs LIBS:MHI/ copied the delfinampeg.device in devs: and selected mhi in amigaAMP but it doesn't work at all
I am not able to use my delfina lite with MHI and delfinampeg.devide for mp3 decoding, using AmigaAMP 3 i always get an error message, just like MHI library cannot find any mpga hardware.
I followed the instructions i found here.
Amplifier works ok with delfinampeg.device though
i plugged an SD reader to the IDE port and i use it to make bootable installations (Morphos 1.4.5., AmigaOS 4.1FE, AmigaOS 3.2 as emergency boot when the main Boot partition corrupts and finally to backup my system) i was thinking to use it to transfer files using a FAT32 formatted SD.
I know...
Hello,
is it possibile to read a FAT formatted HD on the IDE port of the amiga 1200?
I tried but failed i'm in doubt if it's an hardware related issue or a software one.
Who can explain?
i changed several PSU for my towered A4000 heavily expanded and i can suggest you to use a good adapter that provides strong 5V rail.
i bought one of this https://www.amibay.com/threads/a4000-direct-atx-adapter-for-modular-corsair-and-seasonic-psus.2442346/
and i can give you a very good...
AmigaOS 4.1FE works ok now with 3.1 roms.
Roms 3.2 gave that DF0: error message on 4.1 booting up but i was able to manage installation.
Does anyone know if 3.2.2 roms fixed this kind of issues?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.