David, I'll send you the test program to run so you can confirm if your REX# has a hardware issue. ..Steve
On Tue, Nov 10, 2020 at 8:01 AM David Kinzler <[email protected]> wrote: > I'd like to first acknowledge that I'm a new Model 100 user, and I suspect > user error is a large component of my woes. > > Basically, after installing my new REX#, I've been experiencing data loss > and erratic behavior. I've played with it entirely too long, and I reliably > experience severe corruption that even affects images that are not loaded. > I've been in talks with Steven Adolph, and we've verified that the ROM is > probably seated okay. > > I've seen all manner of things happen. Weirdest was the machine locked up > and left the modem/cassette relay clicking. I've had BASIC lose the ability > to use function keys. Programs have needed me to quit with the reset button > on the back - F8 wouldn't work. I've repeatedly had my images get mixed up, > e.g, if I have images named "work" and "play," the contents of play might > suddenly appear in the "work" image and vice versa. In such a case, > many/most programs will no longer run. BASIC programs will often just > indicate "OK" when launched after such a fault. Text files seem unaffected > corruption-wise -- a file that shows up loads into TEXT. I've also had > spontaneous cold boots on launching an app that have not only cleared the > active RAM but have also caused inactive images to appear empty when > loaded. The image reassignment and corruption seems correlated with these > cold boots. I also had the experience of using F6 in Rex Manager to copy a > tokenized basic program to another bank. The program was around 12KB in > size, but in the opposite pane the size showed up as around 4KB. The system > became unusably erratic directly after I tried to launch the copied 4KB > version. > > The unit was working to my expectation before installing the REX#. I think > part of these issues is that I would only have a program or two loaded at a > time because of RAM, and now I'm running into machine language conflicts > between REX# and/or multiple programs with assembly routines. Is there any > way to know whether a program needs REX# uninstalled before launching? How > can I know which programs can co-exist without causing a cold-boot? > > I tried copying over just one program per image, and avoided launching any > programs. I lost the contents of more than one image just switching from > one of these banks to another. The banks pointed to data initially saved in > another bank, and when I tried, I couldn't get a program to run on the > machine. > > The last part suggests this isn't simply user error and a case of "It's a > Model T! Don't do that!" >
