Yep. Thanks. This commandline works and yep this is only testing.I know WinUAE very well. At the moment this Amiga emulation in Mame/Mess is no competition against Winuae. But I would very much welcome it and am happy that the emulation will be just as good.
for Buddha
a2000n -zorro1 a2058 -zorro2 buddha -zorro2:buddha:ata_0:0 hdd -hard1 %s -fdc:0 35dd -flop1 %s -fdc:1 35dd -flop2 %s -homepath \Config -inipath .\Config
for a2091
a2000n -zorro1 a2058 -zorro1 a2091 -zorro1:a2091:scsi:0 harddisk -hard1 %s -fdc:0 35dd -flop1 %s -fdc:1 35dd -flop2 %s -homepath \Config -inipath .\Config
a2058 is the Expansion Ram.
But the a2000 will only boot with kick 3.1. (I think because the Bootblock from 2.04)
In combination with Floppy and Buddha HD, the A2000 does not want to boot (Kick 1.3 & kick 2.04) only with Kick 3.1 where you have to explicitly select the drive DF0 from the boot menu. I set up a hard disk with the a600 and mounted it with the A2000. Both boot (HD0,DF0) priorities are at 5. I don't even know if that's right. Always thought priority in HDs is 1 or 0. Maybe that's why the A2000 with kick 1.3 can't boot from DF0 when the HD is mounted. When I start HDtoolbox or do other things like renaming or anything else about saving to the floppy disk, mame freezes. Or I do something false what I forgot. It's been a long time since I worked with a real Amiga 2000. I have only an Amiga 4000 Tower /PPC..
Offtopic Info: The character in my commandline "%s" is a placeholder for the media/images of my frontend. Just so you don't get confused.
Offtopic 2: I somehow miss the access to the CHD's hard drives from the host (here windows) to manually copy files in and out.
greetings