top of page

The Prayer Circle

Public·11 Prayer Partner

The Last Haven Free [VERIFIED] Download (v1.10.03)


------------------------------Subject: comp.os.msdos.programmer FAQ part 1/5This is part 1 of the frequently asked questions list for the newsgroupcomp.os.msdos.programmer.Part 1: Section 1. General FAQ and Newsgroup Information Section 2. General Reference------------------------------Subject: comp.os.msdos.programmer FAQcomp.os.msdos.programmer FAQ Version 2.07Copyright 1996 by Jeffrey Carlyle, Stratoware. All rights reserved. Thisarticle is not in the public domain, but it may be redistributed so longas this notice, the acknowledgments, and the information on obtaining thelatest copy of this list are retained and no fee is charged. The codefragments may be used freely; credit would be polite. This FAQ is not tobe included in any static archive (e.g. CD-ROM or book); however, a pointerto the FAQ may be included. ============================= TABLE OF CONTENTS =============================Part 1: Section 1. General FAQ and Newsgroup Information Section 2. General ReferencePart 2: Section 3. Compile and Link Section 4. KeyboardPart 3: Section 5. Disks and files Section 6. Serial ports (COM ports)Part 4: Section 7. Other hardware questions and problems Section 8. Other software questions and problemsPart 5: Section 9. Downloading Section 10. Vendors and products------------------------------Subject: Section 1. General FAQ and Newsgroup Information - What is this article for? - Who has contributed to this article? *revised* - How can I search this article for a particular topic? - Are the answers guaranteed to be correct and complete? - What is comp.os.msdos.programmer about? - Is comp.os.msdos.programmer just for C programmers? - What is comp.sys.ibm.pc.programmer? - Is comp.os.msdos.programmer available as a mailing list? - What's this "netiquette"? - How can I learn more about Usenet? - What other technical newsgroups should I know about? - Where are FAQ lists archived? - Where can I get the latest copy of this FAQ list?------------------------------ Subject: - What is this article for? Date: Fri, 13 Jan 95 15:34:00 CDT This is the FAQ (Frequently Asked Questions) list for the newsgroup comp.os.msdos.programmer. This list is maintained in versions; new questions and revised questions in this version are not marked do to the restructuring of the FAQ; however, in future versions new or revised questions will be marked with "*new*" or "*revised*" in the subject. This list is posted every 20 days. FAQ lists are intended to reduce the noise level in their newsgroups that results from the repetition of the same questions, correct answers, wrong answers, corrections to the wrong answers, corrections to the corrections, debate, etc. This list should serve as a repository of the canonical "best" answers to the questions in it. The names of folks who have helped to improve this FAQ list are listed in - "Who has contributed to this article?". ------------------------------Subject: - Who has contributed to this article? *revised*Date: Fri, 7 Jul 95 12:00:00 CDT This list is maintained and edited by Jeffrey Carlyle. To contact him send email to or via surfact mail to: Jeffrey Carlyle Stratoware Software Services 297 Meadowlark Trail Bowling Green, KY 42101-9427 The major contributor to this list is Stan Brown, the former list maintainer. Most of this list was written by Stan. Many articles posted in comp.os.msdos.programmer sparked ideas or provided information for the first version of this list. Though they are not responsible for any errors, thanks are due to the following persons for posted articles or private email that led to improvements in this FAQ list: Jamshid Afshar, Mark Aitchison, Sanjay Aiyagari, George Almasi, Aaron Auseth, Robert Baker, Preston Bannister, Scott Barman, Denis Beauregard, Per Bergland, Mike Black, Chris Blum, Ron Bodkin, Mark Brader, Jon Brinkmann, Andrew James Bromage, Glynn Brooks, Paul Brooks, Ralf Brown, Stan Brown, Shaun Burnett, D'Arcy J.M. Cain, Jeffrey Carlyle, Raymond Chen, Kelly Cooper, Denny de Jonge, Eric DeVolder, Alan Drew, Paul Ducklin, Gary Dueck, Roland Eriksson, Mark Evans, Markus Fischer, George Forsman, Roger Fulton, Vincent Giovannone, Robert Grunloh, B.Haible, Janos Haide, Klaus Hartnegg, Kris Heidenstrom, Tom Haapanen, Joel Hoffman, Ari Hovila, Chin Huang, Daniel P Hudson, Joe Huffman, Michael Holin, Mike Iarrobino, Byrial Jensen, Rune Jorgensen, Ajay Kamdar, Igor Kerp, Everett Kaser, JJ Keijser, Jeff Kellam, Jen Kilmer, Reinhard Kirchner, Dave Kirsch, Chad Knudsen, Samuel Ko, Jan Kotas, Janne Kukonlehto, Robert Luursema, Benjamin Lee, Stephen Lee, Jim Lynch, Greg Malknecht, Sidney Markowitz, Jim Marks, Dimitri Matzarakis, Fred McCall, Ken McKee, Doug Merrett, Tom Milner, Bill Moore, Duncan Murdoch, Steve Murphy, Daniel Neri, Mert Nickerson, David Nugent, John Oldenburg, David Pape, Keith Petersen, Karl Riedling, Arthur Rubin, Gerald Ruderman, Timo Salmi, Tapio Sand, Charles Sandmann, John Schmid, Russell Schulz, Huseyin Sevay, Adam Seychell, Ajay Shah, Bob Smith, Bob Stout, Sean Sullivan, Steve Summit, Tom Swingle, Anders Thulin, Curt Tilmes, Rick Watkins, Ya-Gui Wei, Morten Welinder, Joe Wells, Scott Winder, Gregory Youngblood, Eli Zaretski, kh...@vax1.umkc.edu------------------------------Subject: - How can I search this article for a particular topic? To search for a particular topic, save this article to a text file and use your favorite editor's find function to search for a word. You can use the MS-DOS Editor to search for a topic. Run the editor and load the FAQ. Press ALT+S to activate the search menu then press F. In the box that says find what enter the word you want to look for. When you are completed, press enter. If a match is found EDIT will highlight it. If that is not what you were looking for press F3 and EDIT will show you the next match.------------------------------Subject: - Are the answers guaranteed to be correct and complete?Date: Wed, 05 Sep 94 15:34:00 CDT There has been an attempt to check all facts, but THERE IS NO WARRANTY ON THE CODE OR ON THE TECHNIQUES DESCRIBED HEREIN. Please send corrections to car...@tocnet.com. All the code has been tested; but the testing may not have been perfect, and machines and configurations vary. (Except where otherwise noted, C code was tested with MSC 5, BC++ 2.0, or BC++ 4.x.) The mention of particular books or programs must not be construed to reflect unfavorably on any that are not mentioned.------------------------------Subject: - What is comp.os.msdos.programmer about?Date: Wed, 05 Sep 94 15:34:00 CDT comp.os.msdos.programmer (comp.sys.ibm.pc.programmer until September 1990) concerns programming for MS-DOS systems. The article "USENET Readership report for Jul 94" in news.lists shows 120,000 readers of this newsgroup worldwide. Traffic (exclusive of crossposts) was 1981 articles aggregating 3.1 Megabytes. It ranked as the 79th most popular newsgroup. Much of our traffic is about language products (chiefly from Borland and Microsoft). More programming topics focus on C than on any one other language, but we are not just for C programmers (see - "Is comp.os.msdos.programmer just for C programmers?"). Since most MS-DOS systems run on hardware that is roughly compatible with the IBM PC, on Intel 8088, 80188, or 80x86 chips, we tend to get a lot of questions and answers about programming other parts of the hardware.------------------------------Subject: - Is comp.os.msdos.programmer just for C programmers? No, it is for all programmers who want to share information about programming in MS-DOS and DOS replacements like 4DOS. Programs and questions are also posted in Pascal, assembly, and other languages (including MS-DOS batch programming.) Why does the newsgroup seem to be so C-oriented sometimes? There are two reasons. First, comp.lang.c and comp.lang.pascal have evolved in different directions. comp.lang.pascal welcomes vendor- specific discussion, such as Turbo Pascal. Since so many of TP's features are tailored to programming on PCs and in MS-DOS, Turbo Pascal programmers tend to find DOS questions welcomed there, so that comp.os.msdos.programmer gets less of the "DOS in Turbo Pascal" traffic. On the other hand, comp.lang.c has stayed closer to talking only about the C language, and vendor-specific or operating- system-specific questions are not welcome. This tends to push questions about disks, DOS file structure, video, the keyboard, TSRs, etc. to comp.os.msdos.programmer even when those programs are written in C. This FAQ is definitely C-oriented, not because that's necessarily best but because I tried to stick to what I could verify personally. As a C programmer (with some assembler), I could most carefully verify solutions in C or assembler. I felt that short, clear programs could be published in just one language and programmers could translate them into their languages of choice. But the FAQ list also contains several long programs written only in C; this is a defect with no obvious remedy. Most answers that point to source code at archive sites include both C- and Pascal-language source when available. ------------------------------Subject: - What is comp.sys.ibm.pc.programmer? comp.sys.ibm.pc.programmer is the old name of comp.os.msdos.programmer, and has been obsolete since September 1990. However, many systems have not removed the old group, or have removed it but aliased it to the new name. This means that some people still think they're posting to comp.sys.ibm.pc.programmer even though they're actually posting to comp.os.msdos.programmer. You can easily verify the non-existence of comp.sys.ibm.pc.programmer by reference to the "List of Active Newsgroups" posted to news.groups. It's available at: (For more info see - "Where are FAQ lists archived?") ------------------------------Subject: - Is comp.os.msdos.programmer available as a mailing list? Sorry, no.------------------------------Subject: - What's this "netiquette"? Netiquette is good Usenet etiquette. It includes basic rules like the ones below. (See also - "How can I learn more about Usenet?") - Always read a newsgroup for a reasonable time before you post an article to it. - Pick the one right group for your article; don't crosspost unless absolutely necessary. If you absolutely must post an article to more than one group, do crosspost it and don't post the same article separately to each group. See - "What other technical newsgroups should I know about?" when considering where to post an article. - Before you post a question, make sure you're posting to the right newsgroup; the best way to do that is to observe the preceding rule. Check the group's FAQ list (if it has one) to make sure that your question isn't already answered there; see "Where are FAQ lists archived?". - When you post a question, if you ask for email responses then promise to post a summary. Keep your promise. And make it a real summary: don't just append all the email you got. Instead, write your own (brief) description of the solution: this is the best way to make sure you really understand it. - Before you post a follow-up, read the other follow-ups. Very often you'll find that someone else has already made the point you had in mind. - When someone posts a question, if you want to know the answer don't post a "me, too". Instead send email to the poster asking him or her to share responses with you. - When posting a follow-up to another posted article, remove all headers and signature lines from the old article; just keep the line "In , so-and-so writes:". Also cut the original article down as much as possible; just keep enough of it to remind readers of the context. - Keep lines in posted articles to 72-75 characters. Many newsreaders chop off column 81 or arbitrarily insert a newline there, which makes longer lines difficult or impossible to read. But you need to keep well below 80 characters per line to allow for the > characters that get inserted when other people post follow-ups to your article. - Keep your signature to 4 lines or less (including any graphics), and for heaven's sake make sure it doesn't get posted twice in your article. - Don't post email without first obtaining the permission of the sender. ------------------------------Subject: - How can I learn more about Usenet? There are two important newsgroups for learning about how Usenet and newsreader software works: - news.announce.newusers contains periodic postings that everybody is asked to read before posting anything to Usenet. (In theory, all new users are subscribed to news.announce.newusers automatically. But in practice not all newsreader software does that, so that many people violate the guidelines given there simply because they don't know about them.) - news.newusers.questions is described as "Q & A for users new to the Usenet". But new and long-time users can ask or answer questions about Usenet and newsreader software there. There's an important article, "Welcome to news.newusers.questions! (weekly posting)", that everyone is asked to read before posting to news.newusers.questions. (See below for ways to get a copy of that article.) The following postings in news.announce.newusers might be considered the "mandatory course" for new users: Introduction to news.announce.newusers What is Usenet? Answers to Frequently Asked Questions Rules for posting to Usenet A Primer on How to Work With the Usenet Community Hints on writing style for Usenet Emily Postnews Answers Your Questions on Netiquette The articles mentioned above are downloadable via ftp from rtfm.mit.edu in the following files: Welcome to news.newusers.questions! (weekly posting) Introduction to news.announce.newusers What is Usenet? Answers to Frequently Asked Questions Rules for posting to Usenet A Primer on How to Work With the Usenet Community Hints on writing style for Usenet Emily Postnews Answers Your Questions on Netiquette For rtfm.mit.edu instructions, see "Where are FAQ lists archived?" ------------------------------Subject: - What other technical newsgroups should I know about?Date: Wed, 02 Oct 94 15:34:00 CDT Caution: Some of these newsgroups have specialized charters; you'll probably get flamed (and deserve it) if you post to an inappropriate group. Most groups have FAQ lists that will tell you what's appropriate. Don't post a request for the FAQ list; instead, retrieve it yourself: see - "Where are FAQ lists archived?" - misc.forsale.computers.d and misc.forsale.computers.pc-clone are where you post notices of equipment, software, or computer books that you want to sell. Please don't post or crosspost those notices to comp.os.msdos.programmer. - comp.os.ms-windows.programmer.* groups (formerly part of comp.windows.ms.programmer): Similar to comp.os.msdos.programmer, but focus on programming for the MS-Windows platform. - comp.sys.ibm.pc.hardware is for more hardware-oriented discussions of the machines that run DOS. - the various comp.lang.* groups for articles and questions on the programming languages. Caution: some groups welcome discussions that are operating-system dependent or vendor specific; others do not. For example, comp.lang.c is definitely _not_ for questions about programming DOS or PC system features, even if the programs are written in C. - comp.binaries.ibm.pc.wanted: AFTER you have looked in the other groups, this is the place to post a request for a particular binary program. - comp.archives.msdos.announce (moderated) explains how to use the archive sites, especially Garbo and SimTel, and lists files uploaded to them. Discussions belong in comp.archives.msdos.d, which replaced comp.binaries.ibm.pc.archives in December 1992. - comp.binaries.ibm.pc.d is for discussions about programs posted in comp.binaries.ibm.pc, and only those programs. This is a good place to report bugs in the programs, but not to ask where to find them (see cbip.wanted, above). comp.binaries.ibm.pc.d is NOT supposed to be a general PC discussion group. - comp.sources.misc: a moderated group for source code for many computer systems. It tends to get lots of Unix stuff, but you may also pick up some DOS-compatible code here. - alt.sources: an unmoderated group for source code. Guidelines are posted periodically. - comp.os.msdos.djgpp is specifically for support of DJGPP. For more information on DJGPP see - What and where is DJGPP? - comp.os.msdos.programmer.turbovision is specifically for programming in Turbo Vision. - rec.games.programmer discusses many graphics programming topics. - Garbo-Ann is a moderated one-way mailing list which is used by Garbo MsDos and Windows archive managers to announce new additions to Garbo collections. This is for those who cannot subscribe to the comp.archives.msdos.announce newsgroup. To subscribe to Garbo-Ann send a message to Majo...@Garbo.uwasa.fi using the format below. To: Majo...@Garbo.uwasa.fi Subject: subscribe subscribe garbo-ann your...@somewhere.net.land - MSDOS-Ann is a moderated one-way mailing list which is used by SimTel, the Coast to Coast Software Repository (tm), to announce new additions to the msdos collection. This is for those who cannot subscribe to the comp.archives.msdos.announce newsgroup. To subscribe to Msdos-Ann send a message to list...@SimTel.Coast.NET using the format below. To: list...@SimTel.Coast.NET Subject: subscribe subscribe msdos-ann------------------------------Subject: - Where are FAQ lists archived? Very possibly the FAQ list you want is already at your site. Check the newsgroup news.answers; if your site doesn't carry news.answers, check comp.answers, rec.answers, etc., according to the top-level name in the FAQ list's "home" newsgroup. Articles are posted to the *.answers groups in a way that should make them last until the next versions are posted. If they expire sooner at your site, you might want to lobby your sysadmin to treat the moderated *.answers groups as a special case and grant them longer expiration times than other groups. To ftp most FAQ lists, connect to rtfm.mit.edu, and change to directory /pub/usenet/news.answers. The name of the file that you want is the Archive-name from the top of the article. For instance, if the Archive-name is software-eng/part1 you would retrieve /pub/usenet/news.answers/software-eng/part1. By email (only if you have no ftp access, please), the server is mail-...@rtfm.mit.edu . It accepts "send" commands that omit the leading "/pub/" from file names; for example: send usenet/news.answers/software-eng/part1 For full instructions about the mail server, send it a message consisting of these two lines: help index Not just FAQ lists, but every article listed in the "List of Periodic Informational Postings" (LoPIP) can be obtained by ftp or email from rtfm.mit.edu. If you have an old copy of an informational article, look for an "Archive-na


About

Welcome to the group! You can connect with other members, ge...
Group Page: Groups_SingleGroup