The Universal TCP/IP Network Bootdisk is a DOS bootdisk that provides TCP/IP networking support. It's designed for use in Microsoft networking environments, on either peer-to-peer or domain based LANs. Currently 98 different network card drivers all included, all on the single 1.44MB disk! Most people use this bootdisk for "Ghosting" PC's over a network connection. This disk will provide the DOS networking and drivers to allow the mapping of a network drive containing your imaging software and files. TCP/IP based image transfers, like GhostCast is also supported!
Adding Network Card Drivers
It is possible to add network card drivers. The M$ Client software uses NDIS2 Real-Mode .DOS drivers. Here are the basic steps for advanced users:
- Part 1 - Adding (or update) the driver itself:
- Find your NDIS2 .DOS Realmode driver. It'll have 2 files, a .DOS file and a protocol.ini file. For this example I'll call it demo.dos
- In the protocol.ini file, look for the line that contains the drivername=something$ entry point line. Remember this!
- Create a new text file with the same filename as your new driver's filename, however use the .INI extension instead. eg: demo.ini
- In your new .INI file, copy the drivername=something$ line from the protocol.ini file. eg: drivername=demo$ - Most of the time the entry point is the same as the driver's filename - but not always!!! Try hexediting the DOS file if you're lost for idea's of what it could be. It's normally written in plain text within the error message strings inside the file.
- Once you have your two files, use UHARC 0.6b to modify/add files to FILES.UHA
- Part 2 - Editing the Menu (for new drivers):
- Edit carddata.txt within files.uha This is a space delimited text file that the menu program reads. It's pretty easy to follow, so just insert a line for your new card.
- The P/I/C column states if the card is PCI, ISA, or CardBus/PCMCIA. This has no real effect other than to make the end user's life easier.
- The 10/100/1000 Column is also for display purposes.
- Three short lines of comments can be included. Take note of the spacing!!
- The * next to some entries means this entry is a duplicate, so don't use it to resolve an autodetected driver's name.
- Part 3 - Adding PCI autodetection codes:
- Edit the NDIS.MAP within FILES.UHA
- This is a text file. There's sample syntax included inside it.
UHARC Compression Syntax
I use this compression syntax for UHARC:
uharcd a -y+ -p- -r -mx -ac+ files.uha .\zip\*.*
...where the files to compress are located in a subdirectory called ZIP.
