Re: [Freedos-user] re: FreeDOS FDISK another partition problem

2005-07-29 Thread Gerry Hickman

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=7477alloc_id=16492op=click
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] re: FreeDOS FDISK another partition problem

2005-07-28 Thread Eric Auer

Hi...

 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.

  run some heavy calculation job, FreeDOS surely will better than any
  Windows server, since DOS have no (or very little) overhead.

 Yes, that's what I'm thinking. The problems will arise when you can't do 
 multi-tasking and multi-threading, and utilizing full power of load 
 balancing on dual XEON:(

Sorry, DOS for heavy server work is like who needs a building to run
a power grid? It is much lower overhead to just hold those wires togeth...

 Have you tried DR-DOS's multitasking?

Even that will not virtualize the hardware - there is only ONE network
card and DR DOS will still run on only ONE CPU (no hyperthreading either).
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.

The small DOS overhead can be nice if you run a single program which
has to crunch lots of numbers without getting disturbed by other running
tasks and by a variety of gadgets that you have in RAM and maybe even
eating some CPU time while your number cruncher does not need them at all.
On the other hand, there are things for which DOS is definitely NOT best.

Eric


---
SF.Net email is Sponsored by the Better Software Conference  EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile  Plan-Driven Development * Managing Projects  Teams * Testing  QA
Security * Process Improvement  Measurement * http://www.sqe.com/bsce5sf
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user