Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Can't create a Boot Disk for USB to Fast Ethernet adapter

Created: 06 Jun 2011 | 3 comments
GFradelakis's picture
0 Agree
0 Disagree
0 0 Votes
Login to vote

I would like to know if Symantec is working on a solution for creating a "USB to Fast Ethernet Adapter" Boot Image. My School District is in the process of purchasing 1000 "Acer Iconia Tab W500" computers. They have the Asix Ax88772b USB 2.0 to Fast Ethernet Adapter.

Symantec does not provide a solution for Multicasting with this adapter.

Comments 3 CommentsJump to latest comment

jgillfeather@savills.com.au's picture

Howdy,

did you ever have any joy with this?  We're trying to do the same thing with the W501.

Am guessing you need to pre-load some USB controller drivers before the NIC driver itseelf, but no clue which ones. Weirdly, the ASIX driver seems to load into the PXE setup aok, but does not show in the list after a refresh...

regards,

Justin

 

0
Login to vote
jgillfeather@savills.com.au's picture

OK, working.

In brief, requires WinPE 3.0, which we've dodgied up as posted elsewhere in the Community (copy & pasted below) to get working in 6.9 SP4 or better.

If you haven't already, install a standard WinPE 2.1 environment as per Altiris documentation. Then from a WinPE 3.0 WAIK install, create a new winpe.wim as follows -

  1. make a mount folder - e.g. C:\mount
     
  2. make a package folder - e.g. C:\Package
     
  3. make a driver folder - e.g. C:\Driver
     
  4. copy the following cab files (winpe-wmi.cab, winpe-scripting.cab, winpe-hta.cab) from C:\Program Files\Windows AIK\Tools\PETools\x86\winpe_fps -> C:\package
     
  5. Copy the Windows 7 version of thr ASIX LAN card drivers (the inf and all files in that folder) to C:\Driver
     
  6. From the Deployment Tools Command Prompt (WAIK) mount the winpe 3 standard wim (insert the path to your new winpe3 WIM file)-

    DISM /mount-wim /wimfile:<path to ver 3 wim file>\winpe.wim /index:1 /mountdir:c:\mount
     

  7. add the Packages to the WIM file

    DISM /image:c:\mount /add-package /packagepath:c:\package
     

  8. add the ASIX LAN nic to the WIM file

    DISM /image:c:\mount /add-driver /driver:c:\driver /recurse
     

  9. Dismount and save the WIM file

    DISM /unmount-wim /mountdir:c:\mount /commit
     

  10. copy this newly created winpe.eim to your express share under \WAIK\Tool\PETools\x86\winpe.wim replacing the existing file
     
  11. Now use PXE config manager to create a new winpe boot image. It will utilise the new winpe3.x winpe.wim file and create the "winpe2.1" image from that. Note you do not need to add the LAN nic as we've already done so when creating the WIM file.

    Once all is finshed, as long as pxe config manager shows that the boot file is winpe2.1 then all should be good. If pxe config manager only shows the boot file as "winpe", then it wont show up as a valid selectable winpe boot image. The only way around it I have found is to reinstall DS.

Only other trick I've found is that on a warm boot the Iconia's tend not to PXE, so when the DS agent wants to capture the PC information the first time, it tends to re-boot into Windows rather than start the PXE boot. Basicaly requires manual intervention.

regards, and all credit to the original poster, whom now i can't find, sorry

Justin

 

 

 

+1
Login to vote
Fedor's picture

Thanks a lot for ur reply! It hepled me with Asix AX88772b and Asus u21x.

btw i found the original poster. It was qman_au in this post: http://www.symantec.com/connect/ideas/ds-69-and-ds-71-should-integrate-support-winpe-3x

0
Login to vote