I'm also playing with the Microchip TCP/IP stack. I've got it working on my hardware. Integrating it with my application is the next challenge. A couple things I've noticed so far: 1. I'm using a PIC24HJ256GP610 with the SPI ENC chip. It appears the TCP/IP stack initializes the SPI port for the ENC, then never touches the SPI control registers again. Since I'm using SPI to talk with other devices that require different SPI configuration, my code is trashing their initialization. I think I have three options. Those are: use a separate SPI port for the ENC; modify their code to initialize the SPI before each use; modify my code to save and restore SPI configuration before and after use. 2. Organization of a project using the TCP/IP stack can be interesting. I'm trying to leave the generic TCP/IP code in the Microchip Solutions directory while putting my project (and its specific hardware and software configuration) in its own directory. I started by copying their demo ap over to my project directory. I had to change a bunch of search paths since they were using relative paths from the demo directory. 3. I've ended up using a copy of their maindemo.c (in my project directory) as the main program. I've made a subdirectory with my project specific TCP/IP stuff and another subdirectory with my project application. Their main.c then calls their initialization, my initialization, then loops the stack tasks and my tasks. 4. I've used the Generic TCP Client as a model for an HTTP client. It works, but when I add additional headers (a byte range header), the GET request is never sent. I suspect I'm overflowing a buffer somewhere. Finding out what's wrong is today's project. Documentation on this appears skimpy and out of date. I'd really like to see something like the documentation for PHP at http://www.php.net . Their user comments on each function are excellent. Harold -- FCC Rules Updated Daily at http://www.hallikainen.com - Advertising opportunities available! -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist