OWC Neptune Firewire 400 160gb, not working right on beige..

it is showing the whole capacity of the drive (i.e. about 147 gb if I
recall).
vdubreeze RemoveThis @earthlink.net wrote:
> When the Neptune is mounted is the full capcity of the drive being
> recognized? There might be some combination of factors (including a
> generic PCI card) that won't recognize over 137 gigs (as the G3
> internal won't) over the Firewire. Seems unlikely, but that's the
> behavior when you put a larger formatted drive on a chain that suffers
> from that, and between the older G3/OS9/old (?) Firewire card and a
> newer drive it's something to check out.
>
> Naturally it won't show a capacity of 160, but it should be more like
> 150 due to the way a drive formats. (Same way the 120 will show 115
> available gigs.) But if it shows 137 capacity there's something in
> the chain that's not up to date.
>
> Might not be this, but I had a generic Firewire card that was extremely
> fussy on my last Mac.
>
> V
>
>
>
> michaelalcandor RemoveThis @gmail.com wrote:
> > I am using a firewire PCI card. I also use an OWC Mercury elite 120gb
> > drive that works flawlessly. This neptune though is causing my machine
> > to freeze whenever I copy a somewhat large file to it. I'm using OS
> > 9.2.2
> >
> > has anyone had similar problems?

michaelalcandor DeleteThis @gmail.com wrote:
> it is showing the whole capacity of the drive (i.e. about 147 gb if I
> recall).


Then I'll bet it's a screwed up directory, or similar. If you run
Apple's Disk Utility on it does it say something like "reports
incorrect number of blocks" or something like that? (Haven't run 0S9
in a while). That kind of thing is the result of a crash or
interuption of a drive activity so the drive is confused or insisting
that things aren't where they actually are and tries to copy something
over to a block it thinks is empty but isn't (unless, of course, you
hear platters clacking, which is, well....... : ( )

If it is a problem like that sometimes Apple's utility or a third party
one won't get it on the first time, so sometimes using one then the
other and back and forth can oddly enough fix it after a few rounds.

Apple's utility alone was never been enough to get me out of most
software based drive screw-ups, but it was usually the first thing I'd
reach for. You'll need a third party's OS9 utility if it's deeper
than the common directory stuff.