Main
What's New?
About
Introduction
Abbreviations
Installation Tips
Icon Operation
Compatibility
Disk & File Operation
Internet Applications
Keyboard Shortcuts
Undocumented Features
3rd Party Utilities
Miscellaneous
Known Bugs
Disclaimer
|
Installation Tips
- After installation, I have SetPatch v44.13 in my C: directory. Is this the latest version of SetPatch?
- After installation, I have FastFileSystem v45.1 in my L: directory. Is this the latest version of FastFileSystem?
- Font loading in my Font Prefs editor seems to be as slow as ever. Was the font cache properly installed and activated during installation?
- Have the printer drivers been updated since the OS 3.5 Boing Bag 1 release?
- What should I know about running third-party patches and installing OS 3.9?
- I own a SurfSquirrel SCSI; are there any special steps to follow when installing OS 3.9?
- Are there any compatibility issues with Directory Opus Magellan-II?
- After installation, double-clicking an executable file with a default tool icon returns a "No default icon" error requester. Why?
- Where are the icons for the commodity files? They were not copied during installation.
- Do I still need the AslPrefs patch file in WBStartup or called from S:User-Startup?
- "scsi.device" from DEVS:AmigaOS ROM Update is installed unneccessarily, which erroneously overwrites some third-party controller software calling itself "scsi.device". Is there a workaround until a fix is released in Boing Bag 1?
- Some special controller software is neither copied to the Emergency-Disk, nor to the installed AmigaOS 3.9 system. Are there workarounds until a fix is released in Boing Bag 1?
- Regarding 4GB problems, some drivers are either not being taken care of, or the solution is overkill. Is there a workaround until a fix is released in Boing Bag 1?
- There are two files in OS 3.5's Boing Bag 2a newer than what's on the OS 3.9 CD. Can (or should) I use these with OS 3.9?
- AmiDock crashes with a "00000004" guru on my A4000T when I try to boot up from the pre-installation Emergency disk (Workbench is ghosted, and my system is unusable). Why?
- The installer appears to create the Emergency Disk OK, but when I boot, it opens a screen that I cannot use with my monitor (I use an SVGA monitor and Productivity Mode (640x480)). No matter what I do, I cannot get the boot disk setup so that Productivity Mode is loaded. Why?
- I've noticed that the copy of OS 3.9 I bought recently is a revised AmigaOS 3.9 CD-ROM. How does it differ from the original CD?
- How can I get a Jaz or Zip drive to mount from my Emergency Disk (in case I want to restore a backup quickly after a hard drive crash)?
1.
Q: |
After installation, I have SetPatch v44.13 in my C: directory. Is this the latest version of SetPatch? |
A: |
No. The latest version of SetPatch on the 3.9 CD (v44.16) is not copied to your hard drive during installation, and needs to be copied manually. There are five copies of SetPatch on the CD, so you'll want to copy the last entry listed in bold:
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]
|
2.
Q: |
After installation, I have FastFileSystem v45.1 in my L: directory. Is this the latest version of FastFileSystem? |
A: |
No. The latest version of FastFileSystem on the 3.9 CD (v45.9) is not copied to your hard drive's L: directory during installation, and needs to be copied manually. There are two copies of FastFileSystem on the CD, so you'll want to copy the second entry listed in bold:
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:
- Make sure that the tooltype "ASKDEVICE=YES" is entered in the latest version of HDToolBox (44.23).
- Run HDToolBox, and select the FFS-installed device that you want to update, and click on "OK".
- Select the entry that you want to update from the "Hard Drives in System" window, and click on "Partition Drive".
- Click the "Add/Update" button in the bottom right corner.
- Select the old FileSystem entry (should be version 45.1), and click on the "Update File System" button at the bottom right corner.
- 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.
- Click "Save" in the bottom left corner.
- Click the "Exit" button in the bottom middle of the window.
- Your FastFileSystem is now updated.
|
3.
Q: |
Font loading in my Font Prefs editor seems to be as slow as ever. Was the font cache properly installed and activated during installation? |
A: |
No. Type the following from a Shell window to activate the Fonts cache:
- makedir FONTS:_Cache
- 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]
|
4.
Q: |
Have the printer drivers been updated since the OS 3.5 Boing Bag 1 release? |
A: |
Not yet. Please note that there are two sets of printer drivers on the 3.9 CD:
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.
|
5.
Q: |
What should I know about running third-party patches and installing OS 3.9? |
A: |
Before installation, disable or remove any and all patches. This includes MCP, and any non-essential entries (i.e. commands needed for your accelerator are OK) to S:Startup-Sequence and S:User-Startup. Remember to remove any patch programs from the SYS:WBStartup drawer as well. Before enabling your patches after installation, be sure that none of your patches are duplicating new functionality already built-into--or offered by--OS 3.9. Remember that WBCtrl, DefIcons, AslPrefs, and others are now integrated into the OS. You can get an idea of what new functions/features are included in 3.9 here. |
6.
Q: |
I own a SurfSquirrel SCSI; are there any special steps to follow when installing OS 3.9? |
A: |
Yes. See entry 6 of the Compatibility page.
|
7.
Q: |
Are there any compatibility issues with Directory Opus Magellan-II? |
A: |
Yes. First of all, for maximum compatibility, be sure you're using v5.82, and NOT running it in Workbench replacement mode. Directory Opus Magellan-II patches workbench.library in order to offer much of it's functionality. As soon as Directory Opus Magellan-II is run, Workbench automatically disables many of it's new features found in workbench.library v44 and higher (without this, Directory Opus wouldn't even run). As a result of this, AnimatedIcons will not work. |
8.
Q: |
After installation, double-clicking an executable file with a default tool icon returns a "No default icon" error requester. Why? |
A: |
The icon type is incorrectly set for SYS:Prefs/Env-Archive/sys/def_tool.info. Load this file into IconEdit (or RAWBInfo), and change it's type from "project" to "tool" and save it again. [Albrecht Kinzkofer]
|
9.
Q: |
Where are the icons for the commodity files? They were not copied during installation. |
A: |
This was a mistake in the installation script--they are located in the AmigaOS3.9:OS-Version3.9/icons/ directory.
|
10.
Q: |
Do I still need the AslPrefs patch file in WBStartup or called from S:Startup-Sequence / S:User-Startup? |
A: |
No, it is no longer required with OS 3.9's new functionality. All you need is the "Asl" preferences editor (v45.6 or higher) from AmigaOS3.9:OS-Version3.9/Workbench3.9/Prefs/ in your SYS:Prefs directory. |
11.
Q: |
"scsi.device" from DEVS:AmigaOS ROM Update is installed unneccessarily, which erroneously overwrites some third-party controller software calling itself "scsi.device". Is there a workaround for this? (Controllers affected: Buddha, Catweazel IDE, X-Surf IDE, IDEfix Express). |
A: |
Rename "DEVS:AmigaOS ROM Update" or put:
SetPatch SKIPROMUPDATES "scsi.device"
in "Emergency-Disk:S/Startup-Sequence" [Martin Steigerwald]
|
12.
Q: |
Some special controller software is neither copied to the Emergency-Disk, nor to the installed AmigaOS 3.9 system. Are there workarounds until a fix is released in Boing Bag 1? (Controllers affected: FastATA, GVP SCSI, SurfSquirrel, X-Surf IDE). |
A: |
- 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 6 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]
|
13.
Q: |
Regarding 4GB problems, some drivers are either not being taken care of, or the solution is overkill. Is there a workaround until a fix is released in Boing Bag 1? (Controllers affected: Buddha, Catweazel IDE, FastATA, GVP SCSI, X-Surf IDE, IDEfix Express). |
A: |
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]
|
14.
Q: |
There are two files in OS 3.5's Boing Bag 2a newer than what's on the OS 3.9 CD. Can (or should) I use these with OS 3.9? |
A: |
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)
|
15.
Q: |
AmiDock crashes with a "00000004" guru on my A4000T when I try to boot up from the pre-installation Emergency disk (Workbench is ghosted, and my system is unusable). Why? |
A: |
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]
|
16.
Q: |
The installer appears to create the Emergency Disk OK, but when I boot, it opens a screen that I cannot use with my monitor (I use an SVGA monitor and Productivity Mode (640x480)). No matter what I do, I cannot get the boot disk setup so that Productivity Mode is loaded. Why? |
A: |
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]
|
17.
Q: |
I've noticed that the copy of OS 3.9 I bought recently is a revised AmigaOS 3.9 CD-ROM. How does it differ from the original CD? |
A: |
The revised AmigaOS 3.9 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 & rename a backup copy of your original Startup-Sequence file before installation.
[Martin Steigerwald]
|
18.
Q: |
How can I get a Jaz or Zip drive to mount from my Emergency Disk (in case I want to restore a backup quickly after a hard drive crash)? |
A: |
- 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]
|
|