Date: Mon, 5 May 1997 12:32:50 -0700 (PDT) From: Jonathan Mini <j_mini@efn.org> Cc: emulation@FreeBSD.ORG Subject: Re: Report on DOSCMD Message-ID: <Pine.SUN.3.95.970505123058.636A-100000@garcia.efn.org> In-Reply-To: <Pine.SUN.3.95.970505120910.28327D-100000@garcia.efn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 May 1997, Jonathan Mini wrote: Heh. This is what I get for writing email in a public lab -- I never mention ed the point. Which was that those errors are "proper" -- they should be there, since the service being probed isn't there. Unless doscmd become some sort of super-emulator that emulates every strange sort of protocol ever outdated or obseleted, (got I hope not, some of them were nasty) we will always see errors like that. > On Mon, 5 May 1997, Pedro F. Giffuni wrote: > > Interestingly enough, most of those "unknown interrupts" are the programs > probing for services that doscmd does not support. > Querying for services in DOS is not a polite process, and the > application expects an error like that so it assumes the service isn't > avialable. =) > > > Howdy, > > The doscmd is great, I stood up all day testing all the DOS 5.0 programs > > I could find. I'm attaching my report, if you guys need more detailed > > debugging please tell me and I'll help as I can. > > The OpenDOS source code is also available at: > > http://www.caldera.co.uk/ > > > > best regards, > > > > Pedro. > > > > Jonathan Mini (j_mini@efn.org) > > ... Desolation ... Despair ... Plastic Forks ... > Jonathan Mini (j_mini@efn.org) ... Desolation ... Despair ... Plastic Forks ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.95.970505123058.636A-100000>