Strange Problem with XP and Windows 2000

I tried this scanario with both windows 2000 and XP and got the same results. I have arm 1.03 installed and connect rio via ethernet. ARM assign an ip address to the rio. The LCD of the rio show the correct ip information. But I can not access the music. The LCD does not show me the initial screen that I am suppose to see. ARM window show the rio reciever so I assume that it is connected. following is the last few line of logs I got from the ARM.

Hope someone could help me to figure out the problem.

00:02:27.515 NFS Server: Starting...
00:02:27.515 Using image file: C:\Program Files\Audio Receiver\receiver.arf
00:02:27.515 bootp: binding to 192.168.0.2:67
00:02:27.515 Hostname : 192.168.0.2
00:02:27.515 IP : 192.168.0.2
00:02:27.515 Gateway IP : 192.168.0.2
00:02:27.515 Server IP : 192.168.0.2
00:02:27.515 Netmask : 255.255.255.0
00:02:27.531 httpd: binding to 192.168.0.2
00:02:27.531 Binding to 192.168.0.2:12078
00:02:54.531 BOOTP: Got a DHCP discover/request
00:02:54.531 BOOTP: Got matching vendor class ID
00:02:54.531 Trying to find IP address for MAC address 00:90:00:11:27:61
00:02:54.531 Need to find an IP address.
00:02:54.531 Found an unassigned address: 192.168.0.129
00:02:54.546 Assigned IP address 192.168.0.129 to unit with MAC address
00:02:54.593 BOOTP: Got a DHCP discover/request
00:02:54.593 BOOTP: Got matching vendor class ID
00:02:54.593 Trying to find IP address for MAC address 00:90:00:11:27:61
00:02:54.593 The last IP address used was 192.168.0.129
00:02:54.593 This IP address was last used for this MAC. Good.
00:02:54.593 The IP isn't currently in use so just use it
00:02:54.593 Assigned IP address 192.168.0.129 to unit with MAC address

Is there any firewall software enabled on the computer? For instance, the personal firewall that's built in to Windows XP?

There is no firewall installed in the machine. The only fireawall is the router connected to the cable modem but that does not prevent any communication inside the LAN. What are the ports used by rio to communicate to the server ? Is there a way we can check the server to see whether it is responding to the requests ? According to the logs the server does not seem to receive any requests from the rio.

Is it plugged into the cable router, or is it on a separate hub? Do you have the ability to check it by plugging it into a separate hub?

Port numbers are detailed here.

Thanks for all the suggestions. Yesterday, I figured out the problem. I was using server version 1.03. I installed 1.04 and now it is working.

Which rebroaches the question of whether we can get 1.04 on a download site somewhere.

I just happen to have 1.04 CD with me today, the whole disk zips to around 76MB, so if anyone has anywhere to put it let me know and I will try to get it to you.

If you only want a smaller selection if what is on the disk, let me know what is needed and I can do something about that too.

Mark.

TPTB have had issues one the empeg side with people making software publicly available, so I don't think that they would have much truck with that for the reciever, either.

Bitt,

I was just saying I have the CD, and if someone here wants a copy I can arrange for them to recieve it, I have no intentions of making it publically available outside of this thread.

On a side note I have a zip with acrobat and all languages but english removed, and that runs just over 17MB.

Mark.

I was using server version 1.03. I installed 1.04 and now it is working.

I had considered this to be a possibility, but discounted it when I didn't see the word "Dell" when I skimmed your post.

The 1.04 software is supposed to be functionally identical to the 1.03 software except for the Dell receiver support.

If that's not correct, if there are addtional bugfixes in 1.04, then, as Bitt says, why isn't it on the FTP site for download?!

Heck, for that matter, why isn't it on the FTP site at all, regardless of whether it's got bug fixes or not?

1.04 software is supposed to be functionally identical to the 1.03 software ...

Right. Time to clear this one up once and for all. I did a diff of the source code between the 1.03 and 1.04 releases. I found:

• numerous changes to the .dsp and Makefiles -- none of which appear to affect functionality/bugs
• Global volume control (me -- Ibiza)
• Better escaping of characters in HTTP requests.
• Sorting support in the list of units in Receiver Manager (me -- Ibiza)
• Minor changes to the tracing.
• Support for rebadged Dell units.
• A couple of (minor) fixes to pause/play behaviour on the unit.
• Better support for servers that don't support saving "favourite" playlists.
• Changes to the version number and copyright years.
  

So, none of the changes between v1.03 and v1.04 will have affected the ability of a (non-rebadged-Dell) unit to boot.

Why v1.04 isn't on the FTP site, I don't know.

If you just need the ARM 1.04 installation software, (not the source code, manual, adobe acrobat software, q&as on the install disk), the required directory is about 5.5Mb. I would be happy to send to anyone who needs it, private message me if your email provider allows receipt of files this large.

Support for rebadged Dell units.

A pretty significant issue for those of us with such units. I argued with it for hours until I loaded 1.04 and it magically worked.

Somewhere I got the impression that the official word was that there was no significant difference, but it obviously wasn't true.

the official word was that there was no significant difference

I don't know where you got that impression. I've made it perfectly clear that "there is no significant difference, apart from support for the rebadged units".

I guess it was the fact that it's yet to be put on the FTP site. (I'm not trying to be difficult -- honest.)

The real problem is that the rebadged receivers are being shipped with the new software, but absolutely nothing that indicates that 1) there is new software, the Rio installation CD appears to be identical to the other install CDs that I had and 2) the new software must be installed for the "new" unit to function correctly. That has led several of us with existing systems to agonize over why the rebadged unit wasn't recognized. That being said, given that these units are essentially being liquidated and are being sold below cost, I can fully understand why the documentation on the v1.04 is missing and why the files aren't available on an FTP site.