Contents | < Browse | Browse >

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%  Important notes for 2.x -> 3.1 upgraders     By: Dan Barrett       %%
%%  (No, it's not a BLAZEMONGER message)         barrett@cs.umass.edu  %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

        Here is some advice for everyone upgrading from AmigaDOS 2.x to 3.1.
I discovered these things the hard way -- through trial and error (and help
from Net friends).  If you are having weird problems after the upgrade,
maybe you will find a solution below.

PREFERENCES FILE PROBLEMS (especially mouse pointer problems)

        Are you experiencing any weird preference behavior like the
following?

        o       The busy pointer does not appear.
        o       The mouse pointer is the wrong color.
        o       Pointer preferences (and others) don't get saved between
                reboots.
        o       The Workbench screen turns strange colors.
        o       WBPattern backdrops don't work correctly.

          The prefs file format apparently changed from AmigaDOS 2.x to
3.x.  To solve such problems,

        (1)     Run all of your preferences programs and write down (on
                a piece of paper) all your settings.

        (2)     Go to the directory ENV:sys and delete all the files with
                names ending in ".prefs".  (You can copy them to another
                directory first, if you want to be safe.)  These are your
                preferences settings that are created when you click "Save"
                in a preferences program.

        (3)     Go to the directory ENVARC:sys and, as above, delete all
                files with names ending in ".prefs".

        (4)     Run all of your preferences programs and re-create all your
                desired preferences settings (that you wrote down on paper
                in step (1).)  Click "Save" after running each program.

        (5)     Reboot.  All should be OK now.

        DO NOT simply run the 3.1 preferences programs, change the settings
and click "Save."  YOU MUST DELETE YOUR PREFS SETTINGS FILES FIRST.


COMMODITIES

        If you are using the SwitchNTSC commodity, get rid of it.  It will
crash your system under 3.1 due to (I believe) changes in the Screen
structure.


CPUBLIT

        If you are using CPUBlit, start using the "-b" option, or else
it may not work.  See the CPUBlit documentation for more details.


DATATYPES NOT WORKING?

        If you assign LIBS: somewhere in your user-startup file, beware!!
The AmigaDOS 3.1 startup-sequence has a new "Assign add" line:

                Assign >NIL: LIBS: SYS:Classes ADD

If you reassign LIBS: and forget to include SYS:Classes, your datatypes will
not work.  For example, MultiView and WBPattern will work incorrectly or
refuse to run.


WSHELL 2.0

        If you are using the PATH: handler from WShell 2.0, and reassign
LIBS:, beware of the problem mentioned above.  For example, I had in my
user-startup:

                assign LIBS: PATH:sys:libs,another:libs

and forgot about sys:classes.  I changed it to

                assign LIBS: PATH:sys:libs,sys:classes,another:libs


MUI (Magic User Interface)

        If you use MUI, watch out for a conflict between sys:classes and the
MUI "classes" directory.  If your datatypes are not working or MUI
does not work, this may be the problem.  For me, with WShell 2.0's PATH
handler, I had to do:

                Assign Libs:    PATH:sys:Libs,sys:Classes
                Assign Libs:    usr:Lib/Classes ADD

If you don't use WShell, you might not have a conflict.


THAT'S ALL - GOT ANY MORE TIPS?

        If anybody has more AmigaDOS 2-to-3 tips, please mail them to me,
and I'll keep this list up-to-date.

                                                        Dan