Installing Amigaos 3.9 Winuae



Alternatives to the AmigaOS 3.9 CD Alternatives to the AmigaOS 3.9 CD Introduction This tutorial explains some alternative methods of making it possible to install AmigaOS 3.9 on a real Amiga by using the Emergency Disk II boot floppy, and it's mainly intended for those who doesn't have a CD-ROM drive connected to their Amiga. Installing AmigaOS 3.9 on WinUAE from the AmigaOSXL CD. Create a new directory where OS3.9 should be installed to. Lets call it OS39XL. Get LhA.run from Aminet and copy it into that directory. Start WinUAE and create a new config: RAM: 2MB Chip, 32MB Z3-Fast, 4 MB RTG ROM file must be Version 3.1 CPU: 68040, fastest possible, 4MB cache. The Green Amiga Alien guide on how to set up a hard disk in WinUAE with Workbench 1.3, Workbench 2.x, Workbench 3.1 with all the enhancements/add-ons (Picasso96, MagicWB/New Icons, Scalos, whdload etc.).

HomeDownloadContactTipsFAQBugs

IMPORTANT:

In order to use this Workbench, you MUST follow the install procedure provided.

You'll need a valid OS 3.9 install updated with Boing Bags 1 and 2, without one this pack will fail.

Vital and copyright files contained on the 3.9 install will be copied during the installation.

This is required because Workbench is still sold commercially.

The copyright holders can be found at: amigaforever.com

Required

  • Emulator to run the HDF provided (WinUAE is assumed)
  • 3.1 ROM
  • OS 3.9 HDF install with official BoingBags 1 and 2 (Please read this guide)

Example Configuration

Install Amigaos 3.9 Winuae

Chip2MB
Fast0
Slow0
Z3-Fast16MB
RTG4MB
ROM3.0/3.1
CPU68020 + FPU
SPEEDFastest Possible but maintain chipset timing
JIT8MB (Force settings and Hard Flush boxes cleared)
Display800x600 (Windowed)
ChipsetAGA
MiscUAEscsi.device checked in order to allow CDROM access
SoundEnabled

A WinUAE config file is supplied including these settings. The informationabove is provided in case of config file incompatibility with new releases orother emulators. Note this is only a suggested setup - feel free tomodify.

Instructions

  1. Place the 'ClassicWB_OS39.UAE' file into the WinUAE configurations directory.
  2. Start WinUAE and load the ClassicWB_OS39 config.
  3. Select a relevant ROM file in the ROMS tab.
  4. Add your OS 3.9 HDF file to the Hard Drives tab using 'Add Hardfile' - make sure it's listed as being device DH0:
  5. Add the 'System.hdf' file to the Hard Drives tab using 'Add Hardfile' - make sure it's listed as being device DH1:
  6. Boot into OS 3.9
  7. Find the 'Install' icon left out in the centre of the Workbench and double click it to begin installation.
  8. Follow the onscreen instructions to complete the ClassicWB OS39 HDF
  9. Remove the OS 3.9 HDF from the Hard Drives tab, then move the 'System.hdf' from DH1: to DH0:
  10. Save the configuration and boot.

Keymaps, locale and regional settings

ClassicWB defaults to the Great Britain locale and keymap settings.Obviously this is no good if you live elsewhere and your time zone andkeyboard layout differs.

In order to change these settings, do the following:

  1. Move the required keymap from the 'Storage/Keymaps' to 'Devs/Keymaps' drawer
  2. Place the 'gb' keymap back into the 'Storage/Keymaps' drawer, or it will take up memory
  3. Reboot the Amiga and open up the 'Prefs/Input' requester
  4. Select your corresponding keymap and save the setting
  5. Open up the 'Prefs/Locale' requester and select your region, again saving the setting

Note that those with an American keyboard layout are able to simplyremove the 'gb' keymap, placing it back into the 'Storage/Keymaps' drawer, leaving the 'Devs/Keymaps' drawer empty. The required keymap is built into theROM as its default setting, so to finish just save the 'Prefs/Input' with'American' selected.

WHDLoad kickstarts for games and demos

WHDLoad is a tool that allows disk based games/demos to be installed and runfrom the hard drive, even if they were never designed to do so. It also fixesincompatibility problems between different kickstarts and Amiga models.

Just as with Workbench disks, kickstart images required for WHDLoad areunfortunately still sold commercially and therefore illegal to distribute.

In order to obtain the required images, refer to the instructionsprovided.READ HERE

Using a PC directory

I don't support copying this Workbench into a PC directory; you may encounterproblems with files. Feel free to do so if you wish. Seethe FAQ for details why.

IMPORTANT:

Included is a utility that prevents Amiga disk drives clicking. Apparently,there are a few rare third party drives that get louder when using suchutilities. These drives are usually from the A1000 days so I doubt you'llexperience problems. Just be aware if a drive continues to click a few secondsafter the Workbench has finished booting, disable 'Anticlick' in the settingsmenu.

If your Amiga hard drive is larger than 2GB, read the FAQ

Note

One advantage of the ClassicWB being on a HDF is you can use an emulator tocustomize it before transferring to a real Amiga.

Every version has been made as small as possible by removing redundant files.In order to reduce the install further however, you may wish to remove items(such as those found in the icons drawer) before transferring.

Method 1

WinUAE has the option ofmounting and preparing a real hard drive for use on an Amiga! This option isonly available in Win2k-XP. Win9x-ME unfortunately won't allow this feature.

Once mounted and formatted, the contents of the HDF can simply be copieddirectly over to the hard drive. Then it can be placed back into the Amiga readyfor use.

The WinUAE device name to use with HDtoolbox or similar utility is'uaehf.device'. If you've already partitioned the drive Amiga side, it should bevisible in the hard drives tab after using 'Add Harddrive'.

Read the WinUAE documentation for further details, or refer to theinternet.

Method 2 - a slower alternative to Method 1 or direct copying of files

Basics

  • The ClassicWB install ADF provided must first be written back to a real Amiga disk.
  • Install procedure works by unzipping the file 'DH0:System.zip'.
  • The first hard drive partition must be called DH0: for the install floppy to work. I suggest using HDtoolbox found on the Workbench Install disk to name partitions. This can be done without losing any data stored on those partitions.
  • Creating the 'System.zip' file is done in WinUAE (or other compatible emulator) and copied onto a real Amiga hard disk partition identifiable as device DH0:

Creating 'System.zip' in WinUAE

  1. Load the now installed ClassicWB config created above. image
  2. Add a PC directory to the Hard Drives tab. You can call this whatever you wish, however using 'PC' for either the device or volume name will produce a nice Workbench icon shown in the pictures. image
  3. Boot the ClassicWB and load 'Dopus' from the popup menu. image
  4. Select 'DH0' for one window and the 'PC' directory added in 1) for the second window. image
  5. Highlight all the ClassicWB files on 'DH0' and click the 'ZIP' button. image
  6. When asked to enter an archive name, type 'System'. image
  7. Hit return and wait for the archive to be finalized (may take a while). image
  8. Test the archive's integrity either in Dopus or Windows. image

Updating a Pre-installed Amiga Partition

  1. Copy the 'System.zip' file onto your first hard drive partition, device DH0:
  2. Write 'Real_Amiga_Install.ADF' back to a normal Amiga 3.5' disk. Details of how to achieve this can be found in the file transfer section.
  3. Boot your Workbench disk and manually delete all workbench related files on DH0:, except 'System.zip'.
  4. Boot from the install disk created in 2) and follow the on-screen instructions.

Installing from scratch

  1. Boot your Workbench install disk and use HDtoolbox to setup your hard drive, naming the first partition DH0:
  2. Boot the disk again and format DH0: , calling it whatever you wish.
  3. Copy the 'System.zip' file onto your first hard drive partition, device DH0:
  4. Write 'Real_Amiga_Install.ADF' back to a normal Amiga 3.5' disk. Details of how to achieve this can be found in the file transfer section.
  5. Boot from the install disk created in 4) and follow the on-screen instructions.
HomeDownloadContactTipsFAQBugs

HstWB Installer is an application, which can automate installation of Amiga OS, Kickstart roms and packages with additional content.

Creating new harddrive images for Classic Amiga and installing Amiga OS, Kickstart roms, ClassicWB, WHDLoad games and demos properly can be a cumbersome task unless you spend a lot of time figuring out how this is done step by step.

This is where HstWB Installer comes to aid and can help simplifying installations and make it possible for almost anyone to do with very little knowledge about Amiga.

To simplify installation HstWB Installer presents options to choose which Amiga OS, Kickstart roms and packages to install. Installation process can be run on a real Amiga by writing harddrive image to CF/SD-card or harddisk or using an emulator.

Running HstWB Installer requires Amiga OS iso, adf files or floppy disks and optionally Kickstart roms, if harddrive images will be used for running WHDLoad demos and games.

It's recommended to use prebuild self install images and run the installation process on a PC or Mac using an emulator first as it's faster than real Amiga. Afterwards the harddrive image can be written to CF/SD-card or harddisk for use in a real Amiga.

For more advanced installation, HstWB Installer can be run to build own customized images or self install images. HstWB Installer uses either WinUAE or FS-UAE emulator to build images

Hits: 7197

This article explains my way to install Amiga OS using FS-UAE under linux ubuntu.

There are many tutorials explaining how to install Amiga OS on a real Amiga using WinUAE under windows but none for the linux side of the world.

This is a bit different than on Windows. All the tutos I’ve read are for WinUAE on Windows, so, this is my two cents for the linux side.

Note : this tuto can be simply adapted for your Amiga 500 using the right fs-uae configuration, and downloading the good classic workbench package.

Contents

  • 4 Mount the CF card on linux
  • 6 Installing

Arrrrgh ! The fast memory (128Mb snif) included on my aca1232 accelerator board seems to be a bit trashy, so Amiga OS 3.9 has problems to load correctly on my real a1200. After many attempts, i decided to downgrade to Amiga OS 3.1. This is a complete success as the OS is stable, fast, and because i don’t need more on my A1200 (making music and watching demos).

Fortunately, Linux understand Amiga OS FFS, and now it also understands Amiga partition tables, that helps a lot.

I have written and article on “how to access Amiga partitions on linux” there, i’ll use it as a base for this article.

  • Workbench 3.1 disks (ADF and REAL, or HFE for HxC) – needed to boot on the amiga OS
  • A blank CF card for installing the Amiga OS, and a CF card reader on your linux computer
  • An internet connexion for downloading the classic workbench packages
  • FS-UAE and Amiga ROMS

First you need to create the partitions on the Amiga side.

launch HDToolBox

Create the first partition, in FFS (Fast File System). 1Gb is enough. Some tells it’s better to make it littler, but we will stay in FFS, wich implies we will not be able to mount partitions that are upper than 2Gb on the real amiga at the beginning, and we will maybe want to load stuffs (packages, pictures, …) from the linux side, so we will take the place we need.

When done, format it

Swith off the Amiga

YOUR TUTORIAL FOLLOWS BELOW. IT IS A HUGE WORK FOR ME TO WRITE THOSE TUTORIALS, SO SHOW ME YOUR SUPPORT IN LIKING MY FB PAGE BELOW :

Create a directory in media to host the amigaos partition :

make it world writable

and make it your own

You need to know what is the name of the device when it comes to linux.

Installing Amigaos 3.9 Winuae

You can see it in the /devs/ directory : when inserting the CF card, the partition appear as “sdn1”, on my computer it is “sdc”.

So, you mount it manually cause it is not automatically recognized

make it world writable

and make it your own

It is needed each time you connect the CF card in linux. This is due to the security flags (rwed under linux and wed under FFS) that are differently understood by linux and by amiga os.

Including Scalos, 16 colors palettes, many tools… it is a perfect installation for those who often reinstall AmigaOS like me those days !

FS-UAE config

So you need to configure FS-UAE-LAUNCHER like this :

  • First Hard Drive : System.hdf given with Classic WB package
  • Second hard drive : a directory on you hard drive we will use to transfer the files from the hdf to the CF card. Some kind of temporary buffer if you prefer. I assume it is ~/amitrans
  • ROMS : 3.x
  • Chip : at least 2Mb
  • Fast : at least 4Mb
  • DF0 : you must add all the Workbench 3.1 disks (Workbench3.1, Install3.1, Locale3.1, Storage3.1, Fonts3.1, extras3.1) to the DF0 switch list

Installation steps

Installing Amigaos 3.9 Winuae Windows 10

At boot time, the installer asks you to insert the disks into DF0: drive, so you just do what is asked

Packages Choice

  1. install artwork yes
  2. palette : optimized 16
  3. theme : regen
  4. aga copper : enabled
  5. stackattack enabled
  6. anticlick enabled
  7. freewheel enabled

Eject DF0:, reboot and tadaaaa!

A wonderfull Amiga OS 3.1 ADVSP including Scalos and many tools is installed.

You can use Directory Opus to transfer the content of this fresh installed Amiga OS from the SYS; drive to amitrans:

Then use linux cp command to copy Amiga OS files from amitrans to the actual real CF card

At the end, you must WAIT for the flashing light of the flash card device to stop blinking, because flash cards are slow, so the drive must finish to handle all the writes before you can go further.

If you have packages to transfer before getting back to you real Amiga, it is the moment to use your knowledge of the cp command. You would prefer cp command to disk explorer in cause of the slow speed of the CF card wich can be badly handled by some graphic disk explorer (pcmanfm for example).

It’s the good time because it is faster to transfer files under Linux than on a real Amiga.

Personally I transfer the install packages for my rapidroad usb, my easynet ethernet pcmcia card, my indivision aga mkIIcr, the acatune tool, demos and programs i know i will use.

WAIT for the flashing light of the flash card device to stop blinking.

We will delete all the .uaem files written by fs-uae

WAIT for the flashing light of the flash card device to stop blinking.

You must make it world writable again

WAIT for the flashing light of the flash card device to stop blinking.

and unmount it

WAIT for the flashing light of the flash card device to stop blinking.

Installing Amigaos 3.9 Winuae Windows 7

Insert the CF card in your amiga.

If you boot directly on your cf card, Amiga OS won’t load, and you’ll get an error like :

Once again, it is due to the security flags not handled in the same way by linux and amiga os…

So, you must boot from Workbench 3.1 disk.

When on the workbench, you open a shell, and type

And you wait for the system to finish the job.

Rename your harddrive DH0: to “System” if necessary

When done, you can boot on your Workbench ADSP installed on your CF card on your real Amiga 1200 (or 500).

Tadaaaa !