These archives contains a boot disk made with Caldera Dos 7.02 which boots up with a menu where you could select a
 Kermit 6-Screen Telnet or a NFS Client. Then a batch asks you for the right netcard driver (for users of EtherBoot the batch
 automatically loads the right driver!). The clients uses packet drivers and expects that a bootp or a dhcp server is active for
 address assignment (which is in most cases true if you use the image for remote booting), otherwise you have to create a
 wattcp.cfg with the proper values (I put a sample in ..\etc, wattcp.cxx). You have only one thing to edit: the ..\etc\hosts file
 needs the correct ip address of your unix host. Of course your unix host must export some directories, and these directories
 must be the same as in the ..\etc\fstab file if you want to use the NFS client, perhaps for making an image of your workstation
 with Ghost, DriveImage or something else. If you use an ISA card, the packet driver needs the correct base address and the
 interrupt, so take also a look at the ..\pkt\startpkt.bat file to load the driver with the proper values. 
 There are two different archives available: cal7pd.zip contains an image file of the boot disk. To make a disk out of the image
 file there a several ways depending on the os you are using, with linux use the following command to make a bootdisk:
 dd if=cal7pd.img of=/dev/fd0. With dos you could use rawrite which comes with most linux distributions, look on your CD
 under \dosutils or so. A fine tool for Windows is WinImage, you can find it here. 
 The other archive, cal7pd.tgz, extracts to a directory cal7pd, and this is useful for making a boot image, as the mknbi-dos
 from the NetBoot distribution has problems with reading the bootdisk. Use the following command to make a boot image from
 the directory version: mknbi-dos cal7pd dosImage. This dosImage could be used by EtherBoot or NetBoot. 

 Another bootdisk I've created, cal7od.zip, uses the odi driver interface from Novell as included with Caldera Dos 7.02. Kermit
 could also use the odi driver interface directly, so no changes to the scripts needed. If you use marsnwe, you could test the ipx
 stack and login with netx. If you use samba, the odi interface might be a good base for the MS-Clients.  

 At the moment the kermit script is a quick hack from the mskermit.ini file, but it works... 
 I'm working on it to make it clean but this will take a bit time.... 
 The keyboard also needs some revision, if someone knows all the codes linux expect please tell me. 
 If you think that something could be done better or if it doesn't work, please mail me.