Path: utzoo!mnetor!uunet!husc6!linus!raybed2!lah From: lah@raybed2.UUCP (LANCE HOLMES) Newsgroups: comp.sys.amiga Subject: Some minuses to Txed Plus Message-ID: <1167@raybed2.UUCP> Date: 26 Apr 88 14:24:50 GMT Organization: Raytheon Co., Bedford, Mass. Lines: 71 Keywords: Txed Arp I have just purchased and tried out txed plus and have the following comments/questions/problems. After installing txed and experimenting I have found the following things to be a major difference and some thing you may want to consider before buying it. The default Memory available is now reduced from 35000 in txed v1.31 to 20000 in txed 2.0. This means that if you have a file larger than 20000 Characters such as a file that you captured from the net and have to clean up so that you can uudecode or un shar it you can't load it into Txed. I have searched through the manual to see if there is any way to set this value but there doesn't seem to be one. I haven't contacted C Heath yet to see if this is true. If some one knows what the story is with respect to this memory limit I'd appreciate it. I realize that this version uses arexx and through some fancy elegant macro you may be able to get around it with some sort of paging sceme. The second minus in Txed Plus is that it uses Arp.library. This means that the file must be available to Txed in the Libs: directory if you try to perform some of the operations used in Txed such as cut and paste. If you liked Txed v1.31 because it was small and could be copied to ram: and run from there with out having workbench available then now your going to have to copy Arp.library and any other libraries to ram: and re-assign the Libs: directory to it. The Loading of txed from boot up routine which uses a demo version of Arexx has some problem. You can load Txed,blitzdisk,ff,funkeys,and Arp.library with out any problem. You also have the option to copy the latest Arp programs to your disk. This copies a copy of Arc to you disk and a copy of Arpexe.arc. You then have to know or guess that you need to De-Arc the Arpexe.arc file,execute the execme file,and then this routine has a small catch-22 which may confuse the easily confused. After copying the Txed program a copy of Arp.library is copied into you Libs: directory. The execme program copyies AEXEC.arc to you C directory and dearcs it. Contained in the programs is a copy of Arp.library which at the end of the execme file is an attempt to rename it to libs/arp.library. Well the catch-22 is that if you have already installed Txed there already is a copy of Arp.library in you libs directory. So the rename program will fail. If there isn't a copy of the file Arp.library in your libs directory and you have booted up your system with this disk the system tries to execute the rename program from that disk you will then see a message that says "you need a copy of Arp.library V33+" which is the file that your trying to copy. This leave you in the situation where you'll have to reboot with a different workbench and give full path names to command like "c:rename" so that the Arp command isn't run. As I said this arrangement will confuse the easily confused. The way in which it will work is if you don't copy Txed first copy Arp.library. Exit out of the installation routine that is running in Txed. Don't reboot but cd to the disk that Arpexe.arc has been copied to. De-arc the file and execute execme. Then after that it you should reboot and try to install Txed. As you can see from my rambiling it is rather confusing and you had to be there to understand. Last but not least If you have not read my previous posting with respect to Arp Resident command then I'll say it again the programs that are made resident do not seem to work. I feel like the system is not recognizing that the program resident in memory should be executed instead it looks on the disk and runs that program. Which leaves me using the Rez program instead. Lance Holmes any answers comments or suggestions are welcome however there seems to be 30 day money back satisfaction Warranty listed in the manual which I presently feel that I may have to use.