comp.lang.asm.x86

• Thread Index

• Re: Vanderpool and Pacifica satisfy Popek and Goldberg virtualization requirements?
  • From: Grumble
• Re: Writing spaghetti code for obfuscation/encryption
  • From: Jim Leonard
• Re: Polling input from the mouse
  • From: Dirk Wolfgang Glomp
• Re: Writing spaghetti code for obfuscation/encryption
  • From: Jim Leonard
• Re: Simple program cwitching thru all video-modes craps-out ...
  • From: Dirk Wolfgang Glomp
• Having trouble posting?
  • From: Clax86
• Re: Writing spaghetti code for obfuscation/encryption
  • From: randyhyde@xxxxxxxxxxxxx
• Re: Writing spaghetti code for obfuscation/encryption
  • From: David J. Craig
• Re: Writing spaghetti code for obfuscation/encryption
  • From: f0dder
• Re: Writing spaghetti code for obfuscation/encryption
  • From: f0dder
• Re: Writing spaghetti code for obfuscation/encryption
  • From: Jim Leonard
• Re: Writing spaghetti code for obfuscation/encryption
  • From: randyhyde@xxxxxxxxxxxxx
• Re: Simple program cwitching thru all video-modes craps-out ...
  • From: Jim Leonard
• Re: Writing spaghetti code for obfuscation/encryption
  • From: f0dder
• Re: Writing spaghetti code for obfuscation/encryption
  • From: jonathon
• Re: Writing spaghetti code for obfuscation/encryption
  • From: Kevin G. Rhoads
• Re: Simple program cwitching thru all video-modes craps-out ...
  • From: R.Wieser
• Writing spaghetti code for obfuscation/encryption
  • From: spamtrap
• Re: Loading a bitmap image
  • From: Galbu
• Re: Using linux's brk for dynamic memory allocation
  • From: Claudio Daffra
• Re: Polling input from the mouse
  • From: Dirk Wolfgang Glomp
• Vanderpool and Pacifica satisfy Popek and Goldberg virtualization requirements?
  • From: spamtrap
• Re: Loading a bitmap image
  • From: Dirk Wolfgang Glomp
• Re: Simple program cwitching thru all video-modes craps-out ...
  • From: Dirk Wolfgang Glomp
• www.devicetools.com - rembedded software resources
  • From: spamtrap
• Re: Polling input from the mouse
  • From: Bjarke Walling Petersen
• Re: Using linux's brk for dynamic memory allocation
  • From: Alex Buell
• Re: Polling input from the mouse
  • From: Bjarke Walling Petersen
• Re: Loading a bitmap image
  • From: Galbu
• Simple program cwitching thru all video-modes craps-out ...
  • From: R.Wieser
• Re: Using linux's brk for dynamic memory allocation
  • From: Jonathan Bartlett
• Re: Polling input from the mouse
  • From: Dirk Wolfgang Glomp
• Re: [Clax86list] Re: parity check
  • From: David J. Craig
• Get the FAQs
  • From: Clax86
• Re: parity check
  • From: Terje Mathisen
• Re: parity check
  • From: f0dder
• Re: [Clax86list] Re: parity check
  • From: Charles A. Crayne
• Re: parity check
  • From: Jack Klein
• Re: parity check
  • From: David J. Craig
• Re: parity check
  • From: Donkey
• Re: parity check
  • From: spamtrap
• Re: bochs vs real world
  • From: Alex
• parity check
  • From: Herbert Haas
• bochs vs real world
  • From: johny_cage
• Re: Loading a bitmap image
  • From: Dirk Wolfgang Glomp
• bochs vs real world
  • From: johny_cage
• Polling input from the mouse
  • From: Bjarke Walling Petersen
• Re: HLA macro question?
  • From: SevagK
• Loading a bitmap image
  • From: Galbu
• Re: assembler too hard?
  • From: JGCASEY
• Re: HLA macro question?
  • From: randyhyde@xxxxxxxxxxxxx
• Re: String cat algo
  • From: Dave Thompson
• Re: Using linux's brk for dynamic memory allocation
  • From: randyhyde@xxxxxxxxxxxxx
• Re: HLA macro question?
  • From: randyhyde@xxxxxxxxxxxxx
• Re: assembler too hard?
  • From: Matt C.
• Re: HLA macro question?
  • From: spamtrap
• Re: assembler too hard?
  • From: JGCASEY
• Re: HLA macro question?
  • From: spamtrap
• Re: assembler too hard?
  • From: Matt C.
• Re: [Clax86list] Using linux's brk for dynamic memory allocation
  • From: Charles A. Crayne
• Re: HLA macro question?
  • From: Alex Buell
• Using linux's brk for dynamic memory allocation
  • From: Alex Buell
• Re: HLA macro question?
  • From: randyhyde@xxxxxxxxxxxxx
• Re: HLA macro question?
  • From: spamtrap
• Re: Replacing SSE2 instructions with another instruction set in a executable
  • From: Maarten Kronenburg
• Re: HLA macro question?
  • From: randyhyde@xxxxxxxxxxxxx
• Re: Problem with program (Pirko's RPSORT)
  • From: Robert Redelmeier
• Re: Replacing SSE2 instructions with another instruction set in a executable
  • From: Daydreamer
• Re: HLA macro question?
  • From: spamtrap
• Re: Problem with program (Pirko's RPSORT)
  • From: SevagK
• Re: HLA macro question?
  • From: randyhyde@xxxxxxxxxxxxx
• HLA macro question?
  • From: spamtrap
• Re: Problem with program (Pirko's RPSORT)
  • From: Terje Mathisen
• Re: pipeline optimization
  • From: Himanshu
• Problem with program (Pirko's RPSORT)
  • From: prino
• Re: pipeline optimization
  • From: wolfgang kern
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: dude84
• Re: pipeline optimization
  • From: Dirk Wolfgang Glomp
• Re: pipeline optimization
  • From: f0dder
• Re: Relevance of .org in Linux Assembly
  • From: Frank Kotler
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: spamtrap
• Re: pipeline optimization
  • From: wolfgang kern
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: dude84
• Re: pipeline optimization
  • From: hutch--
• Re: Relevance of .org in Linux Assembly
  • From: Alex Buell
• Re: pipeline optimization
  • From: Donkey
• Having trouble posting?
  • From: Clax86
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: robertwessel2@xxxxxxxxx
• pipeline optimization
  • From: Himanshu
• Re: Relevance of .org in Linux Assembly
  • From: Bill Marcum
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: f0dder
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: dude84
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: dude84
• Re: Relevance of .org in Linux Assembly
  • From: Frank Kotler
• Re: dual+ processor systems
  • From: Matt Taylor
• Re: Implement memcmp function with help from gcc's inline asm
  • From: Netocrat
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: Spiro Trikaliotis
• Re: Reset vector Location for 128K EEPROM
  • From: ramakrishhna
• Relevance of .org in Linux Assembly
  • From: ramakrishhna
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: f0dder
• Re: Cache identification on INTEL-CPUs
  • From: Andreas Grögel
• Re: Implement memcmp function with help from gcc's inline asm
  • From: hutch--
• Re: Reset vector Location for 128K EEPROM
  • From: wolfgang kern
• Cache identification on INTEL-CPUs
  • From: André Kempe
• Reset vector Location for 128K EEPROM
  • From: rama_desd@xxxxxxxxx
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: dude84
• Re: Implement memcmp function with help from gcc's inline asm
  • From: Netocrat
• Re: Implement memcmp function with help from gcc's inline asm
  • From: hutch--
• Re: Implement memcmp function with help from gcc's inline asm
  • From: Netocrat
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: Donkey
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: hutch--
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: dude84
• Re: Windows XP SP2 assembler for launching cmd.exe
  • From: spamtrap
• Get the FAQs
  • From: Clax86
• Windows XP SP2 assembler for launching cmd.exe
  • From: dude84
• Re: assembler too hard?
  • From: JGCASEY
• FASM Assembler project
  • From: JGCASEY
• Re: accessing hardware from pmode
  • From: Frank Kotler
• Re: String cat algo
  • From: Guga
• Re: assembler too hard?
  • From: Matt C.
• Re: accessing hardware from pmode
  • From: johny_cage
• Re: accessing hardware from pmode
  • From: johny_cage
• Re: accessing hardware from pmode
  • From: Frank Kotler
• Re: accessing hardware from pmode
  • From: johny_cage
• Re: accessing hardware from pmode
  • From: randyhyde@xxxxxxxxxxxxx
• Re: [nasm] accessing hardware from pmode
  • From: Frank Kotler
• [nasm] accessing hardware from pmode
  • From: johny_cage
• Re: String cat algo
  • From: hutch--
• Re: String cat algo
  • From: hutch--
• Re: String cat algo
  • From: Terje Mathisen
• Re: how to get the segments address and print it in hex
  • From: Dirk Wolfgang Glomp
• Re: String cat algo
  • From: f0dder
• Re: String cat algo
  • From: hutch--
• Re: String cat algo
  • From: f0dder
• Re: String cat algo
  • From: hutch--
• Re: how to get the segments address and print it in hex
  • From: Alex Buell
• Re: String cat algo
  • From: f0dder
• Re: String cat algo
  • From: Alex Buell
• how to get the segments address and print it in hex
  • From: spamtrap
• BIOS option ROMs <-> BIOS legacy interrupts
  • From: sijoange
• Re: String cat algo
  • From: hutch--
• Re: [Clax86list] Re: assembler too hard?
  • From: f0dder
• Re: [Clax86list] Re: assembler too hard?
  • From: Robert Redelmeier
• Re: [Clax86list] Re: assembler too hard?
  • From: Charles A. Crayne
• Re: [Clax86list] Re: String cat algo
  • From: Charles A. Crayne
• Re: [Clax86list] Re: String cat algo
  • From: Charles A. Crayne
• Re: copying in the same segment
  • From: johny_cage
• Re: [Clax86list] Re: 64 bit instructions
  • From: bwaichu@xxxxxxxxx
• Re: [Clax86list] Re: String cat algo
  • From: randyhyde@xxxxxxxxxxxxx
• Re: String cat algo
  • From: hutch--
• Re: String cat algo
  • From: hutch--
• Re: String cat algo
  • From: Matt
• Re: [Clax86list] Re: assembler too hard?
  • From: Robert Redelmeier
• Re: the LOCK prefix
  • From: wolfgang kern
• Having trouble posting?
  • From: Clax86
• Re: String cat algo
  • From: Terje Mathisen
• Re: String cat algo
  • From: Terje Mathisen
• Re: [Clax86list] Re: String cat algo
  • From: f0dder
• Re: [Clax86list] Re: String cat algo
  • From: Charles A. Crayne
• Re: [Clax86list] Re: assembler too hard?
  • From: Charles A. Crayne
• Re: [Clax86list] the LOCK prefix
  • From: Charles A. Crayne
• Re: [Clax86list] the LOCK prefix
  • From: Charles A. Crayne
• Re: runtime BIOS: 128kb
  • From: Bill Leary
• Re: assembler too hard?
  • From: hutch--
• Re: [Clax86list] Re: 64 bit instructions
  • From: f0dder
• Re: Recommended Dos Assemblers
  • From: f0dder
• Re: Replacing SSE2 instructions with another instruction set in a executable
  • From: f0dder
• the LOCK prefix
  • From: Scott J. McCaughrin
• Re: copying in the same segment
  • From: Frank Kotler
• Re: String cat algo
  • From: hutch--
• Re: 64 bit instructions
  • From: Alex Buell
• Re: copying in the same segment
  • From: johny_cage
• Re: 64 bit instructions
  • From: BRG
• Re: assembler too hard?
  • From: randyhyde@xxxxxxxxxxxxx
• Re: assembler too hard?
  • From: spamtrap
• Re: String cat algo
  • From: hutch--
• Re: String cat algo
  • From: Virtanen Antti
• Re: runtime BIOS: 128kb
  • From: sijoange
• Re: EBP going crazy
  • From: André Kempe
• Re: assembler too hard?
  • From: Betov
• Re: EBP going crazy
  • From: ¬a\\/b
• Re: assembler too hard?
  • From: Charles A. Crayne
• Re: String cat algo
  • From: hutch--
• assembler too hard?
  • From: spamtrap
• Re: runtime BIOS: 128kb
  • From: Bill Leary
• Re: HLA & device drivers
  • From: spamtrap
• Re: EBP going crazy
  • From: randyhyde@xxxxxxxxxxxxx
• Re: EBP going crazy
  • From: Bill Marcum
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: Grumble
• runtime BIOS: 128kb
  • From: sijoange
• EBP going crazy
  • From: André Kempe
• Re: String cat algo
  • From: randyhyde@xxxxxxxxxxxxx
• Re: String cat algo
  • From: Virtanen Antti
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: Robert Redelmeier
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: bwaichu@xxxxxxxxx
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: bwaichu@xxxxxxxxx
• Get the FAQs
  • From: Clax86
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: Tim Roberts
• Re: HLA & device drivers
  • From: randyhyde@xxxxxxxxxxxxx
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: Robert Redelmeier
• Re: HLA & device drivers
  • From: Tim Roberts
• Re: HLA & device drivers
  • From: Tim Roberts
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: Charles A. Crayne
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: bwaichu@xxxxxxxxx
• Re: [nasm] copying in the same segment
  • From: Frank Kotler
• Re: [nasm] copying in the same segment
  • From: Alex
• Re: GCC-ASSEMBLY VARIADIC functions
  • From: Grumble
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: Charles A. Crayne
• Re: Why do I need a stack frame to use %xmm registers?
  • From: Grumble
• Re: Why do I need a stack frame to use %xmm registers?
  • From: Grumble
• [nasm] copying in the same segment
  • From: johny_cage
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: bwaichu@xxxxxxxxx
• String cat algo
  • From: hutch--
• Re: [Clax86list] Re: Why do I need a stack frame to use %xmm registers?
  • From: Charles A. Crayne
• Re: Why do I need a stack frame to use %xmm registers?
  • From: bwaichu@xxxxxxxxx
• Re: Why do I need a stack frame to use %xmm registers?
  • From: hutch--
• Re: HLA & device drivers
  • From: spamtrap
• Why do I need a stack frame to use %xmm registers?
  • From: bwaichu@xxxxxxxxx
• Re: 64 bit instructions
  • From: Alex Buell
• Re: 64 bit instructions
  • From: randyhyde@xxxxxxxxxxxxx
• Re: [Clax86list] Re: 64 bit instructions
  • From: bwaichu@xxxxxxxxx
• Re: [Clax86list] Re: 64 bit instructions
  • From: Charles A. Crayne
• Re: 64 bit instructions
  • From: bwaichu@xxxxxxxxx
• Re: HLA & device drivers
  • From: T.M. Sommers
• 64 bit instructions
  • From: Alex Buell
• Re: HLA & device drivers
  • From: randyhyde@xxxxxxxxxxxxx
• Re: HLA & device drivers
  • From: Frank Kotler
• Re: HLA & device drivers
  • From: Tim Roberts
• Re: Replacing SSE2 instructions with another instruction set in a executable
  • From: hutch--
• Re: general opcode question
  • From: robertwessel2@xxxxxxxxx
• Re: Replacing SSE2 instructions with another instruction set in a executable
  • From: randyhyde@xxxxxxxxxxxxx
• Re: [nasm][video memory]
  • From: Alex Buell
• HLA & device drivers
  • From: spamtrap
• Replacing SSE2 instructions with another instruction set in a executable
  • From: Trent
• Re: [nasm][video memory]
  • From: Nicholas Sherlock
• general opcode question
  • From: Christian Christmann
• Re: [bochs][nasm][video memory]
  • From: Frank Kotler
• Re: [nasm][video memory]
  • From: wolfgang kern
• Re: newbie question : linux video memory in text mode
  • From: Claudio Daffra
• Re: [nasm][video memory]
  • From: Alex Buell
• Re: [nasm][video memory]
  • From: wolfgang kern
• Re: [nasm][video memory]
  • From: wolfgang kern
• Re: A stupid question about "STACK SEGMENT"
  • From: Maarten Kronenburg
• Re: link my asmlib as shared libbrary with gcc
  • From: T.M. Sommers
• Re: TASM versions
  • From: hutch--
• A stupid question about "STACK SEGMENT"
  • From: dongmonkey1
• Re: newbie question : linux video memory in text mode
  • From: Tim Roberts
• Re: newbie question : linux video memory in text mode
  • From: Claudio Daffra
• Re: Recommended Dos Assemblers
  • From: presentt
• Re: [bochs][nasm][video memory]
  • From: Frank Kotler
• TASM versions
  • From: MrArkus
• Re: [nasm][video memory]
  • From: Alex Buell
• Re: [nasm][video memory]
  • From: wolfgang kern
• Re: Recommended Dos Assemblers
  • From: wolfgang kern
• Re: Recommended Dos Assemblers
  • From: randyhyde@xxxxxxxxxxxxx
• Re: Recommended Dos Assemblers
  • From: Maarten Kronenburg
• Re: [nasm][video memory]
  • From: johny_cage
• Re: Recommended Dos Assemblers
  • From: alex
• Re: Fast xmm register load with copy of 32bit variable
  • From: Michael Moy
• Re: [nasm][video memory]
  • From: Alex
• Re: protected mode bios: option ROMs
  • From: sijoange
• Re: Best way to address array of words?
  • From: spamtrap
• Recommended Dos Assemblers
  • From: ozeasm
• Having trouble posting?
  • From: Clax86
• Re: protected mode bios: option ROMs
  • From: spamtrap
• Re: [bochs][nasm][video memory]
  • From: alex
• Re: [bochs][nasm][video memory]
  • From: Frank Kotler
• Re: [nasm][video memory]
  • From: Frank Kotler
• Re: Best way to address array of words?
  • From: Jerry Coffin
• Re: [bochs][nasm][video memory]
  • From: alex@xxxxxxxxxx
• Re: [nasm][video memory]
  • From: Alex Buell
• Re: [bochs][nasm][video memory]
  • From: Frank Kotler
• Re: [nasm][video memory]
  • From: Frank Kotler
• Re: Fast xmm register load with copy of 32bit variable
  • From: Ludwig Hähne
• Re: Best way to address array of words?
  • From: wolfgang kern
• Re: [bochs][nasm][video memory]
  • From: Alex
• BIOS option ROMs:
  • From: Josef Anruss
• Fast xmm register load with copy of 32bit variable
  • From: spamtrap
• Re: [bochs][nasm][video memory]
  • From: Alex
• protected mode bios: option ROMs
  • From: sijoange
• Re: [nasm][video memory]
  • From: johny_cage
• bios option ROMs: on what else do you depend of the system bios
  • From: Josef Anruss
• Re: [nasm][video memory]
  • From: johny_cage
• Re: [bochs][nasm][video memory]
  • From: Frank Kotler
• Re: Best way to address array of words?
  • From: Jim Leonard
• Re: [bochs][nasm][video memory]
  • From: Frank Kotler
• [bochs][nasm][video memory]
  • From: johny_cage
• newbie question : linux video memory in text mode
  • From: Claudio Daffra
• Re: Best way to address array of words?
  • From: wolfgang kern
• Re: Help data conversion
  • From: Claudio Daffra
• Best way to address array of words?
  • From: Jim Leonard
• Get the FAQs
  • From: Clax86
• Re: Question for console.gotoxy funtion in Art of Assembly language
  • From: SevagK
• Question for console.gotoxy funtion in Art of Assembly language book!!
  • From: Jongmin
• Re: link my asmlib as shared libbrary with gcc
  • From: Claudio Daffra
• Re: nasm, int 10h, speed
  • From: johny_cage
• Re: link my asmlib as shared libbrary with gcc
  • From: asm.20.better@xxxxxxxxxxxxxxx
• Re: link my asmlib as shared libbrary with gcc
  • From: Claudio Daffra
• Re: link my asmlib as shared libbrary with gcc
  • From: Claudio Daffra
• Re: link my asmlib as shared libbrary with gcc
  • From: bwaichu@xxxxxxxxx
• Re: Help data conversion
  • From: Frank Kotler
• Re: nasm, int 10h, speed
  • From: wolfgang kern
• Help data conversion
  • From: REM
• Re: What operations are done when a function is called
  • From: Claudio Daffra
• Re: Hmm...
  • From: Alex Buell
• Re: link my asmlib as shared libbrary with gcc
  • From: Claudio Daffra
• Re: nasm, int 10h, speed
  • From: spamtrap
• Re: nasm, int 10h, speed
  • From: Frank Kotler
• Re: coprocessor error
  • From: Bill Marcum
• Re: nasm, int 10h, speed
  • From: Frank Kotler
• Re: Hmm...
  • From: Frank Kotler
• Re: Hmm...
  • From: Frank Kotler
• Re: nasm, int 10h, speed
  • From: Frank Kotler
• Re: Hmm...
  • From: Frank Kotler
• Re: nasm, int 10h, speed
  • From: Frank Kotler
• Re: link my asmlib as shared libbrary with gcc
  • From: Claudio Daffra
• Re: link my asmlib as shared libbrary with gcc
  • From: Maarten Kronenburg
• coprocessor error
  • From: spamtrap
• Re: Hmm...
  • From: Steve
• Re: Hmm...
  • From: hutch--
• Re: Hmm...
  • From: wolfgang kern
• Re: rep performance
  • From: Tim Roberts
• Re: How declare a function as nested function
  • From: dongmonkey1
• Re: Printing the art of assembly book (f.a.o. randall hyde)
  • From: ab
• Re: Hmm...
  • From: randyhyde@xxxxxxxxxxxxx
• Re: Printing the art of assembly book (f.a.o. randall hyde)
  • From: novice
• link my asmlib as shared libbrary with gcc
  • From: Claudio Daffra
• Re: What operations are done when a function is called
  • From: randyhyde@xxxxxxxxxxxxx
• Hmm...
  • From: Alex Buell
• Re: Printing the art of assembly book (f.a.o. randall hyde)
  • From: randyhyde@xxxxxxxxxxxxx
• Re: What operations are done when a function is called
  • From: IIJIMA Hiromitsu
• Printing the art of assembly book (f.a.o. randall hyde)
  • From: novice
• Re: How declare a function as nested function
  • From: randyhyde@xxxxxxxxxxxxx
• Source code - SHOWVECT.ASM
  • From: Alex Buell
• Re: nasm, int 10h, speed
  • From: spamtrap
• Re: What operations are done when a function is called
  • From: Claudio Daffra
• Re: HLA Exception (5): Conversion error???
  • From: spamtrap
• How declare a function as nested function
  • From: dongmonkey1
• Re: nasm, int 10h, speed
  • From: Jim Leonard
• Re: What operations are done when a function is called
  • From: randyhyde@xxxxxxxxxxxxx
• Re: rep performance
  • From: randyhyde@xxxxxxxxxxxxx
• Re: rep performance
  • From: hutch--
• Re: HLA Exception (5): Conversion error???
  • From: randyhyde@xxxxxxxxxxxxx
• Re: x86 TSR programming information
  • From: Alex Buell
• nasm, int 10h, speed
  • From: spamtrap
• Re: What operations are done when a function is called
  • From: spamtrap
• Re: x86 TSR programming information
  • From: Alex Buell
• Re: x86 TSR programming information
  • From: spamtrap
• rep performance
  • From: Gary
• What operations are done when a function is called
  • From: Abhi
• Re: x86 TSR programming information
  • From: Alex Buell
• Re: x86 TSR programming information
  • From: Abhi
• xmm with pseudo ops ((g)as) - BSD/linux
  • From: bwaichu@xxxxxxxxx
• Re: HLA Exception (5): Conversion error???
  • From: spamtrap
• Having trouble posting?
  • From: Clax86
• Re: x86 TSR programming information
  • From: Tim Roberts
• Re: HLA Exception (5): Conversion error???
  • From: randyhyde@xxxxxxxxxxxxx
• HLA Exception (5): Conversion error???
  • From: spamtrap
• Re: HLA doc [AoA for Linux] error?
  • From: randyhyde@xxxxxxxxxxxxx
• Re: new bie
  • From: Betov
• Re: Slow string search/fast binary search
  • From: Jim Leonard
• Re: indirect addressing on PIV's vs static addressing
  • From: Maarten Kronenburg
• Re: nop's in gcc-generated code
  • From: Cribble
• Re: new bie
  • From: Jason Gurtz
• Re: new bie
  • From: randyhyde@xxxxxxxxxxxxx
• Cann't boot from a BEV card.
  • From: spamtrap
• new bie
  • From: New Bie
• HLA doc [AoA for Linux] error?
  • From: spamtrap
• indirect addressing on PIV's vs static addressing
  • From: Robert Spykerman
• Re: nop's in gcc-generated code
  • From: Ethan Eade
• Re: nop's in gcc-generated code
  • From: randyhyde@xxxxxxxxxxxxx
• Re: newbie seeks info.
  • From: randyhyde@xxxxxxxxxxxxx
• direct acces to video memory under DPMI
  • From: Zedd
• Re: Win98 VDM not V86?
  • From: wolfgang kern
• x86 TSR programming information
  • From: Alex Buell
• Re: newbie seeks info.
  • From: Jhon Smith
• Re: newbie seeks info.
  • From: spamtrap
• nop's in gcc-generated code
  • From: Sorav Bansal
• Re: newbie seeks info.
  • From: Matt
• Re: Slow string search/fast binary search
  • From: Matt
• newbie seeks info.
  • From: Jhon Smith
• Re: Win98 VDM not V86?
  • From: nutso fasst
• Re: indirect addressing on PIV's vs static addressing
  • From: Maarten Kronenburg
• Re: Slow string search/fast binary search
  • From: hutch--
• Get the FAQs
  • From: Clax86
• Re: Implement memcmp function with help from gcc's inline asm
  • From: Dave Thompson
• Re: Slow string search/fast binary search
  • From: Tim Roberts
• indirect addressing on PIV's vs static addressing
  • From: Robert Spykerman
• Re: indirect addressing on PIV's vs static addressing
  • From: randyhyde@xxxxxxxxxxxxx
• Re: Slow string search/fast binary search
  • From: randyhyde@xxxxxxxxxxxxx
• Re: Win98 VDM not V86?
  • From: wolfgang kern
• Re: need list of x86 opcodes
  • From: wolfgang kern
• Re: need list of x86 opcodes
  • From: Bush is a Fascist
• Re: need list of x86 opcodes
  • From: Bush is a Fascist
• Re: Win98 VDM not V86?
  • From: nutso fasst
• Re: Slow string search/fast binary search
  • From: Matt
• Re: Win98 VDM not V86?
  • From: wolfgang kern
• Re: Slow string search/fast binary search
  • From: Jim Leonard
• Re: Win98 VDM not V86?
  • From: nutso fasst
• Re: Slow string search/fast binary search
  • From: hutch--
• Re: Win98 VDM not V86?
  • From: wolfgang kern
• Re: need list of x86 opcodes
  • From: Betov
• Win98 VDM not V86?
  • From: nutso fasst
• Re: Slow string search/fast binary search
  • From: wolfgang kern
• Re: need list of x86 opcodes
  • From: Donkey
• Re: Problem with a little program
  • From: Tim Roberts
• Re: Slow string search/fast binary search
  • From: Ole Nielsby
• Re: need list of x86 opcodes
  • From: robertwessel2@xxxxxxxxx
• Re: Slow string search/fast binary search
  • From: randyhyde@xxxxxxxxxxxxx
• Re: Slow string search/fast binary search
  • From: wolfgang kern
• Re: need list of x86 opcodes
  • From: Maarten Kronenburg
• Re: need list of x86 opcodes
  • From: Betov
• Re: NASM error message
  • From: spamtrap
• Slow string search/fast binary search
  • From: Ole Nielsby
• Re: Optimising lookup table
  • From: Terje Mathisen
• Re: Hexadecimal words
  • From: Alex Buell
• Re: Hexadecimal words
  • From: Alex Buell
• Re: Hexadecimal words
  • From: Keyser Soze

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint