Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ulowell!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga
Subject: Re: 2090A problem
Message-ID: <5528@cbmvax.UUCP>
Date: 19 Dec 88 23:26:28 GMT
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 35

In article <something> bader+@andrew.cmu.edu (Miles Bader) writes:
>I just got a 2090A.
...
>But looking at the addendum (diffs of the 2090A from
>the 2090), it said that the autoboot roms will mess up with 1.2
>kickstart roms (which I have).

	Quite correct.

>So I removed the two rom chips that
>the addendum specifies as the autoboot roms, and tried again.  Still
>won't boot.  Then I remove the disk led wire from J5; now it boots
>from floppy.

	Wierd.

>But prep (after waiting about 7 minutes!) just says
>"Drive not PREPed" (great error messages here).  Thinking that maybe
>it was the disk led in the first place, I put the roms back in.
>System won't boot.

	Did you put the driver AND icon in the expansion drawer of your
boot disk, AND did your startup-sequence run 'binddrivers'?  Both are needed
to make prep work.  (You can copy the icon over, then run binddrivers again
to avoid rebooting before running prep.)  Note that SCSI drives may take a
long time to prep (low-level format).  If the drive light is on (the one on
the drive, if it has one), you know it's probably working.  What type of drive
are you using?

	If you have 1.3 KS roms, then the driver in the expansion drawer isn't
needed, since it is auto-started from the ROM.

-- 
You've heard of CATS? Well, I'm a member of DOGS: Developers Of Great Software.
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup