Bob's Blog

If I were designing an assembly language, I'd insist upon using a # for immediate constant and brackets for memory references, rather that using just the # (like the 6502) or just the brackets (like the Z80).

 

If I were designing a higher-level language, I'd keep C's equality-test operator and Pascal's assignment operator.

 

Increasing the "distance" between different commands would increase the likelihood of typos getting caught.

It's still impressive how quickly you finished Reindeer Rescue.

So I wonder if I'll get the fixed version of Raindeer Rescue whenever Adventure II is finished?

Uihjah

 

Remember? That was one of the the first things I told ya!

 

Greetings,

Manuel

Amazing how we come up with these elaborate explanations as to what's happening, when all along it was just that same old "forgetting the #" thing.

 

Occam's Razor at work!

 

Though I think I was right when I said it had to do with the EPROM affecting the data bus

Uihjah  

 

Remember? That was one of the the first things I told ya!

I know; I feel like an absolute moron.

 

The problem was I was so rushed to finish it. Oh well.

 

I'm not sure if Al has made all the copies of RR yet or not; if he hasn't made the ones that are still to be sent I imagine he'll use the fixed version.

 

Which, by the way, I will now attach to the original post.

Amazing how we come up with these elaborate explanations as to what's happening, when all along it was just that same old "forgetting the #" thing.

 

Occam's Razor at work!

 

Though I think I was right when I said it had to do with the EPROM affecting the data bus

The really crazy thing is that some of those things fixed it! I never touched the problem code. That's what I don't figure. The fact that changing the code that checked P0-to-PF collisions apparently fixed the problem really, *really* threw me off track.

So I wonder if I'll get the fixed version of Raindeer Rescue whenever Adventure II is finished?

Yes, as thankfully I haven't built all of those yet. Although I did program a ton of EPROMs which I'll now have to erase and reprogram. Not completely necessary, since the bug does not exhibit itself with these particular EPROMs, but I'd rather not take a chance since the bug has been identified (and I just realized I still haven't tested it out on real hardware--will have to do that this weekend).

 

..Al