Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: A2091 - question re: which FastFileSystem file to use?
Keywords: A2091 FastFileSystem
Message-ID: <1387@lpami.wimsey.bc.ca>
Date: 10 Apr 90 11:42:24 GMT
Lines: 35
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <1990Apr11.032032.12598@uncecs.edu>, paleo@uncecs.edu (Constantine A. LaPasha) writes:
 >
 >Is there a way I can tell (say, using a hex-editor) what version of
 >the FastFileSystem I have, and if I need to get a newer (different?)
 >version.  

7> type L:fastfilesystem opt h

0000: 000003F3 00000000 00000001 00000000    ...?............
0010: 00000000 00000BED 000003E9 00000BED    .......?...?...?
0020: 600E5633 362E3033 28352F39 2F383929    `.V36.03(5/9/89)
...

 >I have tried the above mentioned 3 versions, and a fourth that I'm
 >using on an A1000+stardrive+MiniScribe setup..  They all seem to act the
 >same with Turbo Silver.  (The "HDFIX" provided by Impulse seems to work,
 >but I thought I heard that I should be able to get everything working
 >ok if I had the correct FastFileSystem.)

They could well be the same. The file date is not a reliable indication of the
sameness of two files.

 >(This is in reference to mem location zero problems)

I think that progblem was a result of the driver, not the file system.

-larry

--
Entomology bugs me.
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+