AmigaOS3.9:OS-Version3.9/First-Install/c/SetPatch ... 44.2 (04.10.99)
AmigaOS3.9:Emergency-Boot/C/SetPatch ... 44.13 (05.03.00)
AmigaOS3.9:OS-Version3.9/Workbench3.5/C/SetPatch ... 44.13 (05.03.00)
AmigaOS3.9:OS-Version3.9/Workbench3.9/C/SetPatch ... 44.13 (05.03.00)
AmigaOS3.9:OS-Version3.9/Emergency-Disk/C/SetPatch ... 44.16 (15.09.00)

As Stephen Rupprecht pointed out, you should always use the latest version of SetPatch available.

[Albrecht Kinzkofer]

AmigaOS3.9:Emergency-Boot/L/FastFileSystem ... 45.1 (09.10.99)
AmigaOS3.9:OS-Version3.9/L/FastFileSystem ... 45.9 (09.03.00)

Please note that you also need to update all other fixed or removable FFS-installed drives with this latest version. Here's how to do it:

1. Make sure that the tooltype "ASKDEVICE=YES" is entered in the latest version of HDToolBox (44.23).
2. Run HDToolBox, and select the FFS-installed device that you want to update, and click on "OK".
3. Select the entry that you want to update from the "Hard Drives in System" window, and click on "Partition Drive".
4. Click the "Add/Update" button in the bottom right corner.
5. Select the old FileSystem entry (should be version 45.1), and click on the "Update File System" button at the bottom right corner.
6. Select the new FastFileSystem file from your L: directory, click "Load" on the file requester, and then the "OK" button at the botton left corner.
7. Click "Save" in the bottom left corner.
8. Click the "Exit" button in the bottom middle of the window.
9. Your FastFileSystem is now updated.

1. makedir FONTS:_Cache
2. setenv ENVARC:diskfont "cache=yes"

Reboot, and you're all done. Thomas Richter adds: "The first font requester or the next FixFonts will create the cache. This first call will be as slow as it used to be since the cache does then not yet exist, but all following calls will make use of the cache."

Also ensure that you're not patching diskfont.library from MCP or any other software.

[David Rey]

The drivers in: AmigaOS3.9:Emergency-Boot/Devs/Printers/ are the original drivers from the OS 3.5 CD, and should work fine.

The drivers in: AmigaOS3.9:OS-Version3.9/Workbench3.9/Storage/Printers/ are from Boing Bag 1, and are known to be buggy.

The icon type is incorrectly set for SYS:Prefs/Env-Archive/sys/def_tool.info. Load this file into IconEdit (or RAWBInfo), and change its type from "project" to "tool" and save it again.

[Albrecht Kinzkofer]

This was a mistake in the installation script—they are located in the AmigaOS3.9:OS-Version3.9/icons/ directory.

Rename "DEVS:AmigaOS ROM Update" or put:

in "Emergency-Disk:S/Startup-sequence"

[Martin Steigerwald]

• Solution for IDEFix (Express):
• The following lines (in bold) should appear in your S:Startup-sequence as follows:
  SetPatch SKIPROMUPDATES "scsi.device"
• Change the entry "C:IDEfix" to C:LoadIDE START QUIET

The necessary reset will be done automatically by SetPatch so the line
"C:LoadIDE RESET QUIET" is not needed.

• Solution for X-Surf IDE / GVP SCSI:
• Type the following from a Shell window:
  MakeDir Emergency-Disk:Expansion
  Copy CLONE SYS:Expansion/XSurfIDE Emergency-Disk:Expansion
  (for the GVPSCSI, type:
  Copy CLONE SYS:Expansion/gvpscsi Emergency-Disk:Expansion)
• Add "BindDrivers" after SetPatch to the "Emergency-Disk:S/Startup-sequence" file

• Solution for SurfSquirrel:
• See entry six on the Compatibility page.

• Solution for FastATA (not really needed as the device is in ROM, but good to have anyway for maximum speed):
• Type the following from a Shell window:
  Copy CLONE FastATA.driver Emergency-Disk:C
  Copy CLONE FastATAPrefs Emergency-Disk:Prefs
  Copy CLONE CheckLMB Emergency-Disk:C
  Copy CLONE ENV:FastATA.prefs Emergency-Disk:Prefs/Env-Archive
• Insert the following at the beginning of "Emergency-Disk:S/Startup-sequence":
• C:CheckLMB
  If WARN
  SYS:Prefs/FastATAPrefs
  EndIf
  C:FastATA.driver QUIET

[Martin Steigerwald]

Disable the following two lines in "DEVS:NSDPatch.cfg" by placing a "#" at the beginning of the line:

DEVICE scsi.device DEVICETYPE NSDEVTYPE_TRACKDISK COMMANDS 1-15,20-23,28,!22 FIXSCSIUPDATE

DEVICE 2nd.scsi.device DEVICETYPE NSDEVTYPE_TRACKDISK COMMANDS 1-15,20-23,28,!22 FIXSCSIUPDATE

The other "scsi.device" lines should be safe as they are only triggered by a certain version of "scsi.device".

[Martin Steigerwald]

There are two newer files that you can take advantage of from OS 3.5's Boing Bag 2a; they are:

• /Workbench/Tools/HDToolbox 44.27 (12/12/00)
• /Workbench/Libs/hdwrench.library 44.122 (12/17/00)

Ensure that you have the following libraries installed in the LIBS: directory on the Emergency disk:

• 68060.library
• 68040.library
• 68040old.library

After installation, check and make sure they're still on the hard drive, too.

[Jeff Sereno]

The installer creates a boot disk which uses an OCS screen (presumably on the basis that it is the lowest common denominator). This works fine if you have an old multisync monitor that can sync down to 15kHz, but if you use a monitor whose lowest sync rate is 31kHz, it obviously doesn't work.

The solution is to boot up normally and copy your screenmode.prefs file into the following directory on the Emergency Disk:

Emergency-Disk:Prefs/Env-Archive/Sys/

[N. James Bridge]

The "Second Edition" CD should be pink; the original CD should be 'warm red'. Also, if your CD has files dated January 26, 2001 (or later) in the root directory, you have the newer "SE" CD. The original CD has no newer files than November 29, 2000.

The Second Edition CD contains various corrections to the installation script. However, please note that when installing OS 3.9 as an update only—NOT a full install, the installation script overwrites the S:Startup-sequence file. Make sure you create and rename a backup copy of your original Startup-sequence file before installation.

Regardless, Boing Bag 3.9-1 fixes most of the issues and problems with the first batch of CDs. There should be no real need for someone who has a first edition/original CD to buy a second edition CD if Boing Bag 3.9-1 is correctly installed.

[Martin Steigerwald]

• Copy SYS:Devs/DosDrivers JAZ0" and "JAZ0.info" from your hard drive to "Emergency-Disk:Devs/DOSDrivers" (if you are using JAZ1 then copy it instead of JAZ0).
• Add the following line to the "Startup-sequence" on the Emergency Floppy Disk (right above "EndCLI" command at the bottom of the Startup-sequence):
• C:Mount >NIL: Emergency-Disk:Devs/DOSDrivers/JAZ0 (or JAZ1 if you are using that device).

An analogous procedure applies to Zip drives.

[Gary Goldberg, courtesy of the late Jim Willis]

Make sure you have—and are using—only one copy of the official installation utility, "Installer" v44.10 (10/01/99) or later. This should eliminate most script problems encountered during installation, including possible errors with the "MakeDir" command. Officially, Installer should be in your SYS:Utilities/ drawer, but it will also work fine in your SYS:C/ drawer. You can use the Workbench menu item "Window/Find..." to check SYS: for the location (and possible duplicates) of Installer.

Please note: If you choose to use the third-party installation utility "InstallerNG", you assume responsibility for any errors or problems encountered during installation. The install scripts are designed to work exclusively for "Installer", and not "InstallerNG".

In many cases the problem message you received did not accurately reflect a missing or even damaged library, but rather the absence of a "#?.gadget" file that the resource.library function depends on. Check the SYS:Classes/Gadgets/ directory on your system partition and the OS3.9 directory of the install CD-ROM and manually copy any missing #?.gadget files. Ensure that all the #?.gadget files are the latest versions (do this by checking the latest Boing Bag first, then the OS 3.9 CD-ROM).

[Mike Wilson/Cor Kriekaart]

Another cause for this message may be a corrupt or incorrectly installed 68040.library and/or 68060.library file. Make sure that you're using the correct—and valid—680x0.libraries. Such a corrupt file may work under OS 3.1, but will fail in OS 3.9.

[Rob Pleak]

Note that UnixDirs3 has the ability to redirect '/' to be the same as ':'; the root of the drive. This causes many poorly written installers to fail that rely on '/' to be 'parent directory'.

[Shawn Holwegner]

The following section is what's being referred to:

; $VER: Startup-sequence 45.4 (4.4.2001)
; Startup-sequence for AmigaOS 3.9

; The following lines disable updating "scsi.device" for driver
; software where this could lead to failures. They also start
; IDEFix if installed.
;
; You can manually disable updating "scsi.device" by setting
; the environment variable "NOSCSIUPDATE" to something.

If EXISTS C:SquirrelSCSI
    C:SquirrelSCSI
EndIf

Set SCSIUpdate 1
If EXISTS C:IDEFix
    C:IDEFix
    Set SCSIUpdate 0
EndIf
If EXISTS SYS:Expansion/XSurfIDE
    Set SCSIUpdate 0
EndIf
If EXISTS SYS:Prefs/Env-Archive/NOSCSIUPDATE
    Set SCSIUpdate 0
EndIf
If $SCSIUpdate EQ 1
    SetPatch QUIET
Else
    SetPatch SKIPROMUPDATES "scsi.device" QUIET
EndIf
Unset SCSIUpdate

This is not intended to remove the annoyance of the SetPatch SKIPROMUPDATES "scsi.device" QUIET line (as even with this line, SetPatch installs the ROM Update), but to do so without "scsi.device" when it exists in DEVS:.

This is just to support the less-than-ideal controller software on the market, and to disable usage of the new "scsi.device" when something like IDE-Fix, XSurfIDE, etc. is found. If neccessary, it also loads SurfSquirrel software.

"SCSIUpdate" is simply a temporary variable used to keep track of whether or not "scsi.device" updating should be skipped. It will be unset after installation and is not saved to either ENV: or ENVARC:.

Providing you're using the Boing Bag 1 version of the SetEnv (45.0) command, you may set the environment variable "NOSCSIUPDATE" to anything and it will disable the SCSI-Update as well; i.e.:

SetEnv SAVE NOSCSIUPDATE "bla"

[Martin Steigerwald]

OS3.9 'sneaks' an emergency CD-ROM driver into the DEVS: directory, and is therefore trying to initialize a non-existant CD-ROM drive. Simply drag the device file out of DEVS: and reboot.

[Kevin Orme]

Stephan Rupprecht suggests adding the following line to either your S:Startup-sequence, or S:User-startup file:

Resident >NIL: C:SetEnv PURE REPLACE

[Stephan Rupprecht]

The system currently has 3.0 ROMs installed, and the upgrade to 3.1 ROMs are needed per the list of requirements for OS 3.9.

[Kent Seaton]