Note: There was a mistake in the video, the GUI Hotkey does work, but I missed a line of config in the .uae file. I have included details in the video description and provided an updated BOOT.ZIP file, link also in video description. Upcoming videos: I'll be making a follow up video to demonstrate Workbench 3.2 running from the USB Disk, without the need to unlock Amiberry. This video will also include the .uae settings to configure monitor mode and screen resolution, joystick autofire, CPU type, kickstart ROM etc. If you'd like to see that video (and others like it), please subscribe and click on the bell to be notified when new content is available.
This is amazing! I thought something like this was probably possible, but yeah the thought of running a full WB installation on this with an HD image and whdload is quite intriguing :)
Hi Junnu. I have Workbench 3.2 running from HDF. Best way to get it running is build an Amiga images using another machine with an emulator of your choice, WinUAE, FS-UAE, Amiberry or whatever - then copy the HDF files on to your A500 Mini USB Disk. Use the unlock process from the video, and configure the HDF drives in Amiberry :)
Locked up my A500 mini after getting WB1.3 w/extras & WB 2 working, but crashed the A500 mini soon after. After much testing I found that my Gampad had failed. I tried a new one and so far everything is good.
Better way; Open Pandory (after installing it). Choose "Load Core", choose "Team Pandory Axxx Core", then "Start Core" On boot screen, press menu. Now you got Amiberry with pad and keyboard working" Now load AFD or HFD. B key is "Enter" Choose "Reset" to startup the disc.
The video was made quite some time ago, but agree - the later version of Pandory does offer more flexibility - mainly due to newer version of Amiberry in the case of the Amiga core
brilliant! thx for that. pls upload the setup (without the wb1.3.adf) to mega or something to make it easier for your viewers. i'm sure we can all find/supply our own wb disk and avoids any legal issues that might arise.
Thanks. There is not really anything much to share/upload. All you really have to do is extract the Citadel LHA (or another may well work) to delete disk1, then re-pack the LHA. All this is doing is preventing the A500 Mini from booting into anything useful, just to the kickstart rom. Next, start the LHA on the A500 Mini. This will create a .uae file. Using another machine, ideally Linux based, edit the .uae file (created by the Amiberry emulator on the A500 Mini to include: use_gui=yes (I usually put it at the end/bottom of the .uae file). Then make sure you set the permissions for the .uae file to read only (very important, or the A500 Mini will strip out / overwrite the .uae config). Put the USB stick back in the A500 Mini and start the LHA. If you've followed all the steps, you should get the Amiberry config screen / gui. Hope that helps.
I have added a link on the description so you can download a ready made boot.lha and boot_ol.uae. They are in a zip file called boot.zip. You can get the zip file here: mega.nz/file/U6RCiCDK#WC-Hh7d9KOopllSkRVEji68POao6naKSkzBV_W0CSLs - although it will (probably) not retain the permissions on the boot_ol.uae file, so you will (may) still need to set these (all to Read Only)
@@RTSRetroTechShed today for the first time I Google whats Amiberry. I used to play couple of Amiga games on PC via winUAE. But Amiga 500 mini is far more better. I am still depressed that my real Amiga I had since early 90's doesnt exists anymore. I left her for many years in my parents appartment and during some ,,removal of old unused stuff,, she was put away. It hurts, but my mistake...
Watching this video I was thinking why didn't you make a custom Amiberry config on the PC with all the settings you want with RAM CPU etc including pointing it at a prepared Amiga HD image that it should boot? Then put it on the SD card (in this case the TEST folder)? Would that work? I'm just asking I'm thinkg of getting an a500 mini if what I'm saying would work. I might just be better off getting a Pi400 - I'm sorta thing that might be best. Maybe I'll get a Mini I don't know (just this minute thinking about my options of what to buy) - but I just thought I'd throw this suggestion out there for anybody to comment on or even use my suggestion should that be something that would work?
Hi Shane. There is another video on the channel that shows what you've described (Amiberry config and HDF images prepared on another machine, a Raspberry PI): th-cam.com/video/CxQRs-NTqoY/w-d-xo.html
Well done! I'm definitely going to study Amiberry now. I'm having serious doubts about if I should buy an A500 Mini at all, especially as I'm a long term Amigan who started with an A500 fitted with Kickstart 1.3 plus a 1084S monitor with the Tenstar Games pack and Photon Paint. The A500 Mini does look nice, but it's too small. Can you hack it to connect to any kind of network as well? BTW, were you using Linux on that computer you used to set up the USB stick?
Hi Paul. Personally, much as I like the look of the A500 Mini, I find the most useful thing about it is the Mouse - to connect to my MiSTer FPGA in an Amiga 500 case - rather than using an original tank mouse with a ball (so I bought another one of those). The video link is here if you want to take a look: th-cam.com/video/OSVJgqWEJg8/w-d-xo.html - although I have since upgraded that machine with a MiSTress board, more details of that on the community page. The machine I used to setup the USB stick is a Raspberry PI 4 running Raspberry PI OS Buster, housed in a DeskPI case. It might be possible to get the A500 Mini connected to a network. It's a case of plugging in a USB/Ethernet card - and see if it get's an IP address (check client list on router or DHCP server). If it get's an address, then enabling the bsdsocket.library in Amiberry should do the trick - although this is not a full TCP/IP stack, so functionality will be limited, but its ok for Web Browsing, FTP, Telnet etc.
Is it possible to update the version of Amiberry on the A500 Mini from version 3.3 to version 4.1.5? If so, can it be possible to play physical Amiga 500 floppy disks on the A500 Mini through a USB floppy disk drive?
Anyway to save state? I've tried the normal way, Home button and I've tried from Amiberry. Using the home button I can save, but when I reload it just brings me back to amiberry and not the game. It's then not possible to resume game. Using the save state in amiberry does nothing.
I think the save state only really works for WHDLoad games. If you're booting using a config (LHA and .uae) with it's own ADF/HDF - then I've not managed to get it working (yet) - only the config. The save state is stored in a hidden folder .a500states (on the USB Disk). In this video, I show how to locate the save state and create a new profile: th-cam.com/video/CxQRs-NTqoY/w-d-xo.html - . It doesn't actually save the settings on exit from Amiberry as such, because these are stored in a private folder (as far as I can tell), but by configuring Amiberry the way you want, then using home, down on joystick and save state - you can save the config. Hope that helps :)
Hi! I tried hard to save my custom configuration but it doesnˋt work (with or without write protection on the modified lha-archive). Do you have an idea how to fix that? Thank you in advance!
Great work. Leaning closer to wanting one after all, having seen this. A question - is it possible to delete the pre-loaded games? Thanks for the excellent video.
Hi Alex, thanks. I’m not aware of a way to delete the pre-loaded games, but I’ll investigate whether they can be hidden when I get a chance and let you know if I find anything useful
It should work if the lines config lines are in the BOOT_ol.uae file, but I have created a new set of configs though which may make life a little easier. They are linked in the description of this video: th-cam.com/video/CxQRs-NTqoY/w-d-xo.html
Good method. Did you ever figure out how to save settings when leaving the amiberry environment? I found that it seems to save the HDF part but nothing else, for example i have to manually select the cpu, the ram size everytime on exiting and relaunching
I've not managed to save the settings from the Amiberry GUI, but you can edit the BOOT_ol.uae to include most of the settings you might want to change (including screen resolution). If you edit the BOOT_ol.uae, remember to set the permissions back to read only afterwards.
@@RTSRetroTechShed Is the reason the settings are not saved due to setting it read only? I've played a lot with WinUAE over the years but never Amiberry.
Hi Paul. Yes, the save state is stored in a hidden folder .a500states (on the USB Disk). In this video, I show how to locate the save state and create a new profile: th-cam.com/video/CxQRs-NTqoY/w-d-xo.html - . It doesn't actually save the settings on exit from Amiberry as such, because these are stored in a private folder (as far as I can tell), but by configuring Amiberry the way you want, then using home, down on joystick and save state - you can save the config. Hope that helps :)
Hi Nick. No, it's not possible to store the configuration in Amiberry because the folder is private. However, see my reply to Paul on how to save the config using the save state option. If you are using ADF/HDF files, it may not actually save the state, but will allow you to create a profile/config using the save state .uae file which will capture the Amiberry settings being used.
That's amazing. Can't wait to try out Say for the first time in 30 odd years. Is it okay with I host your boot files on a website I'm making about the Amiga mini? I will give full credit and include a link to this video to explain it all
Very useful, I've been trying to get to a linux console, found an open serial port on the motherboard, just need a USB to RS232 board, didn't know user, found user is redquark. BTW No need to edit the lha file... Just the config and make read only... Then change settings and mount HD on / was hoping to edit /etc/passwd from within workbench but no luck, can list directories only, even in user folder. filesystem appears mounted read only from within Amiberry...Actually cant even read file contents. Ideas????
Hi David. Sounds like you got further than me :) Yes, quite right, no need really to edit the LHA file, just a nice to have to get the kickstart rom splash screen, unlock can be achieved by simply editing the .uae file and making it read only. I was quite content with being able to boot ADF/HDF - anymore than that and I'd run Amiberry on PI400 or similar. You could try a USB/Ethernet adapter if you really want to get into it - and scan it with some more "advanced" tools (which are perhaps not for discussion here) :)
@@RTSRetroTechShed I always have to replace the config directory to load my settings, so that all my custom settings from my custom file gets loaded. It's sets automatically back to /usr/share/amiberry/conf/ within each startup. But at least it's a one-step task only.
@@RTSRetroTechShed Yes, I'm having just as much fun poking around the hardware than playing the games. Really glad to get working workbench too. Im guessing that licencing may have played its part in why it was locked down so much, but not being able to load ADFs, or run workbench really limits the experience. Overall I always found the original A500 too big for a desktop and this thing takes up hardly any space. The detail thats been captured in this model is impressive. Now that the AmiBerry interface is open and ADF's work I noticed the 2nd FDD Light also works, something you don't see with WHDLoad. One more thing, I noticed your F/W allows more settings than mine, I cant set RAM, CPU, JIT etc, now I can.
You can't save the settings, presumably the folder has permissions set - or the variant of Amiberry is further locked down. All I would be inclined to use it for is booting ADF images. A good working knowledge of Amiberry is advisable. As always, it's at your risk. If in doubt, don't do it.
Tried to recreate all steps 1:1 as you did but with different result... the only thing i did different was to unpack and repack back to LHA under Ubuntu WSL.. and instead of kickstart image i'm getting WHDLoad boot screen with "Setpatch.... Not Found" error :( idk what is wrong repacked LHA file looks fine...
Hi. I've just tested it using LHA on Raspberry PI Buster (Debian Linux) to unpack the LHA - and after deleting Disk.1 from the Citadel directory/folder, to repack the LHA and it works fine for me. The LHA must ONLY contain the Citadel directory/folder and Citadel.info file.I'd suggest naming the resulting LHA file to something like BOOT.LHA and put it on the USB Disk in it's own directory/folder, e.g. TEST.
Thx a lot for the cool guide! Unfortunetly it doesnt work for me. I got the UI up and running but when I start with a ADF file it always shows me an error that DF0 is WRITE PROTECTED :-(
Are you able to spin up a Linux machine to change the permissions? Maybe a Linux VM using VMware Player? It's free and you can get it here: www.vmware.com/uk/products/workstation-player.html
@@RTSRetroTechShed just tried via Ubuntu but when i go to file permissions i do not have same options as you, i have owner option of Access: Read and write and the Group options of Access and Others both set to Read only. Would i just change everything to Read Only?
Yep sorted it by changing to Read Only, working … just need to plug a keyboard in and mess with some configurations. Thanks again look forward to anymore Amiga related content .
That's a good option if you only want to use workbench + whatever else you copy to the USB (inside the boot-data folder). In the video, I did say this is one method. I couldn't include the boot-data option without making the video too long. If you want to boot ADF images (e.g. games) and/or make config changes (e.g. CPU type or video mode) on the fly (as opposed to pre-configuring the .uae file) - then the method in the video might be the best option
I've got a weird issue; whenever I change height/width under game settings I can no longer get the GUI, I just get the 1.3 workbench screen, and then I need a fresh copy of BOOT_ol.uae If I leave game settings alone it loads the GUI fine everytime but some games are then cut off.
If you want to change the screen resolution, you will need to make the change in the BOOT_ol.uae and make sure you set the permissions afterwards to read only again. If you change them using the A500 Mini, the BOOT_ol.uae will be overwritten.
@@RTSRetroTechShed I tried that before but for some reason it ignored the settings in BOOT_ol.uae. I just tried the method Crazy Burger posted on his channel and that worked.
Note: There was a mistake in the video, the GUI Hotkey does work, but I missed a line of config in the .uae file. I have included details in the video description and provided an updated BOOT.ZIP file, link also in video description.
Upcoming videos: I'll be making a follow up video to demonstrate Workbench 3.2 running from the USB Disk, without the need to unlock Amiberry. This video will also include the .uae settings to configure monitor mode and screen resolution, joystick autofire, CPU type, kickstart ROM etc. If you'd like to see that video (and others like it), please subscribe and click on the bell to be notified when new content is available.
This is amazing! I thought something like this was probably possible, but yeah the thought of running a full WB installation on this with an HD image and whdload is quite intriguing :)
Hi Junnu. I have Workbench 3.2 running from HDF. Best way to get it running is build an Amiga images using another machine with an emulator of your choice, WinUAE, FS-UAE, Amiberry or whatever - then copy the HDF files on to your A500 Mini USB Disk. Use the unlock process from the video, and configure the HDF drives in Amiberry :)
Locked up my A500 mini after getting WB1.3 w/extras & WB 2 working, but crashed the A500 mini soon after. After much testing I found that my Gampad had failed. I tried a new one and so far everything is good.
Thank you very much guy!, it woks perfectly on my A500 mini. Hope you to have more subscribers, you deserve it sincerly. Best regards from France 👍
Thanks Bart :)
Better way; Open Pandory (after installing it). Choose "Load Core", choose "Team Pandory Axxx Core", then "Start Core"
On boot screen, press menu.
Now you got Amiberry with pad and keyboard working"
Now load AFD or HFD. B key is "Enter"
Choose "Reset" to startup the disc.
The video was made quite some time ago, but agree - the later version of Pandory does offer more flexibility - mainly due to newer version of Amiberry in the case of the Amiga core
All done in a typical Amiga fashion!
brilliant! thx for that. pls upload the setup (without the wb1.3.adf) to mega or something to make it easier for your viewers. i'm sure we can all find/supply our own wb disk and avoids any legal issues that might arise.
Thanks. There is not really anything much to share/upload. All you really have to do is extract the Citadel LHA (or another may well work) to delete disk1, then re-pack the LHA. All this is doing is preventing the A500 Mini from booting into anything useful, just to the kickstart rom. Next, start the LHA on the A500 Mini. This will create a .uae file. Using another machine, ideally Linux based, edit the .uae file (created by the Amiberry emulator on the A500 Mini to include: use_gui=yes (I usually put it at the end/bottom of the .uae file). Then make sure you set the permissions for the .uae file to read only (very important, or the A500 Mini will strip out / overwrite the .uae config). Put the USB stick back in the A500 Mini and start the LHA. If you've followed all the steps, you should get the Amiberry config screen / gui. Hope that helps.
Andre, agreed, it'd be much more convenient if RTS could make those files available on Mega. Sadly, he's not prepared to do that.
I have added a link on the description so you can download a ready made boot.lha and boot_ol.uae. They are in a zip file called boot.zip. You can get the zip file here: mega.nz/file/U6RCiCDK#WC-Hh7d9KOopllSkRVEji68POao6naKSkzBV_W0CSLs - although it will (probably) not retain the permissions on the boot_ol.uae file, so you will (may) still need to set these (all to Read Only)
@@RTSRetroTechShed thank you so much mate, much appreciated :)
@@RTSRetroTechShed Thanks RTS - you're a champion 👋👋
I say: this is too much I dare to do.
But great work anyway!!!
Thanks :)
@@RTSRetroTechShed today for the first time I Google whats Amiberry. I used to play couple of Amiga games on PC via winUAE. But Amiga 500 mini is far more better.
I am still depressed that my real Amiga I had since early 90's doesnt exists anymore. I left her for many years in my parents appartment and during some ,,removal of old unused stuff,, she was put away. It hurts, but my mistake...
I sold my original Amiga 500 in the early 90s (a very early 1987 model with 1.2 kickstart rom), but have since bought another for the collection :)
@@RTSRetroTechShed lucky 👍 in my case power supply, tv adapter, joystick and huge box of 💾💾💾💾 remains.
Awesome. A very clever little hack.
Thanks, hope it's useful :)
Watching this video I was thinking why didn't you make a custom Amiberry config on the PC with all the settings you want with RAM CPU etc including pointing it at a prepared Amiga HD image that it should boot? Then put it on the SD card (in this case the TEST folder)? Would that work?
I'm just asking I'm thinkg of getting an a500 mini if what I'm saying would work. I might just be better off getting a Pi400 - I'm sorta thing that might be best. Maybe I'll get a Mini I don't know (just this minute thinking about my options of what to buy) - but I just thought I'd throw this suggestion out there for anybody to comment on or even use my suggestion should that be something that would work?
Hi Shane. There is another video on the channel that shows what you've described (Amiberry config and HDF images prepared on another machine, a Raspberry PI): th-cam.com/video/CxQRs-NTqoY/w-d-xo.html
Surely the boot.lha archive can be made a whole lot smaller by deleting all of the disk images within it?
Yes, quite right. In the linked file on the video description, there are no disk images, it's just a dummy WHDLoad
Oh yes, thank you very much!
You are welcome! :)
Well done! I'm definitely going to study Amiberry now. I'm having serious doubts about if I should buy an A500 Mini at all, especially as I'm a long term Amigan who started with an A500 fitted with Kickstart 1.3 plus a 1084S monitor with the Tenstar Games pack and Photon Paint. The A500 Mini does look nice, but it's too small. Can you hack it to connect to any kind of network as well? BTW, were you using Linux on that computer you used to set up the USB stick?
Hi Paul. Personally, much as I like the look of the A500 Mini, I find the most useful thing about it is the Mouse - to connect to my MiSTer FPGA in an Amiga 500 case - rather than using an original tank mouse with a ball (so I bought another one of those). The video link is here if you want to take a look: th-cam.com/video/OSVJgqWEJg8/w-d-xo.html - although I have since upgraded that machine with a MiSTress board, more details of that on the community page. The machine I used to setup the USB stick is a Raspberry PI 4 running Raspberry PI OS Buster, housed in a DeskPI case. It might be possible to get the A500 Mini connected to a network. It's a case of plugging in a USB/Ethernet card - and see if it get's an IP address (check client list on router or DHCP server). If it get's an address, then enabling the bsdsocket.library in Amiberry should do the trick - although this is not a full TCP/IP stack, so functionality will be limited, but its ok for Web Browsing, FTP, Telnet etc.
Is it possible to update the version of Amiberry on the A500 Mini from version 3.3 to version 4.1.5? If so, can it be possible to play physical Amiga 500 floppy disks on the A500 Mini through a USB floppy disk drive?
Maybe, if Retro Games include it as part of a firmware update
So cool man! Tanx a lot.
No worries :) hope it's useful
Anyway to save state? I've tried the normal way, Home button and I've tried from Amiberry. Using the home button I can save, but when I reload it just brings me back to amiberry and not the game. It's then not possible to resume game. Using the save state in amiberry does nothing.
I think the save state only really works for WHDLoad games. If you're booting using a config (LHA and .uae) with it's own ADF/HDF - then I've not managed to get it working (yet) - only the config. The save state is stored in a hidden folder .a500states (on the USB Disk). In this video, I show how to locate the save state and create a new profile: th-cam.com/video/CxQRs-NTqoY/w-d-xo.html - . It doesn't actually save the settings on exit from Amiberry as such, because these are stored in a private folder (as far as I can tell), but by configuring Amiberry the way you want, then using home, down on joystick and save state - you can save the config. Hope that helps :)
cool got mine working now thanks for info
Excellent :)
Hi!
I tried hard to save my custom configuration but it doesnˋt work (with or without write protection on the modified lha-archive). Do you have an idea how to fix that? Thank you in advance!
Hi, I'd need a bit more information on the steps you've used and the problems you are having
Why are you messing around in Amiberry when the raspi itself and it's debian based operating system can handle LHA by itself?
I just didn't have LHA installed at the time. I do now :)
Great work. Leaning closer to wanting one after all, having seen this. A question - is it possible to delete the pre-loaded games? Thanks for the excellent video.
Hi Alex, thanks. I’m not aware of a way to delete the pre-loaded games, but I’ll investigate whether they can be hidden when I get a chance and let you know if I find anything useful
@@RTSRetroTechShed Nice one. Appreciate all the effort you are putting in for the clueless amateurs like me. You're a star.
I just seem to get the disk v1.3 screen when I load the BOOT file, i've checked it's uae and the lines are there. any ideas? thanks
It should work if the lines config lines are in the BOOT_ol.uae file, but I have created a new set of configs though which may make life a little easier. They are linked in the description of this video: th-cam.com/video/CxQRs-NTqoY/w-d-xo.html
@@RTSRetroTechShed i'm not sure what I was doing wrong but the new set works great, thanks so much!
No worries, glad it's working for you :)
Good method. Did you ever figure out how to save settings when leaving the amiberry environment? I found that it seems to save the HDF part but nothing else, for example i have to manually select the cpu, the ram size everytime on exiting and relaunching
I've not managed to save the settings from the Amiberry GUI, but you can edit the BOOT_ol.uae to include most of the settings you might want to change (including screen resolution). If you edit the BOOT_ol.uae, remember to set the permissions back to read only afterwards.
@@RTSRetroTechShed Is the reason the settings are not saved due to setting it read only? I've played a lot with WinUAE over the years but never Amiberry.
Hi Paul. Yes, the save state is stored in a hidden folder .a500states (on the USB Disk). In this video, I show how to locate the save state and create a new profile: th-cam.com/video/CxQRs-NTqoY/w-d-xo.html - . It doesn't actually save the settings on exit from Amiberry as such, because these are stored in a private folder (as far as I can tell), but by configuring Amiberry the way you want, then using home, down on joystick and save state - you can save the config. Hope that helps :)
Hi Nick. No, it's not possible to store the configuration in Amiberry because the folder is private. However, see my reply to Paul on how to save the config using the save state option. If you are using ADF/HDF files, it may not actually save the state, but will allow you to create a profile/config using the save state .uae file which will capture the Amiberry settings being used.
That's amazing. Can't wait to try out Say for the first time in 30 odd years. Is it okay with I host your boot files on a website I'm making about the Amiga mini? I will give full credit and include a link to this video to explain it all
Thanks :) . Yes, feel free to share the files - they don't contain any software
How make in wb 1.3 fullscreen
Hi Adis. If you watch this video and download the config files linked in the description it may help you: th-cam.com/video/CxQRs-NTqoY/w-d-xo.html
Very interesting
Very useful, I've been trying to get to a linux console, found an open serial port on the motherboard, just need a USB to RS232 board, didn't know user, found user is redquark. BTW No need to edit the lha file... Just the config and make read only... Then change settings and mount HD on / was hoping to edit /etc/passwd from within workbench but no luck, can list directories only, even in user folder. filesystem appears mounted read only from within Amiberry...Actually cant even read file contents. Ideas????
Hi David. Sounds like you got further than me :) Yes, quite right, no need really to edit the LHA file, just a nice to have to get the kickstart rom splash screen, unlock can be achieved by simply editing the .uae file and making it read only. I was quite content with being able to boot ADF/HDF - anymore than that and I'd run Amiberry on PI400 or similar. You could try a USB/Ethernet adapter if you really want to get into it - and scan it with some more "advanced" tools (which are perhaps not for discussion here) :)
@@RTSRetroTechShed I always have to replace the config directory to load my settings, so that all my custom settings from my custom file gets loaded. It's sets automatically back to /usr/share/amiberry/conf/ within each startup. But at least it's a one-step task only.
Dave, please make some videos on your discoveries 🙂
@@RTSRetroTechShed Yes, I'm having just as much fun poking around the hardware than playing the games. Really glad to get working workbench too. Im guessing that licencing may have played its part in why it was locked down so much, but not being able to load ADFs, or run workbench really limits the experience. Overall I always found the original A500 too big for a desktop and this thing takes up hardly any space. The detail thats been captured in this model is impressive. Now that the AmiBerry interface is open and ADF's work I noticed the 2nd FDD Light also works, something you don't see with WHDLoad. One more thing, I noticed your F/W allows more settings than mine, I cant set RAM, CPU, JIT etc, now I can.
@@txtworld Ha ha that sounds like a lot of work
Hey... manipulating those settings in unlocked GUI of Amiberry can permanently brick device or not?
You can't save the settings, presumably the folder has permissions set - or the variant of Amiberry is further locked down. All I would be inclined to use it for is booting ADF images. A good working knowledge of Amiberry is advisable. As always, it's at your risk. If in doubt, don't do it.
Tried to recreate all steps 1:1 as you did but with different result... the only thing i did different was to unpack and repack back to LHA under Ubuntu WSL.. and instead of kickstart image i'm getting WHDLoad boot screen with "Setpatch.... Not Found" error :( idk what is wrong repacked LHA file looks fine...
Hi. I've just tested it using LHA on Raspberry PI Buster (Debian Linux) to unpack the LHA - and after deleting Disk.1 from the Citadel directory/folder, to repack the LHA and it works fine for me. The LHA must ONLY contain the Citadel directory/folder and Citadel.info file.I'd suggest naming the resulting LHA file to something like BOOT.LHA and put it on the USB Disk in it's own directory/folder, e.g. TEST.
Good news though... besides that I didn't see kickstart image as you I could still edit .uae file and gain access to Amiberry GUI :)
Excellent, then you've basically "cracked" it. The LHA file manipulation is kind of optional anyway.
Thx a lot for the cool guide!
Unfortunetly it doesnt work for me. I got the UI up and running but when I start with a ADF file it always shows me an error that DF0 is WRITE PROTECTED :-(
Got it ;) I needed to remove the WHDLoad config first so he boots from ADF file!
That's great :)
Trying this on windows PC, used Winuae to extract and prepare the boot.lha, but having problems trying to change file permissions in windows.
Are you able to spin up a Linux machine to change the permissions? Maybe a Linux VM using VMware Player? It's free and you can get it here: www.vmware.com/uk/products/workstation-player.html
@@RTSRetroTechShed thanks for quick reply quick reply, will try it on Ubuntu via Virtual Box
@@RTSRetroTechShed just tried via Ubuntu but when i go to file permissions i do not have same options as you, i have owner option of Access: Read and write and the Group options of Access and Others both set to Read only.
Would i just change everything to Read Only?
If you set all permissions to Read Only, that should do the trick
Yep sorted it by changing to Read Only, working … just need to plug a keyboard in and mess with some configurations. Thanks again look forward to anymore Amiga related content .
It's far easier just to make a Workbench whdload .lha file, copy to USB, boot it directly from the Mini home screen.
That's a good option if you only want to use workbench + whatever else you copy to the USB (inside the boot-data folder). In the video, I did say this is one method. I couldn't include the boot-data option without making the video too long. If you want to boot ADF images (e.g. games) and/or make config changes (e.g. CPU type or video mode) on the fly (as opposed to pre-configuring the .uae file) - then the method in the video might be the best option
I've got a weird issue; whenever I change height/width under game settings I can no longer get the GUI, I just get the 1.3 workbench screen, and then I need a fresh copy of BOOT_ol.uae If I leave game settings alone it loads the GUI fine everytime but some games are then cut off.
If you want to change the screen resolution, you will need to make the change in the BOOT_ol.uae and make sure you set the permissions afterwards to read only again. If you change them using the A500 Mini, the BOOT_ol.uae will be overwritten.
@@RTSRetroTechShed I tried that before but for some reason it ignored the settings in BOOT_ol.uae. I just tried the method Crazy Burger posted on his channel and that worked.