Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with 8086
Search options not deleted
user 25013
For questions specifically regarding the Intel 8086 16-bit microprocessor
12
votes
1
answer
414
views
What is the difference between the different versions of the SID or SID86 debugger for the x...
I did a little research about Digital Research's 8086 Symbolic Instruction Debugger. Short name SID86.EXE and SID.EXE in later versions. But I couldn't find some sort of version history? …
- 1,220
5
votes
What is the difference between the different versions of the SID or SID86 debugger for the x...
And I found this:
SID 1.0 (Concurrent DOS 3.1, Release Date 1983)
assembles and disassembles 8086 and 8087 opcodes.
supports symbolic debugging when symbol files in the syntax of Digital Research's RASM … In SID 3.2, support was still limited to 8086 and 8087 instructions when using the command A - "Assembly into memory".
Command history with cursor keys DOWN / UP. …
- 1,220
13
votes
1
answer
2k
views
Did x86 CPU vendors like Intel, NEC, AMD, and Cyrix provide their own debugger for DOS with ...
MS-DOS's debugger DEBUG.EXE did only support the assembly/disassembly of 8086 opcodes. … In the DOS days, there were CPU manufacturers like NEC that had additional opcodes in their V20/V30 CPUs which where compatible replacements for the Intel 8080 and 8086. …
- 1,220