Xref: utzoo comp.sys.amiga.misc:761 comp.sys.amiga.hardware:6247
Path: utzoo!mnetor!tmsoft!becker!bdb
From: bdb@becker.UUCP (Bruce D. Becker)
Newsgroups: comp.sys.amiga.misc,comp.sys.amiga.hardware
Subject: Re: WB2.0 for non-A3000
Message-ID: <71748@becker.UUCP>
Date: 10 Feb 91 09:56:54 GMT
References: <1222@stca77.stc.oz> <824@cbmger.UUCP>
Organization: G. T. S., Toronto, Ontario, Canada
Lines: 38

In article <824@cbmger.UUCP> peterk@cbmger.UUCP (Peter Kittel GERMANY) writes:
|In article <1222@stca77.stc.oz> peter@stca77.stc.oz (Peter Jeremy) writes:
|>There has been a lot of smoke and heat generated in the net regarding the
|>(lack of) WB2.0 for machines other than the A3000.  One question I haven't
|>seen asked (or answered) is why can't the existing WB2.0 be used on the
|>A500/A1000/A2000?
|
|It actually DOES run on any Amiga. The only thing currently needed is Fast
|RAM as first autoconfigured device plus a utility program only available
|for registered developers and not for the public. But when it is in ROM,
|then every machine should work with it.

	I had the notion that the Kickstart 2.0
	image needed to load at address 0x200000.
	There was once a version that could load
	at 0xF00000, but that doesn't seem to have
	been continued.

	I'd love to get a version of zkick/Kickstart
	which could load at an arbitrary address.
	Several people I know have added memory at
	0xC00000, which would be handy to use.

	An acquaintance has managed to get Kickstart
	loaded into a non-autoconfig memory board,
	and then rebooting to jump into it.

	Also, ROMs won't be much use for an A1000.
	In addition, they only have 256K of memory
	for Kickstart loading, so there are some
	interesting problems to be solved.


-- 
  ,u,	 Bruce Becker	Toronto, Ontario
a /i/	 Internet: bdb@becker.UUCP, bruce@gpu.utcs.toronto.edu
 `\o\-e	 UUCP: ...!uunet!mnetor!becker!bdb
 _< /_	 "Que es mas macho: moral fiber, o oat bran?" - lala