**Need Setup HELP** with Classic Amiga 2000 HARD DISK (Bridgeboard)

[Raffaele]

ROM SWITCHER (Do I need Kickstart 1.3?)

So I've been playing with AmigaOS3.1 and the Kickstart 3.1 ROM.

However, Workbench 1.2 won't load, and that's the only Workbench I have working perfectly with Bridgeboard/Janus/RLL drive.

Which means I need to put back the 1.2 ROM to figure things out.
->Or I get Bridgeboard working the same on OS3.1 (Which could take some work. So easier to just Boot off Gotek for the demo).

When the ROM switcher arrives, I will have a choice of ONLY TWO ROMS to put into it.  ( may mod it for 3, but not sure)

At this point my only two choices are KS1.2 and OS3.1 ROM.

If I got a KS1.3 ROM would it work for Workbench1.2?  (At least WB1.3 would work and I feel more confident getting Bridgeboard working on it)
->or would it be the same problem as OS3.1 ROM, including not being able to run WB1.2 and some of the Floppy Bootable GAMES (that will go on the GOTEK).

Yes, WHload is another consideration, but I still will always want for Demo purpose ABILITY to run Workbench 1.2, Working-Bridgeboard and the OLD games.

You can also mount Kickstart files in RAM, Cold-Reboot surviving if you have programs like KickBack or Degrader.
They load your kickstart file in RAM (1.2, 2.0, 2.1 etc.) if you have enough memory installed in your system and allow you using your Amiga with previous AOS Operating System versions in their full extent.

[wbrejnia]

You can also mount Kickstart files in RAM, Cold-Reboot surviving if you have programs like KickBack or Degrader.
They load your kickstart file in RAM (1.2, 2.0, 2.1 etc.) if you have enough memory installed in your system and allow you using your Amiga with previous OAOS perating System versions in their full extent.

Thanks Raffaele,

You at least solve one mystery for me.

The GOTEK I purchase came with a USB stick and the Selector program.

But on the USB stick was a DIRECTORY that had some software that I had no idea what it was for.



Now I know.

Since I will have the Rom Switcher, I'll use Kickstart 1.2 and OS3.1 ROMS.

I still am interested in looking into WHDloader.
All this stuff is starting to get complicated on the SW side (for Rookies like me) so will take time for me to learn.

[SACC-guy]

Your BEST bet is the 1.3 rom and 3.1 rom!

1.3 gives you auto boot on that amiga hard drive and still lets older software work.

3.1 was more compatible then 2.04 for older stuff and lets you use newer 3.1 only stuff.

The real issue with older software is memory...

[wbrejnia]

Your BEST bet is the 1.3 rom and 3.1 rom!

1.3 gives you auto boot on that amiga hard drive and still lets older software work.

3.1 was more compatible then 2.04 for older stuff and lets you use newer 3.1 only stuff.

The real issue with older software is memory...

1.3 and 3.1 was my original thinking.  Till I got Workbench 1.3 booting off of 3.1 ROM.

But here is my dilemma since I don't know till I try (how things will behave).

--> Right now my Gotek HXC is wired as DF1:
--> Right now my Amiga 3.5" Floppy is DF0:
------> So if I don't put in a bootable Floppy into DF0: the Hard Drive Boots OS3.1 (which is  on the Hard drive)
------------> This happens since I currently don't have a ROM switcher (and Kickstart 3.1 is in the Motherboard)

But my final planned configuration will be:  (A ROM SWITCHER...)
---> Gotek will be DF0: (So I can boot Game images, and Lower WB1.2,etc booting off the selectable Gotek Floppy images on the USB)
---> The Amiga Floppy will be DF1: as a Utility Floppy. (Little purpose (Copy to Floppy), and will look nice in the case)

So if I have Kickstart ROMS (KS1.3 and OS3.1).
---> What will happen with AutoBoot (when OS on Hard drive is OS3.1) and I enable KS1.3 ROM on the ROM Switcher.
--------> Will the Amiga Crash with KS1.3 ROM and OS3.1 Autoboot on HD?
--------> OR.....Can I also have Workbench 1.3 on the Hard drive? (both?)

If I have Kickstart ROMS (KS1.2 and OS3.1)
-> With KS1.2 ROM (Autoboot won't kick in), and I'll be prompted for a Gotek Image (DF0: )
-> With KS1.3 ROM (Autoboot will kick in) and I'll boot OS3.1 off Hard drive.

Maybe someone knows the answer to above, but I won't till I get a KS 1.3 and try it.
(I wonder is it worth the Investment in a KS1.3 ROM if things won't work?)

Not sure if I can pre-test this on WinUAE. Before buying an KS1.3 ROm.

[SACC-guy]

There are several ways that have have been done for results like you want.

You could make a 1.3 partition on the hard drive and write (copy)scripts to let you choose which option. (see 1.3 booklet)

One reason to continue to have a df0 is that LOTS of programs need it!

And since 3.1 lets you choose booting from the early startup menu, etc.

More to learn...

[wbrejnia]

And since 3.1 lets you choose booting from the early startup menu, etc.

More to learn...

hmm.  
So there is suppose to be a Early Startup Menu in 3.1.
I got the Hard Drive pre-loaded with 3.1 (and it just boots straight to 3.1 without any CHOICE [ie. NO Early-startup-menu]

Lots to learn indeed.

Easiest way I figure is [KICKSTART 3.1]:
-> just boot (OS3.1) autoboot from HardDisk as standard choice (DEFAULT)

-> [KICKSTART 1.2/3.1] Boot other OS W1.2,W1.3, MagiWorkbench, etc (Starting from Gotek Floppy DF0: choice [S/Startup-Sequence]) and have the appropriate (directories ASSIGNED from Hard disk. (ie [C] [libs] [devs] [Expansion] ...)
-----> This is possible since when there is a BOOT DISK in DF0: (Autoboot doesn't go to Hard drive).  [Kind of like a A: Floppy on a Windows PC with Hard disk[

I will still have DF1: as a 2nd REAL Floppy drive.

[Oldsmobile_Mike]

The early startup menu is built into the ROM. Hold down  both mouse buttons on power-on to access it. Allows you to select boot partition, switch between PAL & NTSC mode (if you have the appropriate Angus) and a few other options.

[Raffaele]

The early startup menu is built into the ROM. Hold down  both mouse buttons on power-on to access it. Allows you to select boot partition, switch between PAL & NTSC mode (if you have the appropriate Angus) and a few other options.

Other few but useful options like choosing booting without Startup-Sequence and a checklist of all Expansion Cards installed on the system with informations if they are active. This for ages was way better than any Hardware Configuration page and/or HW utility featured in an any other Operating System.

P.S. Kickstart since 2.1Allow your booting from any Floppy, not only DF0:.

[wbrejnia]

The early startup menu is built into the ROM. Hold down  both mouse buttons on power-on to access it. Allows you to select boot partition, switch between PAL & NTSC mode (if you have the appropriate Angus) and a few other options.

Now that is SUPER COOL!!!

I must be the only person in the AMIGA Universe that didn't know that.

So when did Early-Start-UP BIOS-screen get enabled?  Kickstart 1.3 (Part of AutoBoot, or as Rafaelle mentions OS2.x)?

This is great, since I assume I can make multiple Partitions on my GVP-SCSI HD and pick which one I wish to boot from.

[wbrejnia]

I may need a Kickstart 1.3 ROM after all.

I did some testing and attempted to Install Bridgeboard Janus using Install disk for Workbench 1.3 (with OS3.1 ROM).

WB1.3 booted fine from OS3.1 ROM, but bridgeboard was not recognized at all by JANUS install SW.  (not sure why, but it could be OS3.1ROM)

That same JANUS install disk (the latest version out there) worked fine with Workbench 1.2 and Kickstart1.2ROM.

And what's weird (is if I take off the AUTOBOOT jumper on the GVP-SCSI Controller the Hard Disk is not picked up my WB1.3)
---> So I'm learning that Autoboot must load the device Driver for HD.
---> I'm thinking HD can still be picked up/recognized, but then I need to install HD-Device Driver thru Workbench.

THERE IS A LOT OF MIX and MATCHING to Figure out, for a Multi-Amiga/OS-HD-Autoboot-Bridgeboard-CdriveBooting SYSTEM. (Kind of Fun).

[paul1981]

Now that is SUPER COOL!!!

I must be the only person in the AMIGA Universe that didn't know that.

So when did Early-Start-UP BIOS-screen get enabled?  Kickstart 1.3 (Part of AutoBoot, or as Rafaelle mentions OS2.x)?

This is great, since I assume I can make multiple Partitions on my GVP-SCSI HD and pick which one I wish to boot from.

OS2.x. With regard to your autoboot jumper, it might be like my Megabody IDE controller whereby disabling autoboot disables the device driver (probably gvpscsi.device or something like it) and so to get the drive(s) to then show you'd have to load the driver fron a script or the shell with binddrivers or similar.

With softkicking 1.3, I use this:
http://m68k.aminet.net/package/util/boot/skick346

Personally I use it in my startup-sequences so that holding down a mouse button when booting brings the Kickstart selection screen. You could select 1.3 from there, where it will then reboot with KS1.3. Holding no mouse button upon booting will continue to load Workbench 3.1 or whatever your startup-sequence does. It detects left mouse button, right, or both and the other port too, so there's no shortage of options. There's plenty of these mouse input-read commands on aminet. Off the top of my head I don't know which one I use...but it's normally the one with the least bytes providing functionality is there.

[wbrejnia]

With softkicking 1.3, I use this:
http://m68k.aminet.net/package/util/boot/skick346

Paul,

Thanks.  More Tools for my SW Toolbox.

I peeked at Sidekick.  Sound like it's for ROM2.0 (which I don't have).
I not getting any more ROMs at this point. I'll have (1.2,1.3,3.1).
Also I looked at the SideKick Package and No A2000 on the list.

Since I will have a ROM switcher, I'll be able to craft something together.

I had a peek at the Tools that came with my GVP-SCSI-Controller.

One of them will allow me to pre-partitions (with the Various OS for the Kickstarts).  Probably similar to HDtools (which I noticed on WB1.3)


Paritions, should give me some choices with the the EARLY-START-BootMenu.

The GVP-SSCI drive came with 2nd Partition MaxedOut.
So I need to break it up after I copy off the Software on there.

Personally I use it in my startup-sequences so that holding down a mouse  button when booting brings the Kickstart selection screen. You could  select 1.3 from there, where it will then reboot with KS1.3. Holding no  mouse button upon booting will continue to load Workbench 3.1 or  whatever your startup-sequence does.
It detects left mouse button, right, or both and the other port too, so  there's no shortage of options. There's plenty of these mouse input-read  commands on aminet. Off the top of my head I don't know which one I  use...but it's normally the one with the least bytes providing  functionality is there.

Sound interesting.  I may need a SoftSwitch/Prompter like that.
I'm sure the Mouse Buttons are in a Address Register somewhere.

I have been looking around if there are some 68000 Compilers out there for Amiga (for some mini tool coding).
There is also Amiga Basic (but probably slow).  I haven't even explorer much with basic scripting like in "Startup-Sequence"
In the Old Commodore Pet day's the good old PEEK() and POKE() would have done the job, to figure out when Mouse button is pressed.

[psxphill]

I have been looking around if there are some 68000 Compilers out there for Amiga (for some mini tool coding).

gcc 2.95.3, you can get it here:

http://aminet.net/package/dev/gcc/ADE-repack

[nicholas]

Paul,

Thanks.  More Tools for my SW Toolbox.

I peeked at Sidekick.  Sound like it's for ROM2.0 (which I don't have).
I not getting any more ROMs at this point. I'll have (1.2,1.3,3.1).
Also I looked at the SideKick Package and No A2000 on the list.

Since I will have a ROM switcher, I'll be able to craft something together.

I had a peek at the Tools that came with my GVP-SCSI-Controller.

One of them will allow me to pre-partitions (with the Various OS for the Kickstarts).  Probably similar to HDtools (which I noticed on WB1.3)


Paritions, should give me some choices with the the EARLY-START-BootMenu.

The GVP-SSCI drive came with 2nd Partition MaxedOut.
So I need to break it up after I copy off the Software on there.



Sound interesting.  I may need a SoftSwitch/Prompter like that.
I'm sure the Mouse Buttons are in a Address Register somewhere.

I have been looking around if there are some 68000 Compilers out there for Amiga (for some mini tool coding).
There is also Amiga Basic (but probably slow).  I haven't even explorer much with basic scripting like in "Startup-Sequence"
In the Old Commodore Pet day's the good old PEEK() and POKE() would have done the job, to figure out when Mouse button is pressed.

http://sun.hasenbraten.de/vbcc/

[paul1981]

Paul,

Thanks.  More Tools for my SW Toolbox.

I peeked at Sidekick.  Sound like it's for ROM2.0 (which I don't have).
I not getting any more ROMs at this point. I'll have (1.2,1.3,3.1).
Also I looked at the SideKick Package and No A2000 on the list.

Since I will have a ROM switcher, I'll be able to craft something together.

I honestly don't know whether it works with an A2000, but I do know you can use it from Kickstart 3.0/3.1/3.9 and softkick 1.2/1.3/2.x/3.x with it (doesn't require a 2.0 ROM chip exclusively). It's a fantastic tool! I think it was programmed in the 2.0 days initially, so I'd be very surprised if it didn't work with the A2000. There's plenty of A2000 users around so they should be able to tell you what they use.

EDIT: I forgot to mention MKick to you. MKick works under Kickstart 1.3, and people us it to softkick 3.1 on 1.3 systems. I haven't used it myself yet, but I plan to do so later this year when I get around to finishing my A500 project. So you could use your 1.3 ROM chip if you wanted to and then softkick 3.1. Perhaps you can softkick 1.3 from your 3.1 system too.

MKick:
http://aminet.net/package/util/boot/MKick19

[wbrejnia]

gcc 2.95.3, you can get it here:

http://aminet.net/package/dev/gcc/ADE-repack

Perfect!! This compiler may come in very handy (After I first get A2000  built)
Thanks.