Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site decwrl.UUCP Path: utzoo!watmath!clyde!floyd!harpo!decvax!decwrl!daemon From: daemon@decwrl.UUCP Newsgroups: net.micro.cbm Subject: Re: Problems with MLX Message-ID: <5990@decwrl.UUCP> Date: Fri, 2-Mar-84 09:20:11 EST Article-I.D.: decwrl.5990 Posted: Fri Mar 2 09:20:11 1984 Date-Received: Sat, 3-Mar-84 23:43:34 EST Sender: daemon@decwrl.UUCP Organization: DEC Western Research Lab, Los Altos, CA Lines: 17 From: pogo::lawrence I had a similar problem when I was debugging MLX. It turned out that I was trying to input a program starting at address 32768, saved it and when I read it back, the data was completely different. It drove me nuts until I realized that I had the HES MON64 cartridge plugged in and this also starts at 32768. Since the 64 can share RAM and ROM at the same address, write to the RAM, but only read the ROM, there's the answer. MLX was properly writing the program and also saving it. But when I went back to read it, what I got was what was in the ROM. Once I unplug- ged the Cartridge, MLX worked like a champ. I do have a working version of MLZ, so if you want to send me a cassette, my address is below. P.S., that's MLX, not MLZ. Jim Lawrence 3130 Rhapsody Court Colorado Springs, Colo 80918