Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: alt.os.development,comp.os.msdos.programmer,alt.lang.asm Subject: Re: detecting emulation or console windows Date: Mon, 02 Jun 2014 00:48:59 -0400 Organization: Aioe.org NNTP Server Lines: 37 Message-ID: References: NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.16 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.os.msdos.programmer:1378 On Sun, 01 Jun 2014 15:57:04 -0400, James Harris wrote: > Here's a thought. After altering each hardware setting is there some way > you could check that the setting has taken effect? If it hasn't then you > know not to continue and you are probably running in an imperfect > emulation. Yes, something like that might need to be done, if I stick with the reject all emulation idea. I also need to reject DPMI hosts that don't have certain functionality. Earlier today, I considered creating a test for DPMI client. If it fails, then exit. Currently, I've tested a bunch of DPMI hosts and I'm doing a general check which works for most of them. An explicit run-time test would allow for hosts I simply can't test. > Something up with your line wrapping? > IE6 could be set to auto-matically wrap at a specific length for Usenet posts. This browser (Opera) doesn't auto-terminate posts at a specific length, AFAICT. Maybe, the option is buried somewhere. So, currently, I have to enter a return explicitly. I try to keep it to 72 to 74, but those posts were a bit long. Usenet RFC 1855 recommends a CR at 65, but 72 is common for Usenet. With variable width fonts, I'm constantly guessing where 72 is ... Typing .123456789 repeatedly becomes tiresome. In this case, Google Groups seems to have added their own wrapping to two posts of mine, around 71 to 77. Or, perhaps it was the Usenet provider they receive their posts from. That's not something which should be done. Usenet servers where I read did *not* wrap the posts, even though they were long. Usually, it's those who use GG whose posts don't wrap correctly, i.e., continue forever. Rod Pemberton