Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Wrong system emulated!



  • I’ve managed to list my CD32 games under the Amiga menu in Retropie. Despite the default config in Amiberry being CD32, when I launch games from this menu I get a 3.1 screen from (I think) the A500 and not the cd32! I have been through all the settings but just can’t work it out!



  • I don't have amiberry installed anymore but this is from the wiki
    https://github.com/midwan/amiberry/wiki/Using-Amiberry-WHDBooter-with-RetroPie-(Step-2)

    I think it may not create symlinks for the cd32 kickstart roms.
    ls -la /opt/retropie/configs/amiga/amiberry/whdboot/save-data/Kickstarts/
    you could try looking for the configuration to see where the cd32 and extension point to.

    Maybe they need to be renamed, or maybe a button press is needed to get the cd32 to boot.



  • @Efriim Thanks, I seem to have all the right kick roms. I don’t think I really understand symlinks, or what the roms should be called? I have a path to them in Amiberry, and when I start that, it used them fine. Just from the list, which now just returns me to the list and doesn’t load any Amiga load screen like it used to. This is a most frustrating issue!



  • @Wulmund
    I installed amiberry, I will set it up and maybe have a better frame of reference this evening (+08:00hours). The permissions are probably alright, if you added the roms through samba then it will default to user pi.
    Maybe the config.uae that was copied, depending on how it was edited and copied.
    You'll want to use a notepad++ or edit+ or "programmer's notepad" or nano, or xserver linux notepad etc. anyways not windows notepad because it won't save with the proper line breaks.

    Here are some useful commands and for symlinks.
    symbolic links are versatile and easy to use
    ln -s "filesystem/target" "filesystem/symlink"
    I read in the wiki that the amiberry installation generates some links to the bios files, but if the custom.uae we use points to the bios directly it shouldn't matter.

    you can read a link like this
    readlink "symlink"

    using ls with the options -la (long + all) will read ownership, permissions and hidden files in a directory
    ls -la ./
    it will also list where a symlink points to.

    sudo chown pi.pi ./file this will borrow root(uid:0) to change ownership and group to pi (uid:1000 gid:1000) adding option -R will do this recursively so be careful with that I guess.

    So the list isn't working? I can't discern if you are referencing the amiberry gui, or if it is returning to emulationstation.



  • @Efriim I will check the cd32.uae file I created and see - I think it refers to the roms in the location that amiberry uses and references on the gui. The list in emulationstation, when you click on the name of a cd32 game, get a black screen. Some text flashes up and disappears, then returns you back to the list item.



  • @Wulmund oh okay. you're welcome by the way, I'm happy to help.

    Is the cd32.uae able to boot to amiberry?

    With a text editor mentioned above, you could edit it and save it as the name of the 32 bit disc you want to start rom.uae
    there are a few lines to change so that it will boot I think

    use_gui=no
    cdimage0=,image

    maybe gui is okay, maybe they need more memory.

    If you initialize the run-command prompt when loading the rom, there is an option to launch with verbose logging. And this will give a log file that could help provide information to what is happening with that.



  • Sorry, maybe verbose logging is not applicable to amiberry.



  • @Efriim I appreciate your help! Should be straightforward to emulate a cd32 properly?I don’t want to give up!

    In the cd32.uae file it says:

    kickstart_rom_file_id=1E62D4A5,CD32 KS ROM v3.1
    kickstart_ext_rom_file_id=87746BE2,CD32 extended ROM

    Do these have to be the file names of the roms?



  • @Wulmund
    I'll try to get back to you on this, I have to work for a couple hours. The wiki isn't really providing the information I want about the BIOS names, and some of things I'm expecting to work just aren't like the symlinks it was supposed to make and the paths.

    I think I'll install WinUAE and see what works there first, so I have a better understanding of it.

    kickstart_rom_file_id=1E62D4A5,CD32 KS ROM v3.1

    that looks like it has the crc32, it has probably found that bios in the path, and it is probably something else that it needs.

    Do you mind trying out the other amiga emulators, I think there are at least 3. I'll be back with more.



  • @Wulmund
    Alright bro, lets do this.
    It looks you got the right KS ROMs, sorry if I was being confusing about it, it will give the id when the roms are available in the BIOS folder as long as you have those roms with the right crc they will be detected.

    Here is a program for checking sums in windows. Installing it adds a tab to the properties menu when you right click on a file.

    Make sure to use notepad+ or better for editing the .uae

    First lets change the nvram file to a location out of the system owned amiga folder where it probably has no write permissions, we could also name it after the game that we save this config for or anything different for the default uaeconfig.uae

    flash_file=/home/pi/RetroPie/roms/amiga/humans.nvr
    amiberry.cd_path=/home/pi/RetroPie/roms/amiga/
    

    Optionally we can change the cd path as well, this makes it easier to navigate for the cd. As an alternative to this, you could create the missing symlink for the default cd path by typing into the command line:
    cd /opt/retropie/emulators/amiberry/
    sudo ln -s /home/pi/RetroPie/roms/amiga ./cd32
    sudo ln -s /home/pi/RetroPie/roms/amiga ./disks

    There are a lot of options in the saved configurations, but the rest of the stuff for getting CD32 to work was in the amiberry gui.

    I started with Quickstart > Amiga model: CD32 |NTSC optional checked.
    This will set almost everything:
    CPU > 68020 & 24-bit
    Chipset > AGA |Extra:Cd32
    ROM > Main: CD32 KS ROM v3.1 rev 40.60 (512k) | Extended: CD32 extended ROM rev 40.60 (512k)

    HD/CD > CD drive checked| ... only select the cd file
    Then go to configuration and save it, reset it.



  • @Efriim hi thanks for this, I’m at work now but will try it out later and let you know how I get on.
    Other emulators, I tried fs-uae but it didn’t let me configure the controllers very well and had no default cd32 settings.



  • @Efriim bang head here
    It doesn’t work!
    The answer may be it’s own specific .uae file, this has added the .iso to the game list but still doesn’t work. Maybe it just has a problem with the format of the file names?



  • @Wulmund the QuickStart option in amiberry keeps defaulting to Amiga 500 no matter how many times I change it to cd32. Could that be part of the problem?



  • @Wulmund
    Yeah, that means it probably can't find the cd32 bios and extension. Look around for another one
    CD32 3.1 rev 40.60 & Extended rom 40.60, both 512k
    using that program; 'hashtab' can check the CRC
    CRC32=1E62D4A5 (CD32 KS ROM v3.1 rev 40.60)
    CRC32=87746BE2 (CD32 extended ROM rev 40.60)

    No possibly, when loading it up unless you load the .uae from the roms folder I think it will default to whatever the default uae is.

    Also most everything in linux is case sensitive, the config path pointing to /home/pi/RetroPie/roms/amiga, needs to have accurate capital lettering; RetroPie



  • @Efriim Sorry do you mean the cd32 kick roms I’ve got need replacing?
    They must be ok as games do load from amiberry.
    I think in the default.uae (or did I see it in another file) it refers to the aros built in rom, do maybe need to change that to the path/name of the actual rom, but don’t know if I can add another to refer to the extended rom file?



  • @Wulmund it was in amiberry.conf



  • @Wulmund
    I tried to highlight the important things to change in the game config. The $(FILE_PATH) can remain it is just pointing to the /home/pi/RetroPie/BIOS/ directory the same, but maybe it is a good idea to type out the full path.

    joyport1_mode=cd32joy
    kickstart_rom_file=$(FILE_PATH)/Kickstart-v3.1-rev40.60-1993-Commodore-CD32.rom
    kickstart_ext_rom_file=$(FILE_PATH)/CD32 Extended-ROM rev 40.60 (1993)(Commodore)(CD32).rom
    flash_file=/home/pi/RetroPie/roms/amiga/.nvr
    cd32cd=true
    cd32c2p=true
    cd32nvram=true
    cpu_24bit_addressing=true
    chipset=aga
    chipset_compatible=CD32
    cdimage0=/home/pi/RetroPie/roms/amiga/cdrom.iso
    
    config_description=CD32 Default
    config_hardware=true
    config_host=true
    config_version=4.1.0
    amiberry.rom_path=/opt/retropie/emulators/amiberry/kickstarts/
    amiberry.floppy_path=/opt/retropie/emulators/amiberry/disks/
    amiberry.hardfile_path=/opt/retropie/emulators/amiberry/
    amiberry.cd_path=/opt/retropie/emulators/amiberry/cd32/
    ; 
    ; *** Controller/Input Configuration
    ; 
    joyport0=mouse
    joyport0_autofire=none
    joyport0_friendlyname=Mouse
    joyport0_name=MOUSE0
    ; 
    joyport1=joy1
    joyport1_autofire=none
    joyport1_mode=cd32joy
    joyport1_friendlyname=Sony PLAYSTATION(R)3 Controller
    joyport1_name=JOY1
    ; 
    ; 
    ; 
    input.joymouse_speed_analog=2
    input.joymouse_speed_digital=10
    input.joymouse_deadzone=33
    input.joystick_deadzone=33
    input.analog_joystick_multiplier=15
    input.analog_joystick_offset=-1
    input.mouse_speed=100
    input.autofire_speed=0
    kbd_lang=us
    ; 
    ; *** Host-Specific
    ; 
    amiberry.vertical_offset=0
    amiberry.hide_idle_led=0
    amiberry.gfx_correct_aspect=1
    amiberry.kbd_led_num=-1
    amiberry.kbd_led_scr=-1
    amiberry.scaling_method=-1
    amiberry.use_analogue_remap=false
    amiberry.use_retroarch_quit=true
    amiberry.use_retroarch_menu=true
    amiberry.use_retroarch_reset=false
    ; 
    ; *** Common / Paths
    ; 
    use_gui=no
    kickstart_rom_file=$(FILE_PATH)/Kickstart-v3.1-rev40.60-1993-Commodore-CD32.rom
    kickstart_ext_rom_file=$(FILE_PATH)/CD32 Extended-ROM rev 40.60 (1993)(Commodore)(CD32).rom
    flash_file=/home/pi/RetroPie/roms/amiga/cd32.nvr
    cart_file=
    ; 
    ; *** Floppy Drives
    ; 
    floppy0=
    floppy0type=-1
    floppy1=
    floppy1type=-1
    floppy2=
    floppy3=
    cdimage0=/home/pi/RetroPie/roms/amiga/cdrom.iso
    nr_floppies=0
    floppy_speed=100
    ; 
    ; *** Hard Drives
    ; 
    ; 
    ; *** CD / CD32
    ; 
    cd_speed=100
    cd32cd=true
    cd32c2p=true
    cd32nvram=true
    ; 
    ; *** Display / Screen Setup
    ; 
    gfx_framerate=0
    gfx_width=768
    gfx_height=270
    gfx_refreshrate=60
    gfx_refreshrate_rtg=60
    gfx_lores=false
    gfx_resolution=hires
    gfx_lores_mode=normal
    gfx_linemode=none
    gfx_fullscreen_amiga=false
    gfx_fullscreen_picasso=false
    ntsc=true
    ; 
    ; *** CPU options
    ; 
    cpu_speed=real
    cpu_type=68ec020
    cpu_model=68020
    cpu_compatible=false
    cpu_24bit_addressing=true
    fpu_no_unimplemented=true
    fpu_strict=false
    compfpu=false
    cachesize=0
    ; 
    ; *** Memory
    ; 
    chipmem_size=4
    z3mapping=real
    fastmem_size=0
    a3000mem_size=0
    mbresmem_size=0
    z3mem_size=0
    z3mem_start=0x40000000
    bogomem_size=0
    gfxcard_hardware_vblank=false
    gfxcard_hardware_sprite=false
    gfxcard_multithread=false
    rtg_modes=0x112
    ; 
    ; *** Chipset
    ; 
    chipset=aga
    chipset_refreshrate=60.000000
    collision_level=playfields
    chipset_compatible=CD32
    rtc=none
    ksmirror_e0=false
    ksmirror_a8=true
    immediate_blits=false
    waiting_blits=automatic
    fast_copper=false
    ; 
    ; *** Sound Options
    ; 
    sound_output=exact
    sound_channels=stereo
    sound_stereo_separation=7
    sound_stereo_mixing_delay=0
    sound_frequency=44100
    sound_interpol=none
    sound_filter=off
    sound_filter_type=enhanced
    sound_volume_cd=0
    ; 
    ; *** Misc. Options
    ; 
    bsdsocket_emu=false
    


  • @Wulmund
    With the quickstart, it will load some of the default configurations of the one that you select. When I boot up though anyway, it will show the quickstart at amiga500, it doesn't mean it is selected until you load it and then it loads the defaults again.



  • @Wulmund
    Anyways I got the CD32 to boot with those bios and settings and it is also saving the nvram in the roms directory next to the iso. I've been trying to get The Humans to emulate properly, and there are like four different issues with the graphics and I can only get 2 of 4 right at a time.

    I don't yet know how to best set up the default settings, so that it could just identify the rom type and open the right config. But making the custom .uae files seems to work just as well.



  • @Efriim I’ve tried those settings in a .uae setting for the game. But they don’t work for me. Have changed the paths and been careful with spelling of paths. Also put the name of the .iso in and changed everything I can in the .cue of that game, but still nothing.
    I think we are out of things to try, even if I re-image the card and start from scratch again!



Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.