FAQs

From Omnifi Wiki

Jump to: navigation, search

[This is the Lumkichi guideline. Please remove items from the guideline as you add them below.]

Introduction

  • About the DMP1
  • About the DMS1

Installation Issues

  • Options for install of the DMP1
  • Wireless Issues with the DMP1
  • Wireless Issues with the DMS1
  • Firmware Updates
  • Reformatting the Hard drive
  • Mounting Concerns

Software

  • Simplecenter Issues
    • Playing MyStation
    • Recording Internet Radio Streams
    • Playing more than 10,000 songs
  • Simplecenter patches/fixes
  • FTP access to DMP1 hard drive
  • CD Ripping

DMS1

  • What the DMS1 can do, won't do, and might be able to do
  • Can't update firmware on the DMS1
  • Universal Remotes
  • Other compatible D-Link USB wireless adapters
  • Pictures of the guts and description
  • uPnP

DMP1

  • What the DMP1 can do, won't do, and might be able to do
  • Can't update firmware on the DMP1
  • Synchronization problems
  • Compatible Car Stereos
  • Current thoughts on hacking the firmware
  • Pictures of the guts and description
  • Inline volume control for distorted sound
  • Skipping


Contents

[edit] Software

Q: Can I run more than one UPnP Server on one computer?
A: No.

Q: Are there patches or fixes for SimpleCenter?
A: Yes, this group has provided a number of patches with information available at the SimpleCenter_version_history page.

Q: Why doesn't my SimpleCenter see my DMS1 and vice versa on my network?
A: This is a very, very complicated topic. Those people whose machines work without any problems cannot fathom the troubles that the people who can't make it work go through.

It is probably a matter of set up. Check the following, to the best of your ability. If you're not as able, get a friend to help.

  • Connect your DMS1 to the network via Ethernet adapter until connectivity problems are resolved
  • Assign a static IP address to your DMS1 from the front-panel, rather than letting your network's DHCP server assign it one
  • This value can be the same as what your router assigned for your DMS1, but it is best to set a static IP, especially when it comes to troubleshooting wireless issues later.

  • On the PC with SimpleCenter installed, ping your DMS1.
  • This is to ensure that physical network connectivity exists before proceeding. Open a DOS prompt (on Windows 2000 and XP) using Start->Run->cmd or (on Windows 95/98/Me) using Start->Run->command

    In this example, the DMS1 has an IP address of 192.168.1.10. Substitute your DMS1's IP here:

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    
    C:\>ping 192.168.1.10
    
    Pinging 192.168.1.10 with 32 bytes of data:
    
    Reply from 192.168.1.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.10: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.10: bytes=32 time<1ms TTL=128
    
    Ping statistics for 192.168.1.10:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    
  • Turn off Windows Firewall (Windows XP Service Pack2 users only)
  • Until such time you establish connectivity, disable the Windows Firewall. From your Windows Control Panel (Start->Control Panel) select the Windows Firewall icon and double-click it. A dialog box will appear. Select the OFF (Not Recommended) option and click OK. If it's already off, fine.

  • Turn off/Disable any other Firewall software.
  • Norton Internet Security, Symantec Client Security, MacAffee, Zone Alarm, Black ICE Defender, etc. all have an option to disable firewall. Do not try to lower the security settings on the firewall--make sure you either shutdown the firewall or disable it so it will not interfere at all with what needs to work. You'll work on enabling your firewall later, and configuring it to work with SimpleCenter.

  • Reboot the DMS1, then restart SimpleCenter
  • To reboot the DMS1, either unplug it and wait 10 seconds and plug it back in, or press the power button for about 10 seconds and let go. After a delay, it'll begin its restart sequence. Let it get to the point where it says, "Searching for Media..."

    On your PC, shutdown SimpleCenter by right clicking the systray icon and select Shutdown SimpleCenter Server and answer Yes to the query.

    Then start it up again by finding the SimpleCenter icon and clicking on it. This is to allow the DMS1 to get out of its "hung" state (if it ever got into it), and will cause SimpleCenter to broadcast information about itself to the network.

  • Disable UPnP on your Router
  • Your router may have the option to enable UPnP for itself. While enabling it does not prevent SimpleCenter and DMS1 from working, it DOES create a lot of network traffic and will fill up your SimpleCenter logs with errors. Turn it off; it's only needed by certain programs (Such as games that want to act as a server for clients on the Internet) to remotely and automatically configure your router to its liking. Personally, a trojan horse can conceivably open your router up to the entire world this way. Turn it off.

  • If the DMS1 cannot find your SimplleCenter after a few seconds, then there are other things in your Windows.
  • Go to the Services screen. (Windows2000/XP users only: Start->Control Panel->Administrative Tools->Services). Stop and disable the following services that exist:

    Universal Plug and Play Device Host
    SSDP Discovery Service
    

    These two services, if they exist, are not needed and worse--SSDP Discovery Service prevents SimpleCenter from broadcasting its presence and thus the DMS1 cannot find it!

Here is a write up of what should happen on a more nitty-gritty level.

It would seem some of the ports needed are opened but not all...  I'll share with you what's on mine:

Before:

C:\> netstat /a
  Proto  Local Address          Foreign Address        State     
  TCP    999LX2B:epmap          999LX2B.int.mvnt.lan:0  LISTENING
  TCP    999LX2B:microsoft-ds   999LX2B.int.mvnt.lan:0  LISTENING
  TCP    999LX2B:8082           999LX2B.int.mvnt.lan:0  LISTENING
  TCP    999LX2B:1029           999LX2B.int.mvnt.lan:0  LISTENING
  TCP    999LX2B:1029           localhost:1070         ESTABLISHED
  TCP    999LX2B:1030           999LX2B.int.mvnt.lan:0  LISTENING
  TCP    999LX2B:1045           localhost:1046         ESTABLISHED
  TCP    999LX2B:1046           localhost:1045         ESTABLISHED
  TCP    999LX2B:1070           localhost:1029         ESTABLISHED
  TCP    999LX2B:3017           999LX2B.int.mvnt.lan:0  LISTENING
  TCP    999LX2B:netbios-ssn    999LX2B.int.mvnt.lan:0  LISTENING
  TCP    999LX2B:427            999LX2B.int.mvnt.lan:0  LISTENING
  TCP    999LX2B:1071           64.233.171.83:http     ESTABLISHED
  TCP    999LX2B:1349           10.20.98.73:8081       SYN_SENT  
  UDP    999LX2B:microsoft-ds   *:*                              
  UDP    999LX2B:1025           *:*                              
  UDP    999LX2B:1041           *:*                              
  UDP    999LX2B:8082           *:*                              
  UDP    999LX2B:8084           *:*                              
  UDP    999LX2B:ntp            *:*                              
  UDP    999LX2B:1765           *:*                              
  UDP    999LX2B:ntp            *:*                              
  UDP    999LX2B:netbios-ns     *:*                              
  UDP    999LX2B:netbios-dgm    *:*                              
  UDP    999LX2B:427            *:*                              
  UDP    999LX2B:1036           *:*                              

After:

C:\> netstat /a
Proto  Local Address          Foreign Address        State                   
TCP    999LX2B:epmap          999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:microsoft-ds   999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:8001           999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:8082           999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:12083          999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:14834          999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:17984          999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:1029           999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:1029           localhost:1070         ESTABLISHED             
TCP    999LX2B:1029           localhost:1373         TIME_WAIT               
TCP    999LX2B:1030           999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:1045           localhost:1046         ESTABLISHED             
TCP    999LX2B:1046           localhost:1045         ESTABLISHED             
TCP    999LX2B:1070           localhost:1029         ESTABLISHED             
TCP    999LX2B:1375           localhost:1029         TIME_WAIT               
TCP    999LX2B:1379           localhost:1029         TIME_WAIT               
TCP    999LX2B:1382           localhost:1029         TIME_WAIT               
TCP    999LX2B:1396           localhost:1029         TIME_WAIT               
TCP    999LX2B:1398           localhost:1029         TIME_WAIT               
TCP    999LX2B:1400           localhost:1029         TIME_WAIT               
TCP    999LX2B:1402           localhost:1029         TIME_WAIT               
TCP    999LX2B:1405           localhost:1029         TIME_WAIT               
TCP    999LX2B:1408           localhost:1029         TIME_WAIT               
TCP    999LX2B:3017           999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:netbios-ssn    999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:427            999LX2B.int.mvnt.lan:0  LISTENING              
TCP    999LX2B:1071           64.233.171.83:http     ESTABLISHED             
TCP    999LX2B:1376           scweb-ntc0s-0.stream.aol.com:http  TIME_WAIT   
TCP    999LX2B:1380           128.177.10.211.available.above.net:8080  TIME_WA
TCP    999LX2B:1383           128.177.10.211.available.above.net:8080  TIME_WA
TCP    999LX2B:1397           128.177.10.211.available.above.net:8080  TIME_WA
TCP    999LX2B:1399           128.177.10.211.available.above.net:8080  TIME_WAIT
TCP    999LX2B:1401           128.177.10.211.available.above.net:8080  TIME_WAIT
TCP    999LX2B:1403           128.177.10.211.available.above.net:8080  TIME_WAIT
TCP    999LX2B:1406           128.177.10.211.available.above.net:8080  TIME_WAIT
TCP    999LX2B:1407           ZULU.OMNIFIMEDIA.COM:8091  ESTABLISHED         
TCP    999LX2B:1409           128.177.10.211.available.above.net:8080  TIME_WAIT
TCP    999LX2B:14834          192.168.1.10:2189      TIME_WAIT               
TCP    999LX2B:14834          192.168.1.10:2190      TIME_WAIT               
TCP    999LX2B:14834          192.168.1.10:2191      TIME_WAIT               
TCP    999LX2B:14834          192.168.1.10:2192      TIME_WAIT               
TCP    999LX2B:14834          999LX2B.int.mvnt.lan:1377  TIME_WAIT           
TCP    999LX2B:14834          192.168.1.192:1059     TIME_WAIT               
UDP    999LX2B:microsoft-ds   *:*                                            
UDP    999LX2B:1025           *:*                                            
UDP    999LX2B:1041           *:*                                            
UDP    999LX2B:1372           *:*                                            
UDP    999LX2B:1404           *:*                                            
UDP    999LX2B:1900           *:*                                            
UDP    999LX2B:7000           *:*                                            
UDP    999LX2B:8082           *:*                                            
UDP    999LX2B:8084           *:*                                            
UDP    999LX2B:ntp            *:*                                            
UDP    999LX2B:1381           *:*                                            
UDP    999LX2B:1765           *:*                                            
UDP    999LX2B:ntp            *:*                                            
UDP    999LX2B:netbios-ns     *:*                                            
UDP    999LX2B:netbios-dgm    *:*                                            
UDP    999LX2B:427            *:*                                            
UDP    999LX2B:1036           *:*                                            
UDP    999LX2B:16745          *:*                                            

==========================

If you ever have access to another machine (a friend's laptop, let's say).  There are a couple of things you can try:

a) install SimpleCenter there and see if your DMS1 can see it
-and/or-
b) install a packet sniffer on your friend's machine and see if you can find the following bit of traffic coming from your SimpleCenter on your mchine (I use NetworkActiv Sniffer http://www.networkactiv.com/NetworkActivPIAFCTMv1.5.exe - free version)

From:  <IP of SimpleCenter machine>
Port: 2008 (or some port)

To: 239.255.255.250
Port: 1900 (must be this destination IP and port)

Packet data:

NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age = 1800
LOCATION: http://192.168.1.107:14834/upnp/description/10cb3465-aa92-11d9-80df-8d5d012e489a
NT: uuid:10cb3465-aa92-11d9-80df-8d5d012e489a
NTS: ssdp:alive
SERVER: Windows XP/5.1 UPnP/1.0 SimpleCenter/2.0.3.11
USN: uuid:10cb3465-aa92-11d9-80df-8d5d012e489a

This is SimpleCenter UPnP advertising on a Multicast address that it is available.  Your DMS1 needs this info to detect a UPnP server for its music needs...  Several more packets (TCP) follow.

SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 5
ST: upnp:rootdevice

etc...

Eventually, the DMS1 should respond:

From: <DMS1 IP address>
Port: <arbitrary>

To: <SimpleCenter IP>
Port: 14834

GET /upnp/description/10ccbb06-aa92-11d9-80df-8d5d012e489a HTTP/1.1
HOST: 192.168.1.107:14834
DATE: Thu, 01 Jan 1970 01:21:13 GMT
CONNECTION: close
USER-AGENT: Linux/2.4.18-rmk7, UPnP/1.0, Intel SDK for UPnP devices /1.2

SimpleCenter should respond with:

HTTP/1.1 200 OK
Content-Type: text/xml
<?xml version='1.0' encoding='UTF-8'?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.107:14834</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:MediaServer:1</deviceType>
<friendlyName>SimpleCenter (999LX2B)</friendlyName>
<manufacturer>SimpleDevices, Inc.</manufacturer>
<manufacturerURL>http://www.simpledevices.com</manufacturerURL>
<modelDescription>SimpleCenter Media Server is a UPnP Media Server implementation giving your UPnP compliant devices access to your SimpleCenter Media Library.</modelDescription>
<modelName>SimpleCenter Media Server</modelName>
<modelNumber>2.0.3.11</modelNumber>
<modelURL>http://www.simpledevices.com/simplecenter</modelURL>
<UDN>uuid:10ccbb06-aa92-11d9-80df-8d5d012e489a</UDN>
<serviceList>
<service>
<serviceType>urn:schemas-upnp-org:service:ContentDirectory:1</serviceType>
<serviceId>urn:upnp-org:serviceId:ContentDirectory</serviceId>
<SCPDURL>/upnp/description/ContentDirectory</SCPDURL>
<controlURL>/upnp/control/ContentDirectory</controlURL>
<eventSubURL>/upnp/events/ContentDirectory</eventSubURL>
</service>
<service>
<serviceType>urn:simpledevices-com:service:MetaData:1</serviceType>
<serviceId>urn:upnp-org:serviceId:MetaData</serviceId>
<SCPDURL>/upnp/description/MetaData</SCPDURL>
<controlURL>/upnp/control/MetaData</controlURL>
<eventSubURL>/upnp/events/MetaData</eventSubURL>
</service>
<service>
<serviceType>urn:simpledevices-com:service:Synchronization:1</serviceType>
<serviceId>urn:upnp-org:serviceId:Synchronization</serviceId>
<SCPDURL>/upnp/description/Synchronization</SCPDURL>
<controlURL>/upnp/control/Synchronization</controlURL>
<eventSubURL>/upnp/events/Synchronization</eventSubURL>
</service>
</serviceList>
</device>
</root>
 
This lets DMS1 know what the Server name is (and it should be displayed on the DMS1).

---------

This whole point being, SimpleCenter has to be able to broadcast its presence.  If another computer on the network cannot detect its presence at all, then there is an issue with the SimpleCenter installation, or worse - settings on your Windows that we do not know of.

If the broadcasts can be detected by another machine, then there is a problem with your DMS1.

You should be able to put a copy of SimpleCenter onto your friend's machine directly (without the CD) from http://www.omnifimedia.com/scripts/omnifitech.cfg/php.exe/enduser/std_adp.php?p_faqid=80&p_created=1077817126

This sniffer result and friend's installation of SimpleCenter should narrow it down to whether it's your Windows installation or your DMS1.

Try installing TwonkyVision http://www.twonkyvision.de/UPnP/index.html#musicserver on your SimpleCenter machine.  Shut down SimpleCenter and fire up Twonky and see if your DMS1 sees them.  If it can then you may have to retry install SimpleCenter and/or see what's up with the Windows Setting.

Q: The SimpleCenter "Guide" and "Account" areas are empty, how can I get these to properly display?
A: This is critical for new installs since until SimpleCenter is registered (or registration is retrieved) you will be unable to use any of the internet streaming that is accessible through the Channels area. The server that SimpleCenter connects to in order to populate the Guide and Account areas is no longer correct. The server still exists on the internet but you will need to force SimpleCenter to connect to the new address. The host name that SimpleCenter uses to connect is prodapp2.simpledevices.com but the IP address that it needs to connect to is actually 204.126.173.61. (Correct as of June 2006) prodapp2.simpledevices.com does not resolve to this address. The solution is to add a manual redirect pointing the host name to the proper IP address via the HOSTS file in Windows. In Windows XP this can be found in the C:\windows\system32\drivers\etc folder if Windows was installed with "windows" as the install directory. The location is similar in other versions of Windows. Note that the file has no extension in the name, like .txt or .pdf. The file is plain text and can be opened in Notepad. You will want to add a new line at the end of the file which contains the IP address and the host name listed above, separated by at least one space. Save the HOSTS file and try looking at the Guide and Account areas now, they should be accessible. Register SimpleCenter or retrieve your registration info to gain access to the Channels area. Once you have completed the registration process the information will be saved in SimpleCenter and connecting to the "prodapp2" server is no longer required. If you don't care about seeing the data in the Guide or Account areas then the added line is not needed in the HOSTS file. It can be left as is, removed or simply commented out with a hash mark at the beginning of the line.

[edit] Windows MediaConnect

Q: Will Windows MediaConnect work with my OmniFi device?
A: Yes, it will only work with the DMS1.

Q: Can Windows MediaConnect be configured to serve my songs from my network drive?
A: Yes, version 2 of this application can be configured to use network drives, but version 1 is limited to local drives.

Q: How can I get Windows MediaConnect?
A: Typically it will be pushed with Service Pack 2 (SP2), but it can also be downloaded for free from microsoft.com.

[edit] Nero MediaHome

Q: Will Nero MediaHome work with my Omnfi device?
A: Yes, it will only work with the DMS1.

Q: Can Nero MediaHome be configured to serve my songs from my network drive?
A: Yes.

Q: How can I get Nero MediaHome?
A: Typically it is packaged with the NeroVision set, but that set must be purchased with Nero Ultra Edition 6+. It can be found here at nero.com.

[edit] TwonkyVision MusicServer

Q: Will TwonkyVision MusicServer work with my OmniFi device?
A: Yes, it will only work with the DMS1.

Q: Can TwonkyVision MusicServer be configured to serve my songs from my network drive?
A: Yes, the application is setup to read ID3 tags and the filesystem for navigation.

Q: How can I get TwonkyVision MusicServer?
A: It can be downloaded for free from TwonkyVision.de.

Q: What operating system is TwonkyVision MusicServer compatible with?
A: They are distributing it as working with Windows XP, Mac OS X, and Linux/UNIX.

[edit] MP3 Tagging

Q: Will my SimpleCenter/OmniFi support v2 ID3 Tags?
A: Yes, it support v2 and v1 ID3 Tags, but v2 will have priority.

Q: What genres will SimpleCenter/OmniFi support?
A: Any genre will be supported by v2, but v1 must be in this list:

Blues, Classic Rock, Country, Dance, Disco, Funk, Grunge, Hip-Hop, Jazz, Metal, New Age, Oldies, Other, Pop, R&B, Rap, Reggae, Rock, Techno, Industrial, Alternative, Ska, Death Metal, Pranks, Soundtrack, Euro-Techno, Ambient, Trip-Hop, Vocal, Jazz+Funk, Fusion, Trance, Classical, Instrumental, Acid, House, Game, Sound Clip, Gospel, Noise, AlternRock, Bass, Soul, Punk, Space, Meditative, Instrumental Pop, Instrumental Rock, Ethnic, Gothic, Darkwave, Techno-Industrial, Electronic, Pop-Folk, Eurodance, Dream, Southern Rock, Comedy, Cult, Gangsta, Top 40, Christian Rap, Pop/Funk, Jungle, Native American, Cabaret, New Wave, Psychadelic, Rave, Showtunes, Trailer, Lo-Fi, Tribal, Acid Punk, Acid Jazz, Polka, Retro, Musical, Rock & Roll, Hard Rock


[edit] Streaming URL

Q: How do I use the ADD URL option in the Media Library?
A: try the following (URL is good as of 6/17/2005):

  1. Click the MEDIA LIBRARY tab
  2. Click the ADD URL button
  3. Enter the following info
  4. Title:  Indie Pop Rocks
    URL:    http://www.somafm.com/indiepop.pls
    
  5. Click OK
  6. From the ALL MEDIA tree view, locate the Indie Pop Rocks entry and double click it
  7. If the URL is still good, you should be able to enjoy the streaming music

Search the Internet (such as www.google.com) for the keyword "Internet Radio". The above URL came from the following site: SomaFM Commercial Free Internet Radio. You should be able to find many, many others.

[edit] DMS1

Q: Will other Wireless Adapters work with my DMS1?
A: Yes, but they must be a certain specification. Check out the details here: OmniFi Wireless Adapters

[edit] DMP1

Q: Can I change the color of the LEDs?
A: Yes, see the HowTo#Backlight page for details.

Q: Can I upgrade my harddrive to something larger than 20GB?
A: Yes, see the HowTo#Harddrive page for details.

Q: What can I do to reduce/eliminate engine noise?
A: Purchase a Ground Loop Isolator and install between the RCA cable and the Wiring Adapter. The Ground Loop Isolator should cost between $12-$30 (USD).

 RadioShack (p/n 270-054 $16.99+tax) View Item

Q: Do polarized sunglasses affect the display on my DMP1?
A: Yes, each screen is different, but you will notice darkening of the screen. In some cases, you cannot see the text on the screen at all. The primary reason is that the DMP1 display is a LCD type display. By pure physics, LCD displays depend on polarized filters to display the images correctly (even your LCD watch and Palm Zire has a thin layer of polarized film pasted to the LCD screen). When your polarized sunglasses are out of phase with the polarized film, the display blanks out. The DMP1 also yields a strange Moire pattern when viewed through sunglasses. Try rotating your sunglasses 360 as you peer through it at the DMP1 display, you'll see the screen go totally black, then come back and go black and come back again.

Q: How can I fix my DMP1 to prevent the 'Temperature out of range' error?
A: At this point, you can't adjust the temperature, but you can bypass the monitor. See the HowTo#DMP1_Temperature_Monitor page for details.

Q: Why won't my SimpleCenter or Windows recognize my HD cartridge?
A: The USB Cable may be too long. Try a shorter cable or install a powered USB 1.1 Hub between the HD cartridge and the PC. If the cable supplied with the DMP1 is too long (wrt to the power output of your PC's USB port), then a cable supplied with a Palm Zire may be short enough to work.

Q: I have playlists which show up on my DMS1, but are not present on the DMP1. What do I do?
A: You must specifically select your playlists to upload to the DMP1. Under the DEVICES tab, select the Omnifi Digital Media Player (DMP1) and select the MEDIA sub-tab. There, you'll see a check box and an expand folders view of the Playlists. Check the box and attempt your sync. Your playlists (if any listed) should be uploaded to the DMP1 HD cartridge, (or if you do wireless sync, it should come over)

Q: I have issues with the DMP1's shuffle mode. Is this a bug?
A: It depends. Perhaps the shuffling algorithm is not up to scratch, but it will shuffle. There is no "industry standard" for shuffling--each company implements what they feel is best. Some will take a folder and play each song once, others will play it randomly. The DMS1 shuffle may play your songs several times in the course of a shuffle period, and when it is restarted (ignition turned back on), it will forget what it played before and will play the rest of the current song and find another song to shuffle. In other words, it's "working as coded." Perhaps it's not cool or sexy and not meet your expectations, but it doesn't reboot or GPF trying to shuffle...

Q: Why does my DMP1 hang up, requiring me to eject the HD cartridge?
A: This is a bug. If you can describe the exact steps that another person can reproduce to cause this to occur, please let us know so we can all report this to OmnifiMedia.

Q: Why does my DMP1 say "Initialized Hard Drive Cartridge, Rebooting..." over and over but never boot up?
A: Perhaps you've recently upgraded your HD cartridge or you've at least reformatted your HD Cartridge. In order for the stock DMP1 to work at all, the HD cartridge must be formatted as FAT32 in a PRIMARY partition. If you format it as FAT32 in a LOGICAL partition, then the DMP1 will exhibit the above behavior. The same goes if you format the HD to anything else (let's say ext2). Setting the partition to Active (bootable) or Hidden seems to have no effect on the DMP1. The "Hidden" attribute will affect Windows' ability (thus SimpleCenter) to see the drive. It's best not to mark your HD cartridge as Hidden.

Q: Can I copy my /usr directory from one HD cartridge to another without having to let DMP1 re-initialize the drive?
A: Yes! If you've kept a copy of the contents of the old HD prior to replacing the drive or reformatting it, you can simply copy the whole thing back onto it, provided you have created a single FAT32 on a primary partition. If you have multiple DMP1's, then you might want to exit the root.xml and change the serial number slightly. Otherwise, the serial number would identify the DMP1, not the HD cartridge--you should be able to leave it alone.

[edit] General Troubleshooting

Q: My DMP1 HD cartridge works fine in the DMP1, but neither my PC nor SimpleCenter recognizes it when I connect using USB. Why?

A: There may be multiple things going on. Please explore each of the following carefully, as they have worked for others in the past:
  1. the USB cable you have might be too long. Try a shorter cable
  2. try plugging your HD cartridge into a USB 1.1 powered hub
  3. your PC may not recognize your HD cartridge or has not properly installed drivers for the USB mass storage device. Go to the Device Manager, remove the device from the configuration and let Windows try to reinstall, or attempt to reinstall the drivers yourself. Windows 2000 and XP will recognize the USB Mass Storage Device (not the HD, but the electronics that connect your HD to the PC) as:
  4. XP:

    Device Type: Universal Serial Bus Controllers
    Manufacturer:  Compatible USB Storage Device
    Location: Location 0 (Omnifi USB Drive )
    Driver Provider: Microsoft
    Driver Date: 7/1/2001
    Driver Version: 5.1.2600.0
    Driver:  C:\WINDOWS\system32\drivers\USBSTOR>SYS
    Driver File Version: 5.1.2600.2180 (xpsp_sp2_rtm.050803-2158)
    Signed by: Microsoft Windows Publisher
    

    2000:

    USB Mass Storage Device
    Device Type: Universal Serial Bus Controllers
    Manufacturer: Microsoft
    Location: Omnifi USB Drive
    Driver Provider: Microsoft
    Driver Date: 11/14/1999
    Driver Version: 5.0.2183.1
    Digital Signer: Microsoft Windows 2000 Publisher
    

    Get a PC-saavy friend to help you do these steps as it requires someone being right in front of your computer...

  5. Send the HD off to Omnifi for an RMA. This is the most unfortunate of events, but lately Omnifi has been cordial about replacing your HD cartridges. Take advantage of the situation if you're really stuck.

Q: Can the DMS1 and DMP1 play VBR MP3 files?
A: Yes, but the time progress bar will not display correctly. This is a limitation of the SimpleCenter cataloguing system which incorrectly reads the VBR mp3 duration and stores it. If you know the actual time, and feel confident enough to edit your mediadb.xml, then it can be made to display the progress bar just as correctly. For more info, check out Tips For Smooth Operation.

Q: Why do some mp3's click and pop loudly on my DMS1 and DMP1 then go to the next song?
A: The mp3 is most likely recorded at a sample rate of 48,000 Hz. At this frequency, the DMP1 and DMS1 cannot play the song back. The song *will* play on SimpleCenter because it uses Windows Media with the appropriate codecs. You'll have to get a bulk mp3 -> mp3 converter and downsample the song to 44,100 Hz, or re-rip at the lower sample rate.

Q: I've added songs on a networked drive to my SimpleCenter. They won't stream to the DMS1.
A: Try to re-add the songs by mapping a drive letter to the networked drive. Right click My Computer or Network Neighborhood and select Map Network Drive. Add your songs by referring to the drive letter.

Q: SimpleCenter hangs up trying to add more than 15,000 songs. Why?
A: You've downloaded and installed one of the SimpleCenter updates from the Yahoo! forum, no doubt. SimpleCenter I and J updates have a max of 20,000 songs. K update can handle 50,000 songs. But that's only half the story. To be able to actually load that many songs, you'll have to increase the java heap sizes. In your SimpleCenter install directory is a file called simplecenter.lax. This is a text file which you'll have to add the following lines suggested by Cameron and restart SimpleCenter.

 # Added by Cameron
 # If you want to set the heap sizes for your application, you need to set the
 # lax.nl.java.option.java.heap.size.initial and lax.nl.java.option.java.heap.size.max.  
 # The property only accepts byte values.  If you want to set the max heap size to 128
 # megabytes, you’ll need to set lax.nl.java.option.java.heap.size.max to 
 # lax.nl.java.option.java.heap.size.max=134217728

 lax.nl.java.option.java.heap.size.initial=268435456
 lax.nl.java.option.java.heap.size.max=536870912

The K Update version comes with an already marked-up copy of simplecenter.lax in the Special Files folder. There is also an associated README. Rename the original simplecenter.lax and copy this simplecenter.lax into the SimpleCenter install directory and restart SimpleCenter.

There is an unfortunate side-effect of having that many songs loaded--SimpleCenter sluggishness, DMS1 might "hang" trying to navigate using the << (double-back button), DMP1 sync takes forever or hangs, DMP1 might "hang" trying to navigate using << or >>. There was a reason for the 10,000 song limit. Try Twonkyvision for the DMS1 and try Lincomatic's DMP1Sync for the DMP1, instead.

Q: Why doesn't the record button on SimpleCenter work?
A: Actually it does work for the SHOUTCast and LaunchCast streams as of SimpleCenter L update. Virgin Radio and Live365 don't even record at this time. As for Virgin and Live365, we'll have to see if it can be made to record, at all.

Q: How do I get Rhapsody v3 doesn't work with my DMS1?
A: According to Omnifi Media and sk8man, a particular firmware version **will** work with Rhapsody v3. If you've got v 2.1.012, alas you'll have to downgrade to 2.0.313. (as of 5/2005) From SimpleCenter, press the upgrade device firmware button and the 2.0.313 version will be downloaded and pushed up to the DMS1.

[edit] Related Links:

The thing you need to know about cellulite treatments is that, it takes particular attention and constant monitoring. It should not be treated once and leave it at that. Cellulites do come back in a short period of time and you can have it worse than before. The great news is you don't have to pass under the stab to have it removed.

cellulite treatments

Personal tools