comp.lang.asm.x86

• Date Index

---

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

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

coding.derkeiler.com  > Archive  > Assembler  > comp.lang.asm.x86  > 2005-08