Date: Thu, 16 Apr 1998 10:01:09 +0300 (IDT) From: Eli Zaretskii To: lou smith <9813152 AT fharga DOT sun DOT ac DOT za> cc: djgpp AT delorie DOT com Subject: Re: farnspoke/peek and the ".byte 0x64" thingy In-Reply-To: <28AB7905E4C@fharga.sun.ac.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On Wed, 15 Apr 1998, lou smith wrote: > someone replied to some of my previous questions (i.e. "is it > neccesary for EVERY memory access instruction to be preceded by a > segment override ") and told me that memory access instructions dont > need to be preceded by a segment override - he told me that > farnspoke/peek ,for example, dont precede every memory access with a > "byte 0x64" You misunderstood the explanation. farnspeek does NOT eliminate the need to use the FS: overrides. It just avoids reloading the FS register with the selector that allows access to memory which is outside the limits of the selector loaded into DS. Please note that this is all explained quite clearly in the library reference (from the DOS prompt type "info libc alpha _far" and read there). The library reference is a standard place to look for explanations of anything that is related to library functions. > could someone please explain to me what segment overriding is all > about -- because quite clearly i'm extremely confused. However confused you might be, please observe some minimal net etiquette. During the last couple of days you posted several almost identical queries to this group asking about this issue. I would like to kindly request that in future you refrain from doing this. Please let some time pass before you ask about the same issue again, so that net propagation delays will let people who read this group see your questions and reply to them. It is extremely annoying to see several similar questions about the same issue posted within hours. Also, please make a good-faith effort of reading the available docs before posting. This forum is usually very tolerant to people who ask questions whose answers are easily found in the docs, but please don't test our patience too hard ;-). Since this is not a free hotline, annoying people is NOT recommended if you need efficient help.