From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stas Sergeev Subject: Re: tcp/ip + samba + dosemu Date: Mon, 26 Jun 2006 22:10:59 +0400 Message-ID: <44A02333.9000500@aknet.ru> References: <449EAAA4.8030502@aknet.ru> <200606251754.02465.zswi@pers.pl> <44A01130.8080308@aknet.ru> <200606261952.43162.zswi@pers.pl> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <200606261952.43162.zswi@pers.pl> Sender: linux-msdos-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="windows-1252"; format="flowed" To: =?UTF-8?B?UmFmYcWCIEN5Z25hcm93c2tp?= Cc: linux-msdos Hello. Rafa=C5=82 Cygnarowski wrote: > I have similar configurations elsewhere. I use DosEMU + Novell Client= to run=20 > sales program (based on clarion database). So locks works as they are= =20 > expected to work. I see. But for the msclient there is no way, so you'll have to somehow deal with the dosemu locks at that point (which are not). > Maybe... I can risk some unstability (and I'm doing this just becouse= of=20 > choosing DosEmu instead of separate computer with DOS) but I can't ri= sk data=20 > lost (at least not too much).=20 That's why the testing is due before running it on a mission-critical data. If your data is so critical that you can't even trust your own testing, then I guess the software without a warranty is a bad choice for you. :) Obviously you can't trust dosemu being called stable. Have you seen dosemu-1.0.0 or 1.0.2? They were called "stable"... - To unsubscribe from this list: send the line "unsubscribe linux-msdos" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html