Thursday, 12 June 2014

Amiga 600 CF AmigaOS Setup Part 2

Today I am continuing my work in Part 2 of building the AmigaOS3.1 install on my CF Card on the Amiga 600!


Please read Part 1 here first if you haven't already and want to follow from the beginning of the process to see what was done. I cover a lot of ground here.

Note that to extract an lha file on AmigaOS3.1 requires lha (from Aminet here). It is not included with AmigaOS3.1. I forgot to mention this in part 1 and thought I had better cover it. The command line I used for lha in this case is:

lha x file.lha RAM:

Normally you extract lha archives to RAM: and check the read me included in the archive for install instructions first.

You should update the default c:installer program that is included with AmigaOS3.1. Quite a few installers expect a newer version of the installer and will break without it.

There are quite a few installers to choose from such as InstallerNG and more - however I chose to use the Amiga Technologies Installer 43-3 available here on Aminet. Once installed (copy the installer program from RAM: to C:), it will support pretty much most installation programs written for AmigaOS3.

Below is the ACATune command line tool, which comes on a floppy disk with the ACA630 Accelerator installed in the Amiga 600. Just copy it wherever you want it on the SYS: drive, I put it in Sys:c so I can run it from anywhere as it is in the standard path - ACATune allows me to quickly poll the card to confirm it is working, and confirm it's current configuration:


In order to run AWeb web browser on the Amiga 600 (and other applications like DiskImageGUI too), I will need to install ClassAction 3.3 first - On AmigaOS 3.9 this is included, but on a base AmigaOS3.1 install I need to download it from Aminet and install it manually. There is a 3.6 version on Aminet but the 3.3 version is actually the later version, and the one you need for DiskImageGUI so grab that version (classact33.lha).

When extracted to RAM: you end up with two folders that need to be copied to the SYS:classes and SYS:prefs equivalent folders. I used Directory Opus 5.9 to do this:


The install of ClassAct 3.3 is then completed.

However I found when installing ClassAction earlier that the prefs program needs reqtools.library latest version to run. This can be downloaded from Aminet as well, the v39 version is here.

The V39 library you need to copy using the shell from RAM (once extracted) to the libs: folder. I check the version number in AmigaShell to make sure of the versions before copying the newer one to libs:


You can then run the CAPrefs program which is now in SYS:Prefs folder to confirm everything is working:


Next I extracted Directory Opus 5.9 to Sys:Utilities/Dopus5.

Here it is once extracted:


I could of installed Directory Opus 5.8 Magellan II (Which I own on floppy disks from 1998), but with the recent work done to update it and release the latest Directory Opus 5.9 in 2014 - including on AmigaOS3 version, I couldn't resist running the latest version on the Amiga 600.

Make sure you edit s:user-startup file to create an assign DOpus5: to wherever you extracted Directory Opus 5.9 to, in my case is sys:utilities/dopus5

;BEGIN DOpus5
Assign >NIL: DOpus5: SYS:Utilities/Dopus5
;END DOpus5


Then copy the Opus5_Startup and Opus5_Startup.info files from the WBStartup folder in the DOpus5 folder, to your SYS:WBStartup folder. This will then allow Directory Opus 5.9 to run automatically on boot.

Here it is, running on top of the standard AmigaOS3.1 Workbench (after I modified the preferences in Directory Opus 5 default fonts to use XEN font as per the rest of the Workbench - btw this font was installed by Magic WB2 in part 1 blog entry):


You can see that the Directory Opus 5.9 toolbar icons don't render very well in 8 colours on the Workbench - they are intended for AGA or higher colour Workbench screens. I plan to fix this by copying the original toolbar icons from Directory Opus 5.8 Magellan II to use instead, but for now keeping them there will help me with something else I want to try out shortly. ;-)

Another view below, running Delitracker 2.32 to play back one of Hoffman's recent excellent modules created on the Amiga:



Next I wanted to customise the Directory Opus 5.9 User Menu, which appears in the title bar of the AmigaOS Workbench.

Specifically, I wanted to add a new menu to put commonly used applications in it. You can use ToolManager or some other "dock" program on the Workbench for this, but on the Amiga 600 low resolution screen you lose a lot of real estate having it there. So I want to use the User Menus.

In the User Menu options, I have now added an Applications Menu, and a new item I will call Delitracker2 as below:


Next I have to edit the Delitracker2 item in the function editor. I click on the Cycle gadget until Workbench appears, then select the Delitracker2 program from the requester. It then populates the function editor screen as below:


I also added another entry for AmigaAmp, which I downloaded here and installed to use with the MAS Player hardware attached to my Amiga 600 (AmigaAmp not setup for this yet - patience!):


This Application Menu and the 2 Menu items I created now appear on the titlebar menu as below, making running these applications easy and quick:


While here, you may note that the border around the Workbench above is black - this is not standard in AmigaOS3.1. It is achieved using a program called Border Blank - available on Aminet here. Just copy the extracted bblank file only to the SYS:c folder, and add c:bblank to the s:startup-sequence file, after the line c:iprefs. This is shown below:


After a reboot you should have a black border around your AmigaOS3.1 Workbench screen! Much cleaner looking.

In the default AmigaOS3.1 installation, the default program for viewing Images, AmigaGuide files, Sound files and so on is a program called Multiview. However, this is limited to the very limited number of datatypes included in AmigaOS3.1 to use it.

Fortunately plenty of work has been done to improve datatype support in AmigaOS3.1, particularly via the Warp Datatypes available from Aminet (many others are available there too of course). These Warp Datatypes are shareware, but work fine for 30 days for you to try out and decide if you want to keep using them or not.

Here are Warp Datatypes folders extracted for PNG, BMP, JPG, TIFF and PCX image files, and PSD files too - plenty of install work to do here:


When I ran the Warp PNG installer though, I hit an issue with the picture.datatype version not being high enough - basically saying I need AmigaOS3.5 or higher to run it...


I fixed this problem by installing Picasso96, also downloaded from Aminet here. This will update the picture.datatype to a version compatible with the installer. When installing Picasso96, select the Graffity driver and accept the defaults.

A reboot is needed after installing Picasso96. Ensure that the Workbench Screen mode prefs is set to use the standard PAL screen mode before rebooting and remove the Graffity file in Sys:Devs/monitors, as we don't plan to use Picasso96 here - we just want the updated picture datatype to allow the installation of the Warp datatypes to install and work.

Whew. Lots of installs to do. Really.

Next up is a fascinating thing I read in this forum thread here (mostly in German but the important bit is the first post and subsequent information posts in English) that allows you to run a 256 colour AmigaOS3.1 Workbench display on the Amiga 600 using the Indivision ECS! 

How . Cool . Is . That!

It looks like a lot of work (and is) - the alpha driver status makes it a bit unreliable, but I wanted to try it out! The procedure in the link assumes a lot of knowledge, and I wanted to explain it a bit more so hopefully more people can get it working on their setup! If nothing else it is a reminder for me how to do it later on!

Indivision_ECS_V101.lha Config Tools: http://www.icomp.de/products/indivision_ECS_e.htm

(Note the last file is a 7zip and lha file - I used a pc to extract the 1.1 INDIVECS.UPD file)

(This contains the 0.2b INDI.card driver and Picasso96 config files)


There are newer driver versions up to 0.2w - these didn't work for me, but links are available on the forum thread if you want to try the later versions out.

First I downloaded all the files above.

I extracted the Indivision_ECS_V101.lha to my SYS:utilities folder, which looks like this:


When I run the Indivision_ECS_Config tool I get this display of the Indivision ECS currently installed in the Amiga 600:


I only have one Indivision ECS installed, so only one is visible.

The Mode button under Miscellaneous Settings allows us to change whether the output is 1.0 (PAL) or 1.25 (NTSC), with the option to use Graffiti mode in either (or not at all).

The Graffiti mode can be used by Picasso96 to display a higher colour Workbench (or screen) on the Amiga 600!

I already installed Picasso96 earlier in this post so we are good to go on that front.

But there is a catch that stops it working - the Indivision ECS "bus" speed is insufficient to send through the required data throughput for a higher resolution screen and colour depth.

A suite of programs called MMULib (Available on Aminet as above) needs to be installed for this to work. It uses the MMU on the ACA630 accelerator to manage data going through the Indivision ECS to keep the performance acceptable. You must have an Accelerator with an MMU to use this - the default Amiga 600 does not have it. Please don't ask the technical details of this MMULib process - I have no idea - it just works!

When installing MMULib, Please use the default install MMULib modules selected already - this program is a bit daunting with many options to trap the unwary:


Once installed, I turned my attention back to the Indivision ECS.

In order to get the 256 colour Workbench working, we need to upgrade the firmware in the Indivision ECS to the 1.10 Core INDIVECS.UPD file we downloaded.

I copied the v1.10 INDIVECS.UPD file extracted (by PC) from the 7zip archive file to the Indivision ECS config folder we extracted earlier.

We can check/update the Indivision ECS firmware by using the Indivision Flash tool included in the Indivision ECS config folder.

When running the Indivision Flash tool, I can confirm I am running v1.01 as below, so I need to upgrade the firmware:


I strongly recommend you backup the current v1.01 firmware to a file on your system before attempting to upgrade the firmware. (I backed up to INDIVECS.UPD.ORIG) This will allow you to boot using the Amiga 600 AV out to re-flash it back to v1.01 (if something goes wrong during the upgrade).

Needless to say, when you tell it to flash the core (and select the v1.10 INDIVECS.UPD file), it makes sure you really want to do this - I take no responsibility if you do this and brick your Indivision ECS.

I didn't write the new firmware and cannot vouch it works for everyone - it worked for me, but please back up the current Indivision ECS firmware first to protect yourself:


The flashing process runs, and when complete, close and reopen the Indivision Flash tool - it will then show the upgraded firmware version, like below:


There are a bunch of files from the PIC96IEC_0.2.lha file that you need to copy to the right places, which contain the INDI monitor (Devs:Monitors), picasso96settings (DEVS:), screenmode.prefs (ENVARC:sys/) and the picasso96.library and Picasso96 subfolder (both to LIBS:) containing the card driver for Indivision ECS (INDI.card).

The upshot of this is that you don't need to configure the screen modes or picasso96 settings yourself - it is done already correctly configured for the Indivision ECS!

In testing I found that only the version 0.2b INDI.card Picasso96 driver worked on the Amiga 600 with Indivision ECS. The later version drivers didn't display correctly at all for me, and was unusable. Your mileage may vary! This is what I got with the later drivers in case you are curious - as I said, unusable:


Note that you can't change the screen mode when using the working 0.2b driver - you must leave it as configured in the files you copied. Later versions let you change it, but those versions didn't work for me as I covered above.

We are not finished the setup yet, though.

Once done, you need to modify the properties of the Sys:Devs/Monitors/INDI icon. Highlight the tool type SoftSprite=No as below:


Modify it so it says SoftSprite=Yes, press Enter to update, and it should appear similar to below:


Then click Save. This change is needed, otherwise the mouse pointer is not visible!

Now reboot, and cross everything it works properly.

On boot up the MMULib initialises, and connects to the Indivision ECS as below:


Note that the screen flashes a blue/black colour for a second while initialising before the Workbench displays in the correct resolution and colours, just wait a bit for the warning message above to change the resolution automatically for you - you don't need to do anything except wait.

And here it is, my 256 colour AmigaOS3.1 workbench working on the Amiga 600, using the Indivision ECS, looking fantastic in 800x600:


(Off topic: for some reason my date keeps resetting to April 2014 - still need to find out why that is happening!)

You can see the Directory Opus toolbar icons are now rendered correctly on the Amiga 600 with 256 colours now available on the Workbench - this is why I kept the default icons to test this:


Seriously cool in my opinion!

Didn't expect to be doing this as part of the CF build, but I saw the thread and really wanted to try it - it works!

Here is the Screenmode preferences using the INDI driver for those curious - it uses a 640x400 resolution modified from default sizes to 800x600, which fills the screen correctly with no scrolling, presumably using MMUlib to achieve this:


Is it fast - hmmm, not great performance to be honest, the screen refresh slows down a lot with larger windows open, but you can work with it. Screen switching to run programs in PAL/NTSC works, but sometimes will crash or hang trying to come back to the Workbench again. It is an alpha driver after all - very promising work so far though!

I will convert back to the standard PAL interlace screen mode with 8 colours for normal use, but this was fun to setup and play with. I can now set the Amiga 600 to this mode anytime I want to test stuff in 256 colours at 800x600 resolution!

Plenty more build work and configuration still to do - I will continue this build in part 3 soon!


1 comment:

  1. This inspire me to do my A600 project. It will be other modification but some parts will be the same as yours. This blogs are more like "howto" for me and I also follow your X1000 blog as that is my main Amiga.
    // Johan

    ReplyDelete

Note: only a member of this blog may post a comment.