[PHP-DEV] Re: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
On Friday 11 May 2001 23:26, Richard Lynch wrote: If you ignore it, you'll continue the problem: People attempt to install PHP with PWS on Win95/98 and get frustrated, and have to dig all over creation to find install instructions that should have been in the PHP release. What I'm suggesting that we ignore is the fact that PWS4 on NTWS might for legacy reasons look at the registry - although I have no evidence that it does other than the old PHP installation instructions. The new installation instructions I've submitted to the phpdoc team give instructions on fiddling with the registry for W9x/ME users, and updating the IIS metabase for IIS4+/PWS4+ users on NT server, NTWS and W2K. In other words, I believe that the new instructions are both consistent and correct :) Cheers -- Phil Driscoll -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
I think PWS on 95/98 looks in the registry... Agreed - PWS on these platforms is fundamentally a cut down version of IIS3. I suspect it is possible to have this on NTWS as well, but PWS4 which comes with the NT option pack (same CD as IIS4) certainly looks in the Metabase - though I don't know whether it also checks the registry. In any event, even if it does, it will only be for legacy reasons, so I think we can ignore it. If you ignore it, you'll continue the problem: People attempt to install PHP with PWS on Win95/98 and get frustrated, and have to dig all over creation to find install instructions that should have been in the PHP release. -- WARNING [EMAIL PROTECTED] address is an endangered species -- Use [EMAIL PROTECTED] Wanna help me out? Like Music? Buy a CD: http://l-i-e.com/artists.htm Volunteer a little time: http://chatmusic.com/volunteer.htm -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
then please merge the install.txt in there, as it's currently somewhat incomplete I will attempt to do that this afternoon. Cheers -- Phil Driscoll Dial Solutions +44 (0)113 294 5112 http://www.dialsolutions.com http://www.dtonline.org -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
I don't think so, it looks ok. But I must admit that I prefer plaintext readme's... But that's just me. At 13:40 10.5. 2001, Liz wrote the following: -- I noticed no comments at all about the HTML version of the readme I offered.. Does it suck that bad? -- PHP Quality Assurance Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] --end of quote-- [EMAIL PROTECTED] - And the eyes of them both were opened and they saw that their files were world readable and writable, so they chmoded 600 their files. - Book of Installation chapt 3 sec 7 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
Does it suck that bad? No - it doesn't suck at all! It's just that James's suggestion that we update the installation chapter of the manual and generate the installation noted from that is so eminently sensible, that it would be foolish to do otherwise - which sadly means that the efforts both you and I did earlier will be consigned forever to languish in the 'deleted items' folder :) Cheers -- Phil Driscoll Dial Solutions +44 (0)113 294 5112 http://www.dialsolutions.com http://www.dtonline.org -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
I don't think so, it looks ok. But I must admit that I prefer plaintext readme's... But that's just me. Depends, for a unix system, I'd agree, I dont want a HTML one, but for windows, its nice to have one you can easily skip to bits. So, in this case, Id say it was worth it. As every windows machine has file association and a browser to view it with. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
It's just that James's suggestion that we update the installation chapter of the manual and generate the installation noted from that is so eminently sensible, that it would be foolish to do otherwise - which sadly means that the efforts both you and I did earlier will be consigned forever to languish in the 'deleted items' folder :) damn. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
On the subject of updating the manual though.. the IMAP, POP and NNTP functions section.. it only contains imap functions. Im sure this is confusing to people. It's just that James's suggestion that we update the installation chapter of the manual and generate the installation noted from that is so eminently sensible, that it would be foolish to do otherwise - which sadly means that the efforts both you and I did earlier will be consigned forever to languish in the 'deleted items' folder :) -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
Quoting Liz [EMAIL PROTECTED]: the IMAP, POP and NNTP functions section.. it only contains imap functions. Im sure this is confusing to people. It's the names of the functions that are wrong, not the name of the section. Read the documentation for imap_open() - it'll talk to pop3 and nntp servers just fine, and almost all of the functions work with all three. -chuck -- Charles Hagenbuch, [EMAIL PROTECTED] When you can't even start, it's time to stop - Jason -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
Liz wrote: On the subject of updating the manual though.. the IMAP, POP and NNTP functions section.. it only contains imap functions. Im sure this is confusing to people. maybe i should move the 2nd paragraph on http://php.net/imap up? Note that these functions are not limited to the IMAP protocol, despite their name. The underlying c-client library also supports NNTP, POP3 and local mailbox access methods. or should we rename theese functions from imap_* to mailclient_* and keep the imap_* style as aliases for compatibility? -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
On Thu, May 10, 2001 at 04:22:35PM +0200, Hartmut Holzgraefe wrote: Liz wrote: or... imap_* pop3_* nntp_* just for good measure? as it certainly reads better to see pop3_open(..) polluting the function namespace by even more aliases? no way Right, that would be overkill. A 'mail_' prefix (or a 'cclient_' prefix would be more appropriate, but I don't really seen the need to add function aliases, especially when the IMAP module has been around for so long. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
I'm in the middle of sorting out the windows installation instructions for the manual and the readme file for the windows distribution. What I thought would be a quick job, as usual, is much more complicated than I thought. The readme.txt, install.txt and the manual all contradict each other, and all are wrong in various places :( Anyway, I'm well on with the job, but I have an issue with the instructions on installing PHP with PWS on NT Workstation. All the instructions everywhere talk about editing the registry, but as far as I am aware, PWS on NTWS is not in the least bit interested in the registry - it uses the IIS metabase just the same as IIS 4 and above. The windows installer certainly edits the metabase rather than the registry when doing an install of PWS on NTWS, and that works fine. As far as I'm concerned, the instructions for installing PHP on PWS/NTWS should be the same as for installing with IIS/NT Server. Does anyone know something I don't on this issue, or is it ok for me to go ahead and change the instructions accordingly? Cheers -- Phil Driscoll Dial Solutions +44 (0)113 294 5112 http://www.dialsolutions.com http://www.dtonline.org -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
Anyway, I'm well on with the job, but I have an issue with the instructions on installing PHP with PWS on NT Workstation. All the instructions everywhere talk about editing the registry, but as far as I am aware, PWS on NTWS is not in the least bit interested in the registry - it uses the IIS metabase just the same as IIS 4 and above. The windows installer certainly edits the metabase rather than the registry when doing an install of PWS on NTWS, and that works fine. As far as I'm concerned, the instructions for installing PHP on PWS/NTWS should be the same as for installing with IIS/NT Server. As I was aware the PWS on NT4 did use registry stuff, as the management console sucks. But, its been a long time since I looked at one. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
To the best of my knowledge, it used to when it was based on IIS3 (and was essentially the same thing currently shipped as PWS for 9x/ME) but the current PWS for NTWS is essentially IIS4. Could only be an improvement. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] RE: [PHP-QA] Modifications to Windows Readme file
In the bit where you say assign php4isapi.dll to the .php extension woudlnt it be beneficial to say for the CGI version use php.exe etc.. and for the ISAPI version use the DLL? I know from my own experience that the DLL has caused me problems, but the exe is very reliable.. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
PHP 4.0 for Windows comes in two flavours - a CGI executable (php.exe), and an ISAPI module (php4isapi.dll). what about php4apache.dll? shouldn't that be mentioned too? BTW, that reminds me: ASF guys have changed the names of the win32 Apache modules to match the unix names; apachefoo.dll became mod_foo.so. shouldn't PHP follow this pattern? The latter is new to PHP 4.0, maybe somewhat new? it's been around for quite some time. the PHP ISAPI module uses the thread-safe version of the PHP code, which is completely new to PHP 4.0 well, win32 Apache is also threaded, and win32 mod_php.so is thus thread-safe, sans the horror IIS users experience. (no pun intended, I'm just glad I'm on the other side of the fence :) so, I wouldn't say it's completely new... Hmm, after reading the whole file I realized it doesn't mention installation for win32 Apache. Is this information someplace else? At 14:50 9.5. 2001, Phil Driscoll wrote the following: -- The attached file is a modified version of the README.txt file for the Windows distribution. Changes I've made are as follows: I've changed the wording of the opening paragraph about the ISAPI module to make it clear that users really are likely to have a bad time with the ISAPI module stability. I've added a section at the end on how to fix common problems which should save a good bit of list traffic. If anyone has any comments, changes or suggestions please let me know, or if people are happy with the changes, would someone be kind enough to commit the file to CVS - I'm in the middle of setting up my new computer and don't yet have a working CVS client up and running. Cheers -- Phil Driscoll Dial Solutions +44 (0)113 294 5112 http://www.dialsolutions.com http://www.dtonline.org -- PHP Quality Assurance Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] --end of quote-- [EMAIL PROTECTED] - And the eyes of them both were opened and they saw that their files were world readable and writable, so they chmoded 600 their files. - Book of Installation chapt 3 sec 7 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
There is a separate file called install.txt which covers installation on a wider range of servers. Ideally there would be one document - I was just soaking up a spare 10 minutes to improve things a bit! Cheers -- Phil Driscoll Dial Solutions +44 (0)113 294 5112 http://www.dialsolutions.com http://www.dtonline.org -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
In the bit where you say assign php4isapi.dll to the .php extension woudlnt it be beneficial to say for the CGI version use php.exe etc.. and for the ISAPI version use the DLL? Yes it should. I did do this a while ago, and I thought that that was in this file, but it is in fact in the install.txt file. That'll teach me to read things more carefully! Damn! Perhaps I should combine both files into just the one - but I'm out of time for today. Cheers -- Phil Driscoll Dial Solutions +44 (0)113 294 5112 http://www.dialsolutions.com http://www.dtonline.org -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
the readme shold be nuked as it's pretty out of date. info's not covered by install.txt should be moved there, IMO. One thing I noted when setting my windows stuff up was that there were various details in different places, makes it a little more confusing. A simple HTML file including with jump points, so people can go to the type they want.If people see an install.txt and dont see instructions they'll label it as crap. People do often read a readme, but if again they see some install instructions but not the ones they want, it will be labeled as crap -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Re: [PHP-QA] Modifications to Windows Readme file
At 18:58 09.05.2001 +0100, James Moore wrote: Well keep the manual up to date and we can generate install.txt from this very simply.. make lynx -dump html/install.windows.html install.txt in the manual dir. I think this is probably the best way to do it. then please merge the install.txt in there, as it's currently somewhat incomplete. daniel /*-- daniel beulshausen - [EMAIL PROTECTED] using php on windows? http://www.php4win.de -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
