[MS4W-Users] ms4w windows 10
Jeff McKenna
jmckenna at gatewaygeomatics.com
Wed May 4 08:29:53 EDT 2016
Hi,
For the record, I run Windows 10 and MS4W all day here, plus its
development occurs on Windows 10 as well; so there is a connection
between Windows 10 and MS4W.
Please do try installing MS4W on another Windows 10 machine, preferably
without any other FOSS software at first.
Again please contact me directly if you need professional assistance, or
if you can help fund development in the software that your organization
so depends on, MS4W, so it can keep helping all organizations around the
world share their information.
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/
On 2016-05-04 9:21 AM, Björn Danielsson via MS4W-Users wrote:
> Hi
> and thanks that you bother!
>
> However, I tend to have a different opinion about the problem than you.
> Ok, I have both postgis and qgis installed, but I have had that for a
> long time together with Apache without problems. The problem occurred
> when Windows 10 took over my developing machine.
> Before that I ran ms4w version 3.1.3 for two weeks under Windows 7
> without encounter any problem.
>
> I immediately ran Dependency Walker ( is noone updating that program any
> longer? ) after the first locking, without seeing anything suspicious.
>
> On your advice in your first mail I renamed libeay.dll and ssleay.dll in
> postgis and qgis without any positive result. Like I had expected,
> because those dlls have with SSL to do and Microsoft is hardly
> interested in SSL, and those dlls are not present in my machines under
> Windows 7 that do not contain ms4w, postgis or qgis.
>
> As the only thing that happened was migrating from Windows 7 to Windows
> 10 I strongly suspect that the problem is connected to Windows 10. Of
> course not Windows 10 per se, but something concerning Apache, php and
> Windows 10.
>
> I have not got time to delve further in this, and the problem is
> 'solved' by having moved the entire developing environment to a Windows
> 7 machine.
>
> Perhaps in the future some newer releases automatically solve the problem.
>
> Björn D
>
> -----Original Message-----
> From: Jeff McKenna via MS4W-Users <ms4w-users at lists.ms4w.com>
> To: ms4w-users at lists.ms4w.com
> Cc: Jeff McKenna <jmckenna at gatewaygeomatics.com>
> Date: Tue, 3 May 2016 17:14:50 -0300
> Subject: Re: [MS4W-Users] ms4w windows 10
>
> As my original message stated, my guess is that a shared dll on that
> machine, such as PostgreSQL, is conflicting. This will definitely
> affect Apache, especially if it is the dlls that I mentioned in my last
> message.
>
> Next you can try to install MS4W on a fresh Windows 10 machine (without
> PostgreSQL, QGIS); I bet you have no issues.
>
> Likely this has nothing to do with the Windows version, but instead it
> is software conflicting on it. I would try renaming the shared dlls
> (mentioned in my last message) installed in the other software folders,
> then retry Apache etc.
>
> I did mention one of the tools I use to debug this on client machines.
>
> If you are stuck I am also available for professional support.
>
> Sorry to hear about your situation.
>
> -jeff
>
>
>
> --
> Jeff McKenna
> MapServer Consulting and Training Services
> http://www.gatewaygeomatics.com/
>
>
>
> On 2016-05-03 3:56 AM, Björn Danielsson via MS4W-Users wrote:
> > Hi,
> >
> > I have not found out why this error occurs despite having dealt
> with it
> > a lot.
> >
> > The application is php intensive at startup, many phps are starting
> > concurrently although none of them is time intensive. The phps are
> > accessing a database, either Oracle or postgreSQL.
> > The timeouts decrease in number when the php scripts are called
> > synchronously.
> >
> > I found out early that the problem is not bound solely to php but in
> > some way involves both php and Apache.
> > After noticing that timeout almost always occurs the first time after
> > opening the browser ( type of browser does not matter ) I clocked the
> > time in both the first php script and in the calling javascript.
> >
> > Javascript:
> >
> > kaC2.prototype.GetOrgid = function () {
> > "use strict";
> > var szURL, myRand, d;
> > szURL = myC2.phpDIR + "phpC2LM/C3GetOrgid.php?user=" +
> myC2.username +
> > "&sessid=" + myC2.sessid + "&appl=C3L";
> > myRand = parseInt(Math.random() * 999999999999, 10);
> > szURL += "&rand=" + myRand;
> > d = new Date();
> > myC2.time = d.getTime();
> > call(szURL, "", myC2.GetOrgidCallback);
> > };
> >
> > kaC2.prototype.GetOrgidCallback = function (dbres) {
> > "use strict";
> > var aa, o, j, i, bb, d;
> > d = new Date();
> > alert(d.getTime() - myC2.time);
> >
> > The time in milliseconds between the start of the php script until the
> > call returned to javascript was in one case 65270.
> > The time spent in the php script, however, was just 32 milliseconds.
> > What went on in the meantime is anybody's guess.
> >
> > When everything goes ok with this call the time between start and
> return
> > is around 190 milliseconds.
> >
> > The 'call' function in the javascript above uses the GET method by an
> > ordinary XMLHttpRequest.
> >
> > Everything works fine in Windows 7. This started with Windows 10.
> >
> > Björn D
> >
> >
> > -----Original Message-----
> > From: Jeff McKenna via MS4W-Users <ms4w-users at lists.ms4w.com
> <mailto:ms4w-users%40lists.ms4w.com> >
> > To: ms4w-users at lists.ms4w.com <mailto:ms4w-users%40lists.ms4w.com>
> > Cc: Jeff McKenna <jmckenna at gatewaygeomatics.com
> <mailto:jmckenna%40gatewaygeomatics.com>>
> > Date: Mon, 11 Apr 2016 13:07:27 -0300
> > Subject: Re: [MS4W-Users] ms4w windows 10
> >
> > Hi Björn,
> >
> > You will happy to know that all MS4W development now occurs on
> Windows
> > 10. A few months ago I purchased a server dedicated just for MS4W
> > builds, running Windows 10.
> >
> > I have not encountered your problem with Windows 10. But, I
> have seen
> > your exact problem before on client's machines - most likely
> you are in
> > "dll hell", where a different version of a dll found in your
> path is
> > mistakenly used by MS4W (Apache, MapServer or in your case likely
> > php-cgi.exe). I bet your test machine runs something like QGIS or
> > PostGIS/PostgreSQL, and one of those other softwares has a dll
> that is
> > older than the dll that is supposed to be used by MS4W.
> >
> > You can use a tool like Dependency Walker to find which dll's
> are being
> > used, for your php-cgi.exe file. If I had to guess, it would be a
> > common dll like "libeay32.dll" or "ssleay32.dll" that is causing a
> > problem.
> >
> > Since we are speaking of PHP, and I know how important PHP and
> MS4W is
> > to your organization (and all of the organizations that are on
> this
> > mailing list): I have begun the detailed process of
> preparations for PHP
> > 7 with MS4W. In fact PHP 7 requires a recent compiler, in
> fact the most
> > recent compiler, so that means I have begun compiling all
> (over 160)
> > libraries for the new compiler. It will be a month-long
> effort. (the
> > last time I did this, switching to a new compiler, was in year
> 2009, and
> > it was the same big effort over a month, and that effort
> fueled hundreds
> > of thousands of free downloads and users for over the next 6
> years).
> >
> > So if your organization can help fund this work, as I know how
> important
> > MS4W is to so many out there, please contact me directly. The
> changes
> > that your organization help fund will be available for the whole
> > community, for years to come.
> >
> > Thank you for sharing your spatial information with MS4W.
> >
> > Talk soon,
> >
> > -jeff
> >
> >
> > --
> > Jeff McKenna
> > MapServer Consulting and Training Services
> > http://www.gatewaygeomatics.com/
> >
> >
> >
> > On 2016-04-11 12:32 PM, Björn Danielsson via MS4W-Users wrote:
> > > Hi,
> > > I have been running Windows 7 and after 8 billion times
> having closed
> > > the 'Update to windows 10'-window I obviously hit the wrong
> button, so
> > > after returning from lunch I was met by 'Welcome to Windows 10'.
> > > I now run Windows 10.
> > > Apache did not start but that was a known problem and easily
> solved by
> > > shutting down some World Wide Web exe that stole port 80
> from Apache.
> > > But, when running my web application as localhost ( luckily the
> > > production server runs under Server 2012 ) , based on ms4w,
> sometimes,
> > > say once out of four, php times out. And sometimes the horrific
> > 'End of
> > > script output before headers' occur.
> > > I have clocked the time out to circa 30 secs. Which surprises me
> > because
> > > I have set max_execution_time to 300 in php.ini.
> > > Do anyone know what's different in Windows 10 compared to
> Windows
> > 7? Is
> > > something running faster and causing trouble when running
> asynchronous
> > > php-scripts?
> > > I have begun to cut the application to pieces and adding one
> piece
> > at a
> > > time but I still have no clue.
> > > I don't like intermittent errors.
> > > Björn Danielsson
> > >
> >
> >
More information about the MS4W-Users
mailing list