WB installation fo both 1.3 and 2.04 ?

[Darrin]

Is there a way where upon booting i may have a choice like a boot menu where i decide what kickstart i have?

My old A2000 had KS1.3 and 2.0 installed on a ROM switcher controlled by the keyboard.  I added a free program to my startup sequence that checked to see which ROM was active and then jumped to different user-startups containing either WB1.3 or WB2.0.  IIRC there was a lot of "ASSIGN" use such as "ASSIGN C: C13:" or "ASSIGN C: C20", etc where C13 contained all of the C files for WB1.3 and C20 contained all of the C files for WB2.0.

This was back in 1995 and I can't remember what the damn thing was called.  Something like "WHATKICK".  It read a value from the ROM and then you could do the equivalent in your startup of "IF WHATKICK = xxx THEN  RUN USERSTARTUP13" (I can't remember what the correct format was, but it was in the README file).

[Darrin]

Worth noting is that I quickly discovered that I almost entirely ended up using WB2.0 for hard drive installed software and the KS1.3 ROM was just for a couple of quirky games that booted off floppies.

[Darrin]

Use this:

http://m68k.aminet.net/util/misc/VerCheck.lha

VerCheck V2.00

Copyright (c) 1993 by Jan Hagqvist

This program is FREEWARE.

What is VerCheck?

   VerCheck is a utility for 2.04 hard drive users with 1.3 ROM
   sharer/ReloKick who need to use their hard disk in both 2.04/1.3
   modes.

   New in V2.00:

   Now you can check 68000/010/020/030/040/881/882 too.

How does it work?

   When VerCheck is run it will read the current system version
   from Execbase and compare it with the given version and returns
   WARN if the requested system version has been found. Because
   VerCheck reads the version number from Exec instead of reading
   it from a specific absolute address it also works with software
   ROM sharers such as ReloKick.

How do I use it?

   The usage of VerCheck is very simple indeed and there are two
   modes available. In the first mode the syntax is:

   VerCheck vn      , where vn is the Kickstart version number

   VerCheck reads the Exec version number and compares it with the
   given version. If the two are exactly same, WARN will be returned.

   The other mode is:

   VerCheck vn>      , where vn is the Kickstart version number

   VerCheck reads the Exec version number and compares it with the
   given version number. If Exec version is the same or greater than
   the given version, WARN will be returned. So adding a '>' in the
   end of the version number means that any version vn or greater will
   be accepted.


   To check processors the syntax is:

   VerCheck pr      , where pr is one of the following:
              68000/68010/68020/68030/68040/68881/68882

   WARN is returned if the GIVEN processor OR BETTER is found.
   Also have a look at the example c (VerTestC) in the examples drawer.

Example

   This example is for booting the hard disk in 2.0/1.3 modes.

   VerCheck 34
   If WARN
     Place your 1.3 startup-sequence here
   Else
     Place your 2.0 startup-sequence here
   EndIf

   Also have a look at the examples drawer.

Notes

   Please don't enter V ahead the version number or revision number
   after it. So Kickstart version 37.175 translates to 37.