Yes. Mikolaj Calusinski (with help from Olaf Barthel) has provided an archive that patches ToolsDaemon to work correctly with OS 3.9.

Simply download ToolsDaemon22.lha from Aminet, and install according to the instructions in the ToolsDaemon22.readme file.

Yes, but there are two things you should be aware of with MCP:

• First, make sure that you don't have any options in MCP that patch diskfont.library, as this will prevent 3.9's font cache from working correctly. You still need mcpramlibpatch in your startup as the ramlib problem is caused by third-party libraries performing too complicated/stack-hungry tasks (opening other diskresident libs) within their init function. These libraries are therefore breaking certain programming rules; and it's not a bug in ramlib itself. [Stephan Rupprecht]
• Lastly, activating the "Processor" feature of MCP removes the ability of the RAD: device to be resident, so switching this off in MCP will restore it.

[Philippe 'Elwood' Ferrucci]

Yes. Make sure Birdie is run without the NOICONBORDER and FLOODMASKWB options.It may cause problems with the prefs editors that use the ReAction GUI. Timo Moretto reported that several lines of text are written to the same space, and when trying to resize the window to force a redraw, all gadget-graphics in the window disappear. [Rolf Max Rotvel] Note that WBClock refuses to 'show up' if Birdie is running with the NOICONBORDER switch on.

[Rolf Max Rotvel]

Re-installing CyberGraphX v4.0 may help (the screen requester may not be opening properly).

[Steve Smith]

If you use a gvpscsi.device-based system, make sure that you're using at least v5.3 of the gvpscsi file available from GVP-M. This mounts a gvpscsi.device that works with PlayCD. To use that file, you have to disable automount on the GVP SCSI card by moving the boot jumper. Then install the new gvpscsi and gvpscsi.info files into your SYS:Expansion drawer. Be sure that your startup-sequence has the "BindDrivers" command in it. [Jeff Gilpin]

For omniscsi.device users, this is a bug in PlayCD, and a workaround called "playcdkludge" is available from http://babel.de/amiga.html#omni. See his "Known incompatibilities" section for more info.

Please note:

• PlayCD needs a SCSI device that understands SCSI-2 commands. PlayCD does not depend on any filesystem (AsimCDFS, CacheCDFS, AllegroCDFS, etc.). It also does not work with the AmigaOS cd.device.
• In general, you don't have to set any tooltypes for PlayCD. PlayCD will automatically scan for the following SCSI CD-ROM devices:

  scsi.device, 2nd.scsi.device, 3rd.scsi.device
  4th.scsi.device, 5th.scsi.device, 6th.scsi.device
  7th.scsi.device, 8th.scsi.device, atapi.device
  2060scsi.device, 1260scsi.device, 1230scsi.device
  cybscsi.device, cybppc.device, blizzppc.device
  z3scsi.device, dkbscsi.device, omniscsi.device
  tekscsi2.device, wildfirescsi.device, squirrelscsi.device
  oktagon.device, gvpscsi.device, dracoscsi.device
  

  If you don't want to use the autoscan feature, or your drive is connected to a device that is not listed here, you should use the tooltype DOSDEV or (exclusive-or) the Tooltypes DEVICE and UNIT to provide the device to which your drive is connected to.
• If your CD-ROM drive is already mounted, you can use DOSDEV to provide PlayCD with this mountpoint (e.g. DOSDEV=CD0:). PlayCD will then ask the filesystem responsible for this DOSDEV (e.g. CD0:) for the device and unit of the CD-ROM drive.

[Markus Poellmann]

Follow these steps when installing OS 3.9 over an existing OS 3.5/3.1 system:

• Place C:SquirrelSCSI before C:Setpatch QUIET in S:Startup-sequence (OS 3.5/3.1 seem to be able to mount devices on the squirrelscsi.device without running SquirrelSCSI first. In OS 3.9 this is no longer the case due to the RAM signal usage patch in the new SetPatch).

Follow these steps when installing OS 3.9 on a clean system:

• After the emergency floppy has been created, type the following three lines in a Shell window:
• COPY CLONE C:SquirrelSCSI DF0:C
• COPY CLONE LIBS:Squirrelscsi.library DF0:Libs (or surfsquirrel.library if that's the only file you have)
• COPY CLONE DEVS:squirrelscsi.device DF0:Devs
• Place C:SquirrelSCSI before C:Setpatch in DF0:S/Startup-sequence.
• Ensure that DF0:Devs/DOSDrivers/CD0 is using the squirrelscsi.device directly, and not the CD32 emulated cd.device. If the latter is true, change it to squirrelscsi.device and change the UNIT number to the SCSI-ID.

After installing OS 3.9, make the same changes to the files mentioned above. Replace DF0: with the partition name where you installed OS 3.9 on.

[Staf Verhaegen]

AnimatedIcon needs features of workbench.library v44+. As soon as Directory Opus Magellan (not to be confused with Directory Opus v4.xx) is run, Workbench disables those features for compatibility reasons (or Directory Opus Magellan wouldn't work).

[Markus Poellman]

It is a known problem that TurboPrint (at least v7.04 or older) does not preserve unknown IFF chunks, but erases them (affecting the SYS:Prefs/Env-Archive/Sys/printer.prefs file).

[Hubert/Markus Poellman]

There are three possible solutions (none are guaranteed to work on your system):

Possible solution #1:

• Ensure the following lines are in your S:Startup-sequence after the command:
  "Assign >NIL: ENV: RAM:ENV"
• C:FBlit (with its default settings)
• C:WBCtrl IMT=ICONFAST
• C:LoadWB SIMPLEGELS
• In the SYS:Prefs/Workbench preferences editor, set the "Images in:" cycle gadget to "Graphics Memory", and click "Save".
• Reboot, and you should have more available CHIP RAM.

Possible solution #2, David Woolley:

• Ensure the following lines are in your S:Startup-sequence after the command:
  "Assign >NIL: ENV: RAM:ENV"
• C:FBlit


• C:WBCtrl IMT=ICONFAST
• C:LoadWB (without the SIMPLEGELS argument)
• In the SYS:Prefs/Workbench preferences editor, set the "Images in:" cycle gadget to "Other Memory", and click "Save".
• Reboot, and you should have more available CHIP RAM.

Possible solution #3:

• In the SYS:Prefs/Workbench preferences editor, set the "Images in:" cycle gadget to "Other Memory", and click "Save".
• Ensure the following lines are in your S:Startup-sequence after the command:
  "Assign >NIL: ENV: RAM:ENV"
• C:FBlit (with AddBobPatch & RemIBobPatch switched off, and the QBSBlitPatch on in FBliGui)
• C:LoadWB (without the SIMPLEGELS argument)
• Reboot, and you should have more available CHIP RAM.

Yes. This can happen if you have the "1:1 Aspect Ratio" checkbox selected in the IControl prefs editor—it interferes with Visual Prefs. Note that one of the earlier beta releases of CyberGraphX had this problem, so make sure you're using the latest CyberGraphX beta release. A particular option in Birdie may also be causing this. [Remco Komduur]

You need to switch off the 1:1 aspect ratio option, save your new IControl preferences, and reboot. Just selecting "Use" is not enough to make VisualPrefs work again. Note that when using VisualPrefs, IPrefs' 1:1 aspect ratio feature is not needed anyway, so turning it off shouldn't be a problem for anyone.

[Massimo Tantignone]

This is not a VNC bug; it is a gadtools bug. The gadtools.library "LayoutMenusA()" hangs if the screen is too small and no menu could be built. The function just loops forever and never returns, not even with a failure code (which wouldn't be a problem for VNC in first place). Unfortunately, this is not so easy to reproduce. It depends on the screen mode, on the font and on some unfortune when selecting the screen size.

The solution is to redirect SetVNC to a different screen by dropping the "width" and "height" parameters of the window path as then ViNCEd will figure out the default window size.

[Thomas Richter]

According to Thomas Richter, RamLibFix is redundant (already fixed by SetPatch), and PatchRAM is obsolete (Thomas is working on a permanent "fix" to the ram-handler).

[Steve Holland]

Remove DefIcons from your SYS:WBStartup drawer, as it clashes with Directory Opus's file definition system.

[Douglas Valentine]

Oliver Roberts shares the following:

"Quite a few people (including myself) have found that IBrowse 2.2 is actually more stable under OS 3.9, for some reason, than it was with previous OS versions. It's not bug-free though, and hopefully this will be addressed in IBrowse 2.3, although the development state seems to be a bit "fragile" at the moment. Most (if not all) of the common bugs in 2.2 have already been logged on the IBrowse bugtrack, so hopefully they will get fixed.

The External Viewers stopped working in OS3.5 BB2 and OS3.9—this problem has already been fixed in the current development version of IBrowse, but in the meantime, I made a patch for IBrowse 2.2 (also fixes one of the most common crash bugs), which can be found at:"

http://groups.yahoo.com/group/ibrowse/files

Serial.device v43.7 is buggy and is causing the problem. Until a bug fixed version is released, use serial.device v43.4, which allows you to connect fine.

[Gabriele Favrin/Martin Steigerwald]

Did all your screenmodes disappear when you installed OS 3.9 Boing Bag 2? If so this is the same error that happened a few months back when a newer version of BlizKick was released. The problem is related to a version check of exec.library. Newer exec versions (> v40) cause problems when scanning the display database for cgxsystem.library less than version 42.6. Any exec.library patch or hack with a version > v40 runs into this problem. You will need cgxsystem.library 42.7 or higher. This can be found in the CGX 4.2pre11 or later release (found at http://vgr.com/v4/) for normal Amiga graphics card users, or G-Rex PCI card users can use the CGX V4.3beta R3 for G-Rex archive (found at http://vgr.com/g-rex/#software).

Note that you can use AmigaOS 3.9 and Boing Bag 3.9-2, but do not install the new ROM Update...or simply replace the "SetPatch" line in your Startup-sequence with:

SetPatch QUIET SKIPROMUPDATES "exec.library"

or

SetPatch QUIET SKIPROMUPDATES "exec.library,scsi.device"

(when you have IDE-Fix) ...again, it's all documented.

SetPatch QUIET SKIPROMUPDATES "exec.library"

[Andreas Benden and CyberGraphX wesbite]