pwp@iuvax.UUCP (02/27/86)
Which RAM disk are you using? With the public domain RAM disk I am using, things don't work after a few compiles. Removing all files from the disk before each recompile seems to keep it going longer but that is not convienent if you also put libraries on it. (I tried to mail this, but my machine does not know how to reach you.) Paul Purdom (purdom@indiana on CSnet).
bammi@cwruecmp.UUCP (Jwahar R. Bammi) (03/02/86)
> > Which RAM disk are you using? With the public domain RAM disk I am > using, things don't work after a few compiles. Removing all files > from the disk before each recompile seems to keep it going longer > but that is not convienent if you also put libraries on it. > (I tried to mail this, but my machine does not know how to reach you.) > > Paul Purdom (purdom@indiana on CSnet). *** REPLACE THIS LINE WITH YOUR MESSAGE *** The problem is not with the Ramdisk but with the version of tos you are using. The later versions anf the rom tos fix the problem. One caution about using floppies or ram disk to compile and link is that you should have plenty of free space for temp. files. The linker in particular does not tell you when it runs out of temp file space. You realize that this happened when you end up with a ridiculusly large/small .prg file after running relmod on the .68k file. Will someone from Atari on this net hold the programmers who wrote link68 and ar68 upside down for a little while for me :-). Seriously, when are you going to upgrade these two very weak links in the dev system? My biggest objections are the speed due to the brain damaged ar format (at least provide a ranlib), link not understanding pathnames, and link not informing the user of some errors. In fact i see no reason to have a relmod at all, link should generate the correct output (Gemdos is not cp/m68k remember!). -- Jwahar R. Bammi Usenet: .....!decvax!cwruecmp!bammi CSnet: bammi@case Arpa: bammi%case@csnet-relay CompuServe: 71515,155