#2090a and 2.04
9 messages in this thread
Ummm, this is either so simple it is confusing or Commodore is expecting me
to know too much. I've been running a 2000 with a 2090 controller and 1.2
rom. This combo does not allow autobooting of the HD. I picked up a 2090a
on here, but the 1.2 rom would not coexist with it so it has remained on
the shelf. With 2.0 coming out any minute now, buying a 1.3 rom seemed
foolish.
Well, my 2.04 kit came in this week. Boy was I surprised by the size of
the box. Anyhow, I've installed the rom, cut the traces, installed the
2090a and booted up the 2.04 disk. DH0: shows up as NDOS. Since there is
no hard drive entry in the startup sequence, I guess that makes since. But
the instructions aren't making me feel good. HDtoolbox is for 2091 and
SCSIs. Use your old stuff, it says. Well, I got a A2500 diskette with the
2090a, but how do I tell it to use the new FFS that had never been thought
of for the A2500? (I got the whole system used so I never even went
through the first setup, though I have modified the mountlist a while back
to support AMAX.)
Oh, and the used CSA 68020 card I got that worked fine with the 1.2 ROM
seems allergic to the 2.04. I get a bad card notice right at bootup and
when I continue thru it, I only have chip memory. It can't see the 2MB of
expansion ram. When I remove the card, all is well (but slow).
Any hints will be appreciated while I hammer on the machine over the
weekend. Oh, its a 4.3 rev with ECS Denise and 1MB Agnus. —–Paul—-
Paul,
You don't need to tell it to use FFS, for 2.04, FFS was moved into
the ROM, so the Amiga knows all about it at boot time. Simply use PREP to
set up the whole drive as DH0: (or whatever partitioning you prefer). And
after booting (off the floppy first time of course) you then format it with
the FFS switch to the FORMAT command.
After that, it should be bootable.
Don
Ok, thanks Don. I've gotten to where I (kinda) understand the way MSDOS
machines work and every change I make with the AMIGA throws me for a loop.
—–Paul—–
Paul:
Once you begin to understand the Amiga, I suspect you will begin to _hate_
msdos. I sympathize with your situation. The initial learning curve on
the Amiga is very steep, mostly because of its increadible power and
flexiblity.
I had exactly the same problem when I got my Amiga three years ago.
However, the folks around here helped me get up to speed, and I read a
_lot_ of magazines. In about three months, I was fairly proficient with
the Amiga (by that I mean I had a real handle on the OS), and today I
wouldn't trade it for any other platform. On my last job, I managed to get
an Amiga with a bridgeboard into my office (they were an msdos shop)
because I hated clones so much (but know a lot about using them).
My new job is in a total MAC shop. Since I've only been there six months,
I haven't tried to get an Amiga there _yet_. But, since I have Amax at
home, I'm compatible when I need to work on projects over the week-end
(Amax lets you turn your Amiga into a MAC).
When you run into a problem, post a message here. I can assure you from
personal experience, you will get lot's of help!
?|^] Ray Lewis
Ray–
If you put a Doubletalk board in your Amiga, it would probably fit right in
with the Mac-only shop. What do those folks do with their Macs, anyway?
Jonathan
– via Whap!
I agree. I've been climbing on here every couple of days for about a year
to try to figure out what is going on. The hardest part of changing from
MSDOS to AMIGA is understanding the use of ASSIGN. To understand that
disknames are more important than generic disk addresses is mindboggling.
Mountlist comes next in the hierarchy of what-the-heck. Once you figure
out scripts are batch files, that much comes easy. Anyhum, once I
discovered that the 2.0 prep was not limited to 2091 and scsi, I was
functional. MSDOS is easier because it offers fewer possibilities.
Appreciate your availability.
—-Paul—-
> My new job is in a total MAC shop. Since I've only been there six
> months I haven't tried to get an Amiga there _yet_.
Tell 'em to buy a Mac Toaster. 🙂
steve
Pual – another problem may be that you need new rom's for your A2620 card
(the 68020 board) – those have been out for a few weeks now – it took
Commodore some time to gear up for production of those rom's, months after
2.04 came out. You need the new Rev. 7 or greater rom's to boot up with
2.04; there have been some questions about whether some of the very early
A2620 cards can use the Rev. 7 or above rom's; seems most work fine, some
have problems (mine works fine). The new rom's work fine with all the
A2630 cards.
– via Whap! – Rick Stiphout 🙂
OK, thanks. I will check this out.
—–Paul—-