The Shop > Electronics & IC Programing
Adventures in old 80s computers.
DavidA:
Dave,
And don't you just love the way that erroneous assembler programs can rampage through your system like Atilla the Hun on one of his bad days.
There is NO room for error.
Dave
Assembler86 on PC 386 and Z80 Assembler on the TRS-80.
awemawson:
Once you manage to get a protected mode kernel running as supervisor, you can then run your assembler under it's supervision at a lower interrupt priority, saving your copy of the register set on exit. All that Pushing and Popping on the stack ! Then when you think it's all stable the dreaded 'stack overflow' error rears it's ugly head :ddb:
S. Heslop:
That's more or less what I mean by "it's probably hell to write a program of any serious length", it seems the difficulty would be keeping track of stuff as it gets bigger.
vtsteam:
Z-80 had the signifigant bites in the opposite order, too. I used to actually recognize op codes.
It was easier to just write most code in FORTH for me and include assembly subroutines (well "words" in FORTH) in it. FORTH had a built in assembler, so definitions for a word could be either FORTH words or assembly language. It didn't care.
AdeV:
I spent ages (literally) typing in an Assembler program written in Sinclair SuperBASIC. The listing was printed over 4 or 5 months in QL World magazine.
Being young and naive at the time, I hadn't realised that Assembler was not the same as Compiler.... I thought it would take my BASIC programs and turn them into super-fast machine code.... oops.
IIRC The program was nicknamed QSLUG in recognition of its slowness...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version