>> On Mon, Jun 18, 2012 at 6:25 AM, Tom Ehlert<t...@drivesnapshot.de>  wrote:
>>> conclusion: don't use FreeDOS as a 'server' machine.
>> Sure, that's the obvious "easy" way out.
>> But wouldn't it be better "overall" (and wiser) to 1). actually find
>> out what MS-DOS does, and 2). "fix" it in FreeDOS' kernel?    ;-)

> If it's mission critical then it should be running on an operating 
> system designed to do that kind of task.
software should NEVER run on a *buggy* system.

but, from http://en.wikipedia.org/wiki/File_locking
  'Windows inherits the semantics of share-access controls from the MS-DOS 
   where sharing was introduced in MS–DOS 3.3'

looks like MSDOS 3.3 was designed for this sort of problem.

that FreeDOS kernel doesn't implement proper 'multitasking' with
NET.EXE is an entirely different story

anjd yes, Linux is the better tool at hand.


Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Freedos-user mailing list

Reply via email to