--------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EBV00010Date: 07/25/97 From: MERVYN BALDWIN Time: 12:06pm \/To: BARRY BLOCK (Read 1 times) Subj: Re: fade >Hello Mervyn, sorry this took so long. The BBS I am a point off has been >down for two+ weeks! I think he went on holiday and left no co-sysop >in charge. Also no local message of explanation. Barry, That's OK. Things like that happen even in the best regulated families. > All of this may be because I use AnsiPlus. One of Denis's progs > did not work for me until I booted without Ansiplus. Just use plain old NWDOS's ANSI.SYS here. I do remember a couple of progs that didn't go quite as expected unless I "removed" it. > The fade works, it fades slowly, but the delays did not make it > fade any slower, so I removed them. Now that IS strange. Here, you see, if I take out the delays I get an instant black screen. No fade at all! All this video stuff is getting very odd. Have been struggling recently with a little prog to make a "window" for data input. It works fine on a friends machine but will NOT work on mine. My version is much shorter, and probably faster, than his and works fine here but doesn't go on his. Both progs use only standard BIOS calls and both systems are quite standard 486/VGA outfits. So none of it makes sense. And now James Vahn tells me mine doesn't work on his machine either. Here it is: try it for me please. ;start--------------------------------------------------------- mov dh,5 ;start row -1 mov dl,5 ;start column xor bh,bh ;video page 0 mov ax,01303 ;func 13h mode 3 mov cx,70 ;string length lea bp,s1 ;top string call doit lea bp,s2 ;middle string L1: call doit cmp dh,9 ;end row jl L1 lea bp,s3 ;bottom string call doit exit: mov ax,04c00 int 021 ;-------------------------------------------------------------- doit: inc dh int 010 ret ;-------------------------------------------------------------- s1 db 0da,04c,68 dup(0c4,04c),0bf,040 s2 db 0b3,04c,68 dup(020,044),0b3,040 s3 db 0c0,04c,68 dup(0c4,040),0d9,040 ;-----------------------------------------------------------end That's code for A86 of course. If you use MASM I guess you'll know what to do. I would add the COM file but I think binaries are forbidden here. -- vyn@abaldwin.demon.co.uk (Mervyn Baldwin) --- ifmail-tx (i386 Linux) * Origin: 300 miles East of Seattle, WA (1:346/15.1) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EBV00011Date: 07/25/97 From: JANIS KRACHT Time: 10:47pm \/To: ALL (Read 1 times) Subj: FileGate Upload area available at filega22:47:4107/25/97 Hello Folks! I've set up a domain on the internet for filegate.org and I've got a section set up for authors to drop off files for distribution via the IFDC FileGate, the Filebone and all of our links (see http://www.filegate.org or the FileGate.ZXX file for the list ) If you would like to upload files rather than send them via e-mail for the FileGate/FileBone PDN File Distribution, just let me know - I'll send you the user name and password so that you can upload the files via either ftp or telnet. Include a file description and I'll be happy to send the file on it's way ;-) Take care, Janis E-Mail: jkracht@thepoint.net http://www.thepoint.net/~jkracht http://www.filegate.org/ --- * Origin: IFDC FileGate HUB (1:2320/38) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EBV00012Date: 07/25/97 From: BRIAN MCCLOUD Time: 07:44am \/To: GILES JACOBSEN (Read 1 times) Subj: bits GJ>What is the best way to deal with bits? This is the way I have delt with them GJ>so far (just started learning asm 3 days ago): GJ>and al,00100000b GJ>cmp al,00100000b GJ>Is that the best way to test bits? No. A better way is to use the operand TEST, which ANDs the bits, but stores only the flags from doing so, and not the results. Anyway, after an AND or a TEST, the CMP is unnecessary. The Zero flag will be the opposite of the bit being tested, and if you used TEST, you don't lose the original value of the register. ((Cloud)) MauveCloud@juno.com * OLX 2.2 * Detour: The roughest distance between two points. --- PCBoard (R) v15.3/M 10 * Origin: Next time, Dial The Wrong Number! (209) 943-1880 (1:208/205) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EBV00013Date: 07/23/97 From: JOHN GARDENIERS Time: 06:43pm \/To: PETER LOUWEN (Read 1 times) Subj: sex Hi Peter, -=> 15 Jul 97 17:12, Peter Louwen wrote to Kurt Wismer <=- KW>> but this is an assembly language echo whose main focus is the KW>> 80xxx line of intel microcomputers.. PL> Which, as we all know, IS sex. With knobs on. Boy! You really should get out more, maybe even meet people. ;-) ttyl, >>> Fuse >>> ... 3 stages of sex: Tri-weekly, Try-weekly, Try-weakly. --- GoldED/386 3.00.Alpha4+ * Origin: The Cubby House, assembled by hand (3:632/360.70) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EBV00014Date: 07/25/97 From: JOHN GARDENIERS Time: 03:09pm \/To: DAVID KIRSCHBAUM (Read 1 times) Subj: 80x86 versus Z80 Hi David, -=> 08 Jul 97 15:02, David Kirschbaum wrote to Bert van Dam <=- >> Is it possible to take a 80x86 assembler code and translate it to Z80 >> assmbler code (automatically ofcourse, manually I'm sure it can be DK> But as I recall (it's been a long time) those cross assemblers were a DK> real PITA to use, required special host systems, etc. But you might DK> want to look at this. There's a quite a few Z80 cross assemblers available for the PC. I think I have, or have had, at least a dozen. Unfortunately, as I read the message, Bert isn't after a cross assembler. What he appears to be after is more along the lines of an interpreter, one which reads 80x86 source code and outputs Z80 source code. BTW, a good way to locate Z80 cross assemblers is to grab the various CP/M emulators. Most of ones I've seen include either an 8080 or Z80 assembler, sometimes both. ttyl, >>> Fuse >>> ... Serial Interface - a spoon --- GoldED/386 3.00.Alpha4+ * Origin: The Cubby House, assembled by hand (3:632/360.70) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: EBW00000Date: 07/26/97 From: MATHIEU BOUCHARD Time: 12:52am \/To: DAVID KIRSCHBAUM (Read 1 times) Subj: Constant speed > At this moment, I like to find a way to keep the speed of the > program the same for all types of computers, independently of > how much system resources are taken away by other programs. > Someone an idea? DK> loops against a system clock to get a relative system DK> speed .. but I'm concerned with Windows and other DK> processes possibly kicking in right when we're trying DK> to do the speed test and throwing our results off. a better idea might be to hook the timer interrupt (irq0), and if necessary, reprogram to 60 Hz for example... depends what you need, but staying at 18.2 Hz is being more compatible... so every frame the interrupt signals the next frame. without hooking the interrupt, and while staying at 18.2 Hz, a good idea could be to just read the timer and calculate the tick number. after one chunk is done read until it changes, then reloop... basically j0: stuff goes here j1: read timer into ax does ax change? if not, jmp j1 jmp j0 matju --- Maximus 3.01 * Origin: BitByters BBS, Rockland ON, Can. (613)446-7773 v34, (1:163/215)