--------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00000Date: 12/27/97 From: GLEN MCNABB Time: 10:09pm \/To: SCOTT MCNAY (Read 1 times) Subj: How to's (again ;) SM> *** Glen McNabb wrote in a message to Peter Magnusson: SM> SM> PM> CI> Does the video memory start at $A000 on all gfx. cards?? SM> PM> SM> PM> $A000:0000 or (flat) $000A0000, yes. SM> SM> GM> Except CGA (cruddy graphics adaptor) B800:0000 amounts SM> GM> vary... SM> SM> GM> Propriatary graphics on AT's class and up vary on a rare SM> GM> basis... SM> SM> There's also the 8514, which is apparently accessed via commands, and SM> apparently doesn't need memory space. SM> SM> I don't know what PGA uses, but I think it's B800. It's so rare, though, SM> even at the time that it was sold, that I doubt that anyone would SM> complain if you decided to ignore it. If your writing for the market it makes little sense to write for anything other than VGA (velcro graphics). You almost can't do anything without one. I reluctantly switched from EGA since most of the apps I run are in text modes. I only get testy when writers are trying to sell programs the require 6 bizillion hertz pentium with 64 mega gigs of memory and enough hard drive for greyhound. Most people can't afford an upgrade every 10 days or so. :) It's great that computers of today are so fast and have so much storage. It saddens me that it also lends to some very sloppy programming in the terms of size and speed. Whatever happened to tight fast code? Glen... --- ProBoard v2.16 [Reg] * Origin: NC/NEC SEWAnet, Bucolic Fair (1:3407/25) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00001Date: 12/28/97 From: HUGH NOLAND Time: 09:51am \/To: FRANS FLIPPO (Read 1 times) Subj: Simple Dos/Bios calls HN> mov ah,9 HN> mov al,'A' HN> mov bh,0 ;text page number, usually 0 HN> mov bl,0eh ;bg and fg color attributes HN> mov cx,1 ;print character just once FF> just curious: is any checking done here..? if i try to put 70 characters FF> starting from the lower right corner of my screen (24,79 or so), what FF> happens? Interesting question. To which I don't know the answer. I've done a little experimenting, but without any convincing results. The following is an excerpt from Dave Williams' Technical Reference Manual and leads me to speculate that what happens probably depends on your BIOS: --------------------------------------------------------------------------- Function 09h Write Character and Attribute at current cursor position entry AH 09h AL ASCII code of character to display BH display page number - text mode BL attribute (text modes) or color (graphics modes) CX number of characters to write return none note 1) CX should not exceed actual rows available, or results may be erratic. 2) Setting CX to zero will cause runaway. --- Maximus/2 3.01 * Origin: Madman BBS * Chico, California * 530-893-8079 * (1:119/88) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00002Date: 12/28/97 From: DARRYL GREGORASH Time: 02:34pm \/To: PETER MAGNUSSON (Read 1 times) Subj: pure Hex Programming Replying to a message of Peter Magnusson to Scott McNay: SM>> The most blatant bug must be the POP CS bug in the 808x; SM>> Intel was (probably) forced to leave it in for SM>> compatibility, so it wasn't changed until the 8018x. PM> What kind of bug was it? Think for a moment what will happen if you execute POP CS.. the IP remains unchanged... --- FleetStreet 1.21 NR * Origin: BIG BANG Burger Bar: Regina SK Canada (1:140/86) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00003Date: 12/28/97 From: DARRYL GREGORASH Time: 02:36pm \/To: SCOTT MCNAY (Read 1 times) Subj: pure Hex Programming Replying to a message of Scott McNay to Peter Magnusson: SM> You might take a look at the AAM and AAD instruction. As SM> you probably know, it's officially a two-byte opcode, but SM> it's actually a one-byte opcode followed by a single data SM> byte, 0x0A. If, for example, you use 0x08 instead, you get SM> an instruction that converts binary to/from octal. SM> Apparently, on the NEC chips (I dont have a PC or XT SM> motherboard to test with anymore, and I doubt that I still SM> have any NEC chips either, so I can't confirm this), SM> supposedly the AAM and AAD instructions don't work SM> correctly for any operand other than 0x0A. Thus, a good SM> reason to not rely upon such ondocumented behavior. I had a V20; they work fine for any byte following the opcode, because they ignore that byte.. decimal values only. --- FleetStreet 1.21 NR * Origin: BIG BANG Burger Bar: Regina SK Canada (1:140/86) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00004Date: 12/28/97 From: GLEN MCNABB Time: 11:26am \/To: JEREMY STROUD (Read 1 times) Subj: what the hell is this area? On <27 Dec, 17:33>, Jeremy Stroud wrote to All : JS> is this like an area were ppl can have porn talks and sex chats?... since JS> it has the triple xxx in the name? Hi Jeremy, not that I'm the moderator or nothing but, this echo is dedicated to the discussion of assembly language programming on the Intel "style" series of microprocessors. Such processors include the 8088, 8086, 80186, 80188, 80286, 80386sx-dx-dx2-dx4, etc etc... To cover the processor types the echo was named 80XXX as 80??? is not an allowed name for all mail tossers... As such, discussions on the "XXX" level will likely meet an unfriendly response or ignored all together. Unless you can see a way to have "XXX" with a microprocessor. In which case you'll have to ask the moderator about that one... Glen... --- ProBoard v2.16 [Reg] * Origin: NC/NEC SEWAnet, Bucolic Fair (1:3407/25) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00005Date: 12/28/97 From: DARRYL GREGORASH Time: 05:12pm \/To: GLEN MCNABB (Read 1 times) Subj: How to's (again ;) Replying to a message of Glen McNabb to Scott McNay: GM> It's great that computers of today are so fast and have so GM> much storage. It saddens me that it also lends to some very GM> sloppy programming in the terms of size and speed. Whatever GM> happened to tight fast code? Disappeared into the great black hole known as C++ --- FleetStreet 1.21 NR * Origin: BIG BANG Burger Bar: Regina SK Canada (1:140/86) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00006Date: 12/28/97 From: GLEN MCNABB Time: 02:01pm \/To: MARTIJN VAN DE STREEK (Read 1 times) Subj: pure Hex Programming On <27 Dec, 06:50>, Martijn van de Streek wrote to Scott McNay : MvdS> MvdS>> The processor reported to exist, but which I've never seen MvdS> MvdS>> is a 80186. It must have been succeeded by the 286 too soon. MvdS> SM> I've never seen one either, probably because it was designed for MvdS> SM> embedded systems. MvdS> Aah. MvdS> Strange. MvdS> A whole series for PC use, and one of them is different. (More than one) Not really. Originally, the 8080 was never intended for PC usage. As a matter of fact PC usage itself was not intended. The 8085 was designed as a faster replacement for the 8080 that also reduced the number of support chips to operate it. The 8086 was to be the 16bit replacement. It featured things that a 8085 didn't have along with a "more" structured nemonics that went with it. The 8088 was essentially designed to be backward compadable with 8 bit support IC's. Up to this point, idea of PC's was still beyond the reach of the consumer as a product. Imbedded controllers became a second market after the introduction of personal computers. Hardware wise, PC processors needed to be free of the need with support IC's along with the ability to use them. Controllers were marketed under the idea that they had these support IC's built in and thus removed costing from imbedded designs. Intel was wise to make an embedded controller that used the same code as the PC processors. An engineer could code on his PC with languages that were available to him without extra cost. Intel was more sure of imbedded sales. Lastly, they didn't have to re-invent a new processor but make additions on an existant one. They kept this trait through the 8048 and MCS-48 series, the MCS-5? series, and on up. Intel wasn't the only ones who did this. Motorola, Zilog, RCA, and many others were/are doing the same. I thought that the 68705 was a neat imbedded controller. It was designed for the hobbiest. Then, with the introduction of Basic-Stamp, it was even easier for the hobbiest to use imbedded controllers. Almost all of these were essentially code compadable with previous fare processors... Glen.. --- ProBoard v2.16 [Reg] * Origin: NC/NEC SEWAnet, Bucolic Fair (1:3407/25) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00007Date: 12/28/97 From: GLEN MCNABB Time: 02:03pm \/To: PETER MAGNUSSON (Read 1 times) Subj: pure Hex Programming On <27 Dec, 15:11>, Peter Magnusson wrote to Scott McNay : PM> SM> The most blatant bug must be the POP CS bug in the 808x; PM> SM> Intel was (probably) forced to leave it in for PM> SM> compatibility, so it wasn't changed until the 8018x. PM> PM> What kind of bug was it? PM> PM> [peter] Not a bug. :) A feature... This is the fastest form of Segment JMP you'll find... :) Glen... --- ProBoard v2.16 [Reg] * Origin: NC/NEC SEWAnet, Bucolic Fair (1:3407/25) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EGY00008Date: 12/28/97 From: JAMES AVERY Time: 08:25pm \/To: CHRISTIAN IVERSEN (Read 1 times) Subj: How to's (again ;) Hullo Christian! Friday December 26 1997 satte Brian McCloud p sit keyboard, og flgende blev afsendt til Christian Iversen: CI>> Does the video memory start at $A000 on all gfx. cards?? BM> In all video modes better than CGA, the graphics in real mode can be BM> accessed at segment A000h. Color text modes and CGA graphics are accessed BM> at segment B800h. Monochrome text and Hercules graphics can be accessed at BM> segment B000h. These segments are for Real mode. A small correction : the (EGA?)/VGA standard requires that video memory is read from 0xa000:0 / 0x000a00000. SVGA modes have no such standard placement. --- GEcho 1.00 * Origin: Have YOU beaten Your goldfish today? (FidoNet 2:235/215.10)