- Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo 7 image cannot write changes message on startup

by PBKResearch

Sanjay I have had messages like this when I inadvertently tried to start two copies of the same image (in my case pharo 6.1). The first image was running happily in the background, the second gave this message (but still seemed to start OK). I am also on Windows 10, using 32-bit Pharo. HTH Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sanjay Minni Sent: 13 January 2018 05:50 To: pharo-users(a)lists.pharo.org Subject: Re: [Pharo-users] Pharo 7 image cannot write changes message on starup Hi Richard, the path for the image/changes/sources is C:\Users\Myself\Documents\DevArea\p7\Pharo7.0-32bit-eb0a6fb.changes. in which I have all the rights (this is a desktop in which I have admin rights) the pharo image messages also shows the same path (in my earlier post I had replaced with ...) the VM is is a separate directory which is in the path so what could be the issue here Richard Sargent wrote > Hi Sanjay, > > It depends on where you installed Pharo. The ... in the path cited is > important. (And maybe Pharo elided the path.) > > If the path involves either of the Program Files directories, they > cannot be written by an unprivileged user/program. > > Check your access rights on each directory or file in the path via > their properties. > > > On Jan 12, 2018 21:09, "Sanjay Minni" < > sm@ > > wrote: > >> Hi >> >> I get the following message when I try to startup the latest Pharo 7 >> image >> (32 bit VM in Windows). >> >> "Information >> Pharo cannot write to the changes file named >> C:\...\Pharo7.0-32bit-eb0a6fb.changes. >> Please check that you have write permission for this file." >> >> This is a desktop and there is really no issues o permissions What is >> wrong here >> >> regards >> Sanjay >> >> >> >> ----- >> --- >> Regards, Sanjay >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> ----- --- Regards, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 13, 2018

Re: [Pharo-users] Pharo 7 image cannot write changes message on starup

by Alistair Grant

Hi Sanjay, You're not the only one. :-) This problem has been reported on the pharo-dev mailing list as well. Cheers, Alistair On 13 January 2018 at 06:49, Sanjay Minni <sm(a)planage.com> wrote: > Hi Richard, > > the path for the image/changes/sources is > > C:\Users\Myself\Documents\DevArea\p7\Pharo7.0-32bit-eb0a6fb.changes. > > in which I have all the rights (this is a desktop in which I have admin > rights) > the pharo image messages also shows the same path (in my earlier post I had > replaced with ...) > > the VM is is a separate directory which is in the path > > so what could be the issue here > > > Richard Sargent wrote >> Hi Sanjay, >> >> It depends on where you installed Pharo. The ... in the path cited is >> important. (And maybe Pharo elided the path.) >> >> If the path involves either of the Program Files directories, they cannot >> be written by an unprivileged user/program. >> >> Check your access rights on each directory or file in the path via their >> properties. >> >> >> On Jan 12, 2018 21:09, "Sanjay Minni" < > >> sm@ > >> > wrote: >> >>> Hi >>> >>> I get the following message when I try to startup the latest Pharo 7 >>> image >>> (32 bit VM in Windows). >>> >>> "Information >>> Pharo cannot write to the changes file named >>> C:\...\Pharo7.0-32bit-eb0a6fb.changes. >>> Please check that you have write permission for this file." >>> >>> This is a desktop and there is really no issues o permissions >>> What is wrong here >>> >>> regards >>> Sanjay >>> >>> >>> >>> ----- >>> --- >>> Regards, Sanjay >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> > > > > > > ----- > --- > Regards, Sanjay > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Jan. 13, 2018

Re: [Pharo-users] Pharo 7 image cannot write changes message on starup

by Sanjay Minni

Hi Richard, the path for the image/changes/sources is C:\Users\Myself\Documents\DevArea\p7\Pharo7.0-32bit-eb0a6fb.changes. in which I have all the rights (this is a desktop in which I have admin rights) the pharo image messages also shows the same path (in my earlier post I had replaced with ...) the VM is is a separate directory which is in the path so what could be the issue here Richard Sargent wrote > Hi Sanjay, > > It depends on where you installed Pharo. The ... in the path cited is > important. (And maybe Pharo elided the path.) > > If the path involves either of the Program Files directories, they cannot > be written by an unprivileged user/program. > > Check your access rights on each directory or file in the path via their > properties. > > > On Jan 12, 2018 21:09, "Sanjay Minni" < > sm@ > > wrote: > >> Hi >> >> I get the following message when I try to startup the latest Pharo 7 >> image >> (32 bit VM in Windows). >> >> "Information >> Pharo cannot write to the changes file named >> C:\...\Pharo7.0-32bit-eb0a6fb.changes. >> Please check that you have write permission for this file." >> >> This is a desktop and there is really no issues o permissions >> What is wrong here >> >> regards >> Sanjay >> >> >> >> ----- >> --- >> Regards, Sanjay >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> ----- --- Regards, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 13, 2018

Re: [Pharo-users] Pharo 7 image cannot write changes message on starup

by Richard Sargent

Hi Sanjay, It depends on where you installed Pharo. The ... in the path cited is important. (And maybe Pharo elided the path.) If the path involves either of the Program Files directories, they cannot be written by an unprivileged user/program. Check your access rights on each directory or file in the path via their properties. On Jan 12, 2018 21:09, "Sanjay Minni" <sm(a)planage.com> wrote: > Hi > > I get the following message when I try to startup the latest Pharo 7 image > (32 bit VM in Windows). > > "Information > Pharo cannot write to the changes file named > C:\...\Pharo7.0-32bit-eb0a6fb.changes. > Please check that you have write permission for this file." > > This is a desktop and there is really no issues o permissions > What is wrong here > > regards > Sanjay > > > > ----- > --- > Regards, Sanjay > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Jan. 13, 2018

Pharo 7 image cannot write changes message on starup

by Sanjay Minni

Hi I get the following message when I try to startup the latest Pharo 7 image (32 bit VM in Windows). "Information Pharo cannot write to the changes file named C:\...\Pharo7.0-32bit-eb0a6fb.changes. Please check that you have write permission for this file." This is a desktop and there is really no issues o permissions What is wrong here regards Sanjay ----- --- Regards, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 13, 2018

Re: [Pharo-users] Any perspective of Woden in Pharo 6.1/7 ?????

by Alexandre Bergel

Excellent! Let us know how it goes. We will be happy to help Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jan 12, 2018, at 1:47 PM, casimiro barreto <casimiro.barreto(a)gmail.com> wrote: > > Will try. Currently on 2 projects involving pharo. The most pressing one is a system for the calculation of uncertainties in measures. This system is part of a homologation system for smart card readers and smart card chips. The other is a simulation system thatÂ´s under non disclosure clause. Woden would be used in a third incoming project (simulations in crowd management in airports). > > Best regards, > > Casimiro > > 2018-01-10 19:43 GMT-02:00 Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>>: > Hi Casimiro! > > Sorry for the late reply. > We do have a working version of Woden for Pharo 7. > It would be great if you could try. > https://github.com/ronsaldo/woden2 <https://github.com/ronsaldo/woden2> > > On OSX, I did: > -=-=-=-=-=-=-=-=-= > git clone https://github.com/ronsaldo/woden2.git <https://github.com/ronsaldo/woden2.git> > cd woden2 > ./loadWoden2.sh > -=-=-=-=-=-=-=-=-= > > It takes time to install & compile (~ 10 minutes?), but it works well > > Alexandre > > > > On Jan 2, 2018, at 5:21 AM, Casimiro - GMAIL <casimiro.barreto(a)gmail.com <mailto:casimiro.barreto@gmail.com>> wrote: > > > > Is there any perspective of Woden working in Pharo 6.1 or later versions (7)???? > > > > Best regards, > > > > > > Casimiro > > -- > > The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions. > > > > == > > > > This email may be signed using PGP key ID: 0x4134A417 > > > > > -- > The information contained in this message is confidential and > intended to the recipients specified in the headers. If you received > this message by error, notify the sender immediately. The > unauthorized use, disclosure, copy or alteration of this message > are strictly forbidden and subjected to civil and criminal sanctions.

Jan. 12, 2018

Re: [Pharo-users] Any perspective of Woden in Pharo 6.1/7 ?????

by Ronie Salgado

> > Do you have a travis or jenkins for woden in Pharo 7? This is on my big todo list. In fact I need the travis to be able to support Windows. During the last months I have been rewriting the core of Woden 2 in order to improve stability and reduce dependencies. By using Lowtalk for the math library, I removed the requirement on Lowcode. During the weekend I am gonna spend some time on implementing the scripts for Travis. Best regards, Ronie 2018-01-12 13:47 GMT-03:00 casimiro barreto <casimiro.barreto(a)gmail.com>: > Will try. Currently on 2 projects involving pharo. The most pressing one > is a system for the calculation of uncertainties in measures. This system > is part of a homologation system for smart card readers and smart card > chips. The other is a simulation system thatÂ´s under non disclosure clause. > Woden would be used in a third incoming project (simulations in crowd > management in airports). > > Best regards, > > Casimiro > > 2018-01-10 19:43 GMT-02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > >> Hi Casimiro! >> >> Sorry for the late reply. >> We do have a working version of Woden for Pharo 7. >> It would be great if you could try. >> https://github.com/ronsaldo/woden2 >> >> On OSX, I did: >> -=-=-=-=-=-=-=-=-= >> git clone https://github.com/ronsaldo/woden2.git >> cd woden2 >> ./loadWoden2.sh >> -=-=-=-=-=-=-=-=-= >> >> It takes time to install & compile (~ 10 minutes?), but it works well >> >> Alexandre >> >> >> > On Jan 2, 2018, at 5:21 AM, Casimiro - GMAIL < >> casimiro.barreto(a)gmail.com> wrote: >> > >> > Is there any perspective of Woden working in Pharo 6.1 or later >> versions (7)???? >> > >> > Best regards, >> > >> > >> > Casimiro >> > -- >> > The information contained in this message is confidential and intended >> to the recipients specified in the headers. If you received this message by >> error, notify the sender immediately. The unauthorized use, disclosure, >> copy or alteration of this message are strictly forbidden and subjected to >> civil and criminal sanctions. >> > >> > == >> > >> > This email may be signed using PGP key ID: 0x4134A417 >> >> > > > -- > The information contained in this message is confidential and > intended to the recipients specified in the headers. If you received > this message by error, notify the sender immediately. The > unauthorized use, disclosure, copy or alteration of this message > are strictly forbidden and subjected to civil and criminal sanctions. >

Jan. 12, 2018

Re: [Pharo-users] Any perspective of Woden in Pharo 6.1/7 ?????

by casimiro barreto

Will try. Currently on 2 projects involving pharo. The most pressing one is a system for the calculation of uncertainties in measures. This system is part of a homologation system for smart card readers and smart card chips. The other is a simulation system thatÂ´s under non disclosure clause. Woden would be used in a third incoming project (simulations in crowd management in airports). Best regards, Casimiro 2018-01-10 19:43 GMT-02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi Casimiro! > > Sorry for the late reply. > We do have a working version of Woden for Pharo 7. > It would be great if you could try. > https://github.com/ronsaldo/woden2 > > On OSX, I did: > -=-=-=-=-=-=-=-=-= > git clone https://github.com/ronsaldo/woden2.git > cd woden2 > ./loadWoden2.sh > -=-=-=-=-=-=-=-=-= > > It takes time to install & compile (~ 10 minutes?), but it works well > > Alexandre > > > > On Jan 2, 2018, at 5:21 AM, Casimiro - GMAIL <casimiro.barreto(a)gmail.com> > wrote: > > > > Is there any perspective of Woden working in Pharo 6.1 or later versions > (7)???? > > > > Best regards, > > > > > > Casimiro > > -- > > The information contained in this message is confidential and intended > to the recipients specified in the headers. If you received this message by > error, notify the sender immediately. The unauthorized use, disclosure, > copy or alteration of this message are strictly forbidden and subjected to > civil and criminal sanctions. > > > > == > > > > This email may be signed using PGP key ID: 0x4134A417 > > -- The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions.

Jan. 12, 2018

Re: [Pharo-users] OT: Re: Open Debugger, Save and Quit

by Ben Coman

On 12 January 2018 at 22:15, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Wed, Nov 8, 2017 at 1:45 AM, Joachim Tuchel <jtuchel(a)objektfabrik.de> > wrote: > >> Ben, >> >> (this is a bit off-topic) >> > Sorry I didn't reply earlier. For some reason you email from 8 Nov didn't show up in my inbox until the same time just now that Mariano's did. > >> do you happen to know the purpose of that pre-debug-window? I must say >> that I find it annoying every time I get it in Pharo or VA? Why doesn't the >> debugger show up immediately? >> > I don't know, but could speculate that it performs the function of an error message - with some additional context seeing the top of the call stack. cheers -ben I disabled that in all my images (via a startup setting). See #*alwaysOpenFullDebugger > *below: > > "Define some settings/preferences for GTDebugger" > (Smalltalk at: #GTGenericStackDebugger) perform: # > enableDebuggerWindowDistinctColor: with: true. > (Smalltalk at: #GTGenericStackDebugger) perform: #enableStackColoring: > with: true. > *(Smalltalk at: #GTGenericStackDebugger) perform: #alwaysOpenFullDebugger: > with: true.* > > > Cheers, > > > > > But your suggestion is a good one, imo. In the startup phase of an image, >> the image might not be ready to provide any means of reacting to a problem, >> so why bother showing errors that early? >> >> What you describe should be quite easy to achieve with a handler that >> records and resumes errors during startup. >> >> Joachim >> >> Am 08.11.2017 03:54 schrieb Ben Coman <btc(a)openinworld.com>: >> > >> > >> > >> > On Wed, Nov 8, 2017 at 10:16 AM, Sean P. DeNigris < >> sean(a)clipperadams.com> wrote: >> >> >> >> In a headless image, I'd like to do the following: if there's any >> error, >> >> arrange to have a debugger open on the next (headful) launch, and then >> save >> >> and quit. >> >> >> >> I'm drawing a blank - how would I do that? >> >> >> >> I explored various dead ends, the culmination of which was the >> >> image-breaking: >> >> actualWorkBlock on: Error do: [ [ Smalltalk snapshot: true andQuit: >> true ] >> >> fork. Halt now ] >> >> >> >> Thanks! >> > >> > >> > Sorry not a solution, but you sparked a side-thought... To avoid >> sometimes being swamped by Pre-Debug windows. Instead of an error bringing >> up an individual Pre-Debug window, we could have error go into a queue >> which a singleton Pre-Debug window could have a view into. This "Error >> Queue Viewer" would have on row per error, and you click on a row to open >> a normal debugger, much like you click <Debug> button in the existing >> Pre-Debug window. In a headless image, the Error Queue Viewer would not >> appear, but the error would keep being queued until the next time the Error >> Queue Viewer is manually opened. The same error-queue might provide a >> similar interface point for Pharo Remote Tools, so you can see errors that >> occurred while you were not connected. >> > >> > cheers -ben > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Jan. 12, 2018

Re: [Pharo-users] Any perspective of Woden in Pharo 6.1/7 ?????

by Stephane Ducasse

Do you have a travis or jenkins for woden in Pharo 7? Stef On Wed, Jan 10, 2018 at 10:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Casimiro! > > Sorry for the late reply. > We do have a working version of Woden for Pharo 7. > It would be great if you could try. > https://github.com/ronsaldo/woden2 > > On OSX, I did: > -=-=-=-=-=-=-=-=-= > git clone https://github.com/ronsaldo/woden2.git > cd woden2 > ./loadWoden2.sh > -=-=-=-=-=-=-=-=-= > > It takes time to install & compile (~ 10 minutes?), but it works well > > Alexandre > > >> On Jan 2, 2018, at 5:21 AM, Casimiro - GMAIL <casimiro.barreto(a)gmail.com> wrote: >> >> Is there any perspective of Woden working in Pharo 6.1 or later versions (7)???? >> >> Best regards, >> >> >> Casimiro >> -- >> The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions. >> >> == >> >> This email may be signed using PGP key ID: 0x4134A417 > >

Jan. 12, 2018