--------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E5S00013Date: 05/21/97 From: STEFAN WAGLER Time: 12:00am \/To: ALL (Read 2 times) Subj: definition of win95 ".LNK" files Hello, I'm looking for the exact definition of the Windows 95 ".LNK" files (link files). If anybody out here can give me some information about how they are constructed, it would really help me... hopefully waiting for some answers, Stefan  E-Mail: Sky-Guard@ganymede.line.org Stefan Wagler@2:2448/6060.13 --- CrossPoint v3.11 * Origin: origin.txt (2:2448/6060.13) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E5S00014Date: 05/17/97 From: SYLVAIN LAUZON Time: 06:35pm \/To: ALL (Read 2 times) Subj: old patches is there any patches for masm 5.0/5.1 available around to fix anything. If someone has an history revision could the person netmail me. --- * Origin: Silicon Palace {514}432-2953 Lafontaine, Qubec (1:242/100) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E5S00015Date: 05/21/97 From: CHRISTOPHER HANKINSON Time: 06:58am \/To: ALL (Read 2 times) Subj: Debug We somwone please post a Program that will let you edit the program in hex, memory module's, caputure the code while you are running the program. I am not saying you have to make one. Just a program you got of the Internet. For compression will you please use Rar, PKZIP, THanks Christopher Hankinson --- ProBoard v2.15 [Reg] * Origin: Gentle Breeze BBS Cliffside, N.C. (704)657-6898 (1:3667/7) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E5S00016Date: 05/20/97 From: JOE KOSS Time: 08:05am \/To: SAM IZZO (Read 2 times) Subj: Re: scrolling > JK> No, I surely meant Least Significant Byte and Most Significant > JK> Byte, as the source code I posted suggests: > JK> xchg ah, al > JK> in al, 50h ; MSB of timer 0 > JK> xchg ah, al > Ahh yep ok fair 'nuff! I guess it would be kinda hard to read in > one bit from a particular port! > > JK> and woah, that should be 60h not 50h > Heh.. Lucky I made a blunder then eh? =) Woah again, that should be 40h =) --- GEcho 1.02+ * Origin: Midnight Madness <-> Hartford, CT (1:142/8076) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E5S00017Date: 05/21/97 From: JAMES VAHN Time: 07:54pm \/To: BARRY BLOCK (Read 2 times) Subj: Re: implode (cls) From: jvahn@short.circuit.com (James Vahn) Barry Block wrote: > What else can I use as a timer so that the speed is the same on all > machines? Try OUT 4Fh, AL in a loop. My notes mention 8Dh will work too. Maybe someone here can explain better, but my understanding is that the ports under FFh all use the motherboard BUS speed of 8 to 10 MHz and this is standard on all 80X86 boards. The reason for an OUT is that the CPU will wait (I need help here) until the OUT is finished, unlike reading a port. Since a write is needed, it must be an unused port, and it appears 4Fh is a good candidate. ... The Moon is Full --- ifmail v.2.10-tx8.2 * Origin: (jvahn@short.circuit.com) (1:346/15.1) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E5S00018Date: 05/21/97 From: BARRY BLOCK Time: 01:37pm \/To: DAVID KIRSCHBAUM (Read 2 times) Subj: Bosskey.Asm - sysreq. Hello David, and/or Mervyn, DK> .CODE DK> SaveSS dw 0 DK> SaveSP dw 0 DK> SaveBP dw 0 DK> SafeInt2Eh: DK> MOV CS:[SaveSS], SS DK> MOV CS:[SaveSP], SP DK> MOV CS:[SaveBP], BP DK> INT 2Eh DK> CLI ; make sure the restoration of the registers is uninterrupted DK> MOV SP, CS:[SaveSP] DK> MOV SS, CS:[SaveSS] DK> MOV BP, CS:[SaveBP] DK> STI ; registers restored, so interrupts OK DK> RET Why is it not just as important to CLI and STI when saving the registers? Kind regards, Barry --- Terminate 4.00/Pro * Origin: EBO-BBS A'dam +31-20-6002828 (2:280/901.42) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E5S00019Date: 05/21/97 From: BARRY BLOCK Time: 02:23pm \/To: ALL (Read 2 times) Subj: diffuse.asm Hello all, I asked for a timer routine with better resolution than 1/18 sec. In the meantime I rewrote the program and renamed it to something more appropriate. Anyone want to share a screen clearing routine? ===cut=== ;Diffuse.com v1 - Barry Block 5-97 - assemble w/A86 ;slowly fills a mode3 screen with space characters, black on black (CLS) ;this version adds moving the cursor to top left corner. mode3 equ 0B800h srn_end equ 0BFD0h space_on_black equ 0720h first_pass equ 512 delay equ 1 mov ax,mode3 mov es,ax ;screen seg. mov dx,first_pass ;hold data for di increments L1: xor di,di call timer mov ax,dx shr ax,1 mov dx,ax cmp ax,1 ;di must be even ja L2 xor ax,ax ;last pass L2: add di,ax cmp di,srn_end ja L3 push ax mov ax,space_on_black stosw pop ax jmp short L2 L3: cmp ax,0 ja L1 xor bh,bh ;cursor to top left corner, page 0 xor dx,dx mov ah,2 int 10h ;set cursor int 20h ;exit program ;------------------------------- timer: ;Wait CX clock ticks push ds mov cx,delay ;X/18 second mov ax,40h ;point DS to BIOS mov ds,ax _wait: mov ax,ds:[6Ch] ;get low word of tick counter wait1: cmp ax,ds:[6Ch] ;wait for it to change je wait1 loop _wait ;count CX changes pop ds ret ===cut=== Kind regards, Barry --- Terminate 4.00/Pro * Origin: EBO-BBS A'dam +31-20-6002828 (2:280/901.42) --------------- FIDO MESSAGE AREA==> TOPIC: 145 ASSEMBLY LANG. Ref: E5S00020Date: 05/21/97 From: BRIAN MCCLOUD Time: 04:55pm \/To: BARRY BLOCK (Read 2 times) Subj: int2e BB>Hello Denis, BB>I didn't like what Debug did with your int2etst.dbg (512 bytes), BB>so I had A86 assemble it. 17 bytes. QEMM took exception. BB>Tried without QEMM and got your results. BB> * Note to A86 users * BB>Added mov ss,cs and A86 gave no error but changed the code "behind my ack" BB>to push cs pop ss which of course did not work! BB>(yes I know, mov ax,cs/mov ss,ax) The method it used is the more standard, and (in most cases) more accepted method of transferring values between segment registers... Obviously A86 had not expected the stack to be invalid at that point... Perhaps you could find way to disable "SMART" code generation (which is what tried to help you out y fixing your mov ss, cs), and then you can use your own methods to make SURE t does it the right way. ((Cloud)) MauveCloud@juno.com * OLX 2.2 * You tell 'em Chloroform, You can put them to sleep. --- 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: E5S00021Date: 05/22/97 From: DAVID KIRSCHBAUM Time: 10:12am \/To: BARRY BLOCK (Read 2 times) Subj: int2e > Hello Denis, > I didn't like what Debug did with your int2etst.dbg (512 > bytes), so I had A86 assemble it. 17 bytes. QEMM took > exception. Tried without QEMM and got your results. > * Note to A86 users * > Added mov ss,cs and A86 gave no error but changed the code > "behind my back" > to push cs pop ss which of course did not work! > (yes I know, mov ax,cs/mov ss,ax) > Here is what I sent to A86. > Mov Bx,0200h ;DOS:set memory block size > Mov Cl,04 ; BX=paragraphs > Shr Bx,Cl ; ES=block seg > Inc Bx ; BX=para avail > Mov Ah,4ah ; ret if error > Int 21h > Mov Si,0080h > Int 2eh ;DOS Internal > nop > nop > mov ss,cs ;should be via ax. A86 assembled this as > push cs/pop ss > mov sp,0fffeh > mov ah,4ch > int 21h > Kind regards, Barry Don't'cha just _love_ Stone Age attempts at AI in an assembler? I'd expect a compiler to do strange and wondrous things in attempts to optimize, do memory models, etc. etc. But not a bleedin' assembler! I wants my bytes where I puts 'em, and not what some bleedin' filthy assembler author decides is better for me .. or helps him enforce his licensing ... And people wonder why A86 requires a religious conversion :-( --- * Origin: Toad Hall (1:3634/2.4)