|
 |
Scott Gammans's furious key-hammering produced this:
>>> And now I can't seem to get
>>> POV-Ray to crash Windows... whether I have "Automatically reboot"
>>> checked or not.
>>
>> How is that a bad thing? ;)
>
> Eh... only a bad thing in that I now hold my breath every time I start
> POV-Ray, not knowing whether or not Windows might decide to BSD all over me.
> :p
Heh, I see your point.
Well, you just *know* that Windows is going to wait until you're comfortable
with starting up POV-Ray and then it's going to start BSOD'ing again. ;)
--
/*^*/light_source{100*<-5,2,-5>2}#macro I(i,n)#while(strlen(i)>=n)#local A=asc(
substr(i,n,1));#local a=asc(substr(i,n+1,1));cylinder{<div(A,8)-12,mod(A,8)-4,4
><div(a,8)-12,mod(a,8)-4,4>,0.1pigment{rgb z}}#local n=n+2;#end#end I("ScUe[]"1
/*<*/)I("mkmtlttk"1)//@_$#!,:<"Thhis polysig brought to you by Ian Burgmyer :)"
Post a reply to this message
|
|
|
|
"Scott Gammans" <nos### [at] scottgammans spamisevilcom> wrote in
news:3e76414a@news.povray.org:
> All three logs (application, system and security) are set to overwrite
> events > 7 days old.
>
> --sg
>
>
>
If the log fills up and the oldest event is less than seven days old, it
can sometimes hose windows. With the logevent utility from the resource
kit you can fill the event log up and see if that was the issue.
Post a reply to this message
|
|
|
|
That jibes with what I remember about a similar problem I experienced a few
years ago. I'll try and find a copy of the Windows Resource Kit and see if
that's the cause (I tried finding logevent on MSDN without success)...
Thanks Tom!
"Tom Galvin" <tom### [at] imporg> wrote in message
news:Xns### [at] 204213191226...
> "Scott Gammans" <nos### [at] scottgammansspamisevilcom> wrote in
> news:3e76414a@news.povray.org:
>
>
> > All three logs (application, system and security) are set to overwrite
> > events > 7 days old.
> >
> > --sg
> >
> >
> >
>
> If the log fills up and the oldest event is less than seven days old, it
> can sometimes hose windows. With the logevent utility from the resource
> kit you can fill the event log up and see if that was the issue.
Post a reply to this message
|
|
