Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

351 Excellent

About StickJock

  • Rank

Profile Information

  • Location
    Silicon Valley

Recent Profile Visitors

409 profile views
  1. Maybe it's just bad kerning and what it is supposed to say is, "Left Cart Ridge"? It's actually a temporary manufacturing label indicating where a ridge was to be applied to the left cart. Unfortunately, they used really cheap glue so nearly all of the left cart ridges have fallen off. If you have one that still has the ridge, you can probably get a fortune for it on eBay!
  2. Good point. You really only need one, so you should send me all of your extras. 😀
  3. But if you put a label on the top end of the cartridge, how will you know which cartridge slot to use??? 😀
  4. In the above code, you are actually copying $500 bytes instead of $400 bytes. Your last mva line will copy bytes $400..$4FF. For a character set, you only want to copy bytes $000..$3FF (1KB).
  5. Or you just wanted to really make sure those $100 bytes were copied! 😀
  6. Almost.... You still need to inc $E1 & $E3 in the outer loop. As written, it will just copy the same $100 bytes four times.
  7. I just weighed the box of them, minus the dups, on the bathroom scale. 48 pounds.
  8. "Kids these days" have virtually unlimited resources - Disk space, RAM, CPU speed, etc. My first computer was a ZX81 with only 1K or RAM. I wrote a lot of code on a 4K Wang 2200T at school as well before I got my 48K Atari 800 with only 90K per side on the floppy drive and limited cycles in the DLIs and VBIs. Now, the down side is that for interpreted code, I skipped the comments as they took up space. But still, it instilled a sense of coding conservatism, where every instruction mattered and arranging conditionals so that the more common case is the quickest to save cycles. Even when I was "forced" to use higher level languages before I retired, I would look at the generated assembly and tweak my source so that the compiler would generate better/shorter/faster code. I used to think of it as the difference between a computer programmer and a software engineer. But then again, kids these days.... (Get off of my lawn!)
  9. We called that "Eyeball Pressure". It makes the bugs & optimizations pop out! Some people thought code reviews were drudgery, but I always enjoyed them. It was a fun challenge to spot bugs & find optimizations.
  10. The only thing we have to fear, is running out of code space. - FDR
  11. I feel your pain. I spent over a decade of my career working on a micro that only had 2K of OTP ROM and 128 words of RAM. It did have a nice instruction set, though.
  12. An instruction saved is an instruction earned. - Ben Franklin
  13. FJC, in your code above, is the asl an asl A, or is it operating on one of the instructions at the label @? Typo/bug? It looks to me like you are trying to double A, and then set the bottom 3 bits, in which case you can optimize it a little by removing the AND and changing the ADC #7 to an ORA #7. This saves 2 bytes & 2 cycles. So, @ ASL A ORA #$07 TAX LDY #$07 @ LDA TimerData,X
  14. They have been in a cardboard box since at least 1990, when I moved from Texas to California. They have been stored indoors, in a closet, so they don't have any mold or anything that I can tell. I took them out of the box to take the pictures, and then put them back into the box. I am in Fremont, CA 94536.
  15. Why am I reminded of Custer's Revenge? 🤠
  • Create New...