In message <C9E46BCD-C5A1-11D6-8A0F-0003939E5310@boeing-online.de>, you write: 

-> Ladies and Gents,
-> 
-> I have yet another question regarding NetBSD installation on Indy:
-> 
-> I am using the files from the 200209080000 directory on releng.netbsd.org.
-> 
-> I have set up a server (NetBSD/alpha with DHCP client entry for the Indy, 
-> TFTP enabled and boot kernel in /tftpboot/netbsd) with kernel 
-> netbsd-INDY_INSTALL.ecoff. The Indy root directory holds the contents of 
-> installation/netboot/diskimage.gz.

Your Indy probably should be fine with the ELF version, but that's not
the issue here... 

-> I am booting the Indy from PROM:
-> 
->  >>boot -f bootp():/netbsd/netbsd-INDY_INSTALL.ecoff
-> Setting $netaddr to 172.16.254.20 (from server 172.16.254.2)
-> Obtaining /netbsd/netbsd-INDY_INSTALL.ecoff from server 172.16.254.2
-> 5876528
-> Cannot load bootp():/netbsd/netbsd-INDY_INSTALL.ecoff.
-> Error reading text section: cnt=0xc0, expected 0x59ab30.
-> Unable to load bootp():/netbsd/netbsd-INDY_INSTALL.ecoff: no such device.
-> 
-> The whole process takes a couple of minutes.

Please check the FAQ (at http://www.netbsd.org/Ports/sgimips/faq.html), esp.
the following link: 
    http://www.netbsd.org/Ports/sgimips/faq.html#prom-tftp-client-failing

The problem is most likely the Indy's PROM getting confused by the returned
TFTP packets and timing out the transfer.

--rafal

----
Rafal Boni                                                     rafal@attbi.com
  We are all worms.  But I do believe I am a glowworm.  -- Winston Churchill