Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73928 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40213 invoked from network); 6 May 2014 02:28:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 May 2014 02:28:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=xwisdom@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=xwisdom@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.54 as permitted sender) X-PHP-List-Original-Sender: xwisdom@gmail.com X-Host-Fingerprint: 209.85.213.54 mail-yh0-f54.google.com Received: from [209.85.213.54] ([209.85.213.54:63118] helo=mail-yh0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 79/68-44049-FD848635 for ; Mon, 05 May 2014 22:28:48 -0400 Received: by mail-yh0-f54.google.com with SMTP id i57so158322yha.27 for ; Mon, 05 May 2014 19:28:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=66hpYj2wcwsnYr8ZEdEfPM+DYFnUMIuQ4mUtuIQs3+0=; b=v+2PA+yyQ5xDXqxghlkea6wzwhPLCDZQQcV4I7aAa+WHP+q16WIK2mm+oLhCkHWO0+ kor7Wq7Tq6F9MrZhTU+8o7Tt+eaZCTwNqvyAOA9/fSkFsjfBmbyNhKO8d3koHqs5vvxK nCLn0z5tlmUayg1GA3WQDGoWt/LZlO+ez/KebM+P5VB6t+aPrO1svYNbnwao+5x8NYft uYPJyD7hN9e7xNxm3rGmvjqUA/cTWsStYNSCzLq4r0psD9OXg+JNAO3TOeS9AuD/J10r 3kD0Sajsq//JfYx4Iffi4lMtKjzKxDi/B9t+yRcm+OuLl0CDyVlZ5TyREXeF2cpErI3b wgig== MIME-Version: 1.0 X-Received: by 10.236.81.6 with SMTP id l6mr53673915yhe.29.1399343324705; Mon, 05 May 2014 19:28:44 -0700 (PDT) Received: by 10.170.211.6 with HTTP; Mon, 5 May 2014 19:28:44 -0700 (PDT) In-Reply-To: <53557F80.8000503@lsces.co.uk> References: <53545EA8.2020703@sugarcrm.com> <5354F257.3030508@lsces.co.uk> <53557F80.8000503@lsces.co.uk> Date: Mon, 5 May 2014 21:28:44 -0500 Message-ID: To: Lester Caine Cc: PHP internals Content-Type: multipart/alternative; boundary=20cf3011dcc5c9bb0c04f8b20123 Subject: Re: [PHP-DEV] PHP on 64-bit windows From: xwisdom@gmail.com (Raymond Irving) --20cf3011dcc5c9bb0c04f8b20123 Content-Type: text/plain; charset=UTF-8 Hi Lester, How about using a separate machine with linux/php to access your legacy hardware? You could then create a php web service and expose methods to read/write to the hardware. This will allow you to run php on window 64-bit and communicate with your linux box via web services. Best regards, __ Raymond On Mon, Apr 21, 2014 at 3:28 PM, Lester Caine wrote: > Pierre Joye wrote: > >> hi, >> >> On Mon, Apr 21, 2014 at 12:26 PM, Lester Caine >> wrote: >> >>> Pierre Joye wrote: >>> >>>> >>>> php 6 will actually have real 64bit support, hopefully, the int64 >>>> branch has all necessary changes and I seriously hope that the RFC >>>> will be accepted. >>>> >>> >>> Pierre ... I'm still fighting 32/64 bit problems with windows on legacy >>> systems. 64 bit windows does not allow access to the parallel port which >>> we >>> use for controlling additional hardware. >>> >> >> I have no parallel port at hand to do tests but it should work like >> any devices. Please report a bug, add a stack trace (process monitor >> output) to see what happens. >> > > This is not a general PHP problem, but relates to use of the parallel port > in other hardware drivers. NTPort lib still only supports 32bit > applications, and 'fastmode' access is specifically blocked by 64 bit > windows! A number of drivers that my legacy hardware systems use are > unusable on 64 bit windows and those projects are now advising staying with > 32bit windows as they have been unsuccessful in producing a 64bit driver > due to the blocks applied in kernel access. > > > While not directly a problem for >>> simple code, is the way 64 bit builds of windows handle memory access a >>> problem for PHP builds? Having moved the servers over to Linux for PHP >>> and >>> database support, the remaining elements are STILL locked to 32bit >>> windows >>> simply because of legacy hardware, but I'm trying to work out the best >>> way >>> forward as we are still tied to XP on a number of systems ... with PHP >>> access for control ... so things are getting very messy :( >>> >> >> If you use XP it means you use 5.4, we do not provide any 64bit >> support for windows with 5.4, only 5.5+, experimental. >> > > My point is that moving things to 64 bit builds of windows, which are the > norm for windows 8.1 - or at least I have not yet found a pre-installed 32 > bit windows 8.1 - is now highlighting problems that are not easy to get > around. Simply running 32bit builds of applications does not mean they will > actually work on 64it windows! One needs to have 32 bit windows for some > kit for which there is no later drivers. XP may be end of life, but there > is currently no alternative that I've managed to get working on even W7 and > now testing on W8.1 is throwing up new failures. Having now picked up a > 32bit build of W8.1 I'm hoping to make some progress, but this is all very > messy and time consuming! > > > -- > Lester Caine - G8HFL > ----------------------------- > Contact - http://lsces.co.uk/wiki/?page=contact > L.S.Caine Electronic Services - http://lsces.co.uk > EnquirySolve - http://enquirysolve.com/ > Model Engineers Digital Workshop - http://medw.co.uk > Rainbow Digital Media - http://rainbowdigitalmedia.co.uk > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --20cf3011dcc5c9bb0c04f8b20123--