I am trying to get Ghosting peer-to-peer running over a LAN. The boot disk is a floopy running MS-DOS. The network used to perform fine until a recent upgrade by the "gurus" to 100MB Full Duplex caused my Ghosting p2p to become a nightmare. Checking under NT4, the network cards are capable of 100Full. But how can I force the boot disk to go to 100 Full and not just Auto? I have tried [E100B_NIF] Drivername = E100B$ FORCEDUPLEX = 2 but the Ghosting, which used to take 5 mins now wants about 30 hours to run !! I am thinking that somehow the duplex is keeping to half, but really can't figure out what is happening. Oh, btw, sometimes I will find two ports, and I can ghost like a dream. There seems to be no consistency. I cannot get to the switches (Cisco).....or is there a way via DOS to at least interogate a switch port to see what it is set at? Many thanks, JB

You have a good question here. I would venture a suggestion of not setting speed or duplex. See if autonegociation doesn't work it out correctly. Otherwise I would think you would have to have managed switches and you could then view what pc, by port, connected at what speed/duplex. You would run the appropriate script for that port setting setting for that workstation. Autonegociate, as nonreliable as it is, might be your best bet.

hi, We discovered if using Cisco equipment the best results are when the ports on the switches and servers are set to "auto" duplex and speed. also, check that they havent messed about with the multicasting features. cheers