Help installing OS3.9 on to a A4000D

[Thomas]

You must not remove Setpatch. It's an essential part of AmigaOS (no matter which version) and becomes especially important with OS 3.9.

Your problem most likely is the Warpengine. It's known to be a non-standard 68040 accelerator which often causes problems.

After installing OS 3.1, you should install the 68040.library which came with the accelerator. Then make an OS 3.9 emergency disk (I don't know why people always ignore this. It's the very first choice in the installer and selected by default). Make sure that the same 68040.library has been copied to the disk. If it's not, copy it manually. Now boot from the emergency disk. If it boots ok, install OS 3.9 to the HDD. After installation again check 68040.library and copy the right one if needed.

If you don't get it to boot, try to delete the file "AmigaOS ROM Update" from the Devs drawer. This will deactivate half of OS 3.9, but probably solve the boot problem.

BTW, you should only make one small partition on the HDD and leave the rest empty. The boot partition must be within the first 4GB of the drive anyway and OS 3.9 by default cannot access more than 128 GB. If it tries, it will crash. Only the latest patch from Aminet fixes this.

Regarding BB1 installation, make sure that you have only one (the latest) version of the program "Installer" installed anywhere on your HDD. It belongs into the Utilities drawer. If there is an older version in the C drawer, this makes installation fail.

Bye,
Thomas

[Thomas]

Am I correct in assuming that my Amiga is now booting without skipping any ROM updates (as it should be I guess)?

Select "version/copyright" from the Workbench menu. If it says "ROM 3.9" in the title and both versions are 45, then yes, it's working with ROM update now.

1. The Amiga boots but a warning appears - 'Can't install BenchTrash'. Any ideas what this might be?

Don't know, never saw this. If you don't need a global trashcan, you can remove BenchTrash from the WBStartup drawer, then the message will go away.

a) It is reporting the size to be 127.9G

That's the LBA48 issue. Install either this or that to fix it.

b) when I partition it the partitions don't add up to anywhere near that amount.

That's because Kickstart 3.1 cannot see more than 7.8 GB (and access more then 4GB). Now that the ROM update is working, you can use this to extend the partitionable area.

Make sure that you update the FastFileSystem which is stored in the Add/update dialogue of HDToolbox. Otherwise you may loose all your data sooner or later.

Bye,
Thomas

[Thomas]

Do you still use the 3.1 version of SetPatch ?

If you enter setpatch into a shell window, it lists what has been patched. Should look like this:

Code: [Select]


AMIGA ROM Operating System and Libraries
Copyright © 1985-2002 Amiga, Inc.
All Rights Reserved.

SetPatch (V44.38) has already been installed.  Patch list:
        68040 Support Code Loaded
        Enabled Advanced Graphics Modes
        HWG IEEE Single Precision Mul/Div/FPU Fix
        ramlib signal usage
        stack size check for CON:, RAW:, RAM:, PAR:, PRT:, SER:
        graphics/WritePixelLine8()
        graphics/WriteChunkyPixel()
        Enabled data cache
ROM updates installed by SetPatch:
        shell, shell 45.7 (13.01.2002)
        console.device, console 44.8 (12.6.2001)
        ram-handler, ram 44.23 (8.4.2001)
        scsi.device, IDE_scsidisk 43.43 (16.1.2002)
        FileSystem.resource, filesysres 45.10 (3.8.2001)
        filesystem, fs 45.13 (3.8.2001)
        bootmenu, bootmenu 44.7 (25.2.2002)
        exec.library, exec 45.20 (6.1.2002)
        AmigaOS ROM Update, ROMUpdate 44.57 (25.2.2002)


Bye,
Thomas

[Thomas]

Something about 'Intuition' is all I could see.

Probably some program is writing some text to the initial shell window, which should not happen normally. Edit s:startup-sequence and insert a line between loadwb and endcli reading

ask "press enter"

This will keep the shell window open until you press enter so that you can read any messages which appear earlier.

I was back to the green flashing reboot cycle.

Does this only happen if you let it cool down for some time, or does it also happen if you switch it off and only wait a few seconds before you switch it on again ?

If it is a heat (or rather coolness) problem, then there is nothing we can do about it in software.