On Aug 17, 9:03 pm, Polymorph <polymorp...@hotmail.com> wrote:
On Aug 18, 10:24 am, commodorej...@gmail.com wrote:
> On Aug 17, 6:43 pm, "Bill Garber" <willy4...@comcast.net> wrote:
> > <commodorej...@gmail.com> wrote in message
> >63539f71-9ede-4aca-b620-e5d78e25cb1a@59g2000hsb.googlegroups.com">news:63539f71-9ede-4aca-b620-e5d78e25cb1a@59g2000hsb.googlegroups.com...
> > >I don't think this is the case, since, as stated, the setup was
> > > working just fine until a few days ago; no hardware or settings were
> > > changed. If this were the case, what could I do to fix it?
> > If no hardware or setting changes were made, and the BRAM battery
> > is good, then this leaves only one thing, software. Was anything added
> > or deleted between the time that it worked and the time that it did not?
> > Bill Garber from GS-Electronicshttp://www.garberstreet.com
> Shortly before it stopped working, I formatted the empty space on the
> drive as an HFS partition, to keep the SCSI card from searching
> through 700+ MB of empty space for partitions. It worked for about a
> day after that, then stopped working. Could that be the cause of the
> problem?
This sounds suspiciously like the cause of your problems.
Incidentally, how did you manage to format part of the drive as a HFS
partition? The CMS SCSI card only supports ProDOS partitions and the
partition info is only known by the CMS SCSI card itself - i.e. the
partition table is not written to the disk unlike the Apple SCSI and
RAMFast SCSI cards.
Cheers,
Mike
Hmm. Well, I did the formatting by hooking it up to my Mac; had I
known that about the CMS card, I probably would've thought twice! I'll
try backing up my stuff and reformatting it tomorrow, but I do wonder
why it worked for a day with the HFS partition before giving out if
that was the problem...huh.