Eric Auer wrote:
2. FDISK /CLEARALL 1 3. FDISK /MBR 4. FDISK /PRI:2000
That would be dangerous, I think. The bug report was just "it does not boot after fdisk and sys", not "I want to kill all my data". The solution FDISK /MBR will already be enough.
He's testing on a new server, that's soon going to be rebuilt. I think this is a more concise series of steps. I made it clear in my post that "all data will be lost".
If you use a multitasking operating system, then the kernel controls the network drivers, and it will be able to give several programs at the same time access to the network, by managing connection queues and whatnot.
That's the one! You explained it much better:) -- Gerry Hickman (London UK) ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
