CompuServe Thread

#M2Sprint problem

4 messages in this thread
#22098From: Harry CallesisMar 9, 1991 8:04 PM
David – Well, guess what? I can't get the example to run correctly. Depending on how I link it (originally with RTR, but then I tried RT) it opens the custom screen, titles it "Testing TestSetFont", and then crashes ("Software error – Task Held). Do you think there's a problem with my setup? I've recompiled all the .sym and .lnk files in M2: so I'm current (as far as I know) with what I have on the release and upgrade disks. I'm really stumped. I'm tempted to give up on Modula-2 and translate this sucker from Pascal to C instead, since C works … 8^). Hopefully AG will have something to say soon. Thanks for trying … Harry
#22101From: David CzayaMar 9, 1991 8:37 PM
It sounds like you have a problem somewhere. Why did you recompile all the M2 files? Something strange must have crept in. I have tried this over and over and it works perfectly here. Maybe you should ask AG for a new disk of .lnk files. That may clear up a lot of problems for you. As I said, I wouldn't place too much blame on M2Sprint. It works darn near perfectly. If you have corrupted files, that isn't M2Sprint's or AG's fault. You want to go to C? Aarggh! David Czaya
#22131From: Harry CallesisMar 10, 1991 5:13 PM
David – I have some really wierd stuff going on. I completely re-installed M2Sprint version 1.00 so I'd have a known starting point, and your code works fine in that environment. But, when I do the update (disks say 1.10, programs say either 1.10 or 1.11) and rebuild the libraries, that's when the code starts crashing (yours, I mean – mine shows the same behavior under either 1.00 or 1.10). I don't know why; I use the compile batches supplied (I have to change the ARP directory and add the EasyConsole stuff), and do the RunTime stuff manually to make the RT#?.lnk files, but something must happen to make the code start crashing. It's really frustrating. I'll send my test code to you so you can see how it behaves in your setup – it won't matter what disk font you put in, or even if you use a ROM font, all that needs doing is making the NewScreen font pointer non-NIL. I'll let you know if I have any major breakthroughs (or breakdowns 8^) ). Thanks … Harry
#22149From: David CzayaMar 10, 1991 11:42 PM
Yeah, sounds like you have a corrupted source file somewhere. I'd recom asking AG for a new set of files. I recall some problems related to the upgrade, but they were mainly just revision-trap problems (this had to be compiled before that, etc.). David Czaya