attachment-0001
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>While studying the architecture of the configuration files,
you may think of various ways to implement the concept into an installation
process.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Some possible scenarios:</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>1. CD installation, device configuration instance on
CD</FONT></DIV>
<DIV><FONT size=2>1.1. the traditional way</FONT></DIV>
<DIV><FONT size=2>all files are on the CD. the references to instance names are
pure file names, no path included.</FONT></DIV>
<DIV><FONT size=2>1.2. web site reference</FONT></DIV>
<DIV><FONT size=2>all files are on the CD, but only get used as a fallback. the
references to instance names are URLs. depending on the installer the URLs are
used automatically or as default (install from CD as second
choice).</FONT></DIV>
<DIV><FONT size=2>keep in mind that the option configuration references can
point to completely different web sites from third-party
developers.</FONT></DIV>
<DIV><FONT size=2>2. network installation</FONT></DIV>
<DIV><FONT size=2>not too much different from the two CD methods.</FONT></DIV>
<DIV><FONT size=2>3. Device installation, device configuration instance in
device</FONT></DIV>
<DIV><FONT size=2>it is not necessary to store more than this single instance in
the device.</FONT></DIV>
<DIV><FONT size=2>all other files could be pulled from web sites or as a
fallback from CD.</FONT></DIV>
<DIV><FONT size=2>this allows for a driver independent installer. imagine the
operating system has a generic UPDF driver installed already (and if not, it
knows where to find at least one), it could pull the single device configuration
file from the device and would find all other information in there.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I see various combinations of the different
methods.</FONT></DIV>
<DIV><FONT size=2>keep in mind that any option configuration stays separate,
even after installation, and can therefore be disconnected or updated
at any time without hurting the installation of the base unit and any other
optional unit.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>These scenarios are not described in the specification
document.</FONT></DIV>
<DIV><FONT size=2>just some personal ideas.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Regards</FONT></DIV>
<DIV><FONT size=2>Norbert Schade</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Norbert Schade<BR>69 Prescott Drive<BR>North Chelmsford<BR>MA
01863<BR>phone: 1-978-251-1017<BR>email: <A
href="mailto:norbertschade@comcast.net">norbertschade@comcast.net</A></FONT></DIV></BODY></HTML>