1. Eu locking harddrives
Eu did it yet again, locking up a harddrive for no apparent reason, for over two
minutes, just to get the include files. This totally wrecked all other time-
sensitive applications, interrupting channels on irc, causing http processes
to halt and disconnect, and even stopping me from launching other apps from
that drive. This time, it was Webshepard that did it (again).
I don't usually use that app, and i needed it again. I have complained about
this behavior for years, preiodically, and it's still occuring.
If you run Eu with multiple includes, move EACH Eu app off to it's own drive,
and don't put apps you use often on that drive!
Kat
2. Re: Eu locking harddrives
----- Original Message -----
From: "Kat" <gertie at visionsix.com>
To: <EUforum at topica.com>
Subject: Eu locking harddrives
>
>
> Eu did it yet again, locking up a harddrive for no apparent reason, for over
> two
> minutes, just to get the include files. This totally wrecked all other time-
> sensitive applications, interrupting channels on irc, causing http processes
> to halt and disconnect, and even stopping me from launching other apps from
> that drive. This time, it was Webshepard that did it (again).
>
> I don't usually use that app, and i needed it again. I have complained about
> this behavior for years, preiodically, and it's still occuring.
>
> If you run Eu with multiple includes, move EACH Eu app off to it's own drive,
> and don't put apps you use often on that drive!
>
Sounds more like a feature of Win95 than Euphoria. I have never experienced this
sort of problem with Eu.
--
Derek
3. Re: Eu locking harddrives
On Wed, 4 Feb 2004 20:42:59 +0000, CoJaBo <cojabo at suscom.net> wrote:
>
>I get that all the time in XP, though rarely in Eu programs.
I get a similar thing in Explorer (win98), when I delete files.
>
>
>Derek Parnell wrote:
>>
>>
>> ----- Original Message -----
>> From: "Kat" <gertie at visionsix.com>
>> To: <EUforum at topica.com>
>> Sent: Thursday, February 05, 2004 5:36 AM
>> Subject: Eu locking harddrives
>>
>>
>> > Eu did it yet again, locking up a harddrive for no apparent reason, for
>> > over two
>> > minutes, just to get the include files. This totally wrecked all other
>> > time-
>> > sensitive applications, interrupting channels on irc, causing http
>> > processes
>> > to halt and disconnect, and even stopping me from launching other apps
>> > from
>> > that drive. This time, it was Webshepard that did it (again).
>> >
>> > I don't usually use that app, and i needed it again. I have complained
>> > about
>> > this behavior for years, preiodically, and it's still occuring.
>> >
>> > If you run Eu with multiple includes, move EACH Eu app off to it's own
>> > drive,
>> > and don't put apps you use often on that drive!
>> >
>>
>> Sounds more like a feature of Win95 than Euphoria. I have never
>> experienced this sort of problem with Eu.
>>
>> --
>> Derek
>>
>>
>
>
>TOPICA - Start your own email discussion group. FREE!
>
4. Re: Eu locking harddrives
On 4 Feb 2004, at 23:33, Pete Lomax wrote:
>
>
> On Wed, 4 Feb 2004 20:42:59 +0000, CoJaBo <cojabo at suscom.net> wrote:
>
> >
> >I get that all the time in XP, though rarely in Eu programs.
> I get a similar thing in Explorer (win98), when I delete files.
RobC, please add a REAL sleep(0) between file fetches when Eu starts up,
and close the files asap, either before or after the Eu.exe is decompressed in
memory. If the include is a big one, how about dropping in some sleep(0) in
the middle of it somewhere, so the OS has a chance to deal with other
programs. This isn't win3.1 or dos anymore, and the bloated OSs today need
more time, and need the app to open more slots for it to get time-sensitive
things done.
Thanks,
Kat,
contrary to popular opinion, windows uses sleep(0) to deal with msg que on
other apps, it's not useless. Modify your misc.e to allow sleep(0).
> >
> >
> >Derek Parnell wrote:
> >>
> >>
> >> ----- Original Message -----
> >> From: "Kat" <gertie at visionsix.com>
> >> To: <EUforum at topica.com>
> >> Sent: Thursday, February 05, 2004 5:36 AM
> >> Subject: Eu locking harddrives
> >>
> >>
> >> > Eu did it yet again, locking up a harddrive for no apparent reason, for
> >> > over two minutes, just to get the include files. This totally wrecked all
> >> > other time- sensitive applications, interrupting channels on irc, causing
> >> > http processes to halt and disconnect, and even stopping me from
> >> > launching
> >> > other apps from that drive. This time, it was Webshepard that did it
> >> > (again).
> >> >
> >> > I don't usually use that app, and i needed it again. I have complained
> >> > about this behavior for years, preiodically, and it's still occuring.
> >> >
> >> > If you run Eu with multiple includes, move EACH Eu app off to it's own
> >> > drive, and don't put apps you use often on that drive!
> >> >
> >>
> >> Sounds more like a feature of Win95 than Euphoria. I have never
> >> experienced this sort of problem with Eu.
> >>
> >> --
> >> Derek
> >>
> >>
> >TOPICA - Start your own email discussion group. FREE!
> >
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>
5. Re: Eu locking harddrives
Kat wrote:
> RobC, please add a REAL sleep(0) between file fetches when Eu starts up,
> and close the files asap, either before or after the Eu.exe is decompressed in
>
> memory. If the include is a big one, how about dropping in some sleep(0) in
> the middle of it somewhere, so the OS has a chance to deal with other
> programs.
I'm not sure what the problem is, but even on a 386, Euphoria
parses files at a rate of many thousands of lines per second.
It closes include files as soon as it sees the end of file.
If there's a delay occurring, it's probably
due to some code your program is executing, maybe some "top-level"
Euphoria code that's executed as the include file is processed
by the interpreter. If you still have doubts about include files,
try the Translator - no run-time include file processing at all.
> This isn't win3.1 or dos anymore, and the bloated OSs today need
> more time, and need the app to open more slots for it to get time-sensitive
> things done.
> contrary to popular opinion, windows uses sleep(0) to deal with msg que on
> other apps, it's not useless. Modify your misc.e to allow sleep(0).
OK, I've adjusted misc.e so sleep(0) will actually call
the system sleep routine, rather than skipping it.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
6. Re: Eu locking harddrives
Rob wrote:
> Kat wrote:
<snip>
>> contrary to popular opinion, windows uses sleep(0) to deal with msg que
>> on other apps, it's not useless. Modify your misc.e to allow sleep(0).
>
> OK, I've adjusted misc.e so sleep(0) will actually call
> the system sleep routine, rather than skipping it.
Does this mean, that we then can and should call sleep(0) in the same
situations, in which we would use Win32Lib's doEvents()?
TIA,
Juergen
7. Re: Eu locking harddrives
>From: Juergen Luethje <j.lue at gmx.de>
>Subject: Re: Eu locking harddrives
>
>Rob wrote:
>
> > Kat wrote:
>
> >> contrary to popular opinion, windows uses sleep(0) to deal with msg que
> >> on other apps, it's not useless. Modify your misc.e to allow sleep(0).
> >
> > OK, I've adjusted misc.e so sleep(0) will actually call
> > the system sleep routine, rather than skipping it.
>
>Does this mean, that we then can and should call sleep(0) in the same
>situations, in which we would use Win32Lib's doEvents()?
>
No, sleep is for long loops used in non-GUI applications. doEvents()
processes windows messages, for the application. sleep() allows *other*
applications to do stuff.
>TIA,
>Juergen
>
8. Re: Eu locking harddrives
I've been getting that with XP on my laptop.
CoJaBo wrote:
>
>
>I get that all the time in XP, though rarely in Eu programs.
>
>
>Derek Parnell wrote:
>
>
>>----- Original Message -----
>>From: "Kat" <gertie at visionsix.com>
>>To: <EUforum at topica.com>
>>Sent: Thursday, February 05, 2004 5:36 AM
>>Subject: Eu locking harddrives
>>
>>
>>>Eu did it yet again, locking up a harddrive for no apparent reason, for
>>>over two
>>>minutes, just to get the include files. This totally wrecked all other
>>>time-
>>>sensitive applications, interrupting channels on irc, causing http
>>>processes
>>>to halt and disconnect, and even stopping me from launching other apps
>>>from
>>>that drive. This time, it was Webshepard that did it (again).
>>>
>>>I don't usually use that app, and i needed it again. I have complained
>>>about
>>>this behavior for years, preiodically, and it's still occuring.
>>>
>>>If you run Eu with multiple includes, move EACH Eu app off to it's own
>>>drive,
>>>and don't put apps you use often on that drive!
>>>
>>>
>>Sounds more like a feature of Win95 than Euphoria. I have never
>>experienced this sort of problem with Eu.
>>
>>--
>>Derek
>>
>>
>
>
>TOPICA - Start your own email discussion group. FREE!
>
>
9. Re: Eu locking harddrives
Rob wrote:
> Kat wrote:
>
>> contrary to popular opinion, windows uses sleep(0) to deal with msg que
>> on other apps, it's not useless. Modify your misc.e to allow sleep(0).
>
> OK, I've adjusted misc.e so sleep(0) will actually call
> the system sleep routine, rather than skipping it.
BTW: How about allowing any atom as argument for sleep(), not only an
integer? I just got an error message from Eu, because I tried to call
sleep(0.5).
Regards,
Juergen
10. Re: Eu locking harddrives
> BTW: How about allowing any atom as argument for sleep(), not only an
> integer? I just got an error message from Eu, because I tried to call
> sleep(0.5).
--for .exw (WinDoze)
include dll.e
include misc.e --for old sleep()
constant
k32=open_dll("kernel32"),
zSleep=define_c_proc(k32,"Sleep",{C_UINT})
--usage:
--c_proc(zSleep,{x})
--where x is in MILLISECONDS! --Zero allowed
--demo is:
printf(1,"%s\n",{"Start"})
c_proc(zSleep,{3500})
printf(1,"%s\n",{"3.5 seconds later..."})
sleep(2) -- ;)
11. Re: Eu locking harddrives
Elliott wrote:
>> From: Juergen Luethje
<snip>
>> Does this mean, that we then can and should call sleep(0) in the same
>> situations, in which we would use Win32Lib's doEvents()?
>
> No, sleep is for long loops used in non-GUI applications. doEvents()
> processes windows messages, for the application. sleep() allows *other*
> applications to do stuff.
Aaaaaahh! The penny has dropped, thanks.
Regards,
Juergen
12. Re: Eu locking harddrives
Wolf wrote:
>> BTW: How about allowing any atom as argument for sleep(), not only an
>> integer? I just got an error message from Eu, because I tried to call
>> sleep(0.5).
>
> --for .exw (WinDoze)
> include dll.e
> include misc.e --for old sleep()
> constant
> k32=open_dll("kernel32"),
> zSleep=define_c_proc(k32,"Sleep",{C_UINT})
> --usage:
> --c_proc(zSleep,{x})
> --where x is in MILLISECONDS! --Zero allowed
> --demo is:
> printf(1,"%s\n",{"Start"})
> c_proc(zSleep,{3500})
> printf(1,"%s\n",{"3.5 seconds later..."})
> sleep(2) -- ;)
Nice, thank you.
Regards,
Juergen
13. Re: Eu locking harddrives
Juergen Luethje wrote:
> BTW: How about allowing any atom as argument for sleep(), not only an
> integer? I just got an error message from Eu, because I tried to call
> sleep(0.5).
On each platform the C library has a sleep() function that
takes an integer, indicating the number of seconds to sleep.
I know it's possible to have better resolution than that,
but it isn't very standardized, so I didn't try to implement it.
Maybe in the future ...
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
