New win32 VM available (was: More than 500MB for windows)
So, after spending unproportionally huge time (2days) dealing with jenkins config idiosyncrasies, it finally managed to build it. http://files.pharo.org/vm/pharo/win/latest.zip This VM should react properly on AddressSpaceLimit=<number of MBytes> setting in .ini file. The ini file is located in same directory as VM executable. If it doesn't exists, you can run VM once and it will create it automatically. Thanks for patience. -- Best regards, Igor Stasenko.
Thanks igor. On Jul 11, 2013, at 4:07 PM, Igor Stasenko <siguctua@gmail.com> wrote:
So, after spending unproportionally huge time (2days) dealing with jenkins config idiosyncrasies, it finally managed to build it.
http://files.pharo.org/vm/pharo/win/latest.zip
This VM should react properly on AddressSpaceLimit=<number of MBytes> setting in .ini file. The ini file is located in same directory as VM executable. If it doesn't exists, you can run VM once and it will create it automatically.
Thanks for patience.
-- Best regards, Igor Stasenko.
Thank you, indeed! Doru On Jul 13, 2013, at 2:24 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Thanks igor.
On Jul 11, 2013, at 4:07 PM, Igor Stasenko <siguctua@gmail.com> wrote:
So, after spending unproportionally huge time (2days) dealing with jenkins config idiosyncrasies, it finally managed to build it.
http://files.pharo.org/vm/pharo/win/latest.zip
This VM should react properly on AddressSpaceLimit=<number of MBytes> setting in .ini file. The ini file is located in same directory as VM executable. If it doesn't exists, you can run VM once and it will create it automatically.
Thanks for patience.
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Be rather willing to give than demanding to get."
I am trying the vm now, and I have a couple of issues: - Why is the executable named PharoS instead of Pharo? - There is no .ini file in the archive. In the older one, I have the following contents in the Pharo.ini: [Global] DeferUpdate=1 ShowConsole=0 DynamicConsole=1 ReduceCPUUsage=1 ReduceCPUInBackground=0 3ButtonMouse=0 1ButtonMouse=0 UseDirectSound=1 PriorityBoost=1 B3DXUsesOpenGL=0 CaseSensitiveFileMode=0 Do I still need these? Doru On Thu, Jul 11, 2013 at 4:07 PM, Igor Stasenko <siguctua@gmail.com> wrote:
So, after spending unproportionally huge time (2days) dealing with jenkins config idiosyncrasies, it finally managed to build it.
http://files.pharo.org/vm/pharo/win/latest.zip
This VM should react properly on AddressSpaceLimit=<number of MBytes> setting in .ini file. The ini file is located in same directory as VM executable. If it doesn't exists, you can run VM once and it will create it automatically.
Thanks for patience.
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every thing has its own flow"
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS? Doru On Mon, Jul 15, 2013 at 3:14 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
I am trying the vm now, and I have a couple of issues: - Why is the executable named PharoS instead of Pharo? - There is no .ini file in the archive. In the older one, I have the following contents in the Pharo.ini: [Global] DeferUpdate=1 ShowConsole=0 DynamicConsole=1 ReduceCPUUsage=1 ReduceCPUInBackground=0 3ButtonMouse=0 1ButtonMouse=0 UseDirectSound=1 PriorityBoost=1 B3DXUsesOpenGL=0 CaseSensitiveFileMode=0
Do I still need these?
Doru
On Thu, Jul 11, 2013 at 4:07 PM, Igor Stasenko <siguctua@gmail.com> wrote:
So, after spending unproportionally huge time (2days) dealing with jenkins config idiosyncrasies, it finally managed to build it.
http://files.pharo.org/vm/pharo/win/latest.zip
This VM should react properly on AddressSpaceLimit=<number of MBytes> setting in .ini file. The ini file is located in same directory as VM executable. If it doesn't exists, you can run VM once and it will create it automatically.
Thanks for patience.
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
On 2013-07-15, at 15:35, Damien Cassou <damien.cassou@gmail.com> wrote:
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog?
StackVM renameAs: #PharoS And you might interpret it in two ways: Pharo+Stack, Pharo+Slow ;)
On 15 July 2013 15:34, Damien Cassou <damien.cassou@gmail.com> wrote:
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog?
yeah, it looks like Esteban by making configs for PharoS VM made a mistake and these VMs uploaded into same location as Cog ones.. (we fixed it already, building new VM, which will copy stuff properly) alternatively , you can download VM from build server: https://ci.inria.fr/pharo/view/VM/job/PharoVM/182/Architecture=32,Slave=vm-b... (to make sure we're talking about same VM)
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
Aha :). Ok. I tested PharoS with 1GB and I got a 800MB image running well. Is there really no chance of getting Cog with this feature? :) Doru On Mon, Jul 15, 2013 at 4:23 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 15:34, Damien Cassou <damien.cassou@gmail.com> wrote:
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog?
yeah, it looks like Esteban by making configs for PharoS VM made a mistake and these VMs uploaded into same location as Cog ones.. (we fixed it already, building new VM, which will copy stuff properly)
alternatively , you can download VM from build server:
https://ci.inria.fr/pharo/view/VM/job/PharoVM/182/Architecture=32,Slave=vm-b...
(to make sure we're talking about same VM)
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every thing has its own flow"
On 2013-07-15, at 17:00, Tudor Girba <tudor@tudorgirba.com> wrote:
Aha :).
Ok. I tested PharoS with 1GB and I got a 800MB image running well.
Is there really no chance of getting Cog with this feature? :)
should be the same setting for both Pharo and PharoS (note there is no more Cog, NBCog and StackVM ;). There was a tiny bug in the configuration, so Windows will decide to finish the build we should have Pharo VM with the same properties.
On 15 July 2013 16:59, Tudor Girba <tudor@tudorgirba.com> wrote:
Aha :).
Ok. I tested PharoS with 1GB and I got a 800MB image running well.
Is there really no chance of getting Cog with this feature? :)
please ,read more carefully.. :) it was error in config, which copied PharoS files over Pharo ones. And answering your question: you should have the same feature in both VMs since they sharing same C codebase.
Doru
On Mon, Jul 15, 2013 at 4:23 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 15:34, Damien Cassou <damien.cassou@gmail.com> wrote:
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog?
yeah, it looks like Esteban by making configs for PharoS VM made a mistake and these VMs uploaded into same location as Cog ones.. (we fixed it already, building new VM, which will copy stuff properly)
alternatively , you can download VM from build server:
https://ci.inria.fr/pharo/view/VM/job/PharoVM/182/Architecture=32,Slave=vm-b...
(to make sure we're talking about same VM)
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
Actually, I did read, but what I understood is only that I should look for another URL do download PharoS :). In any case, thanks a lot. I tried with the Pharo VM and it works as expected, too. I set it to 1GB and got the warning only when the image went passed that limit. Cheers, Doru On Mon, Jul 15, 2013 at 5:36 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 16:59, Tudor Girba <tudor@tudorgirba.com> wrote:
Aha :).
Ok. I tested PharoS with 1GB and I got a 800MB image running well.
Is there really no chance of getting Cog with this feature? :)
please ,read more carefully.. :) it was error in config, which copied PharoS files over Pharo ones. And answering your question: you should have the same feature in both VMs since they sharing same C codebase.
Doru
On Mon, Jul 15, 2013 at 4:23 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 15:34, Damien Cassou <damien.cassou@gmail.com> wrote:
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog?
yeah, it looks like Esteban by making configs for PharoS VM made a mistake and these VMs uploaded into same location as Cog ones.. (we fixed it already, building new VM, which will copy stuff properly)
alternatively , you can download VM from build server:
https://ci.inria.fr/pharo/view/VM/job/PharoVM/182/Architecture=32,Slave=vm-b...
(to make sure we're talking about same VM)
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every thing has its own flow"
On 16 Jul 2013, at 11:33, Tudor Girba <tudor@tudorgirba.com> wrote:
Actually, I did read, but what I understood is only that I should look for another URL do download PharoS :).
In any case, thanks a lot. I tried with the Pharo VM and it works as expected, too. I set it to 1GB and got the warning only when the image went passed that limit.
That _is_ good news !
Cheers, Doru
On Mon, Jul 15, 2013 at 5:36 PM, Igor Stasenko <siguctua@gmail.com> wrote: On 15 July 2013 16:59, Tudor Girba <tudor@tudorgirba.com> wrote:
Aha :).
Ok. I tested PharoS with 1GB and I got a 800MB image running well.
Is there really no chance of getting Cog with this feature? :)
please ,read more carefully.. :) it was error in config, which copied PharoS files over Pharo ones. And answering your question: you should have the same feature in both VMs since they sharing same C codebase.
Doru
On Mon, Jul 15, 2013 at 4:23 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 15:34, Damien Cassou <damien.cassou@gmail.com> wrote:
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog?
yeah, it looks like Esteban by making configs for PharoS VM made a mistake and these VMs uploaded into same location as Cog ones.. (we fixed it already, building new VM, which will copy stuff properly)
alternatively , you can download VM from build server:
https://ci.inria.fr/pharo/view/VM/job/PharoVM/182/Architecture=32,Slave=vm-b...
(to make sure we're talking about same VM)
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
On Tue, Jul 16, 2013 at 11:33 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
Actually, I did read, but what I understood is only that I should look for another URL do download PharoS :).
In any case, thanks a lot. I tried with the Pharo VM and it works as expected, too. I set it to 1GB and got the warning only when the image went passed that limit.
That's a very good news. Tx igor for fixing and Doru for testing ;).
Cheers, Doru
On Mon, Jul 15, 2013 at 5:36 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 16:59, Tudor Girba <tudor@tudorgirba.com> wrote:
Aha :).
Ok. I tested PharoS with 1GB and I got a 800MB image running well.
Is there really no chance of getting Cog with this feature? :)
please ,read more carefully.. :) it was error in config, which copied PharoS files over Pharo ones. And answering your question: you should have the same feature in both VMs since they sharing same C codebase.
Doru
On Mon, Jul 15, 2013 at 4:23 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 15:34, Damien Cassou <damien.cassou@gmail.com> wrote:
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog?
yeah, it looks like Esteban by making configs for PharoS VM made a mistake and these VMs uploaded into same location as Cog ones.. (we fixed it already, building new VM, which will copy stuff properly)
alternatively , you can download VM from build server:
https://ci.inria.fr/pharo/view/VM/job/PharoVM/182/Architecture=32,Slave=vm-b...
(to make sure we're talking about same VM)
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
participants (7)
-
Camillo Bruni -
Damien Cassou -
Igor Stasenko -
Stéphane Ducasse -
Sven Van Caekenberghe -
Tudor Girba -
Usman Bhatti