Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcnc!ecsgate!ecsvax!paleo
From: paleo@uncecs.edu (Constantine A. LaPasha)
Newsgroups: comp.sys.amiga
Subject: Re: The A-590/2091 FFS problem
Summary: none of these fixes work for me either...
Keywords: Location 0
Message-ID: <1990Jul16.023510.12197@uncecs.edu>
Date: 16 Jul 90 02:35:10 GMT
References: <2085@gould.doc.ic.ac.uk> <6600012@okcusr.UUCP> <1449@nyx.UUCP> <1581@nyx.UUCP>
Organization: UNC Educational Computing Service
Lines: 20



I'v got the FastFileSystem installed properly (from the WB 1.3.2 
release disk) and have tried the various other "fixes" to remedy
the non-zero mem loc 0 on boot -- but no luck at getting anywhere.
I assume it's something with the A2091 since it does it without
my A2630 board installed, it does it even if you strip out
*everything* from the startup-sequence, and does the same thing
if you cold boot directly into the 2630 monitor and check the
contents of that mem. 

The interesting thing is that I've never seen the "gdos" string there.
I consistently get 0x0b 0x00 0x00 0x08 as the 1st 4 bytes.

Does anyone else with this "problem" have similar symptoms??
Anybody got any clues??
-- 
===============================================
Kostya LaPasha          paleo@ecsvax.uncecs.edu
==== ... virtually, we can do anything ... ====