denelsbe@pi.cs.unc.edu (Kevin Denelsbeck) (07/11/90)
Help! I'm TAing a summer course in advanced programming and the students are using Lightspeed Pascal (2.0 and up). One student, for some reason, consistently gets a "-36 I/O Error (Bummers)" (or something like that). She's using a unit and a source program in her project, along with the Profiler ( .p and .lib ), and when the error comes up there's no helpful finger to point to the exact problem. We suspect that lack of memory may be the cause of some of this (her source contains a recursive procedure) but it's just a guess. Anybody have a handle on this Bummers message? IM has not been enlightening on the subject. Please respond by email, if possible... Kev @ UNC
siegel@endor.harvard.edu (Rich Siegel) (07/11/90)
In article <15075@thorin.cs.unc.edu> denelsbe@pi.cs.unc.edu (Kevin Denelsbeck) writes: >Help! I'm TAing a summer course in advanced programming and the students >are using Lightspeed Pascal (2.0 and up). One student, for some reason, >consistently gets a "-36 I/O Error (Bummers)" (or something like that). -36 is an unspecified I/O error. The "Bummer" comment was added by Pete Maruhnic, one of the original authors of Quicksilver/Lightspeed/THINK Pascal. If you're running off floppies, one of the floppies may have gone bad; that's the typical etiology behind a -36. R. ~~~~~~~~~~~~~~~ Rich Siegel Staff Software Developer Symantec Corporation, Language Products Group Internet: siegel@endor.harvard.edu UUCP: ..harvard!endor!siegel "In this world there is nothing more thrilling than a lone man facing singlehandedly half a ton of angry pot roast." - Tom Lehrer ~~~~~~~~~~~~~~~