Hello Rob, Tuesday, March 22, 2005, 4:14:55 PM, you wrote: R> That's interesting - it also started happening for me after R> installing PHP 5.0.3. But I have reverted to 4.3.10 for now, and I R> can't see how installing 5.0.3 into an entirely separate directory R> can break my old php install. Hmm.. R> Incidentally, are you using Pear at all? No, I'm not doing anything with Pear (just haven't gotten around to it). I did the same thing you did, installed into a separate directory and fixed all the references in the webserver, and have deleted any PHP 4.3 files from the Windows/System folder. Luckily it doesn't appear to be a big security problem as it only displays the access violation in the browser window (no paths or anything). A reboot fixes it until I do something like refreshing POST data a few times again. Until I get the problem resolved, I don't refresh POST data anymore on that server. The frustrating thing is that the "crash" doesn't show up in any logs. Even the Windows system logs. I also didn't do any major changes from the default php.ini except to enable some extensions I needed, set up the SMTP stuff, and that's really about it. I am running 5.0.3 on other servers (various web servers and MySQL versions, but all Windows), and am not experiencing this problem. The only difference with those servers is that 5.0.3 was installed fresh (no previous PHP). I'm wondering if I missed one of the extension files somewhere from 4.3. -- Leif (TB lists moderator and fellow end user). Using The Bat! 3.0.9.9 Return (pre-beta) under Windows XP 5.1 Build 2600 Service Pack 2 on a Pentium 4 2GHz with 512MB -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
