Re: [PHP4BETA] WIN32 problem
| From: | John-Marc | Date: | Mon, 29 Nov 1999 14:41:07 +0000 |
| Subject: | Re: [PHP4BETA] WIN32 problem | ||
| Groups: | php.version4 | ||
| Request: | Send a blank email to php-version4+get-7044@lists.php.net to get a copy of this message | ||
Teodor,
-----Original Message-----
From: Teodor Cimpoesu <teo@digiro.net>
Cc: php4beta@lists.php.net <php4beta@lists.php.net>
Date: Monday, November 29, 1999 5:05 AM
Subject: Re: [PHP4BETA] WIN32 problem
>> Point taken and already understood. Deadlines bring out the worst in us,
>> and when our servers decide to upgrade without our consent, we either
change
>> servers (messy) or jump in head first. Sorry if I am human and feel
pain.
>> I will keep it to myself.
>
>Hmm, I agree but try to see also the `good' part. Your provider knows
>4.0b
>is a very performant step forward and tries to keep it customers happy.
>I've just finish a project in 3.0.12 and at the and I was asked to port
>it to 3.0.5 cause the customer doesn't want to upgrade no matter what
>[...]
>
>Now, not asking for opinions from customers proves some lack of , you
>name it,
>but now what, you are trying to help your provider to get out of the
>mess?
>A quick solution would be to set-up a personal configuration on a
>personal
>server and ask you provider to accept your machine in until it gets 4.0b
>up
>and running or downgrades to 3.0.12/13
>
>
>--
>CIMPOESU Teodor, Web Programmer
>
Quick solution not so quick here in the woods where it takes months to get a
56K fram relay, let alone a T1!
Will have to tough it out and try to get 4.0 working on home system.
Getting close. One more glitch to go.
Well, it only cost me 3 full (not those wimpy 8 hour kind) days, thanks to
the help on this list.