Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Hidden partition on dual-boot A3000

13 views
Skip to first unread message

Christoph Feck IRZ

unread,
Oct 12, 1994, 8:35:25 PM10/12/94
to
In article <37hi35$12...@bigblue.oit.unc.edu>, uto...@guitar.oit.unc.edu (Todd M. Lewis) writes:
> What mechanism is used to make either the WB_1.3 or the WB_2.x partitions
> invisible when running 2.x or 1.3 respectively on a dual-boot A3000?

I think it is just called 'Magic 36.7'. This ROM tag
is at (or rather 'behind') the end of the ROM. The
mechanism is simple: remove the DosNode entry for the
partition from ExpansionBase. It won't mount then.

> Does it have anything to do with the "1.3 Bonus" or "2.x Bonus" messages
> that MakeFiles displays when it extracts the kickstart files from the
> A3000 Superkickstart disk?

Yes. A3000 Kickfiles are not exactly 256k or 512k big.
The 1.3 bonus adds the scsi.device and memory detection
(the A3000 RAM is not autoconfig). The 2.0 bonus does
not have the scsi stuff, but still sets up some MMU
tables and fiddles with expansion.library to hide the
1.3 partition.

3k// Christoph Feck, TowerSystems - Custom Class Design
\X/ Amiga - Intuition inside.

Chris Hall

unread,
Oct 13, 1994, 1:27:15 AM10/13/94
to
Todd M. Lewis (uto...@guitar.oit.unc.edu) wrote:
: What mechanism is used to make either the WB_1.3 or the WB_2.x partitions

: invisible when running 2.x or 1.3 respectively on a dual-boot A3000?

: They are both visible if I boot from the 2.01 ROM, but not after one
: of the kickstart files is loaded. I suspect it has something to do
: with the "Enabled/Disabled" buttons on the boot menu, but the details
: are a little fuzzy to me.

: Does it have anything to do with the "1.3 Bonus" or "2.x Bonus" messages


: that MakeFiles displays when it extracts the kickstart files from the
: A3000 Superkickstart disk?

A couple of years ago, I went though the kickstart 2.04 file on a 3000 and edited
the name of the WB_1.3 device to something else so it would be visable. It's near
the end of the kickstart file. You can do the same with the kick 1.3 file, just
locate WB_2.x in it. You shouldn't bother doing it to the kick 1.3 file because
you'll have to do some work on your startup sequence. If you do it to the kick 2.04
file, make sure that the WB_1.3 partition's boot priority is one lower than the WB_2.x
one.

Chris Hall

Todd M. Lewis

unread,
Oct 12, 1994, 4:48:37 PM10/12/94
to
I should know this by now, but it's never been exactly clear to me...

What mechanism is used to make either the WB_1.3 or the WB_2.x partitions
invisible when running 2.x or 1.3 respectively on a dual-boot A3000?

They are both visible if I boot from the 2.01 ROM, but not after one
of the kickstart files is loaded. I suspect it has something to do
with the "Enabled/Disabled" buttons on the boot menu, but the details
are a little fuzzy to me.

Does it have anything to do with the "1.3 Bonus" or "2.x Bonus" messages
that MakeFiles displays when it extracts the kickstart files from the
A3000 Superkickstart disk?

Just looking for something to occupy my brain until the Amiga's adoption
papers go through.....
--
Todd_...@unc.edu ASDF - Amiga Software Developers Forum
"Where the Pizza Meets the Code"

0 new messages