drh@sun.uucp (D. Ryan Hawley) (02/04/89)
I have an Amiga 2000 it contains an Pacific Peripheral's controller
and a Fuji SCSI diskdrive. Everything worked o.k. under 1.2 with
one large 47 MB partition. Since I installed 1.3, and created
numerous partitions (FastFileSystem partitions) the system GURUs
with an 8200003 (this number may not be EXACTLY right, but it does
end in 3 (a write to a protected area)), during disk copies. I had
all the exact details of how the disk was partitioned, etc. but it
was lost during a system crash. If anyone is familiar with this
and wants more details, please call me or write to me directly.
I used to have a similar problem during the low level (Overdrive
format (Overdrive is the Pacific Peripheral's driver software)).
The problem then was the ASDG 8 MB memory board. It had to be
removed during the low level format. Could this be part of the
problem? It is somewhat intermittent. It seems that there is
no particular problem with Slow File Systems partitions (DH0:
was partitioned this way for a few days, and I had less problems.
As I said I lost the complete devs/mountlist [copy] that I was
going to post (and I want to get this out!). It was set up
just like the example for FastFileSystems though, except # of
heads, # of Cylinders, driver {overdrive.device}, buffers are
5, and BuffMemType is 5. We also used the mask for FastFileSystems
and DosDiskType. I will post the devs/mountlist, and the
s/startup-sequence if requested to do so.
Thanks, David (Ryan) Hawley, W: <408> 276-3260
H: <408> 773-8158
--
{{{{{{{{{{{{{{{{{{{{{{{{{ * }}}}}}}}}}}}}}}}}}}}}}}
D. Ryan Hawley "And they will fly with the wings of Eagles"
{{{{{{{{{{{{{{{{{{{{{{{{{ * }}}}}}}}}}}}}}}}}}}}}}}fgd3@jc3b21.UUCP (Fabbian G. Dufoe) (02/05/89)
From article <88295@sun.uucp>, by drh@sun.uucp (D. Ryan Hawley): > The problem then was the ASDG 8 MB memory board. It had to be > removed during the low level format. Could this be part of the > problem? It is somewhat intermittent. It seems that there is Check your memory. Defective expansion RAM can cause intermittent problems of all kinds. The system will tolerate it until some system list is written to the bad address. When it tries to read the bad address it's all over. I was getting system crashes quite often because of defective memory. I worked up a software fix that seems to work. It patches the system's memory free list so it will think the bad addresses have already been allocated. At any rate, you need to run a memory diagnostic to see if that could be your problem. --Fabbian Dufoe 350 Ling-A-Mor Terrace South St. Petersburg, Florida 33705 813-823-2350 UUCP: ...uunet!pdn!jc3b21!fgd3