readme.txt

MODC驱动

*************************************************************************
*                                                                      	*
*  DiskOnChip(R) TrueFFS(R) driver for Windows CE - all versions	*
*                                                                      	*
*  Version 6.2.0, from December 30, 2003				*
*  Based on TrueFFS version 6.2.0 					*
*                                                                      	*
*  Copyright M-Systems (c) 2003						*
*                                                                      	*
*  Installation guide & release notes					*
*                                                                      	*
*************************************************************************


GENERAL
--------
This readme explains how to compile the DiskOnChip TrueFFS device driver for 
all versions of Windows CE 

Devices supported by this version
----------------------------------

- DiskOnChip G3 
	Ordering Info:
		MD4811-d512-V3Q18-T-C
		MD4832-d512-V3Q18-T-C
		MD4331-d1G-V3Q18-T-C

- DiskOnChip P3
	Ordering Info:
		MD5832-d256-V3Q18-T-C
		MD5811-d256-V3Q18-T-C

- DiskOnChip 2000 G3
	Ordering Info:				
		MD2402-Dxx-T
		MD2402-Dxxx-T
		MD2403-Dxxxx-T
		
Note: TrueFFS 6.X supports only SAFTL based devices. Devices supported by TrueFFS 5.x are not supported by this release.


Customizing the code for your Windows CE version 
------------------------------------------------
1. For windows CE 3.0 comment the line '#define TALISKER' in FLCUSTOM.H located 
   in TFFSLib\Driver

2. For Windows CE 4.0 uncomment the line '#define TALISKER' in FLCUSTOM.H 
   located in TFFSLib\Driver


Compiling TrueFFS for Windows CE 
---------------------------------
1. Open the Windows CE command line.

   Example: 
   Choose the 'Open Build Release Directory' option in the 'Build' menu item 
   of the platform builder.

2. Make your active directory the root directory of the build tree (the root 
   of this package, in which this readme file is located).

3. If using WinCE 3.00 platform builder or older, make sute #define TALISKER is 
commented in flcustom.h file (which is in the tffslib\driver directory)

3. Type the command: 

   Build -cfs


Customizing and installing the compiled driver into your Windows CE image file 
------------------------------------------------------------------------------
   Detailed explanation for customizing the Windows CE driver for your specific 
   platform and install in the Windows CE image can be found in the 
   binary driver installation manual: Installing TrueFFS for DiskOnChip
   in Windows CE - Installation guide(enclosed). It is recommended to check 
   our web site for the latest version of this manual.

   Note: In version 4.6 of the manual there is a mistake:
   FL_IOCTL_PHYSICAL_FORMAT IOCTL should be replaced with:
   FL_IOCTL_FORMAT_PHYSICAL_DRIVE
   


Known limitations 
-----------------

  1) When cascading DiskOnChip G3 and P3 devices together, 
     TrueFFS will recognize the kind of the two cascaded products as the first product
  2) flChangeProtectionKey() and bdkChangeProtectionKey() functions 
     should not be used when the device configuration contains more than one floor 
     (either dual-die devices or a cascaded configuration).
  3) When using flWriteIPL() and flReadIPL() routines, in order to read/write the IPL 
     in DiskOnChip G3/P3 you should avoid using a larger size then actually supported by the device.
  4) Reading less then a page from a binary partition might return an flOK status even if the block is erased.
     When reading a full page the return status code will report the right status of the block.
  5) Using TrueFFS high level FAT formatter on FAT12/FAT16 boundary is not allowed. 
     The boundary are usually located on 2MB,4MB,8MB,128MB*2^x (x>=0).
     Around those boundary TrueFFS might use FAT16 entries for a FAT12 media which will result in corrupted mount.
  6) The binaries are compiled using the WinCE 4.2 platform builder. 
      The same DLL should work for all CE flavors, but there may be 
      cases where this this DLL is not loaded (no LoadLibrary message at the
      debug messages).
      In those cases, using a binary compiled with the used CE flavor solves
      the problem.
      If you need a binary of a curtain flavor, please contact M-Systems and
      specify which processor and the exact CE version you are using.
 


Contact information
--------------------

  Please visit our website for the latest driver versions and updated 
  information.  

  Internet:      http://www.m-sys.com
  
  E-mail:	 [e-mail]
  
  USA:           M-Systems Inc. 
                 8371 Central Ave, Suite A 
                 Newark CA 94560 USA
  		 Phone: [phone]
  		 Fax:   [phone]
  
  Taiwan:        M-System Asia Ltd. 
                 Room B, 13F, No. 133, Sec. 3
  		 Min Sheng East Road
                 Taipei, Taiwan
                 R.O.C.
                 Phone: [phone]
  		 Fax:   [phone]

  Japan:         M-Systems Japan Inc. 
                 Asahi Seimei Gotanda Bldg., 3F
                 5-25-16 Higashi-Gotanda
                 Shinagawa-ku Tokyo, 141-0022
                 Phone: [phone]
                 Fax:   [phone]
  
  China:         M-Systems China Ltd.
                 25A International Business Commercial Bldg.
                 Nanhu Rd., Lou Hu District
                 Shenzhen, China 518001
                 Phone: [phone]
                 Fax:   [phone]

  Europe:	 M-Systems Ltd. 
                 7 Atir Yeda St. 
                 Kfar Saba 44425, Israel
  		 Tel: [phone]
  		 Fax: [phone]