Note: Although with K2000 appliance version 3.3 KPE environments are no longer supported, conflicting drivers in KBE can still cause computers to fail PxE booting into the K2000 appliance.
To spite your best efforts to get the drivers you need into the KBOX 2000, you still cannot boot your system to KPE.
Oddly enough, the issue is actually that you may have too many copies of the driver in the KBOX.
When driver detection is done during a KPE boot, both KPE and All folders are searched for the driver. In the event the driver is found in both, the one with the highest alphanumeric is the one used. Generally speaking, since KPE has a higher alpha value than All, KPE should win. However, If there are any characters with a higher alpha value at all, that driver will be used.
For example, let’s say that you have a Yukon Marvell driver in All/l/y/yk51x86.inf and you have the same driver in KPE/mar/yk51x86.inf. The driver from All will be used over the one in KPE. This would likely not an issue but for the fact that drivers in KPE are generally RIS based while the ones in All are standard Windows drivers. If the driver is called from the All folder rather than KPE during a PXE boot, that driver will load but may not successfully boot to PXE.
To verify where the drivers are coming from, check the logs under KBOX settings and maintenance under the logs tab. The log on question is called Network driver server output log.
[Thu, Nov 27 2008 12:12:13 PST]
NCQ Packet from 192.168.0.119:47557 received.
Probing for PCI\VEN_1022&DEV_2000&SUBSYS_20001022&REV_10...
Probing for PCI\VEN_1022&DEV_2000&SUBSYS_20001022...
Found driver in /kbox/datastore/current/peinst/drivers/all/vmware/vmxnet/win2k/vmware-nic.inf
[Tue, Apr 21 2009 23:19:04 MST]
NCQ Packet from 192.168.0.119:59200 received.
Probing for PCI\VEN_1022&DEV_2000&SUBSYS_20001022&REV_10...
Probing for PCI\VEN_1022&DEV_2000&SUBSYS_20001022...
Found driver in /kbox/datastore/current/peinst/drivers/kpe/vmxnet/win2k/vmware-nic.inf