| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2299.1 | I think it's a chip swap... | DIXIE1::MCDONALD | Surly to bed, surly to rise... | Wed Mar 01 1989 12:14 | 8 |
| Hmm... I think the only way to get back to Kickstart 1.2 is by
replacing your 1.3 rom chips with 1.2 rom chips. Most people go
in the other direction. However, if it is VERY important, you might
be able to purchase used 1.2 rom chips from someone who has upgraded
to 1.3 roms. (Or do you get to keep your 1.2 chips when you upgrade?)
John
|
| 2299.2 | | GUCCI::HERB | | Wed Mar 01 1989 17:57 | 4 |
| Can I get 1.3 ROM chips for the amiga 500
matt
|
| 2299.3 | Yes | WJG::GUINEAU | | Wed Mar 01 1989 18:00 | 5 |
| > Can I get 1.3 ROM chips for the amiga 500
Yes. I think they're around $40 or so.
John
|
| 2299.4 | | BOMBE::MOORE | So many holes to plug | Thu Mar 02 1989 02:55 | 2 |
| What software fails with 1.3? I don't recall many problems in this
area...
|
| 2299.5 | | LEDS::ACCIARDI | | Thu Mar 02 1989 08:01 | 6 |
|
I thought the only difference between 1.2 and 1.3 ROMs was the ability
to autoboot a hard drive.
Ed.
|
| 2299.7 | Bad ROMs and Compatability | ANT::GERBER | For more information: call 800/555-1212 | Thu Mar 02 1989 09:15 | 9 |
| There have been a number of bad 1.3 ROMs distributed by Commodore.
I had one myself, the symptom was many GURUS (00000003.xxxxxxxx
& 00000004.xxxxxxxx) I exchanged it for a new one and that one
worked. I haven't run into any Kickstart compatability problems,
however, I have run into AmigaDos problems.
The main problem was that the initial setup for MoneyMentor has
to run under 1.2 DOS (KS doesn't matter) but it does run fine on
1.3 after it has been initially setup.
|
| 2299.8 | What BAD ROMs?? | RAIN::WDEREN | | Thu Mar 02 1989 10:42 | 15 |
|
>There have been a number of bad 1.3 ROMs distributed by Commodore.
>I had one myself, the symptom was many GURUS (00000003.xxxxxxxx
>& 00000004.xxxxxxxx).
How can I tell if I have the bad ROMs? I just installed 1.3 in
my A2000 and Autoboot ROMs in my GVP SCSI controller. I had problems
running the GVP install programs until I disabled FAST RAM then
everything ran ok. Finally got everything running but now I get
random visits to the GURU (typical example: did a DIR on a disk then
tried to COPY a file to the hard drive and GURU!). I'm running
a 2Meg Micron board and have had no problems running under V1.2.
Any Ideas?? BTW Autobooting directly into FFS makes for an entirely
different machine (Gee ain't technology grand!!) it's FAST!!
|
| 2299.9 | | ELWOOD::PETERS | | Thu Mar 02 1989 11:45 | 9 |
|
re .8
The problem is the RAM board. The GVP controller and the Micron
memory board do NOT work together. The GURUs are caused by this
combinations.
Steve
|
| 2299.10 | It's run ok with 1.2 | RAIN::WDEREN | | Thu Mar 02 1989 15:07 | 21 |
|
re .9
> The problem is the RAM board. The GVP controller and the Micron
>memory board do NOT work together. The GURUs are caused by this
>combinations.
I've been running this combination under V1.2 for about 5 months
without seeing any problems.
Could the incompatibilities have come up in V1.3 Kickstart code??
Or in the GVP autoboot ROMs?? This makes me wish I had stayed with
Commodore equipment (although it's more expensive) at least it's
(supposedly??) compatible. I'm going to call GVP and see if I can
get any clarification about this problem.
What makes me mad is that I asked about any problems with running
these boards together when I ordered the controller.
Bill
|
| 2299.11 | Direct to FAST in 1.3 | ELWOOD::PETERS | | Thu Mar 02 1989 22:15 | 9 |
|
RE .10
WB 1.3 started the problem. Before 1.3 all DMA was done to
Chip memory and copied into fast ram. If you use 1.3 and the
FFS then DMA goes directly into Fast RAM and shows the problem.
Steve
|
| 2299.12 | GVP and SPIRIT board incompatible | CHPSC::STEIGER | | Fri Mar 03 1989 13:46 | 16 |
| I would like to add an other WARNING to the conference.
I bought a GVP Impact a500 Hard disk, a great product (82Mb and
11mS access time). However I had a SPIRIT 1.5Mb internal extension
board installed. --- Random GURU's 000003.xxxx --- Not configuring
the 1.5 Mb cured the problem. Running the memory test forever did
not show any problem.
Obviously an other incompatible memory with GVP...
I am bringing the SPIRIT Board back to the dealer and buy the 2Mb
option built into the GVP drive. Hopefully this one works.
Btw. I am running V1.3, new kickstart ROM and autoboot from
Fastfilesystem -- works great.
|
| 2299.13 | MAXTRANS was the Problem?? I hope. | RAIN::WDEREN | | Fri Mar 03 1989 15:22 | 23 |
|
Well I think (more like hope!) I have solved my problem with the
random GURU's... a friend who owns 2 A2000's and has had a lot of
experience with add-on hardware (running CSA 68020 w/dragstrip in
both with Commodore and non-Commodore boards) suggested I read an
article on setting up and running SCSI's that was in the Amiga
Transactor. The article talked about problems caused by using too
large a value for MAXTRANS in your mountlist, evidently this value
acts as a limiter to prevent the SCSI from overloading the system
on data transfers.
After reading the article I ran GVPprepHD to re-configure
the HD mountlist that GVP uses and adjusted 2 of the parameters:
BUFMEMTYPE (I had it set to 4=FASTMEM, changed it to 1=any available)
and MAXTRANS (from 8192=max recommended by GVPprepHD to 2048= 1/2
the recommended). I worked the system for about 2 hours last night
and didn't get ANY GURU's sooooo.... I hope this was it. I really
love the way it runs now (15sec on a warm-boot with LOADWB using
the delay switch) and would hate to have to go back to V1.2.
Bill
|
| 2299.14 | | LEDS::ACCIARDI | | Fri Mar 03 1989 16:02 | 7 |
|
The incompatibilities between the GVP and Spirit (.12) seem to
underscore the need to NOT mix DMA and 'plug into the 68000 socket'
type devices. Plug-in type products don't generally have the (more
expensive) hardware needed to do DMA.
|
| 2299.15 | Check your memory connection | TLE::RMEYERS | Randy Meyers | Mon Mar 06 1989 19:01 | 20 |
| Re: memory boards not working with disk controllers
I had a very similar problem awhile back: I have a Pacific Peripherals
disk controller and an ASDG 8 Meg board. (ASDG designed the Micron board.)
When I used the FFS, I would at random times get gurus: usually 3's or 4's.
The problem didn't happen using the old file system. The problem was
improved by using a lower MaxTransfer value.
The problem completely disappeared when I took the memory board out and
reseated it in the slot. I don't know why this fixed the problem. The
board seemed pretty good and tight in the slot before I reseated it, but
it made my problem go away (I've had no problems since last November).
I also vacuumed all the dust out of my 2000 at the same time (who knows,
that may have been the problem). The 2000 collects dust pretty quickly
because of the power supply fan.
I wrote all of this up many notes ago in a note about the Pacific Peripherals
controller.
|
| 2299.16 | AN EXAMPLE | TDCIS3::POUTHIER | | Wed Mar 08 1989 03:36 | 9 |
| re : 2299.4
An example : We have a software call'd DISK MANAGER, which one
authorize to change the drive affectation:
if you have on your config 3 drives DF0: DF1: DF2: with that
program you change intern drive as DF1: extern drive as DF0:
and so on.
with kickstart 1.2 DISK MANAGER will run fine but with 1.3 no at
all ????
|