Yes well good thing I don't have to rely on the log.
After powering on the receiver and getting the
bogus ip as usual, it shows up in the list of receivers on
the server software, but NO log entry is made.


18:19:32.210 AdapterName.....
18:19:32.210 Description..... PCI Bus Master Adapter
18:19:32.210 Index........... 16777218 (0x1000002)
18:19:32.210 << Found Adapter info
18:19:32.210 DiscoverAdapters result: 0
18:19:32.210 HTTP Server: Starting...
18:19:32.210 Using database 'C:\Program Files\Audio Receiver\DB\cur2\audiorcv.dat'
18:19:32.210 httpd: binding to 192.168.1.69
18:19:32.210 Binding to 192.168.1.69:12078
18:19:32.270 NFS Server: Starting...
18:19:32.270 Using image file: C:\Program Files\Audio Receiver\receiver.arf
18:19:32.270 bootp: binding to 192.168.1.69:67
18:19:32.270 Hostname : 192.168.1.69
18:19:32.270 IP : 192.168.1.69
18:19:32.270 Gateway IP : 192.168.1.69
18:19:32.270 Server IP : 192.168.1.69
18:19:32.270 Netmask : 255.255.255.0
18:22:52.250 HTTP Server: Stopping...
18:22:52.250 HTTP Server: Stopped.
18:22:53.240 NFS Server: Stoppin

Well I can make the unit work on a totally flat cable or on
a private hub or unmanaged switch, but not at home
on the managed switch or at work anywhere
Still trying to figure it out. DLed that little snooper
and will check that out.