RE: [PECL-DEV] MailParse Installation on Windows or Binary>

Wez, Guys, Ok I have got all the test scripts working, however I am having some issues though extracting the code for an attachment. It lists as such, now I would have thought these were encased in an array but they don't seem to be. It just stores all this info in a "section" I would like this in an array so I can just get the code for the image. --Boundary_(ID_xTy/xjoRrp4aP65Bfjs7gA) Content-type: image/gif Content-transfer-encoding: base64 Content-disposition: inline Content-Location: True.jpg R0lGODlhgABgAHAAACwAAAAAgABgAIcAAABEAAB3mXcAAP93maoAZv8zM/8zRBFEM1UAM///zAAA AETMmaqqVVVVIhEARFVEVSK7maozAAAARET/zDMzRETMzCIzVUTMVVVERCJVRGb//zNEREQAAGYA Is this the right place to ask for help on this firstly, if not then can someone kindly give me an appropriate forum, I usually use devshed. Regards Ian -----Original Message----- From: Wez Furlong [mailto:wez@thebrainroom.com] Sent: 20 May 2004 16:59 To: iwarner@triangle-solutions.com; pecl-dev@lists.php.net Subject: RE: [PECL-DEV] MailParse Installation on Windows or Binary> > But doesn't pear take the install and compile the C source > code to create > the package. Win32 build doesn't support building packages as standalone extensions. > It seems to do this ok for the inbuilt packages when you hit > go-pear I have > also upgraded these successfully as a test? Is that a statement or a question? > Ok I tried to install mailparse as an extension and it errors > - do I need > other DLLS to go into the System32 folder to make this work - this is > usually the case when I get a load exception error It depends on the mbstring extension.