RomSwitcher and Startup-Sequence
M.D. Madden
I just obtained a Romswitcher and I want to be able to boot to
WorkBench 1.3. Can anyone help me?
Thanks
Michael Madden
Lyle Hazelwood
Michael,
I don't remember the details, but I think I did it something like this.
Put your "higher" version s: first, and early in the startup-sequence
try a few lines like this:
FAILAT 20
setpatch
if WARN
execute s:startup13
ELSE
execute s:startup204
Then rename your "regular" startup to startup204, and your "early"
startup to startup13
Good Luck,
Lyle
Mike Leavitt
> Does anyone have a startup-sequence that works with a Romswitcher?
> I just obtained a Romswitcher and I want to be able to boot to
> WorkBench 1.3. Can anyone help me?
On my old A2000 that was stolen, I had a rom switcher. You selected
1.3 by a key combo at boot up, but it defaulted to 2.04 otherwise. I
had 2 HD's, one formated in 1.3 DOS and one in 2.1 DOS, and if I
selected 1.3, it booted the 1.3 disk, if I defaulted to 2.04, it
selected the other one. 1.3 could not even see the 2.1 HD, but 2.1
could use both. Two patitions of the same HD would work as well.
Make sure the 2.1 partition has the higher priority or 2.04 will boot
the 1.3 disk. Since 1.3 can't see the 2.1 disk, the lower priority
won't hurt the 1.3 boot process if you select that chip. You can
install 1.3 DOS from the disks by just copying them over keeping the
directories intact -- I can't remember there being an installer,
unless like the old supra or dataflyer I had, your controller software
could do it. I've had this A3000 over 6 years now, and I bought it to
replace that stolen A2000, so this is all I can remember.
--
Mike Leavitt ac...@lafn.org + team Amiga +
Lt Hawkes
"Mike Leavitt" <ac...@lafn.org> writes:
>222 201105 <375901FA.M...@lafn.org> article retrieved - body follows
this startup sequence was off a 500 but should work in the 2000.
Brian Savage
>> Does anyone have a startup-sequence that works with a Romswitcher?
>> I just obtained a Romswitcher and I want to be able to boot to
>> WorkBench 1.3. Can anyone help me?
>>
>Michael,
>I don't remember the details, but I think I did it something like this.
>Put your "higher" version s: first, and early in the startup-sequence
>try a few lines like this:
>FAILAT 20
>setpatch
>if WARN
> execute s:startup13
>ELSE
> execute s:startup204
Here's anotherway of doing it too. I have a DKB Multistart. I switch between
WorkBench 2.1 & 3.1 like this:
This is the startup-sequence file on my WorkBench partition where WB3.1 is
installed...
WorkBench:s/startup-sequence
-------------------------------------
version >nil: graphics.library 40 ;the graphics library for WB3.1 is 40.24
;if you are booting with a 3.1 ROM this
;will return '0' (5 or WARN otherwise)
if not warn ;if WB3.1 evaluate this
; the startup-sequence for WB3.1 is called startup-sequence3.1 on my dh0:
; or WorkBench partition
execute s:startup-sequence3.1
endcli
else ;if WB2.1 do this
; WorkBench 2.1 is installed on partition dh2
assign sys: dh2:
assign l: sys:l
assign fonts: sys:fonts
assign devs: sys:devs
assign libs: sys:libs
assign locale: sys:locale
assign c: sys:c
assign s: sys:s
assign rexx: dh0:rexx
execute s:startup-sequence2.1
endcli
endif
---------------------------------------
This of course will also work between other WorkBench revisions; such as
between 3.1 - 1.3 or 2.1 - 1.3. Just change the graphics.library version in
the first line.
Hope this helps.
regards,
________________________________________________________________________
| | |
| Brian Savage | Email: mailto:bsa...@accesscable.net |
| Dartmouth, NS | Homepage: http://homepage.accesscable.net/~bsavage |
| Canada | Date/Time: 5-Jun-99 20:50:50 |
|__________________|_____________________________________________________|
Dean Ridgway
M.D. Madden <mma...@wsnet.com> wrote:
>Does anyone have a startup-sequence that works with a Romswitcher?
>I just obtained a Romswitcher and I want to be able to boot to
>WorkBench 1.3. Can anyone help me?
When I had a ROM switcher installed I used the following:
System:System_1.3.2/c/cd System:System_1.3.2/c
Version >NIL: exec.library 37
If NOT WARN
cd System:
Execute Startup_2.04
Else
System:bin/MoveSys System:System_1.3.2
Execute System:System_1.3.2/s/Startup-Sequence
EndIf
The only thing not part of the standard system is MOVESYS, which I believe
I got off Aminet. My directories were set up as a normal 2.04 install
with an added directory "System_1.3.2" where my 1.3 setup lived. As I
recall, MoveSys just moves a bunch of assigns (l, devs, c, libs, fonts,
etc) all in one command.
/\-/\ Dean Ridgway | Two roads diverged in a wood, and I-
( - - ) InterNet rid...@peak.org | I took the one less traveled by,
=\_v_/= FidoNet 1:357/1.103 | And that has made all the difference.
CIS 73225,512 | "The Road Not Taken" - Robert Frost.
http://www.peak.org/~ridgwad/
PGP mail encouraged, finger for key: 28C577F3 2A5655AFD792B0FB 9BA31E6AB4683126
Gillou
system1.3: 10Mo OFS
system2.1: 10Mo FFS
datas: 80Mo FFS
and so on...
The first partition *MUST* be formatted in OFS for the expansion.library
boot device detection. Later (for the other partitions), we can use FFS.
1) Format the first partition in OFS
Install the 1.3 system on the first partition
Boot
Format the second and others partition in FSS
2) Install the 2.1 (or 3.1) system on the second partition
3) In the system1.3:s/startup-sequence insert the following commands at the
begining
system1.3:c/Version >NIL: exec.library 37
If NOT WARN
assign sys: system2.1:
assign c: sys:c
assign l: sys:l
assign libs: sys:libs
assign s: sys:s
assign fonts: sys:fonts
; startup-sequence of 2.1 or alternate OS
execute s:startup-sequence
exit
EndIf
; Now the following of startup-sequence 1.3
...
And now, it will boot with the rom switcher
;) Enjoy Amiga
George Bayliss
> Does anyone have a startup-sequence that works with a Romswitcher?
> I just obtained a Romswitcher and I want to be able to boot to
> WorkBench 1.3. Can anyone help me?
>
Here is a possible solution to your problem which originally came from
a software user manual for a hard disk controller card. I presume you
have a hard drive, otherwise a soft reset releasing the keys quickly
would probably do the trick. I also assume you have kickstart 2.x as
the second chip but this should work for 3.1 too.
There are two methods of directing a boot sequence to the selected
startup-sequence. Both require two partitions on a hard drive, one
formatted under 1.3 FastFile System and the other under 2.x FFS.
*Method one* - one bootable partition (this must be formatted under
WB 1.3)
Rename the WB 1.3 startup-sequence to startup13.
Create a drawer called WB20 (or similar) and move all your Workbench
2.x files into it.
Copy the WB 2.x startup-sequence to the WB 1.3 S: drawer, renaming it
startup2x and adding these lines at the start :
*Assign ENVARC: DH:0WB20/prefs/env-archive*
*Assign C: DH0:WB20/C*
*Assign L: DH0:WB20/L*
*Assign S: DH0:WB20/S*
*Assign T: DH0:WB20/T*
*Assign DEVS: DH0:WB20/DEVS*
*Assign LIBS: DH0:WB20/LIBS*
*Assign FONTS: DH0:WB20/FONTS*
*Assign SYS: DH0:WB20*
Create a new startup-sequence :
*version >nil: graphics.library37*
*if warn*
*failat 21*
*echo "booting Workbench 2.x"*
*execute s:Startup20*
*else*
*failat 21*
*echo "booting Workbench 1.3"*
*execute s:Startup13*
*Method two* is to create two bootable partitions, one for each
kickstart. The 1.3 partition must be first (e.g. DH:0) and formatted
using kickstart 1.3 and the Workbench 1.3 filesystem. Name it
"Workbench1.3" and install Workbench 1.3 on this partition. Format
and install Workbench 2.x on the other (DH:1), naming it
"Workbench2.x"
The computer will automatically boot from the first bootable partition
under kickstart 1.3 and will not recognise a partition formatted under
WB 2.x FFS.
If it is booting under kickstart 2.x holding both mouse
buttons down while booting brings up the early boot screen from which
you can select a partition to boot from. You may also try increasing
the boot priority of the WB 2.x partition above the WB 1.3 so that WB
2.x is always used when booting with kickstart 2.x
--
Regards
George Bayliss
Rask Ingemann Lambertsen
> Make at minimum two partitions on your disk
> system1.3: 10Mo OFS
> system2.1: 10Mo FFS
> datas: 80Mo FFS
> and so on...
> The first partition *MUST* be formatted in OFS for the expansion.library
> boot device detection. Later (for the other partitions), we can use FFS.
Wrong. You can boot from FFS partitions just fine with OS 1.3.
Regards,
/ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻTŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ\
| Rask Ingemann Lambertsen | postm...@rask.nospam.kampsax.k-net.dk |
| Registered Phase5 developer | WWW: http://www.gbar.dtu.dk/~c948374/ |
| A4000, 775 kkeys/s (RC5-64) | "ThrustMe" on XPilot and EFnet IRC |
| Diplomacy is the art of saying "Nice doggie" till you can find a rock |
Marcel DeVoe
> Make at minimum two partitions on your disk
> system1.3: 10Mo OFS
> system2.1: 10Mo FFS
> datas: 80Mo FFS
> and so on...
> The first partition *MUST* be formatted in OFS for the expansion.library
> boot device detection. Later (for the other partitions), we can use FFS.
Incorrect. 1.3 used the FFS also. It used OFS for floppies only. I believe
pre-1.3 used the OFS for hard drives.
Mr. Madden though, probably has his hard drive formatted under one of the
newer 3.1 International or Directory Cache modes which I don't think will
be recognised by 1.3, and therefore will come up with the insert floppy
disk screen.
I don't ever use any of those modes for my hard drives for compatibility
sakes. I believe you can use HDToolBox to change those modes without
loosing any data or corrupting the drives, which should then now work with
the 1.3 rom and 1.3 files.
I haven't tried it though so please correct me if I'm wrong.
--
Marcel J. DeVoe - mde...@shore.net - Team *AMIGA*
A4091scsi CV64 64 megs CDROM M1764-17" Catweasel FUSION/Emplant
A4000/060 CyberStorm MKII overclocked 66mhz - see "How to Overclock!"
and "DIY A4000 Tower for $45" @ http://www.shore.net/~mdevoe
Got an overclocking story to tell of /any/ kind?
Send it to me and I will post it to my "Overclocker's Web Page".
Gillou
The FastFileSystem is on disk, not in ROM in OS 1.3.
So if you want to boot on FFS, you need to have the first partition in
normal FS. then loaded, it's available for other partitions.
:) If you say that's possible, give us the solution to make the FFS
available at boot time... by modifing eproms of IDE or SCSI adaptater ?
Regards.
Gillou
>pre-1.3 used the OFS for hard drives.
Not usable for boot, because FFS comes on disk with WB1.3. It must be loaded
before the mounting of other partitions (which can be FFS).
>Mr. Madden though, probably has his hard drive formatted under one of the
>newer 3.1 International or Directory Cache modes which I don't think will
>be recognised by 1.3, and therefore will come up with the insert floppy
>disk screen.
Perhaps.
>I don't ever use any of those modes for my hard drives for compatibility
>sakes. I believe you can use HDToolBox to change those modes without
>loosing any data or corrupting the drives, which should then now work with
>the 1.3 rom and 1.3 files.
The "best" utility to manage disks and host adaptater is (:I think:) dkb
rapid recovery (RapidSet utility). HDToolBox can't manage some specific
caracteristics of drive (and sometimes crash).
>I haven't tried it though so please correct me if I'm wrong.
I've got this problem of sharing disk partitions between WB1.3/WB2.04/WB3.1
and that's one of many solutions...
Regards.
Rask Ingemann Lambertsen
>> Wrong. You can boot from FFS partitions just fine with OS 1.3.
> The FastFileSystem is on disk, not in ROM in OS 1.3.
> So if you want to boot on FFS, you need to have the first partition in
> normal FS. then loaded, it's available for other partitions.
No, OS 1.3 boots fine from an all FFS disk. Just as OS 2.x and 3.x boot
fine from PFS, AFS and SFS (or whatever else you use) partitions.
> :) If you say that's possible, give us the solution to make the FFS
> available at boot time... by modifing eproms of IDE or SCSI adaptater ?
It is in the manual. Simply install FFS in the RDB (with e.g. HDToolBox) as
you would with any other file system not in ROM. This feature was introduced
in 1988 - eleven (11) years ago - with Kickstart 1.3.
Regards,
/ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻTŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ\
| Rask Ingemann Lambertsen | postm...@rask.nospam.kampsax.k-net.dk |
| Registered Phase5 developer | WWW: http://www.gbar.dtu.dk/~c948374/ |
| A4000, 775 kkeys/s (RC5-64) | "ThrustMe" on XPilot and EFnet IRC |
| "Compatible": Gracefully accepts erroneous data from any source. |
Gillou
>> available at boot time... by modifing eproms of IDE or SCSI adaptater ?
>
> It is in the manual. Simply install FFS in the RDB (with e.g. HDToolBox)
as
>you would with any other file system not in ROM. This feature was
introduced
>in 1988 - eleven (11) years ago - with Kickstart 1.3.
Yes, it seems to work by installing the FFS 1.3 in the Rigid Disk Block.
But when you boot in 3.1, some tricky things appear... (system frozen or
guru) I spent much time to repair it and that's why I think it's better to
keep the RDB clear and load the FFS by the longest way round...
I know it's ridiculous, because FFS 3.1 is in ROM.
Please explain (if you can) how to do exactly (which version of FFS works in
the RDB)
:) As that, I would fall asleep less idiotic this night.
Regards.
Marcel DeVoe
>>Incorrect. 1.3 used the FFS also. It used OFS for floppies only. I believe
>>pre-1.3 used the OFS for hard drives.
> Not usable for boot, because FFS comes on disk with WB1.3. It must be loaded
> before the mounting of other partitions (which can be FFS).
Then explain to me why my original Quantum 50 meg 1.3 formatted A2000HD
boot hard drive shows up as FFS in HDToolBox?
And it boots whether I boot into 1.3 OR 3.1.
Marcel DeVoe
> Gillou <gilles.p...@lemel.fr> wrote:
>>>Incorrect. 1.3 used the FFS also. It used OFS for floppies only. I believe
>>>pre-1.3 used the OFS for hard drives.
>> Not usable for boot, because FFS comes on disk with WB1.3. It must be loaded
>> before the mounting of other partitions (which can be FFS).
> Then explain to me why my original Quantum 50 meg 1.3 formatted A2000HD
> boot hard drive shows up as FFS in HDToolBox?
> And it boots whether I boot into 1.3 OR 3.1.
Just to followup this post:
I have a blank hard drive in my A2000 with Multistart II ROM switcher that
I use for playing around with.
I formatted this drive with Workbench 3.1 FFS and copied all my
Workbench 1.3 boot files and directories into it's root directory. Then
set it in HDToolBox to "Autoboot". I then disabled "Autoboot"on the
original Quantum boot drive and booted up into Workbench 1.3 via
Multistart II.
It looked at the Quantum drive first (it is at scsi-0 address) and then
proceeded to boot from the 3.1 formatted hard drive into Workbench 1.3
through to completion no problem.
On bootup it says I have Workbench disks version 1.3.3. In a 1.3 Shell
when I type "version" I get a response of " Kickstart version 34.5 and
Workbench version 34.34".
I just learned though from the original poster that the GVP controller
sets the boot priorities of the various hard drives different than usual?
And when he set the 1.3 drive in question to a different priority
(higher/lower?) it then booted alright into 1.3, but has to do this each
time he boots? Any way to set this permanent?
GVP's are strange beasts. :-/
Rask Ingemann Lambertsen
>>> :) If you say that's possible, give us the solution to make the FFS
>>> available at boot time... by modifing eproms of IDE or SCSI adaptater ?
>>
>> It is in the manual. Simply install FFS in the RDB (with e.g. HDToolBox)
>> as you would with any other file system not in ROM. This feature was
>> introduced in 1988 - eleven (11) years ago - with Kickstart 1.3.
> Yes, it seems to work by installing the FFS 1.3 in the Rigid Disk Block.
> But when you boot in 3.1, some tricky things appear... (system frozen or
> guru)
Aarrgghh!! Install the FastFileSystem that comes with OS 3.1, of course.
Regards,
/ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻTŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ\
| Rask Ingemann Lambertsen | postm...@rask.nospam.kampsax.k-net.dk |
| Registered Phase5 developer | WWW: http://www.gbar.dtu.dk/~c948374/ |
| A4000, 775 kkeys/s (RC5-64) | "ThrustMe" on XPilot and EFnet IRC |
| Linux is like a wigwam - no windows, no gates, apache inside! |
Marcel DeVoe
> On 08-Jun-99 15:58:52, Gillou wrote the following about "Re: RomSwitcher and Startup-Sequence":
>>>> :) If you say that's possible, give us the solution to make the FFS
>>>> available at boot time... by modifing eproms of IDE or SCSI adaptater ?
>>>
>>> It is in the manual. Simply install FFS in the RDB (with e.g. HDToolBox)
>>> as you would with any other file system not in ROM. This feature was
>>> introduced in 1988 - eleven (11) years ago - with Kickstart 1.3.
>> Yes, it seems to work by installing the FFS 1.3 in the Rigid Disk Block.
>> But when you boot in 3.1, some tricky things appear... (system frozen or
>> guru)
> Aarrgghh!! Install the FastFileSystem that comes with OS 3.1, of course.
???
I have a 50 Quantum hard drive in my A2000HD (came stock with it) that was
originally formatted with Workbench 1.3 FFS.
When I upgraded to 3.1 ROM and installed AOS 3.1 on top of the 1.3 AOS,
it booted up just fine.
I boot back and forth between to two OS's with the same hard drive.
Rask Ingemann Lambertsen
> Rask Ingemann Lambertsen <postm...@rask.nospam.kampsax.k-net.dk> wrote:
>> On 08-Jun-99 15:58:52, Gillou wrote the following about "Re: RomSwitcher
>> and Startup-Sequence":
>>> Yes, it seems to work by installing the FFS 1.3 in the Rigid Disk Block.
>>> But when you boot in 3.1, some tricky things appear... (system frozen or
>>> guru)
>> Aarrgghh!! Install the FastFileSystem that comes with OS 3.1, of course.
> ???
Ever since FFS appeared in ROM as of Kickstart 2.0, the version on disk has
been for people who need to be able to boot under previous OS releases.
Regards,
/ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻTŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ\
| Rask Ingemann Lambertsen | postm...@rask.nospam.kampsax.k-net.dk |
| Registered Phase5 developer | WWW: http://www.gbar.dtu.dk/~c948374/ |
| A4000, 775 kkeys/s (RC5-64) | "ThrustMe" on XPilot and EFnet IRC |
| Windows NT is the OS of the future and always will be... |
Marcel DeVoe
> On 10-Jun-99 07:41:24, Marcel DeVoe wrote the following about "Re: RomSwitcher and Startup-Sequence":
>> Rask Ingemann Lambertsen <postm...@rask.nospam.kampsax.k-net.dk> wrote:
>>> On 08-Jun-99 15:58:52, Gillou wrote the following about "Re: RomSwitcher
>>> and Startup-Sequence":
>>>> Yes, it seems to work by installing the FFS 1.3 in the Rigid Disk Block.
>>>> But when you boot in 3.1, some tricky things appear... (system frozen or
>>>> guru)
>>> Aarrgghh!! Install the FastFileSystem that comes with OS 3.1, of course.
>> ???
> Ever since FFS appeared in ROM as of Kickstart 2.0, the version on disk has
> been for people who need to be able to boot under previous OS releases.
I understand that. But I have done the same as Mr. Gillou, installed the
FFS 1.3 into my 50 meg Quantum's RDB and I boot into 3.1 without seeing
the freeses or gurus Mr. Gillou states above that he gets.
Maybe I'm just lucky, or maybe my version of 1.3 is a tad newer that his
(1.3.3) and somehow makes a difference. Or maybe he is running
software/hacks that I don't that are just uncompatible with that
particular combination.
One thing I do notice about my other hard drives on the same system that
do have the 3.1 RDB installed in them, I get two disk icons for each
of those drives on the workbench whenever I boot into 1.3, and still only
get one for the 1.3 RDB Quantum.
Peter Hutchison
> Gillou <gilles.p...@lemel.fr> wrote:
>>Incorrect. 1.3 used the FFS also. It used OFS for floppies only. I
> believe >>pre-1.3 used the OFS for hard drives.
>> Not usable for boot, because FFS comes on disk with WB1.3. It must be loaded
>> before the mounting of other partitions (which can be FFS).
1.3 CAN boot from FFS hard disks, because when you set up the hard disk the
FFS is loaded and stored in the RDB where it can read it!
> Then explain to me why my original Quantum 50 meg 1.3 formatted
> A2000HD boot hard drive shows up as FFS in HDToolBox?
> And it boots whether I boot into 1.3 OR 3.1.
The FFS is probably v34 or something.
P.J.Hutchison
http://www.blizzard.u-net.com
** AmigaII. The new standard of computing.