"Switching to Treck TCP/IP stack was the best decision we have ever made in 1999. I am so happy we did that. All of our controllers' communication problems with the old stack disappeared all of a sudden. The transition from our old stack to Treck's was fairly easy and smooth. The Treck code appeared to me as a black box, the only thing I needed to do was follow the rules in the User's Guide, to modify our network device driver, and to supply whatever supporting functions the Treck stack was asking for, such as event flags, count semaphores, etc.. As to customer support, I am very happy with that. Whenever I find a problem, I report it to Treck and the solution comes back very quickly. Several months ago, we had a crisis in several customer fields with sleepy controllers that did not respond to any request at all except ICMP Ping messages. Since the Treck stack was new to us during that time and this was a communication problem, everybody suspected that the Treck stack might be the guilty one. However, after long hours of trouble shooting, it turned out that the Treck TCP/IP stack did not cause any problem at all. All of the troubles came from our other subsystems. During this emergency period, the Treck engineers gave us a lot of help to try to find out where the problems were. I really appreciate their efforts. I have so much confidence in Treck's quality work."

"Our products contain different microprocessor, RTOS, and communication chip combinations. This complexity required a simple and effective TCP/IP stack interface to minimize the cost of stack integration for different platforms. Our research proved well worth the time when we ported our first product to the Treck stack. We successfully transmitted and received packets from a PC to our embedded system within eight hours of receiving the Treck protocols. We also noticed the attention that the Treck engineers gave to real time embedded systems during our code review. Treck kept critical sections where interrupts must be disabled to a minimum. RTOS calls are utilized only when absolutely necessary minimizing the overhead associated with semaphores and events. Treck's support engineers have been extremely helpful in debugging problems that we have encountered. The most interesting problem we faced was related to a bug discovered in our PC OS vendorÍs protocol stack. The Treck engineers quickly reproduced our problem and provided a concise explanation of what went wrong. This expert assistance allowed us to continue our development and stay on schedule."

"When I started working on an embedded µP project that required the use of a TCP/IP protocol stack, I knew exactly nothing about TCP/IP, and had never worked with it before. After studying-up on TCP/IP, I was handed the Treck, Inc. TCP/IP stack and told to make it work on our new product. The process of integrating the Treck stack into my application code and operating system was very, very painless. The accompanying manual was straightforward, concise, and easy to understand. I actually had the stack operational within 2 days. Porting and integrating other code should be so easy. As usual with all embedded µP projects, various bugs, timing problems, unwanted functionality, etc, did begin to appear periodically, due to improper integration. I must say that my questions to the Treck Support Staff have always been answered very, very quickly, almost always within 1 hour. And when I did have an ongoing problem, they always seemed to be working on it, responding with ideas and solutions, until the problem was solved. It has been very refreshing to work with a Technical Support Group that actually helps you in real-time and virtual real-time, as opposed to having wait 1, 2, or more days to get help and responses. What else can an engineer ask for? I know that this superior support made my experience a much better one, and has gotten our new product to where we wanted it to be much faster than it would have with many other Support Groups. The Treck TCP/IP stack has been working flawlessly. It requires an amazingly small amount of code, is very fast, and has a splendid amount of functionality to choose from. If you need an embedded TCP/IP stack, and prefer 1st class technical support, I highly recommend Treck."

"After careful evaluation of TCP/IP stacks, our company selected the Treck TCP/IP stack and their FTP Server application. The design of TreckÍs TCP/IP stack and the quality and readability of the source code made the integration of TreckÍs TCP/IP stack very simple. We spent less than one week integrating TreckÍs stack into our build environment, kernel, and Ethernet drivers. Additionally, the interface provided by the stack to the kernel and Ethernet hardware is extremely simple and complete. TreckÍs FTP Server application exhibits the same standards of quality, ease of integration and configuration as the TCP/IP stack. Within a few hours of reading the supplied documentation, we were able to implement the server, and view our product using a web browser. Treck provides first class support for its product. The user manual is excellent; it provides a clear Ethernet and TCP/IP overview, complete and detailed porting instructions, examples, test code, and complete API descriptions. The technical support staff is knowledgeable and always responsive; they gave invaluable assistance while we were integrating their stack with another vendorÍs OSI stack. Treck truly offers an excellent product with the knowledge and support to back it up."

"We were quite concerned about switching stack vendors. After careful deliberation, we decided to take the plunge. It was the right decision. We have been very impressed with the ease of the port of the TRECK stack. The clarity of the code and the prompt, helpful tech support has made the porting task a pleasure. Once we started testing the stack, it was evident that our decision was correct. We could SEE the speed improvements when we loaded web pages from our embedded web server. We certainly did not expect this! It is amazing that they accomplished this with a smaller footprint. We look forward to working with TRECK in the future."

"RSJ Software GmbH has used the Treck TCP/IP stack in a point of sale electronic cash register project, where integration of TCP/IP over Token Ring, Ethernet, PPP for host connectivity was needed. Integrating of Treck's TCP/IP stack was simplified by the design, which allowed easy integration into the custom multitasking system used on the target system (which is similar to the OS/2 multitasking approach). Treck's documentation detailed all the steps needed. When we needed support from Treck (which has been only one time so far) we got it within a few hours. The answers were very competent. During final testing, we found out, that some of the host systems we were connecting to, could not support PPP without an expensive hardware upgrade. So we switched from PPP to SLIP for these connections. This change was very easy to do. We believe that the Treck IP stack is superb concerning ease of integration, support and quality. If a future project requires a similar form of IP support we would seriously consider Treck's stack again."

"I am happy to announce that I have the TCP/IP stack working. I have been able to send a "ping" message to the DPS-575 and have it report an "echo" message. This tests all the functionality of the Ethernet hardware/driver and the basics of the TCP/IP stack (including ARP support). I still have work to do in improving the performance of the Ethernet driver, and I have to write the TCP/IP interfaces (browser, FTP server) that can control the DPS-575. Plus there is also a good deal of testing that has to be done someday. It looks like we made a good choice with the Treck TCP/IP stack. I didn't need to call their support line (which means our 90-day support is not counting down) and their code looks like it is very well written. I didn't really keep track of my time, but I don't think I spent more than 3 days on this so far!"

"I was quite pleased at the relative ease and speed at which I was able to incorporate your protocol stack and sample Ethernet driver into our design. The documentation is clear and *useful*. I found the source code to be well organized, written and commented and the process of building the library to be clear and easily understood. In the area of customer support, I had the opportunity to speak with "Jason" for support. He was friendly, responsive and knowledgeable. We, at Telinc, would highly recommend Treck, Inc. to anyone endeavoring to add the TCP/IP protocol stack or other Internet application software to their embedded system."

"Monitor Business Machines Ltd, New Zealand, chose the Treck TCP/IP stack, after evaluating several competitors' products, for use in x86 based terminals. We have had no problems with the stack, only our device driver for the CS8900 Ethernet IC in 8 bit mode. We worked through the problems with much assistance from the support crew at Treck. Dealing directly with the stack code writers was an advantage and responses, given the time difference to New Zealand, was only a few hours. We would not hesitate to recommend the Treck TCP/IP stack to other companies seeking to add IP connectivity to their existing products."

"For connectivity with its current embedded development project, Cable Print preferred Treck TCP/IP to other offers mainly because of the following elements : the fact that all functionality is delivered in standard 'C' code, the fact that the full developer's manual was publicly available for evaluation, the fact that most of the stack settings can be made at runtime, and the commitment of the pre-sales technical support. During development, we were most charmed by the following element: the ease with which we were able to generate a PC based version for verification purposes."

"At Orbacom Systems, we have used TRECK to provide a TCP/IP functionality required in our system for communication connections. TRECK seems to have a well documented manual that guides the programmer through the various functions and integration steps. Use of the TRECK library along with our embedded code on MC68360_EN processor, has been straight forward. Customer support has been good during our initial usage period when we asked particular detailed questions. The in-factory class was particularly helpful in orientation to the IP/TCP concept and processes."

"It's always more complicated proposing a project where your support comes from across the world, but with email and the occasional phone call, things went very smoothly. In fact I have had far more problems from local suppliers. The real time kernel hadn't been used before, we were running a wireless application instead of a land line, yet the TCP/IP stack was ported to our environment inside four support calls. The manual clearly explained how to add the extra support for function calls that were not available in our kernel. I still wouldn't say I'm a TCP/IP expert but I do have a working solution."

"The small software group here had the task of connecting our new design of home glucose monitoring machines to the Internet. Having very little knowledge of TCP/IP and Internet connectivity, I was prepared for a long learning curve and many months of hard work. We evaluated a few packages and decided on TreckÍs embedded TCP/IP, PPP and FTP software because of the flexibility and complete source code being available if modifications were needed to tailor it to our 80186 embedded system. TreckÍs tech support was very knowledgeable and extremely helpful in working with us. They walked us through the source code a few times and explained what was going on and was a pleasure to deal with. Within a few weeks we were dialing out, connecting to our ISP and transferring files to and from our central server. Our little embedded 186 consistently transfers data @ 33KB and surpassed all expectations. I highly recommend Treck. Thanks to them connecting to the Internet is no longer a mystery."