User`s guide

KwikNet Universal File System Interface
K
A
DAK
C - 1
C. KwikNet File System Interface
C.1 Introduction
The KwikNet TCP/IP Stack does not require a file system for normal use. However,
several of the optional
KwikNet components, such as the FTP client and server and the
HTTP Web Server, do require file services. For these options, KwikNet offers a variety of
file system solutions, all of which are accessed through the Treck file system application
programming interface (API) which is documented in Chapter 6 of the Treck TCP/IP
Stack User Manual.
C.1.1 Treck File Systems
The Treck TCP/IP Stack includes three file system variants. The Treck RAM File
System offers basic file services using a fixed region of memory for file storage. This
simple file system may be adequate for many applications which do not require
permanent file storage. It is an excellent starting point for testing your application before
a real file system is available. For that reason, all of the KwikNet sample programs which
require file services use the Treck RAM File System as an example.
For 16-bit segmented architectures, you must be aware that the entire RAM file storage
region must reside in one 64Kb segment. This restriction may preclude your use of the
Treck RAM File System for all but the simplest of embedded systems.
The Treck ROM File System offers basic file services using a constant, predefined set
of files located in a fixed region of memory. The files must be created using the Treck
ROM FS Builder, a Windows
®
utility provided with the Treck Web Server. The utility
operates as described in the Treck Web Server User Manual.
The Treck DOS File System interface provides access to the DOS file services on an
MS-DOS
®
or Windows
®
platform. KwikNet does not support this file system variant.
If you wish, you can create your own custom file system interface which uses the Treck
File System API to access the services available in your file system. Use the Treck
source code for the Treck RAM or ROM File System as an example. You may find it
just as convenient to use the
KwikNet Universal File System interface described in the next
section to adapt your file system API for use with
KwikNet.