--------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2K00011Date: 02/15/97 From: PAUL CHAMBERLAIN Time: 10:16pm \/To: JOHN GARDENIERS (Read 3 times) Subj: 80186 -=> Quoting John Gardeniers to Paul Chamberlain <=- JG> Hi Paul, -=> 01 Feb 97 21:09, Paul Chamberlain wrote to John Gardeniers <=- JG>> The only data I have on the 80186 is "advance information", which JG>> obviously doesn't even come close to answering your question. PC> your lucky to have any data on anything less than an 80386 data book. JG> I would consider myself luckier if I had more up to date books. :-) I JG> sort of lost interest in the hardware side of things a long time ago JG> and haven't tried too hard to keep up to date. yes it is very sad that the only books still published are those which are greater than the 80386. i would just wish intel had kept publishing the 8086, 80186, 80286 programmers reference books instead of us getting sencond hand info - this sucks. like where do you find info - original info on how to use the BOUND instruction and the asosiated interupt 5 excemption. PC> i once rang intel sydney and they said they didn't have any data on PC> the 80286 but gave me a number to ring and they said that the 286 PC> was obsolete JG> I have a house full of "obsolete" equipment. That doesn't mean it's no JG> good any more though. JG> I have a simple rule regarding anything I write: JG> If it won't run on an XT it's poorly written and needs fixing. I hate JG> the way computers have become faster and software is being so badly JG> written that it runs slow on a 486. There's NO excuse for that kind of JG> stuff. Considering the prices of commercial software I think they could JG> well spend the little extra time needed to do it right. JG> ttyl, JG> >>> Fuse >>> well i might not have a house full of junk but i do have my room filled with it. :) yes ive noticed that too that - most if not all so called new applications come out that they seem to slow down you computer for what ever reason. this may or may not be true but alot of software companys dont even have a 386dx25 or even an original ibm xt, what they use more likely is a pentium pro 200 running winslows 95 to test their 100% C++ code. their might be some companys who realize that not every one can afford even a pentium yet so some may try say 5% or 10% asembly code just to get the edge on competiors. usaully the reason they may use C?? is becouse some routines are suposedly very time comsuming or dificult to convert to assembly and TIME IS MONEY!!!!. for my test suite: 286 10Mhz oc 8Mhz, 2Mb ram, 30Mb hd - (ferranti) 286 12Mhz, 1Mb ram, 0Mb hd - 16bit isa card fits into ## (wyse) 386 sx 16Mhz, 1Mb ram, 0Mb hd - no hd, no fdd (mitac ps/2 compatible) 386 sx 16Mhz, 1Mb ram, 80Mb hd - (compaq) 386 sx 16Mhz, 3Mb ram, 40Mb hd - (apricot) 386 dx 18Mhz oc 16Mhz, 2Mb, 0 hd - isa card, no hd, no fdd, no vid ## 386 dx 20Mhz, 0Mb ram, 0Mb hd - no hd, no fdd (amstad crap) 386 dx 25Mhz, 0Mb ram, 0Mb hd - motherboard 486 dx2 50Mhz, 8Mb ram, 200Mb hd 486 dx2 66Mhz, 20Mb ram, 256Mb hd 6x86 p166+ 133Mhz, 32Mb ram, 1.6Gb hd and ive only got 4 vga monitors between the ones currenly working. ;) JG> ... Cat fur expands to fill all available disk drives. JG> -!- GoldED 2.50+ JG> ! Origin: The Cubby House, assembled by hand (3:632/360.70) ... They Just Dont Write Like That Anymore. uhh.. ,uhh, uhh. .... ___ Blue Wave/QWK v2.20 [NR] --- FLAME v1.1 * Origin: 500cc: NSW's Largest BBS & $2/Hr Internet (02)9557-0077 3:712/218) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2K00012Date: 02/15/97 From: FRANK TOPPING Time: 12:56pm \/To: ALL (Read 3 times) Subj: Hello examples Recently there was a batch of "hello world in color" examples posted. I was able to retrieve and save all but the first -- I did get it to compile and it was *very* different from the rest; then I lost it. :( Does anyone remember the "hello world" in the little blue box that scrolled off to the left of the screen? ...kinda cute. ...any chance I could ask for a repost if anyone still has a copy? Thanks, -frank:) --- Maximus 2.01wb * Origin: Sacramento Peace Child! Sacramento CA (916)451-0282 (1:203/451) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2L00000Date: 02/16/97 From: BRAD POTTS Time: 06:14pm \/To: MALCOLM BURTONSHAW (Read 3 times) Subj: hello I'm Back ha ha ha ha ha ha ha ha ha ha i'm physic . --- Maximus 2.02 * Origin: The Perth Omen (3:690/660) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2L00001Date: 02/13/97 From: WOUTER DANES Time: 07:16am \/To: NICK COONS (Read 3 times) Subj: SHL. Hello Nick Coons! .o< 10 Feb 97, Nick Coons said to Wouter Danes >o. >> NC> I wasn't trying to point to a memory address, I was referring >> NC> to the actual 32-bit value in DX:AX. >> ah... that is not possible.. :) you can do it by mulling the >> value.. :) NC> And mulling is (fill in the blank) . ehehehehe... mul bx for example will multiply ax by bx and places the result in dx:ax.. bye Nick Coons! Wouter Danes, 2:2801/210 Email: hardey@xc.xs4all.nl BBS: +31-252-221334 --- fmail/pentium * Origin: x-connection - +31-252-221334 - twist whq (2:2801/210) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2L00002Date: 02/14/97 From: TED MENKS Time: 04:47pm \/To: NICK COONS (Read 3 times) Subj: SHL. Hi Nick, (ECHO_PERSONAL, Tuesday February 11 1997 21:43) Nick Coons to Ted Menks about: SHL. >> Sorry, Nick, but I think dx:ax looks like a 32-bit register-pair. >> It isn't like a simple register, but it definitely holds a 32-bit value >> as you pointed out yourself earlier in this thread... NC> Correct, but I was under the impression that you could work with NC> 32-bit values on a 16-bit machine, you just couldn't use 32-bit code. Well, AFAIK not! But I could be mistaken, of course! ;-) Bye, Ted. E-mail: ted.menks@mbs.nl Fido : 2:284/412.51 --- THaT's It BBS --- * Origin: Point 51 of Mail Board Son, Eindhoven Holland (FidoNet 2:284/412.51) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2L00003Date: 02/13/97 From: MIKKO HYVARINEN Time: 07:09pm \/To: NICK COONS (Read 3 times) Subj: SHL. NC> I thought that you could use DX:AX together as a double-word. NC> Isn't that where the product is stored of some multiplications? Yes, DX:AX is the target of some multiplication operations and the source of some division operations, but that doesn't mean it's universally usable as a 32-bit operand. If you're not sure, check out the Intel docs for a list of the operands you can use with a particular instruction. --- * Origin: By myself but not alone... (2:229/229.5) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2L00004Date: 02/13/97 From: MIKKO HYVARINEN Time: 07:14pm \/To: NICK COONS (Read 3 times) Subj: 486 MOV. >> it is an op code for the computer to do nothing. NC> So what's the point? Does it take any clock cycles? Yes, it takes one clock cycle. It's a very useful instruction for hackers and debugger software. You can remove an instruction from a compiled program by replacing it with NOPs. --- * Origin: Roaming the land while you sleep... (2:229/229.5) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2L00005Date: 02/15/97 From: MIKKO HYVARINEN Time: 10:45am \/To: MARTIN VAN DER ZWAN (Read 3 times) Subj: 486 MOV. NC>> What's a NOP? KB>> No OPeration, Just what it says =) it is an op code for the KB>> computer to do nothing. MZ> Do several NOP's also cause a delay? Yes, but the length of the delay is not the same on every machine (it depends on the processor, clock speed, cache and main memory speed, execution state and some other things as well). TPAW: Don't trust NOP for delays. --- * Origin: Out from the new days mist I have come... (2:229/229.5) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2L00006Date: 02/13/97 From: DENIS BOYLES Time: 06:49am \/To: NICK COONS (Read 3 times) Subj: 32 bit code within 16 Hi Nick! NC> > db 66h NC> > shl ax,9 NC> > db 66h NC> > mov [lTemp], ax NC> > db 66h NC> > shr ax,2 NC> > db 66h NC> > add ax, [lTemp] NC> I see what you're getting at, but doing SHL AX, 9 would very likely NC>push bits off that would normally be pushed onto the upper 16-bits, right? It shouldn't if you have the DB 66h over-ride because you would be shifting EAX not AX. Since EAX is a 32 bit register the bits should shift over from AX into the high of EAX. If you didn't have the over-ride, then you're correct, you'd loose those bits. ie: EAX = 0101 0101 SHL 4 EAX = 1010 1010 AX = 0101 SHL 4 AX = 1010 If DB 66h was used then: EAX = 1010 1010 otherwise only AX is shifted, so instead: EAX = 0101 1010 Cheers, Denis Boyles --- Maximus/2 3.01 * Origin: Frog Hollow Port Moody BC 604-469-0264/0284 (1:153/290) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2L00007Date: 02/15/97 From: DENIS BOYLES Time: 11:32pm \/To: MARTIN VAN DER ZWAN (Read 3 times) Subj: Assembler NOP Hi Martin, MVDZ> NC> What's a NOP? MVDZ> KB> No OPeration, Just what it says =) it is an op code for the MVDZ>Do several NOP's also cause a delay? I tend to recall something where one might use several NOPs to wait x amount of time. Say you needed to wait for x amount of time for some hardware to gointo some state. You might use several NOPs as your `delay' rather then coding a timer/delay routine. With today's speedy computers however, I doesn't work out quite the same. :) Cheers, Denis Boyles --- Maximus/2 3.01 * Origin: Frog Hollow Port Moody BC 604-469-0264/0284 (1:153/290)