Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!decwrl!labrea!polya!lipa From: lipa@polya.Stanford.EDU (William J. Lipa) Newsgroups: comp.sys.mac.programmer Subject: Re: Problems with Think Pascal 2.0 Message-ID: <5488@polya.Stanford.EDU> Date: 5 Dec 88 20:42:41 GMT References:<762@husc6.harvard.edu> Reply-To: lipa@polya.Stanford.EDU (William J. Lipa) Organization: Stanford University Lines: 42 In article <762@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes: >In article lipa@POLYA.STANFORD.EDU (William Lipa) writes: >>1. Can't print to a LaserWriter SC in any font other than Monaco 12. > This, as I understand, is not a Lightspeed Pascal problem. You shoud >double-check the installation of your LaserWriter SC drivers and fonts. >(This is coming to me second-hand; sorry I can't be more specific.) I have checked; they appear to be installed correctly. All my other programs can print to the SC successfully. >>2. Occasionally when you Build Code Resource or Build Application, the linker >> will produce an error message "Duplicate File Name", even though you've >> specifically OK'd the overwrite of the previous version in the dialog. > > This has never happened to me, and I overwrite old programs all th >time, and I've not heard any other reports of it. You might try various >disk and directory diagnostics (Disk First Aid, HD SC Setup's disk test) to >check out the hard disk. I tried this; no problems were found. And this error has happened to me on two completely separate machines. >>7. I had a very strange problem with a simple sorting program I wrote. Any >> attempt to access or change the variables of the program caused a Bus >> Error. The problem did not go away even when I created a whole new project >> to replace the old one. The program didn't access the Toolbox at all. >> However, now the program works fine. Very strange. > > There's no relationship between having bus errors and using the >Toolbox. I haven't the faintest idea what happened to your program... The relationship is: if I get a bus error without using the Toolbox, then it is much more likely that the problem is in the compiler, because I can't have messed up the Toolbox/System by some mistake of my own. I realize that it's possible that my Mac II or its hard disk is somehow responsible for these errors. However, this seems unlikely because I've gotten them on different machines (one another Mac II, and one a Plus). Other applications aren't giving me unusual problems. Bill Lipa Bitnet: lipa%polya@stanford