Hi Gunnar,
I'm running Amibian on PI3. The emulation works smooth on OS3.1,
but when I'm trying to get an ISO file loaded as CD-Rom,
i have no luck so far.
In the config I've pointed the system to an Amiga OS v3.9 ISO
(ISO file I know for sure that is working)
and on the Amiga side I've installed AmiCDFS.
I also tested CacheCD Filesystem.
Somehow those ConfigĀ“s don't want play together.
I checked out other ISOs too, but on Amiga-Side they are not recognized.
How can I use CD-Rom Images with Amibian ?
Non of the scsi.device, ide.device or uaehf.device responds
as CD-Rom on Amiga Side.
Can You help me and maybe other Users with the same Problem.
Marc
I've got the ClassicWB 3.1 working perfectly on my Amibian RPi 3B without issues. While the 3B+ is a little different, overall it should work without issues.
Note: I have not been able to get ClassicWB 3.5 or ClassicWB 3.9 to work properly in Amibian, but I am guessing that it is an issue with the configuration or how it reads the HDFs, as I got Workbench 3.5 and 3.9 working properly in Amibian (had to first build in UAE).
I've got a Raspberry Pi 3B+ up and running with the UAE build from ClassicWB , and online as well. I've previously created .HDF images from my various Amigas. Is it possible to modify them so that they work on Amibian please? If so, how do I do it ? I'm happy to create new hdf images if needs be.
So, I got AmigaOS 3.5 and 3.9 both built using WinUAE, and bringing them into the newest Amibian (1.4.1001) working perfectly (well, I got them to boot into the Workbench of each, and played around with them a little). Haven't stress-tested as of yet, but I can verify it works.
Note: I tried to follow the documentation Gunnar posted on the Facebook where the user built for a CF card for an A1200 system, and it didn't work.
I did a normal build-out in WinUAE 3.6.1 (2018.03.04) 64-bit, and it worked perfectly.
I don't know if these are correct, but this is what I used:
CPU and FPU Tab
- CPU/FPu: 68020/68881
- More Compatible checked
- CPU Emulation speed: "Fastest Possible"
- Advanced JIT Settings - Cache Size: 8 MB
- FPU Support checked, Constant jump checked, Hard flush unchecked, No flags checked, Direct selected.
Chipset Tab:
- Chipset: AGA
- Chipset Extra: A1200
- Options: Keyboard Connected checked, Immediate Blitter unchecked, Wait for blitter checked
Video Port display hardware: Autodetect
- Collision Level: Sprites and Sprites vs. Playfield
Advanced Chipset Tab: I checked Compatibility Settings which greyed out everything else
ROM: KS ROM v3.1 (A1200) rev 40.68 (512k) [391773-01/391774-01]
RAM Tab:
- Chip: 2 MB
- Slow: None
- Z2 Fast: 8 MB
- Z3 Fast: 8 MB
- 32-bit Chip: 16 MB
Advanced Memory Settings
- Z2 Fast Ram #1 [8192k]: 8 MB
- Z3 mapping mode: Automatic
Since I want the ability to build out WHDLoad on any of these, I am sizing the system hard drive at 2000 MB (not a full 2GB as the Amiga system doesn't see it), but I would recommend 512 MB if you don't need the space.
When building this out, make sure the main system hard drive is always listed first and as DH0. I ran into some issues when I removed it fully and tried to add a new one. If you have to create a new hard-file, just Edit the current DH0 hard drive. If it is removed, even if it's listed as DH0, I had issues trying to install 3.5 or 3.9 on it (it would see the first "Hard Drive" in my list, which was a shared Programs directory).
For the CD mounting for 3.5/3.9, make sure you have "CDFS automount CD/DVD drives" enabled.
Also, when I installed 3.9, I copied my 3.5 setup and System drive, and installed 3.9 over 3.5 instead of 3.9 over 3.1, as I had nothing but issues trying to install 3.9 and then import into Amibian.
Lastly, once the drive showed up in WB3.1 (booted from floppies before install), I just formatted the normal way (select NDOS drive, right click the title bar and select Format from the Icons menu), then installed 3.1, and was able to upgrade from there.
That should be it. You can pull the drive in, and set your config up as you would for a 3.1 Workbench, and they should come right up. I did have some times where 3.5 would take as little time coming up, 3.9 would take a little longer, but they come up and function fine.
I have also experienced issues with Systems not booting depending on the version of the kickstart you are using.
When creating the .hdf in WinUAE make sure you change the option in Location from "Extended" to "External"
I've tried what you're recommending. The problem is trying to copy those files into a folder via Windows, as some of the files are not supported name-types in Windows.
I'm actually going to try mounting the ISO in WinUAE or Amiga Forever, creating a Hard Disk File, and copying the files to that HDF in an AmigaOS, as it should keep the structure. Then you can just copy the HDF to your Amibian build and mount it. I'll let you know if it works properly.
UPDATE: I tried everything I could think of:
Loading the files into an HDF from another load that supports the SCSI CDRom works, but I keep getting memory faults when trying to run the 3.9 installer.
When I do this in AmigaOS 3.1 from Amiga Forever, it seems to work perfectly, but nothing but issues when trying to do it from Amibian. I definitely would recommend first getting the CDRom mount to work properly in Amibian (definitely test with 3.1 first).
Afterwords, I would recommend testing the 3.9 installer. Gunnar, if you need me to test, please let me know what you would like me to do.
UPDATE #2:
So, from what I've found is that:
- Amibian does not support the CDRom drive in anything but the CD32 system (There was a post I found that Gunnar stated as much, but I didn't save the link. I believe he wants to update the support in future releases.
- I've moved the AmigaOS 3.9 files from CD to HDF via WinUAE (through Amiga Forever) and I run into memory errors every time, regardless of how much memory I give the virtual Amiga system.
- I have also tried building a 3.9 system in WinUAE, but when I bring the HDF to the Amibian built, it sees the HDF file as an unformatted drive. I could just be doing something wrong in how the file is built, but I have had this issue with every HDF I create in something other than the RPi Amibian build. These HDFs work fine on WinUAE or Amiga Forever emulation (And I have tried both UAE and ISO HD emulation)
At this point, I don't know what else to do.
Note: I DID get ClassicWB working with their pre-built "SYSTEM.HDF" drive and my 3.1 workbench ADF file, so I know it's not Amibian rejecting all foreign HDFs, just seems to be 3.9 build.
Kickstart tested: 3.1 build 40.68 and 40.69 builds
Thanks Piana,
i will give it a try when i get time for it.
Problem is connected with lack of support of CD ROM in Amiga OS3.1. In version 3.9 there should be no problem (if some is wrong try to launch option from instalation CD).
What I suggest is to copy files from CD ROM into standard folder and next map this folder as an additional harddisk.