On 6/18/2012 11:00 PM, Rugxulo wrote: > Hi, > > 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? ;-) >
No .. not in this case. If it's mission critical then it should be running on an operating system designed to do that kind of task. I originally thought it was a hardware problem based on the "general error reading drive c" messages. If it really was a hardware fault and you were on a Linux machine, /var/log/messages or dmesg would have narrowed it down pretty quickly. Here we were left to guess at which combinations of DOS and TSRs were screwing up. I'm going to repeat the advice again - run Linux. Any even slightly older version of Linux is going to be stable and robust compared to DOS. DOS just isn't designed to do this kind of thing. Mike ------------------------------------------------------------------------------ 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 Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
