home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
C/C++ User's Journal & Wi…eveloper's Journal Tools
/
C-C__Users_Journal_and_Windows_Developers_Journal_Tools_1997.iso
/
sysembed
/
custom.elh
< prev
next >
Wrap
Text File
|
1995-03-30
|
2KB
|
35 lines
[ 9. Customization]
EMBEDDED LAN CUSTOMIZATION
═════════════════════════════════════════════════════════════════════════
Embedded LAN comes ready-to-run on Ethernet LANs (even on PCs booting
Embedded DOS on any corporate network, using standard Ethernet network
interface cards.) You'll want to customize the modules for your real
embedded application.
Customizing the LAN is easy, since the product is so modular. There
is a module for heap management, and the heap size is controllable.
There is also a module that implements a Physical Provider; the one
that comes with Embedded LAN for Ethernet is called ETHERNET.EXE. Its
interaction with the underlying Crynwr packet driver is configurable.
For example, you may wish to duplicate our ETHERNET.C module and use
it as a base for an ARCNET.C module that provides the PDI services over
new media types.
The Transport Provider that comes with Embedded LAN implements a custom
transport protocol that supports reliable and best-effort connection-
oriented delivery, plus datagrams. You may wish to support TCP/IP, ISO,
IPX/SPX, or other protocols. To do so, just clone the code we provide
and insert a new protocol engine.
The File Sharing Redirector and File Sharing Server are both components
that communicate across the LAN via Transport Driver Interface messages.
Because the underlying transport protocol is transparent to the server
and redirector, any transport protocol may be substituted for the one
provided, and a new file sharing protocol that is compatible with LANMAN
or Novell NetWare can be substituted.
You may also wish to simply integrate the components directly into your
own application program. Because most of the Embedded LAN software is
written in C, it is possible to move the code to ROM to save space.