PXE boot ROMs
Why emBoot should develop your PXE (PreBoot Execution Environment) boot ROM

If you build Network Interface Cards (NICs) for the business environment, you have two alternatives for developing your PXE boot firmware.

You can develop it in-house...but the PXE (PreBoot Execution Environment) base code is no longer available from Intel. You'll then need to develop the Universal NIC Driver Interface (UNDI) component...and develop the boot ROM, design test procedures, conduct the testing, and maintain your design. You'll have to dedicate scarce resources, get them up to speed with the technology, and then worry about keeping them.

Or... you can use emBoot's vast experience do it all for you.

Most major NIC makers agree the second choice makes the most sense. That's why they are choosing emBoot for their boot ROM partner.

Our management and engineering staff's history and experience with network booting is almost as old as the technology itself. We began as Lanworks Technologies in 1986, and our primary focus has been the development and distribution of boot ROMs for network booting. You won't find a source anywhere that can offer the unique experience in boot ROM development and support that we do.

In 1998, 3Com Corporation acquired Lanworks Technologies, and in 2002 we formed emBoot. Our management & staff with over 35 years of particular experience in this field will continue our leadership in networking booting technology as an completely independent company.

What does our years of experience in this technology mean to you?

  • We've developed boot ROMs for a large variety of LAN controller chips from various vendors such as 3Com, SMC, Intel, AMD, Allied Telesyn, DEC, HP, Accton, Realtek, Compaq, Symbol, etc. Consequently, we have a wealth of experience with various LAN controller designs and implementations.
  • You can rely on our knowledge of system architecture. We've developed boot ROMs for various types of adapters like PCI, ISA, MiniPCI, PCCard, USB to Ethernet, etc.
  • You can choose from a variety of code configurations:
    • for a ROM chip that resides on a NIC
    • for integration into a system BIOS
    • monolithic or split configurations
  • You get the benefit of our wide experience in network environments: TCP/IP (Windows, Linux, UNIX), Netware, etc.
  • We know the PXE 2.0 specification - past experience includes being a main contributor to the specification.
  • You don't have to worry about compatibility. Our QA facilities include a variety of third-party client management products for compatibility testing. These include: 3Com Boot Services, 3Com Virtual LAN Drive (VLD), Windows 2000 Remote Installation Services (RIS), IBM's LANClient Control Manager (LCCM), Intel's LANdesk Configuration Manager (LCM), OnTechnology's OnCommand CCM, CA's Unicenter, Symantec's Ghost Enterprise, Altiris eXpress, and more.
  • With all that experience, our test plans have evolved to cover all the bases. Our designers have created countless test scripts and test programs to help ensure the quality and robustness of our code.
  • You can forget about BIOS problems. A boot ROM's interaction with the system BIOS and PCI can be problematic because so many types and implementations are available. Over years of direct experience and a close relationship with Phoenix Technologies, we provide mature and robust system interface code.
  • You always have the latest technology available for your customers. We stay on top of the latest industry advances, including the Extensible Firmware Interface (EFI) that's being introduced with the new IA64 systems. Our boot ROM designs include adding support for EFI.

    You're in good company when you choose emBoot. Major PC vendors such as Dell, HP, EMC, Toshiba, and IBM license boot ROMs that our staff have designed. These industry leaders have great faith in our technologies, and you can, too.



C o p y r i g h t   2 0 0 2 - 2 0 1 9   e m B o o t   I n c o r p o r a t e d .   A l l   R i g h t s   R e s e r v e d .