Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!maverick.ksu.ksu.edu!hoss!hoss.unl.edu!mosemann From: mosemann@hoss.unl.edu (Russell Mosemann) Newsgroups: comp.sys.mac.programmer Subject: Re: Pyro Message-ID: <1990Jul22.121447.9696@hoss.unl.edu> Date: 22 Jul 90 12:14:47 GMT References: Sender: news@hoss.unl.edu (Network News Administer) Organization: University of Nebraska, Computing Resource Center Lines: 23 In hairston@henry.ece.cmu.edu (David Hairston) writes: >[lim@iris.ucdavis.edu (Lloyd Lim) writes:] >[] I am writing an app that I want to be as MultiFinder friendly as possible. >[] Therefore, when I call WaitNextEvent with a sleep value of 0xFFFFFFFF (the >[] app doesn't run on Systems with the sleep bug). Unfortunately, I noticed >umm, i seem to recall a tech note (sorry i don't remember the number but >you could check the sumex archives, info-mac/apple/tn) that stated that >the largest sleep never exceed 50L for empirically derived reasons. >perhaps that is the source of your problem? > -dave- >hairston@henry.ece.cmu.edu A bug in the early MultiFinder did not allow a time larger than 50L. That has since changed. If you are using the latest MultiFinder, you should be able to put any time in. I believe Lloyd is saying the same thing when he states "...the app doesn't run on Systems with the SLEEP BUG [emphasis mine]..." Russell mosemann@hoss.unl.edu