[syslinux] UNDI - Rom-O-Matic -- A bit off topic..

[James_Martin at ao.uscourts.gov]

I don't see how this relates to syslinux..  Even if the customer was using 
memdisk/pxelinux combination to load the DOS image, if the images loads 
ok, then it is not a fault of syslinux.  Me thinks it's a network problem 
or a problem with the DOS image or Samba configuration.

James S. Martin, RHCE
Contractor
Administrative Office of the United States Courts
Washington, DC
(202) 502-2394

syslinux-bounces at zytor.com wrote on 07/29/2005 07:20:49 AM:

> Hi,
> 
> 
> I work in Dell Support and I have a customer with a PowerEdge 1650 
> Server with Intel® PRO/1000 XT (82544GC Gigabit Ethernet Controllers).
> The nic is integrated on the motherboard.
> 
> The customer is using a Linux system with DHCP+tftp to PXE boot and 
> load an MS-Dos 6.22 image, with an UNDI driver, over to the 
> PowerEdge 1650 and then map a Samba share to install Windows 2000.
> 
> The customer get the following problem:
> If the Samba Server is located on a different subnet from the 
> PowerEdge 1650 data transfer fail's, Some of the files are corrupt 
> after transfer.
> However if the Samba Server is locater on the same subnet, it works just 
fine.
> 
> The customer has this same problem with several PE 1650, while other
> systems like PE1750 and 1850 has no problems.
> 
> 
>   Now to my questions:
> 
> - How does the UNDI work?
>      - I belive:  the PXE boot code in the BIOS configures the NIC 
> to be in "UNDI mode"?
> 
>    - Does a Rom-O-Matic created Boot Floppy also set the NIC in 
> "UNDI mode" as well? (If not, any other option?)
> 
> 
> The customer belive the BootCode in the Dell BIOS is causing this 
problem. 
>   I am thinking: 
>    - If he boot with a Rom-O-Matic created disk instead of using the
> BIOS boot code, we can verifi if this is a problem with the Boot 
> Code in the Dell BIOS or not. 
> 
> What do you think?
> 
> 
> 
> Best regards
> Harald Jensås
> MCP, CCNA
> Nordic Server Support
> Dell AB
> http://support.euro.dell.com/
> ***************************
> Please! Keep all history running!
> 
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>