 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I had a bit of a crash last week using XPhome. :/
PCI.SYS was apparently corrupt and I was in a never-ending cycle of
restarts, trying to get into safe mode, trying to use system restore, (which
wouldn't complete the job), trying to boot from CD, etc.
Anyway, I got it all back somehow, but I'm now left with this annoying
problem with the I/O restrictions box popping up twice when I start the
first test render on an image. It doesn't pop up after this and PovRay will
render normally.
It's set on the default settings, and I tried repairing PovRay, but that
didn't work.
Is there a way to fix this?
Thanks for any help.
~Steve~
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"St." <dot### [at] dot com> wrote in message news:42e3a998@news.povray.org...
>I had a bit of a crash last week using XPhome. :/
It's ok, it did it again tonight half way through a long render. It's
definately my graphics card. Took it out, dusted it off, and my PC fired up
nicely.
> Thanks for any help.
:/
~Steve~
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I/O problem hasn't disappeared though.
~Steve~
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Gee, this must be one of the strangest things I've ever heard happen during
POV-Ray running/rendering.
Electronics getting that dusty inside the case, eh? :)
I don't get the connection between the card and POV's I/O Restrictions
thing. That's pretty weird, eh? Hopefully you won't be having more trouble.
I also don't understand how it effected the CD booting, etc. if Safe Mode
was being used, since that should have used a simple VGA display (possibly
from onboard video of the mainboard?).
Well, I just plain don't get it anyhow. I suppose you checked the file
system for errors by running a chkdsk on the drive...?
I see you posted again before I got this reply sent, saying the I/O box
still shows up. Maybe you should have a look at the POV-Ray\ini\pvengine.ini
file and look for the following (mine is set to allow everything) to make
sure POV is finding it there:
[Scripting]
ReadWriteSourceDir=1
NoShellOuts=1
IO Restrictions=0
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bob Hughes" <omniverse@charter%net> wrote in message
news:42eb090e$1@news.povray.org...
> Gee, this must be one of the strangest things I've ever heard happen
> during POV-Ray running/rendering.
>
> Electronics getting that dusty inside the case, eh? :)
Well, yes. ;)
I actually cleaned the whole tower out last week though apart from taking my
graphics card out. I took it out tonight/this morning, dusted it off, and it
fired up ok, so thankfully, I know what to do now. :)
>
> I don't get the connection between the card and POV's I/O Restrictions
> thing. That's pretty weird, eh?
Yeah, it's most irritating Bob! I can live with it though. It only happens
when I start a render, and then if PoV(3.5) stays open, it won't do it
again.
> Hopefully you won't be having more trouble.
Fingers crossed. ;)
> I also don't understand how it effected the CD booting, etc. if Safe Mode
> was being used, since that should have used a simple VGA display (possibly
> from onboard video of the mainboard?).
Well, I couldn't even get to safe mode tonight. That's why I took the GC out
and dusted that off. Everything works fine now.
>
> Well, I just plain don't get it anyhow. I suppose you checked the file
> system for errors by running a chkdsk on the drive...?
XP does this when rebooting from a problem anyway, and this time
(thankfully!) nothing showed. The first time, I had pages and pages of stuff
that showed up.
>
> I see you posted again before I got this reply sent, saying the I/O box
> still shows up. Maybe you should have a look at the
> POV-Ray\ini\pvengine.ini file and look for the following (mine is set to
> allow everything) to make sure POV is finding it there:
>
> [Scripting]
> ReadWriteSourceDir=1
> NoShellOuts=1
> IO Restrictions=0
Thanks Bob. I think this might be the problem. I'm getting this error
when clicking on 'pvengine.ini':
"Command line processing error:
Only /Edit and /Render may be passed to the previous instance."
Clicking on pvengine.ini opens PovRay, and then I get the above error.
I'm thinking this is an 'association' thing?
(Wow! Update: It must be. I've just clicked on unrelated *.ini files and
PoV wants to open them all!)
Thanks for your help Bob, any ideas as to what to do now?
~Steve~
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"St." <dot### [at] dotcom> wrote in message news:42eb128c@news.povray.org...
>
> when clicking on 'pvengine.ini':
>
> "Command line processing error:
>
> Only /Edit and /Render may be passed to the previous instance."
>
> Clicking on pvengine.ini opens PovRay, and then I get the above error.
>
> I'm thinking this is an 'association' thing?
>
> (Wow! Update: It must be. I've just clicked on unrelated *.ini files
> and PoV wants to open them all!)
>
> Thanks for your help Bob, any ideas as to what to do now?
Um... mine opens into Notepad here, Steve.
I chose this way long ago to open these kinds of files but I've forgotten if
POV sets up to do so. I've always wanted to see these files since they are
from various programs, Windows, etc.; not only POV-Ray ones. I just don't
remember any more, but could be POV tries to include them itself when it
gets installed. Then again, INI isn't a renderable file and besides, that
error message suggests it was doing something else with it-- as it probably
should, since it is a settings file. So seems it wants a pov scene file
along with it, if anything.
I tried switching the opening program over to POV (3.6.1 here) and it does
open it into the editor okay, no errors.
You could go into My Computer (or Explorer) menu Tools, then Folder Options,
finally File Types and select INI from the list to make changes in how it is
opened. Or easier still, use the Explorer to right-click on a INI file and
select Properties then the Change... button to choose a different program
like Notepad (or POV-Ray).
Far as ideas, guess that's all I can say.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bob Hughes" <omniverse@charter%net> wrote in message
news:42eb233f$1@news.povray.org...
> "St." <dot### [at] dotcom> wrote in message news:42eb128c@news.povray.org...
>>
>> when clicking on 'pvengine.ini':
>>
>> "Command line processing error:
>>
>> Only /Edit and /Render may be passed to the previous instance."
>>
>> Clicking on pvengine.ini opens PovRay, and then I get the above error.
>>
>> I'm thinking this is an 'association' thing?
>>
>> (Wow! Update: It must be. I've just clicked on unrelated *.ini files
>> and PoV wants to open them all!)
AND it would do the same with *.inc files too! Very strange.
>>
>> Thanks for your help Bob, any ideas as to what to do now?
>
> Um... mine opens into Notepad here, Steve.
>
> I chose this way long ago to open these kinds of files but I've forgotten
> if POV sets up to do so.
> I tried switching the opening program over to POV (3.6.1 here) and it does
> open it into the editor okay, no errors.
>
> You could go into My Computer (or Explorer) menu Tools...
> Far as ideas, guess that's all I can say.
No, you've helped a big deal Bob, thanks. I've now got *.ini's and
*.inc's opening in notepad, and not PoV. The I/O box has disappeared too. :)
Very strange though. I can promise you that I didn't change anything
before or after the crash and I'm sure *ini's and *.inc's used to open in
notepad anyway. Yes, positive about that.
Oh, and when I checked pvengine.ini, it showed "IO restrictions=2",
which I changed to '0'. Hmm...
Thanks again. :o)
~Steve~
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
St. wrote:
> XP does this when rebooting from a problem anyway,
Really? I've never had XP actually run a chkdsk just because of a
reboot, even a crash. It's supposed to just apply/roll back the
journal/log/whatever they call it.
I've often found that problems like this are caused by failing disk
sectors in places like the swap file. You might want to run a
"chkdsk /f /r" a couple times when the machine's otherwise mostly idle.
I've several times had a machine that was acting flakier and flakier
over the course of a week or two, then pop up a dialog saying "found a
bad sector in (important system structure), relocating" and had
everything start being smooth again.
--
Darren New / San Diego, CA, USA (PST)
"You shouldn't buy ice cream. It's bad
for you and it'll make you fat. Oh,
look. A 2-for-1 sale. Get two."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Darren New" <dne### [at] sanrrcom> wrote in message
news:42ed3d87$1@news.povray.org...
> St. wrote:
>> XP does this when rebooting from a problem anyway,
>
> Really?
Well, only from what I've experienced over the last few weeks, but yes,
this is what happened to me.
I've never had XP actually run a chkdsk just because of a
> reboot, even a crash. It's supposed to just apply/roll back the
> journal/log/whatever they call it.
But this was the problem I was having; it wouldn't do that.
>
> I've often found that problems like this are caused by failing disk
> sectors in places like the swap file. You might want to run a
> "chkdsk /f /r" a couple times when the machine's otherwise mostly idle.
I'll try that, thanks Darren.
>
> I've several times had a machine that was acting flakier and flakier over
> the course of a week or two, then pop up a dialog saying "found a bad
> sector in (important system structure), relocating" and had everything
> start being smooth again.
I've had about 20 pages, (read: reboots, scandisk), of that dialogue,
ranging from one bad sector to fifty-ish bad sectors.
HardDisk knackered? I hope not... :(
~Steve~
>
> --
> Darren New / San Diego, CA, USA (PST)
> "You shouldn't buy ice cream. It's bad
> for you and it'll make you fat. Oh,
> look. A 2-for-1 sale. Get two."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
St. nous apporta ses lumieres en ce 2005-07-31 19:32:
>
> "Darren New" <dne### [at] sanrrcom> wrote in message
> news:42ed3d87$1@news.povray.org...
>
>> St. wrote:
>>
>>> XP does this when rebooting from a problem anyway,
>>
>>
>> Really?
>
>
> Well, only from what I've experienced over the last few weeks, but yes,
> this is what happened to me.
>
>
> I've never had XP actually run a chkdsk just because of a
>
>> reboot, even a crash. It's supposed to just apply/roll back the
>> journal/log/whatever they call it.
>
>
> But this was the problem I was having; it wouldn't do that.
>
>
>>
>> I've often found that problems like this are caused by failing disk
>> sectors in places like the swap file. You might want to run a
>> "chkdsk /f /r" a couple times when the machine's otherwise mostly idle.
>
>
> I'll try that, thanks Darren.
>
>
>>
>> I've several times had a machine that was acting flakier and flakier
>> over the course of a week or two, then pop up a dialog saying "found a
>> bad sector in (important system structure), relocating" and had
>> everything start being smooth again.
>
>
> I've had about 20 pages, (read: reboots, scandisk), of that dialogue,
> ranging from one bad sector to fifty-ish bad sectors.
>
> HardDisk knackered? I hope not... :(
>
> ~Steve~
>
>
>>
>> --
>> Darren New / San Diego, CA, USA (PST)
>> "You shouldn't buy ice cream. It's bad
>> for you and it'll make you fat. Oh,
>> look. A 2-for-1 sale. Get two."
>
>
You may have to get a new drive. I once had a drive that started missbehaving, several
bad sectors
alerts, some corrupted files. I just had the time to install a new one, transfert most
files to it
before the drive died. That drive is now a paperweith!
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
