Hi Robert,

The TCP/IP 5.1 version of bootpd supports PXE booting.
A -D option is required only for several specific versions of PXE boot
loaders that expected MTFTP server address in PXE response.

To implement PXE booting with TCP/IP 4.25 stack you can use bootpd
version from attach (with option -p).

> Will the client boot images need to be "tagged" similar to how mkQNXnbi is needed for Etherboot?

No, it's not required. However, for PXE booting you'll require a loader
that transfers control to QNX 4 bootable image. You can use minimalistic
qpxe from the attach. Just add it to the QNX 4 image.
# cat qpxe qnx4.img > pxe-qnx4.img
You can also find useful our article about QNX 4 PXE booting (it's
written in Russian but Goggle translate version is quite understandable)
http://translate.google.com/translate?hl=ru&sl=ru&tl=en&u=http%3A%2F%2Fwww.kpda.ru%2FPublications%2FQNX4PXEBooting


Regards,
Pavel


12.04.2013 01:21, Robert DeFreitas пишет:
> I read in the QNX4 Product Suite 2011 Release Notes that the TCP/IP 5.1 
version of bootpd supports a -D option for PXE client booting.  Is there a TCP/IP 4.25 bootpd version that also supports
 this?  If not then which PXE clients using the -D option in bootpd version 5.1 have worked?  Will the client boot 
images need to be "tagged" similar to how mkQNXnbi is needed for Etherboot?
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post100497
> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
>