--------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2N00022Date: 02/16/97 From: TED MENKS Time: 01:57pm \/To: NICK COONS (Read 3 times) Subj: 486 MOV. Hi Nick, (ECHO_PERSONAL, Friday February 14 1997 19:27) Nick Coons to Ted Menks about: 486 MOV. [About NOP:] NC>>> So what's the point? Does it take any clock cycles? TM>> Right! THaT's the point... and it does! :) TM>> And therefor it's good for making the machine stop and wait for a TM>> while, however short that while may be. NC> But that's a horrible way to make a pause... Horrible??? Go wash your mouth. You should know better than to judge so hard! You *know* how it was in the early 'puting years! ;-))) NC> it's VERY dependant on the speed of the processor. Yeah, sure. But when it's only a single NOP (remember: we're talking nanoseconds here, if a 100MHz internal clock is assumed), then it's the shortest pause you will ever be able to generate. And it's very simple to implement... Just remember `nothing' and write it down, when you need it... ;-) Or would you be able to suggest a shorter pause, or one that is easier to generate? And since when should EVERY pause be stretched to human standards? Suppose, your PerCy is communicating with some external device, which is a bit slow. PerCy sends a byte of data and wants to be sure that the byte is settled in the device's memory, before it proceeds. Should PerCy REALLY wait three minutes for you to realize that it is pausing? Or should it perform a NOP and rapidly continue, so that you don't have to wait all week for this program to finish? And THaT's why NOP is a very practical instruction! ;-) Happy programming, 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: E2N00023Date: 02/16/97 From: TED MENKS Time: 03:30pm \/To: NICK COONS (Read 3 times) Subj: SHL. Hi Nick, (ECHO_PERSONAL, Thursday February 13 1997 16:24) Nick Coons to Ted Menks about: SHL. >> Ah, I see where you're heading... If DX equals 0 before the needed >> shifting operation, then consider multiplying AX by 512. This should >> do wonders to your program... NC> But multiplying is very slow. Is it? Not on MY PerCy! The MUL instruction takes care of all that, and on a 486DX/4-100 it is done quicker than typing NOP! (at least with my troubled eyesight it is ;-))) NC> I've finally figured out how to use the extended registers with my NC> 16-bit assembler (I was having more problems than just a simple db NC> 66h could fix). I think you should search for a more modern assembler. You're `db 66h'-ing like a crippled XT ;-))) Also a more recent instruction-list might do some good... ;-) But I take it, that your proggy is now working? Congrats, then! 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: E2N00024Date: 02/18/97 From: STEVEN READ Time: 10:33am \/To: PETER LOUWEN (Read 3 times) Subj: Re: boot failure Peter, PL> =========================================================================== PL> Packet: PC-OHIO PL> Date: 02-12-97 (08:43) Number: 10903 PL> From: PETER LOUWEN Refer#: NONE PL> To: STEVEN READ Recvd: NO PL> Subj: RE: BOOT FAILURE Conf: (708) 80XXX-F PL> --------------------------------------------------------------------------- PL> -=> Quoting Steven Read to Peter Louwen <=- PL> SR> Maybe it's called a FEATURE not a BUG. PL> That's the oldest excuse in the book. PL> SR> Why aren't you asking these questions in a MS-DOS programmers PL> SR> conference/newsgroup? They could better answer these types of PL> SR> questions. PL> I am labouring under the delusion that this IS a MDPC/N. Sorry, unknown terminology went over my head. PL> I've received no moderated messages telling me to take this PL> question elsewhere, so I think I'm correct in posting this PL> question into this area. Sorry if it seemed like I was telling you what to do. One of the conference rules is to try to help people. It appears you don't want it or my recommendations. I'll make sure that I don't help you in the future. PL> Peter PL> ... Be kind to your web-footed friends; that duck may be a buyer. ... Be kind to your fellow programmer; that person may have the answer. PL> --- GEcho 1.11+ PL> * Origin: Nouveau BBS: ++31-36-5302153/5302156 (X75) (2:283/502) BTW, What_were_you_doing_in_another_conference? ... so, What's good for the goose, is good for the gander. The following is a message in the Pascal conference where you recommended the person get the answer in another conference. SR> ----------------------------------------------------- SR> Conference: (PASCAL-F) SR> Message: 27006 SR> From: PETER LOUWEN SR> To: DANNY KEOGH SR> Subject: RE: UUENCODE/DECODE SR> Date: 02-0897 20:28 SR> ----------------------------------------------------- SR> -=> Quoting Danny Keogh to All <=- SR> SR> 1. Ask the same question in the 80XXX echo (that's the ASM one). SR> SR> Peter SR> SR> ... Zeg Egberts, wil je niet zo lopen te Douwe...! SR> --- GEcho 1.11+ SR> * Origin: (2:283/502) So maybe it's tit-for-tat. If not and you want to continue with the subject, then reply to my e-mail address below. Later, Steve --- * QMPro 1.53 * steven.read@pcohio.com --- InterEcho 1.19 * Origin: PC-Ohio PCBoard * Cleveland, OH * 216-381-3320 (1:157/200) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2N00025Date: 02/18/97 From: STEVEN READ Time: 10:52pm \/To: BRUCE ROESER (Read 3 times) Subj: Cwd BR> ============================================================ BR> Packet: PC-OHIO BR> Date: 02-13-97 (12:03) Number: 10924 BR> From: BRUCE ROESER Refer#: NONE BR> To: NIMA HODA Recvd: NO BR> Subj: CWD Conf: (708) 80XXX-F BR> ------------------------------------------------------------ BR> -=> Quoting Nima Hoda to All <=- BR> EN> ... REAL programmers code in Assembler. BR> NH> REAL programmers code in machine language BR> REAL programmers hand-assemble it in hexadecimal. Bruce, .80xxx mode on Could you post some examples of 'hand-assemble' assembly code? Also could you post an asm program for reverse engineering the 'hand-assembled' hex code. Much thanks. :^) .80xxx mode off Later, Steve, in western New York state (USA) --- * QMPro 1.53 * steven.read@pcohio.com --- InterEcho 1.19 * Origin: PC-Ohio PCBoard * Cleveland, OH * 216-381-3320 (1:157/200) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2N00026Date: 02/18/97 From: JOE KOSS Time: 09:21pm \/To: MIKKO HYVARINEN (Read 3 times) Subj: Re: SHL. > One implementation could be: > > mov al, 10110010b > ral al, 2 > 10110010 -> 11001001 > xabcdefg -> xcdefgab > > i.e. only the 7 LSB are rotated. I see, but what does this type of shifting have to do with arithmetic shifting on an x86? X86's don't use one's compliment. > Another way: > > ral al, 2: xabcdefg -> xcdefgxa (b lost) > rar al, 2: xabcdefg -> xgxabcde (f lost) > > OTOH, I can't imagine a situation where one would actually *need* > these instructions. They are not consistent with the meaning of "arithmetic shifting" or "rolling" in 2's compliment machines. --- GEcho 1.02+ * Origin: Midnight Madness <-> Hartford, CT (1:142/8076) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E2N00027Date: 02/17/97 From: NICK COONS Time: 11:04pm \/To: JOHN GARDENIERS (Read 3 times) Subj: 80186 Hi John! > NC> I think they have taken that "little extra time", but they've > NC> spent it making the program go slower, not faster. > They have taken that "little extra time" to work out how to make Little > Willy even richer. You and I got no consideration whatsoever. That's very true. So why does he bother? He probably couldn't spend the money that he has at this moment in one lifetime. > ... Does banging on a cast iron pan make Heavy Metal music? I think it does... Nick Coons nick.coons@juno.com Dynamic Computer Systems --- FMail/386 1.02 * Origin: Dynamic Computer Systems (1:114/404)