Easy AmigaOS 3.2 & WHDLoad Games setup with HSTWB Installer

[@marquisor]

If you install all of these WHDLoad Packs you should resize your Installer CLI Window to minimum which makes the text passages MUCH faster and so the installation.

[@mkrleza]

Hvala!

[@espressomatic]

It's worth mentioning that one of the benefits of using hstWB is being able to install modified WB packs. For a minimal setup that works well on CRT without RTG, Select the hstWB package (which will also include BetterWB) plus the WHDLoad menus (OCS or AGA depending on your setup). That will get you an optional boot menu and a few different front-ends to launch games. After finishing this video it's worth checking out this other older one for coverage of these options: kzbin.info/www/bejne/o5zcXn2Bi9pqbsk

[@swinterstein]

Thanks for this guide, very helpful!

[@jeffwood8109]

Followed along, mostly, because my system is Linux. Thanks for the guide!

[@C64_and_Amiga_Memories]

Excellent. Giving this a turn just as im writing this!

[@drusso66]

Great follow up video as always, many thanks.

[@JBrianCrawford]

great guide. Question? If I have a pistorm or pistorm 32lite (i have one 1200, 2 a1000s a 500 and a 600) can i use the same process to make the hd files and can they be turned into type 76 drives? or is there a different way to do this.

[@retromark4558]

I have followed this step-by-step but when I get to 13:11 I have "No valid Kickstart rom files detected!" Even when I copied everything in Cloanto/roms/ into kickstart. Any advice?

[@MikeyGRetro]

Try it again, this does work I promise. The files should be called amiga-os-130.rom, amiga-os-310-a1200.rom that your copying.

[@retromark4558]

@@MikeyGRetro yeah, I've copied them straight from the cloanto install just like you did, it's very strange. I can't say I noticed this the first time I did it, but this is the message I'm getting now. I might try it on a different pc just to be sure there's not something weird going on. Just been battling this all day and discovered the 8mb ram simm on my accelerator is faulty 🤣 been chasing a hardware fault that I thought was me messing stuff up. The joy.... Pass me a pc to troubleshoot and I got you covered. After 25+yrs this feels all new to me again, Thanks for all your work and videos.

[@retromark4558]

@@MikeyGRetro Hey, sorry it took so long for me to update, I haven't had much time to mess around with this. I had missed the part where you copied the kick roms to the userpackages/Kickstart folder, all working now as expected :)

[@MikeyGRetro]

@@retromark4558 Cool, glad you got it working Mark

[@RobertGeux]

Thanks for all your content. Appreciate the amount of work you put in every time. I am having so many issues with this tool/script however. For me it's just not as simple as it looks in your video. I've been at it for a few evenings now, no cigar yet. ;-) First I couldn't understand why my OS31 ADF's kept on appearing when I only copied OS32 ADF's to the amigaos directory before running the script. Turns out the script recognizes Amiga Forever being installed on the PC and it copies ADF's and kickstarts from the 'Shared Amiga files' over automatically. It's visible when you run the script, it checks for Amiga Forever first, then checks the HstWB install directories for amigaos and kickstarts. But nevertheless, I can't get my official 3.2 and 3.2.1 ADF's to work. It scans them when building the script, they are there, they show up. But when it comes to installing in WinUAE, I only get 'install with floppies', not 'Install OS3.2'. And even when I try that (by adding the install3.2 ADF via WinUAE to df0) I still get nowhere. It will not even recognize the ADF that way. Tried it multiple times. The ADF (install3.2) is working fine btw, I can boot from that without issues in another configuration. I will try a few more times, maybe with my official 3.1.4 rom's and adf's. Perhaps that will work. ;-)

[@RobertGeux]

3.1.4 did work just now. So maybe an issue with my 3.2 ADF's....

[@espressomatic]

See my other comment with a solution for this.

[@Ti-JAC]

TY for the tutorial MikeyG👍

[@MaksymilianParadys]

Too bad the author discontinued the project before amiga os 3.2.2 update came out because when you install 3.2.2 update in the system installed with HstWB then you screw your startup-sequence by overwriting it. it would be great if the author could add support for version 3.2.2 to the HstWB installer.

[@michaelmclaughlin6141]

It works but its not automated for me sadly, i go through all the steps and then it asks me to insert the workbench adf for os3.2 and then requests each individual disk as it goes through the installation. Not sure why its not automating

[@MaksymilianParadys]

Watch 2:39 ;)

[@Mind-your-own-beeswax]

I just can’t get this to work. Followed your walkthrough step by step and when it comes to showing what OS can be installed I only get 3.1. 3.2 never shows up no matter what I do.

[@MaksymilianParadys]

You need to put amiga os 3.2 adf's in proper subfolder like in 2:39 read the readme inside and you'll see what files are required.

[@Dwarfboysim]

Is there a way to have the hard drive custom partitioned to the sizes you want?

[@MikeyGRetro]

There is, but not in the self installer. It requires a whole other side of HSTWB to make your own images.

[@espressomatic]

@@MikeyGRetro That other whole side, the main installer, is a complete waste of time. I spent way too long with it and what you're showing here is much more complete. Besides that, the installer only still allows pre-defined sizes and partition splits. If someone wants completely custom disk sizing, multiple disks, etc. then it's best to just follow your (these) instructions and then when everything is done and tested working, fire up WinUAE and make new HDFs and clone WB and anything else into them from the Amiga side.

[@NiekkieNick]

I still have to install kickstart 3.1 roms into my a1200. I also have the adf files for workbench 3.1. Will I benefit from upgrade to version 3.2?

[@tekk9995]

Why would you copy those 3.10 ROMS over there for a 3.2 install? Didn't you set the AmigaDos dir manually to the 3.2 one? Are you using an ISO? Thanks!

[@MikeyGRetro]

was just to show that you can copy over multiple versions and select what you want in the menu. if you know what you want just copy that. my 3.2 is copied from the disc that I bought.

[@tekk9995]

@@MikeyGRetro Ty, great vids btw Very happy with your content :D

[@cpaek72]

is there a program in windows where you can burn an hdf to a cfcard?

[@MikeyGRetro]

Raspberry Pi Imager, Win32DiskImager, balenaEtcher :-)

[@poshpaul55]

quick question Mike can i put Amigaos 3.2 on my amgia 600 kickstart 3.1.4 ? i am thinking getting the Cloanto Amiga Forever cd

[@MikeyGRetro]

Hi Paul, yes you could but when you get to the modules bit. Make sure you select A600 Modules instead of Skip. This will then soft kick the AmigaOS 3.2.1 rom into memory when you boot up. You'll notice the amiga reboot quickly when loading workbench to do this. The alternative is to purchase 3.2.1 kickstart rom chips from retropassion for example. Eventually there will be a 3.2.2 but don't know when so the modules and soft kick might be best way. Just a warning, if you have an old Furia accelerator, I had issues with it booting with 3.2 and 3.2.1 so had to resort to 3.1.4. If your Furia is fairly new then hopefully you've have no issue.

[@poshpaul55]

@@MikeyGRetro Hi mike thanks for all your videos you posted they have really help with my A600 i had my A600 Recap at retropassion really good bloke👍 i am thinking of getting a Furia accelerator in a couple weeks i might just stay with my 3.1.4 setup to keep everything stable

[@MikeyGRetro]

@@poshpaul55 Hi Paul, yep retropassion are good. I think the newer furia board will have the firmware updates to make it compatible, mines old and its not simple to update it. Worth you trying it on another card and if it doesn't 3.1.4 is still good :-)

[@poshpaul55]

@@MikeyGRetro Just a quick update here mike i got PIstorm A600 and it work just fine and very fast now

[@md78]

Many problems after install os 3.2 and 3.9 ... ! For example with unpacking lha and using execute command...!

[@MikeyGRetro]

3.9 is much older than 3.2 which can be confusing for new Amiga users. Recommend just using Amiga OS 3.2. You don't give much information on what exactly is happening. If you havn't already, reach out to one of the Amiga forums like EAB or Lemon Amiga and give more information on whats happening and hopefully you'll get the answer to your problem. :-)

[@tekk9995]

Did you mention somewhere else on how to get that 8Gb onto a real CFCard?

[@MikeyGRetro]

one of them yes, use win32diskimager or etcher or raspi imager and select the hdf and image to a sd card. warning if you have a older 3.1 rom inside the amiga you’ll have issues going past 8gb. but if you have 3.2 roms installed you can go bigger than 8gb.

[@tekk9995]

@@MikeyGRetro Thanks again :D

[@MrGareth1973]

Thank you very much!

[@tekk9995]

I have to manually set the AMIGAOSDIR to AmigaOS3.2 or else the script does not recognize the OS 3.2 and gives me an error. And even after doing that the script wants to do a manual install disc by disc. Strange. I can't figure out what I'm doing wrong. Edit: just did a manual install and now getting a KCON Software Failure. Beats me

[@tekk9995]

Checking the logfiles (Detect-Amiga-OS.log) which is an option in the installmenu, I see it does a MD5 check and finds / validates the files of OS3.2. That's OK. Then I see a copy action to an INSTALLDIR per 3.2 ADF file to INSTALLDIR:Temp/Amigz-OS/OS3.2file.adf. Maybe something isn't going right with this copy action. I don't know where that INSTALLDIR is. And the install mapping in UEA is set to R/W.

[@MikeyGRetro]

Hi Tekk, something sounds wrong somewhere. I'd download HSTWB again and start from scratch. You are copying the ADF's to the folder indicated in the video?

[@gshipley21]

@@MikeyGRetro I am having the exact same issue. Been struggling for hours on this. I only have the option to install from floppy even though it sees the adf files and copies them over.

[@5CR4PD09]

Hello, great now AmigaOS 3.2.1 is out. But.... where can i get the .rom files for 3.2.1? I have bought 3.2 then and the roms where on the cd. Now i cant find them with such update. Can someone help me out please ?

[@MikeyGRetro]

Hi ScrapDog, you need to go to hyperion website. Login, register your copy of AmigaOS 3.2, there was a key inside the cd box. Then when you login, in the downloads area there is a Amiga 3.2 folder and in there is the update file. The update file has both the updated adf and the updated roms

[@5CR4PD09]

@@MikeyGRetro thx MikeyGRetro, but incant find any serial in the box. Not in the manual not in or on the box aswell as on the CD-Rom

[@MikeyGRetro]

@@5CR4PD09 I would reach out to the shop you bought it from as you should have a serial number if not it wasn't a legal purchase.

[@5CR4PD09]

@@MikeyGRetro thx again , but i emailed them. now i wait for an answer :(

[@5CR4PD09]

@@MikeyGRetro all i need is the rom files. A4000.47.102.rom A1200.47.102.rom Is it illigal to send them to me ?

[@espressomatic]

HEADS UP - Amiga Forever issue and fix! This won't work right away if you have Amiga Forever installed - you'll get a fatal error as it tries to install 3.1 while you're running 3.2.1 Kickstart FIX: After all the setup, including running the second script and BEFORE running WinUAE, open the "amigaos" folder where you previously copied your adf files into sub-folders. You'll see that the script has copied 3.1 adf files into here from your Amiga Forever installation. Select all those files and DELETE them. Now run WinUAE and you should get the same results as this video. One more Fix: When installing 3.2.1, hstWB seems to not have copied icon.library to the Libs folder. So to fix this, attach the 3.2.1 modules disk adf for your Amiga model to DF1: and click RESET in WinUAE. This should allow the system to boot - once booted, go to DirOpus and copy icon.library from DF1:libs/ to your LIBS: (DH0:Libs/). I also copied workbench.library because I noticed the one installed didn't match the one on the adf. Eject DF1 in WinUAE, reset and all should be fine now.

[@fmlazar]

Amiga Forever won't let you use roms that are not developed by Cloanto itself. You need to just use WinUAE without the AF GUI.

[@eoinlundy]

Thanks!

[@Exitsing]

Can someone please tell what the best Amiga OS is? There are plenty versions and most of them are updates of previous versions. I own a a1200 with soon a pistorm32-lite,. Thanx all

[@MikeyGRetro]

I would look at what kickstart rom chips are inside the Amiga. If it's original then either 3.0 or 3.1. The OS is made up of both those chips physically inside the Amiga and Workbench. Even though 3.1 is old its still good if you are just using small 4GB cards for hard drive. Hyperion's AmigaOS 3.2.1 is the latest that works fine with A1200, has extra features and supports hard drive over 4GB. You would need to swap out the chips inside the amiga for 3.2.1 which you can by from Amiga shops.

[@Exitsing]

@@MikeyGRetro its the latest i ordered from ebay kickstart 3.2.1

[@MikeyGRetro]

Nice, you'll need to install the kickstart chips inside your amiga then or maybe pistorm can do some soft kickstart. I need to check out this pistorm32-lite at some point :-)

[@Exitsing]

@@MikeyGRetro i have found kickstart chips 3.2.1 for about 16 euro exc.shipping