POV-Ray : Newsgroups : povray.beta-test : Testing on XP required. Server Time: 22 Jul 2019 22:22:04 GMT
  Testing on XP required. (Message 5 to 14 of 14)  
<<< Previous 4 Messages Goto Initial 10 Messages
From: StephenS
Subject: Re: Testing on XP required.
Date: 31 Aug 2016 01:19:55
Message: <57c630bb$1@news.povray.org>
On 30/08/2016 8:43 PM, StephenS wrote:
...
>> Is that a symptom you also see with previous development builds?
>>
> It looks like every time I start pvengine32.exe
> (3.7.1-alpha.8764097+av168.msvc14.win32)
>
> It creates a new "pvengine.ini", resetting changes.
>
> Does this help?
>
> pvengine.exe, 3.7.0.msvc10.win32, does not do this.
>
> Stephen S
pvengine.exe, 3.7.0.msvc10.win32, updates the date modified of 
"pvengine.ini" each time it's run, but keeps my changes.

example:
ExtDLL16=C:\Program Files\Bishop3D\Bishop3DPovComm.dll

Stephen S


Post a reply to this message

From: clipka
Subject: Re: Testing on XP required.
Date: 31 Aug 2016 04:36:21
Message: <57c65ec5@news.povray.org>
Am 31.08.2016 um 03:19 schrieb StephenS:
> On 30/08/2016 8:43 PM, StephenS wrote:
> ....
>>> Is that a symptom you also see with previous development builds?
>>>
>> It looks like every time I start pvengine32.exe
>> (3.7.1-alpha.8764097+av168.msvc14.win32)
>>
>> It creates a new "pvengine.ini", resetting changes.
>>
>> Does this help?
>>
>> pvengine.exe, 3.7.0.msvc10.win32, does not do this.
>>
>> Stephen S
> pvengine.exe, 3.7.0.msvc10.win32, updates the date modified of
> "pvengine.ini" each time it's run, but keeps my changes.

To re-iterate my quiz question:

Is that a symptom you also see with previous DEVELOPMENT builds?
E.g. this one:

https://github.com/POV-Ray/povray/releases/tag/v3.7.1-alpha.8737777

I need to know if this effect is something I've introduced with the new
build procedure, or whether it's a pre-existing bug introduced earlier
during development.

If you see the symptom with 3.7.1-alpha.8737777 as well, I might ask you
to also try this one:

https://github.com/POV-Ray/povray/releases/tag/v3.7.1-alpha.8451792%2Bav100

And if the 3.7.1-alpha.8451792 doesn't have it, I'd like to ask you to
try releases in between (excluding those marked "experimental"), to
narrow down where the error was introduced.

If you have the time of course.


Post a reply to this message

From: StephenS
Subject: Re: Testing on XP required.
Date: 31 Aug 2016 10:08:51
Message: <57c6acb3$1@news.povray.org>
On 31/08/2016 12:36 AM, clipka wrote:
...
> If you have the time of course.
>
Some during the week, lots during the weekend.

Will start as time permits.

Stephen S


Post a reply to this message

From: StephenS
Subject: Re: Testing on XP required.
Date: 4 Sep 2016 14:45:31
Message: <57cc338b$1@news.povray.org>
...
> If you have the time of course.
>

I have many of the builds, maybe some experimental, ops.

8451792 av100 not valid
8558038 av124 working
8586521 av129 not valid


8737777 av158 not valid
8764097 av168 working, missing color.inc

working through more.

Stephen S


Post a reply to this message

From: clipka
Subject: Re: Testing on XP required.
Date: 4 Sep 2016 15:31:47
Message: <57cc3e63$1@news.povray.org>
Am 04.09.2016 um 16:44 schrieb StephenS:
> ....
>> If you have the time of course.
>>
> 
> I have many of the builds, maybe some experimental, ops.
> 
> 8451792 av100 not valid
> 8558038 av124 working
> 8586521 av129 not valid

That's seriously odd, as the build process hadn't changed between the
latter two.

I presume that "not valid" means Windows XP is claiming the .exe to be
not a valid XP application, and that you're making sure to run the
32-bit version, right?


Post a reply to this message

From: StephenS
Subject: Re: Testing on XP required.
Date: 4 Sep 2016 15:34:42
Message: <57cc3f12$1@news.povray.org>
On 04/09/2016 10:44 AM, StephenS wrote:
> ...
>> If you have the time of course.
>>
>
> I have many of the builds, maybe some experimental, ops.
>
> 8451792 av100 not valid
8514084 av121 working
8545805 av122 working
8555867 av123 working
> 8558038 av124 working
> 8586521 av129 not valid
8600570 av138 not valid
...all not valid
8730959 av156 not valid
> 8737777 av158 not valid
> 8764097 av168 working, missing color.inc
>
> working through more.
>
> Stephen S
The testing is for pvengine32.exe only, not "-sse2"
Both can run on my computer.
Athlon64 X2 Dual, 4200+, 2gb ram
WinXP sp3 (Media center edition)


Post a reply to this message

From: StephenS
Subject: Re: Testing on XP required.
Date: 4 Sep 2016 15:36:48
Message: <57cc3f90$1@news.povray.org>
On 04/09/2016 11:31 AM, clipka wrote:
...
> That's seriously odd, as the build process hadn't changed between the
> latter two.
>
> I presume that "not valid" means Windows XP is claiming the .exe to be
> not a valid XP application, and that you're making sure to run the
> 32-bit version, right?
>
Correct.
Only the 32-bit downloaded so far.

Stephen S


Post a reply to this message

From: clipka
Subject: Re: Testing on XP required.
Date: 4 Sep 2016 16:33:48
Message: <57cc4cec$1@news.povray.org>
Am 04.09.2016 um 17:31 schrieb clipka:
> Am 04.09.2016 um 16:44 schrieb StephenS:
>> ....
>>> If you have the time of course.
>>>
>>
>> I have many of the builds, maybe some experimental, ops.
>>
>> 8451792 av100 not valid
>> 8558038 av124 working
>> 8586521 av129 not valid
> 
> That's seriously odd, as the build process hadn't changed between the
> latter two.

Hm... in a way it did: Our automated build service, AppVeyor, updated
Microsoft Visual Studio 2015 from version 14.0.24720.0 to version
14.0.25123.0.

So following Mick's famous advice, I guess I'll blame it on the boogeyman.


Post a reply to this message

From: clipka
Subject: Re: Testing on XP required.
Date: 4 Sep 2016 18:30:39
Message: <57cc684f$1@news.povray.org>
Am 04.09.2016 um 16:44 schrieb StephenS:

> 8737777 av158 not valid
> 8764097 av168 working, missing color.inc

I'm folding on this one. No automated XP-compatible builds until further
notice.


Post a reply to this message

From: StephenS
Subject: Re: Testing on XP required.
Date: 4 Sep 2016 21:12:00
Message: <57cc8e20$1@news.povray.org>
On 04/09/2016 11:33 AM, StephenS wrote:
...
>> I have many of the builds, maybe some experimental, ops.
>>
>> 8451792 av100 not valid
> 8514084 av121 working
> 8545805 av122 working
> 8555867 av123 working
>> 8558038 av124 working
>> 8586521 av129 not valid
> 8600570 av138 not valid
> ...all not valid
> 8730959 av156 not valid
>> 8737777 av158 not valid
>> 8764097 av168 working, missing color.inc
sorry, should read: can not find..
>>
>> working through more.
>>
>> Stephen S
> The testing is for pvengine32.exe only, not "-sse2"
> Both can run on my computer.
> Athlon64 X2 Dual, 4200+, 2gb ram
> WinXP sp3 (Media center edition)

8558038 av124 working
8586521 av129 working
...
8737777 av158 not valid
8764097 av168 working, can not find color.inc...

The testing is for pvengine32-sse2.exe

Stephen S


Post a reply to this message

<<< Previous 4 Messages Goto Initial 10 Messages

Copyright 2003-2008 Persistence of Vision Raytracer Pty. Ltd.