My impression is that Arachne beeps on log, graphic rich pages if you try to scroll down before its finished with whatever its doing. This doesn't seem real consistent--sometimes it beeps,sometimes it doesn't. Sometimes you get red squares, sometimes you don't. I can't discern a pattern. Sometimes it crashes, sometimes it doesn't. I'm frustrated by the in- consistency of Arachne's performance. And while I'm on the subject of frustration, I must say that I am frustrated by the premature upload of new versions. I'd be happy to wait a day or two instead of having to go back and reload the corrected third version of a new release. Arachne is such a brilliant and impressive program that it deserves a more careful and meticulous approach to the release of new versions. Not that I'm all that careful and meticulous myself. For instance, it's possible that some of the trouble I'm having is due to the multiple versions of Arachne that I've installed on this 386. At any one time I've got five or six versions installed. I noticed that my path statement had expanded to include five different \arachne directories. A new install gets a new directory with a number-- \arachne5, \arachne6 and so on. Some of these versions have been deleted, some not. I can imagine this leading to all sorts of troubles. Maybe it's time to clean house and do a fresh install of 1.70, version 3. Perhaps multiple versions leads to multiple confusions. On Fri, 26 Jan 2001 18:08:54 +0100, Bernie <[EMAIL PROTECTED]> wrote: > L.D wrote: >> ON ANOTHER NOTE: Has anyone, other than I, found that they are getting >> system beep during certain page & graphics processing? I didn't keep >> track before of which/where/when but will in future. If anyone else has >> experienced this, could you keep track also ... so we can compare notes? > Yes, it happens if I press a key while Arachne is doing something. Mind you > this only happens at school since I've disconnected all internal speakers > here at home ;-) > But I see no sense in comparing notes, anyone (ok - we aren't that many) > with the source can check it out since it's a call to the function beep() > that causes it. I don't know when it happens, nor why Arachne should be > able to beep, IMHO the internal speeker should only be used by the BIOS to > indicate what went wrong during bootup (if one has POST activated that is - > something I removed to speed the computer up <BG>). > //Bernie Sam Ewalt Croswell, Michigan USA -- Arachne V1.70, NON-COMMERCIAL copy, http://arachne.cz/
