ajcole@ai.leeds.ac.UK (Andrew J Cole) (08/31/88)
1186 running Koto 2.02 A SYSOUT failed to complete with a "HARD DISK ERROR" (happens fairly frequently with no obvious pattern & the disgnostics are happy with the drive) and on this occasion seems to have corrupted the LispFiles "directory". SCAVENGEDSKDIRECTORY falls over with the same error. SystemTools gives an immediate 0915 when LispFiles is selected from the Volume Menu & Scavenge from the Installation Utility eventually gives an 0935. Now the question - do other people have similar difficulties creating (& or copying) SYSOUTs? In our case similar HARD DISK ERRORs have always afflicted our machines invariably only when making SYSOUTs or copying them between machines. Cheers, Andrew
schmidt@SUMEX-AIM.STANFORD.EDU (Christopher Schmidt) (08/31/88)
Is your lispfiles volume larger than 16 megabytes? There was a bug in Koto that sometimes signalled spurious hard disk errors when such a large lispfiles volume was in use. We were told by AIS to upgrade to Lyric, and as I recall, that fixed the problem. (For unrelated reasons, our machine that had this problem is no longer partitioned with such a large lispfiles volume.) --Christopher
ajcole@ai.leeds.ac.UK (Andrew J Cole) (08/31/88)
Christopher Schmidt writes.. > Is your lispfiles volume larger than 16 megabytes? There was a bug in >Koto that sometimes signalled spurious hard disk errors when such a large >lispfiles volume was in use. Our largest one is 30000 pages. and Steve Skarupa writes.. >That sounds a little familiar. After initializing the SystemTools >volume, the first thing you should do before the SysIn is to >go into the Profile tool once, do an Apply, and exit. I've not heard that one before, but it so happens that I always set up the profile after initialisation since we sysin across the ether. >Your problem may also be that your Lisp volume is too small to >fit the sysout. When that happens I've always managed to recover with scavenges, sometimes having to fix up the break in SCAVENGEDSKDIRECTORY,in this case there was plenty of space for the sysout. Thanks for the responses, to recover with the minimum fuss I eventually erased the LispFiles volume using the installation tool, reinstalled the Koto systemtools etc - at least I didnt need to repartition & the other LispFiles volumes were OK. Cheers, Andrew