Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!decwrl!frambo.dec.com!CB From: CB@frambo.dec.com (Christian Balzer) Newsgroups: comp.sys.amiga Subject: Re: ARP 1.3 + TxEd+ problem Message-ID: <8905310927.AA08169@decwrl.dec.com> Date: 31 May 89 09:27:26 GMT Organization: Digital Equipment Corporation Lines: 31 [I guess line-eater jokes are kinda outta date?] In article <22373@santra.UUCP>, Jukka 'Cletus' Partanen writes: Yeah, I suffer from the same bug. My solution is to use the old ARP release (it's the arp.library (or TxEd's poor handling of it) that breaks things). Or just don't use TxEd+ until the automatic upgrade to V2.02 will be send to you. When that will be I don't even dare to guess, since it had been anounced for February (hahahahahahahahohohohohihihi, wimper, sob). BTW, with the 1.3 library TxEd often crashed in my A2620 equipped system, while with ole one everything is A-OK. While ARP 1.3 is way better than the last release, there are still numerous bugs and small incompatibilities. What really makes me wonder (to put it very mild) is the fact that COMMERCIAL software from the ARP coordinator breaks with a new freebee ARP release. I had an argument with Charlie Heath about this topic at least a year ago, but obviously to no avail... Hope that sheds some light on something, - -- _ _ / / | \ \ aka Christian Balzer - The Software Brewery - < < |-< > UUCP: ...!decwrl!frambo.dec.com!cb OR cb@frambo.dec.com \ \_ |_/ / CIS : 71001,210 (be brief!) | Phone: +49 6150 4151 (CET!) ------------ Mail: Im Wingertsberg 45, D-6108 Weiterstadt, F.R.G.