It may depend on what the differences are between connecting to server1 and server2. Is there hardware, client, or protocol differences or is the difference merely the domain?<br><br>Hardware profiles can be easily used to differentiate between standalone and networked, basically by disabling the NIC in the standalone profile.<br><br>You can use a "multi-boot" config.sys file to further configure a specific profile. A basic config.sys with multi-boot is as follows:<br><br>[menu]<br>menuitem SA, Standalone <hardware profile name<br>menuitem S1, Server1 <hardware profile name<br>menuitem S2, Server2 <hardware profile name<br>menudefault SA, 10<br><br>[SA]<br>"drivers or settings specific to this profile"<br>[S1]<br>"drivers or settings specific to this profile"<br>[S2]<br>"drivers or settings specific to this profile"<br>[common]<br>"common drivers and settings for all profiles"<br><br>Your autoexec.bat file would need to be configured to branch based upon the selection.<br><br>@echo off<br>goto %config%<br><br>:SA<br>"configuration"<br>:S1<br>"configuration"<br>:S2<br>"configuration"<br><br>The autoexec would be where you took care of the differences in which Hardware Profiles could not.<br><br>This could be done by creating .REG files from registry exports and merging them to get the settings you need using regedit.<br><br>You could also copy and rename INI files for any settings differences.<br><br>If you have more detail on the differences between the server connections please provide that.<br><br><br><br><br> <p>Doug<br><a href=mailto:dxd_2000@yahoo.com>dxd_2000@yahoo.com</a><br><a href= > </a><br>