CompuServe Thread

SAS/C 5.10A Patch

3 messages in this thread
#5644From: John ToebesDec 19, 1990 11:56 PM
The ARP execute is known to be broken. We have had a number of people complain about a similar problem. In fact a significant number of our calls (as much as half) to technical support are problems from people who are using ARP. There is nothing that we can do to ensure that it will work with ARP because the EXECUTE problem is a random failure. The ARP shell also wreaks havok with priorities in the compiler. The only thing that we can do in the future to ease this situation is to check for ARP and fail the patch if it is present so that you don't suffer through half an hour or more followed by a random failure. You can call technical support to request the patch on diskette.
#5863From: Kelvin TuckerDec 25, 1990 3:08 PM
Thanks John, I reinstalled the Workbench 1.3 commands, and removed the ARP Shell, etc.. Now the SAS update appears to have worked fine. I guess I never kept up enough to know that ARP was bug-ridden. I'll miss some of the features though, especially the '*' wildcard. (It sure would be nice to have standard wildcards, etc.. for those of us who use multiple machine types, Oh well) Thanks again, – via Whap!
#5864From: Black Belt SystemsDec 25, 1990 3:33 PM
Kelvin, if yo upick up ARexx you can add the "*" wildcard back to any command you want to have it; and you'll have the most powerful single addition you can add to your Amiga. In my opinion, the only thing from the ARP project you want in your system is the arp.library, which many (misguided) programmers have used as a portion of their programs. In other words, many programs will not run without that library present in your system. Hopefully, if 2.0 is released for all the Amigas (500-3000), many of the "easy" resources in the arp.library will be available right from DOS, and we won't have to worry about which system has what libraries with it. Ben Amateur Radio Callsign is A A 7 A S