![]() |
![]() |
#501 |
Registered User
Join Date: Jul 2014
Location: USA
Posts: 139
|
Okay, I was confident enough with my own selections that I could start the install process now. This is what I get (see attached).
I am not sure why OS3.9 is being included in the mix, however. I do have an .iso file somewhere on a local drive but nowhere near where the HstWB installer sources. I also do not have it mounted in CD0: Nothing that I have selected to install requires OS 3.9. Suggestions? Last edited by jdryyz; 26 January 2020 at 18:06. |
![]() |
![]() |
#502 |
Registered User
Join Date: Jul 2014
Location: USA
Posts: 139
|
EDIT: Nope! I still have something weird happening with the combination of MagicMenu and Tools Daemon. I was fooled again because it was working under WinUAE. Sigh. More digging is necessary.
~~~~ OS 3.9 being listed was of no consequence. The installation completed successfully. I even remembered to include the 3.1.4.1 update. ![]() The longstanding problem I had with MagicMenu has now been solved. Thanks to cyberhead97 and all those that contributed to this! Last edited by jdryyz; 01 February 2020 at 03:32. |
![]() |
![]() |
#503 |
Registered User
Join Date: Jun 2019
Location: greece
Posts: 46
|
cyberhead97
i want to install amiga os 3.1.4 for the raspberry pi3, do i need to have the amigaos 3.9 iso with the BoingBag39 also in the directory "amigaos" or not? |
![]() |
![]() |
#504 |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
You can have both Amiga OS 3.1.4 adds and 3.9 iso + boung bags in AmigaOS directory. But you can only select to install one of them, so in your situation I would just have Amiga OS 3.1.4 adfs.
|
![]() |
![]() |
#505 | |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
Quote:
|
|
![]() |
![]() |
#506 | |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
Quote:
When creating partitions PFS3, please use identifier PDS3 (0x50445303). This makes PFS3AIO use scsi direct communication, if available. For some hdd controllers this is the only way to make PFS3 work properly. A friend of mine had to use PDS3 in order to get his SCSI2SD working on his CDTV with a scsi module installed. The images I have created has all of the above covered including the maxtransfer set to 0x1FE00. So you could maybe try and create a PFS3 image using HstWB Installer and see if you can get that up and running on your Amiga. |
|
![]() |
![]() |
#507 | |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
Quote:
Maybe I need to change the wording to avoid any confusing here. |
|
![]() |
![]() |
#508 | |
Registered User
Join Date: Aug 2017
Location: Essex
Posts: 56
|
Quote:
|
|
![]() |
![]() |
#509 |
Registered User
Join Date: Jul 2014
Location: USA
Posts: 139
|
Yes, I have a clean ClassicWB_68k using 3.1.4.1! I still have the strange behavior with Magic Menu and ToolsDaemon, however.
Since my last attempt at pairing the latest OS and CWB was a bit of a hack, I figured I needed to start fresh with the help of HstWB. This did not solve my problem, which means I need to look elsewhere. Since it works fine under emulation, it must be something to do with my real hardware. I do not know where to start. Perhaps a plain vanilla OS 3.x install and then only adding the two programs. |
![]() |
![]() |
#510 |
Registered User
Join Date: Jun 2019
Location: greece
Posts: 46
|
cyberhead97 is it possible to update the amibian v1.4.1001 hstwb v1.2.0 image for the raspberry pi2/3 only with the latest workbench`s versions that are included in the last 1.4.2 version ??
|
![]() |
![]() |
#511 | |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
Quote:
Note that with this approach I'm making HstWB Installer updateable without having to create a new modified Amibian image for each new release of HstWB Installer |
|
![]() |
![]() |
#512 | |
Registered User
Join Date: Aug 2017
Location: Essex
Posts: 56
|
Quote:
Thanks |
|
![]() |
![]() |
#513 | |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
Quote:
|
|
![]() |
![]() |
#514 |
Registered User
Join Date: Jun 2019
Location: greece
Posts: 46
|
cyberhead97 i want to create a base image of hstwb installer for Raspberry Pi like the previous image first time boot asking for kickstart etc.
what are the steps to do it?? i tried to install with the new usb_self_install it keeps asking for amigaos file aparently something in setup is not correct, i attached 3 photos under to see https://ibb.co/QYXrs27 https://ibb.co/kXR9PMS i changed the locations in the flash drive with the ones from the hard drives panel but nothing still the same what i did after is replace the folder amiga files in the stock hstwb 1.2.1 image with the ones from the 1.4.2 archive and i got this configuration in the hard drives panel of amiberry i changed the locations based in this configuration image but the installer is stil asking for the amigaos file/s https://ibb.co/Dbybnqr is this some bug/error in the new usb_self_install i extracted in the flash drive? since im confused a little bit is it possible that you can make an updated hstwb 1.4.2 image and put it in the downloads for raspberry pi3? or if you cannot now can you describe the steps you take to install hstwb 1.4.2 before and after installing it in this page https://github.com/henrikstengaard/h...er-for-Amibian what are the steps after (Follow the dialog messages to complete installation of HstWB Installer for Amibian) Last edited by symbios24; 02 February 2020 at 12:34. |
![]() |
![]() |
#515 | |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
Quote:
Then you need to use the new USB self install and copy Amiga OS to "amigaos" directory and Kickstart ROMs to "kickstart" directory. With HstWB Installer installed as described in the wiki, you need to insert USB stick with self install files. Then type "hstwb" and select Setup, HstWB Installer and Install HstWB Installer image. This downloads and unpacks the latest image for Amiberry and UAE4ARM ready for use. Next select Setup, Find HstWB Self Install to update symlinks used emulators to access USB self install. Then you can run emulator to start HstWB Installer and it should run as usual. |
|
![]() |
![]() |
#516 |
Registered User
Join Date: Jun 2019
Location: greece
Posts: 46
|
![]()
cyberhead97 thanks
i did that excactly as you said and as the first picture show it cannot find the amiga os iso/files i tried in a fresh amibian image and in the hstwb image the same result cannot find the amiga os files/iso i tried too many times without result is it possible to make an hstwb image ready to work with your setup and put it in downloads?? thanks |
![]() |
![]() |
#517 | |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
Quote:
If you insert your USB stick with self install and from Amibian console type "hstwb" and select Setup, HstWB Installer and Find HstWB Self Install, does this step succeed? Also make sure your USB stick has a hstwb_self_install.txt file in it's root directory. This is included in the latest USB self install files. |
|
![]() |
![]() |
#518 |
Registered User
Join Date: Feb 2020
Location: New Zealand
Posts: 3
|
Can anyone offer some assistance in getting 3.9 working on my real amiga A1200.
I emulate my A1200 in WinUAE exactly and works fine there but installing the CF card into my amiga just gives me a green screen. 3.1.4 works without issue, the only issue is attempting to boot 3.9. |
![]() |
![]() |
#519 | |
Registered User
Join Date: Feb 2016
Location: Denmark
Posts: 333
|
Quote:
Amiga OS 3.9 requires Kickstart rom 3.1 if I remember correctly maybe also Fast ram. I'm not sure you can run Amiga OS 3.9 with Kickstart rom 3.1.4 and it's not something I have tried or know if that's what you have installed. |
|
![]() |
![]() |
#520 | |
Registered User
Join Date: Feb 2020
Location: New Zealand
Posts: 3
|
Quote:
Ahh yes, I do have an MBX 1200 with an additional 8MB fast ram and RTC (No FPU installed), I am also using the 3.1.4 kickstart in the real A1200... I have been digging and digging and have found mentions of the 3.9 install needs to be modified to function on 3.1.4 Kickstarts but I have not found any further details on what modifications should be made... For some reason WinUAE is happy to boot 3.9 even using the 3.1.4 Kickstart. If anyone has managed to get 3.9 to boot with a 3.1.4 rom please point me in the right direction as I am at a loss on what to try next (I could go back to 3.1 rom's to test... but it has been a very very long time since I last burned an eeprom for an amiga, that will be a chore unto itself :P) |
|
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
HstWB Installer for Classic Amiga | AMIGASYSTEM | News | 26 | 05 March 2021 17:31 |
Legal Issues if Sharing RP9 Snapshots? | tygre | Retrogaming General Discussion | 17 | 18 September 2014 20:04 |
Making cf_ClassicWB_FULL.hdf bigger? | emuola | project.ClassicWB | 3 | 06 June 2009 00:23 |
New ruling making retro-archives legal? | Bloodwych | Retrogaming General Discussion | 3 | 24 November 2006 19:30 |
|
|