Since a transfer to MediaPortal 1.0 requires a fresh new install, I'm revisiting a lot of settings that I haven't touched in a while. Among which the maps for My Weather. With many websites using unsupported formats for their weather maps, finding images that My Weather can display is a challenge. For instance, the .png files that are used by the dutch KNMI website and many other weather sites are not supported. But I found a number of close matches:
Satellite: http://www.sat24.com/images.php?country=nl
Temperature: http://www.teleweer.nl/common/data/nl_middag2.gif
UV Index: http://www.knmi.nl/waarschuwingen_en_verwachtingen/images/zonkracht/zonkracht_kaartje_dag0.gif
Winds: http://db.eurad.uni-koeln.de/prognose/data/aktuell/sto_cen_1h_movd0.gif
Humidity: http://icons-pe.wunderground.com/data/640x480/2xeu_rh.gif
Precipitation: http://www3.buienradar.nl/images.aspx?jaar=-3&soort=sp-loop
This also gave me an opportunity to make my first ever contribution to the MediaPortal wiki.
09 September, 2008
07 September, 2008
Network troubleshooting
With the server hardware up and running, there is plenty of troubleshooting to do. My network now consists of a server and two client pc's, connected by 100Mbps ethernet and a router that I use a switch. The router is also connected to an ADSL modem that's also a router.
First of all, the network was behaving weird. Even though all three pc's had the same workgroup name specified, not all of the pc's were showing up when browsing the workgroup node in Windows explorer. Upon further research I found out that "ping" worked for the ip addresses of the pc's, but not always for the computer names. Eventually I learned that without a WINS server on my network, NetBIOS name resolution didn't work properly. I was able to solve this by creating LMHOSTS lookup files on all of the pc's.
Another problem, that I originally linked to the network problem, was very slow file transfers to and from the Media Center PC. When copying a bigger file, the CPU usage went up to nearly 100% while the network usage remained at less than 25%. Over a 100 Mbps network, that equals about 3MB/s, while the harddisk is capable of 133 MB/s (UltraDMA 6). Only after I solved the network problem did I find out that this even occurred while copying files locally on the Media Center PC. First I tried all sorts of driver updates for motherboard and hard disk. After running a Samsung hard disk self diagnostics program and trying the disk in an external drive case, I came to the conclusion that the disk was fine. A forum post directed me to look at the IDE channel transfer mode in the device manager. It appears that Windows XP sets this transfer mode back to PIO indefinitely, after six DMA failures. This PIO transfer mode was the culprit for my high CPU load and low transfer rates. Getting it back to DMA mode requires an uninstall of the IDE driver. Windows XP automatically reinstalls it at the next reboot.
The good thing from all of this is that the Samsung hard disk utility enabled me to set the UltraDMA mode from the default 5 to the maximum of 6. That improves the theoretical transfer rate of the harddisk from 100 to 133 MB/s at no cost.
First of all, the network was behaving weird. Even though all three pc's had the same workgroup name specified, not all of the pc's were showing up when browsing the workgroup node in Windows explorer. Upon further research I found out that "ping" worked for the ip addresses of the pc's, but not always for the computer names. Eventually I learned that without a WINS server on my network, NetBIOS name resolution didn't work properly. I was able to solve this by creating LMHOSTS lookup files on all of the pc's.
Another problem, that I originally linked to the network problem, was very slow file transfers to and from the Media Center PC. When copying a bigger file, the CPU usage went up to nearly 100% while the network usage remained at less than 25%. Over a 100 Mbps network, that equals about 3MB/s, while the harddisk is capable of 133 MB/s (UltraDMA 6). Only after I solved the network problem did I find out that this even occurred while copying files locally on the Media Center PC. First I tried all sorts of driver updates for motherboard and hard disk. After running a Samsung hard disk self diagnostics program and trying the disk in an external drive case, I came to the conclusion that the disk was fine. A forum post directed me to look at the IDE channel transfer mode in the device manager. It appears that Windows XP sets this transfer mode back to PIO indefinitely, after six DMA failures. This PIO transfer mode was the culprit for my high CPU load and low transfer rates. Getting it back to DMA mode requires an uninstall of the IDE driver. Windows XP automatically reinstalls it at the next reboot.
The good thing from all of this is that the Samsung hard disk utility enabled me to set the UltraDMA mode from the default 5 to the maximum of 6. That improves the theoretical transfer rate of the harddisk from 100 to 133 MB/s at no cost.
Subscribe to:
Posts (Atom)
Posts
