Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!netxcom!logan
From: logan@netxcom.netx.com (Jim Logan)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: The Amiga's Future
Message-ID: <441@netxcom.netx.com>
Date: 5 Jun 91 22:23:02 GMT
References: <1991Jun03.053144.3208@ariel.unm.edu> <5202@dirac.physics.purdue.edu> <193f5229.ARN018e@nesbbx.UUCP>
Organization: NetExpress Inc., Vienna, VA, USA
Lines: 28

In article <193f5229.ARN018e@nesbbx.UUCP> billsey@nesbbx.UUCP writes:
# 
# 	Actually, no. When the 3000 came out, and now, it had a set of special
# boot ROMs (or EPROMs) that loads a kickstart off of disk. Just like the 1000
# does. The difference is, it loads that kickstart into system memory, then uses
# the MMU to map it to a ROM location. That means you use up some of your system
# memory whenever you're running. (256K for 1.3, 512K for 2.0) That will go away
# with the release of real 2.0 ROMs, freeing up the 512K for applications to use.

Actually, I hope that when they come out with the ROMs, they
allow you to copy the code into RAM.  I believe that the access
time of ROM is much slower than RAM, and on a 3000UXD I have lots
of memory to spare.  I've never run an application that utilized
more than 2MB of memory.   

I'd like it to be copying the ROMs into RAM while my hard disk is
spinning up so that by the time the disk is ready to be read from,
the OS is already running from RAM.  My current boot ROMs don't wait
long enough for my hard drive to spin up.  I have to do a warm
boot after I turn on the power because I get the "2.0 HD/FD or
1.3 HD/FD" menu with the HD for both shaded out.  That sucks.
(I know people will query me on this one, so I'll beat you to it:
I have a 340MB Maxstor HD.)

-- 
Jim Logan                Home: logan%gimlet@uunet.uu.net
Consultant               Work: logan@netx.com
Net Express, Inc.       Phone: (703) 749-2269