http://wiki.linuxmce.org/api.php?action=feedcontributions&user=Trout&feedformat=atomLinuxMCE - User contributions [en]2024-03-29T05:05:34ZUser contributionsMediaWiki 1.24.1http://wiki.linuxmce.org/index.php?title=Backup-and-Restore&diff=7841Backup-and-Restore2007-12-21T14:38:43Z<p>Trout: removed strange text before redirect</p>
<hr />
<div>#REDIRECT [[Backup and Restore]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=DVD&diff=7840DVD2007-12-21T14:36:54Z<p>Trout: fixed xine link</p>
<hr />
<div>This page outlines information about DVD playing with LinuxMCE.<br />
<br />
As the [[Xine|Xine Player]] is used to play DVD, most of the settings can be changed in the $root/etc/pluto/xine.conf configuration directory. $root points either to the root directory of the Core/Hybrid, ie. the file is /etc/pluto/xine.conf, or one of the diskless orbiters. The diskless orbiters file is /usr/pluto/diskless/$orbiter-id/etc/pluto/xine.conf.<br />
<br />
== DVD Language ==<br />
To change the default DVD language from the current english, locate the line<br />
#input.dvd_language:en<br />
<br />
remove the hash and change it to the preferred language. For example, changing it to german, the line looks like this:<br />
input.dvd_language:de</div>Trouthttp://wiki.linuxmce.org/index.php?title=LinuxMCE_talk:Community_Portal&diff=7390LinuxMCE talk:Community Portal2007-11-26T13:50:19Z<p>Trout: /* Where are all of the Wiki Admins */</p>
<hr />
<div>==Moved from Zaerc's talk page==<br />
=== Categorization ===<br />
<br />
Hi Zaerc,<br />
I have noticed that you have moved a number of hardware articles from more specific categories, such as [[:Category:TV tuner cards]] to the more general category [[:Category:hardware]] and that you have nominated the more specific categories for deletion. Why was this? Surely the more specific categorization is helpful, especially when product codes often do not explain the nature of the equipment [[User:Lozzo|Lozzo]] 00:37, 7 October 2007 (MST)<br />
:Can we please hold fire on further re-categorization until further community consensus is sought. Many thanks [[User:Lozzo|Lozzo]] 00:59, 7 October 2007 (MST)<br />
::Why did you de-categorize everything from the TV tuner card category? [[User:Lozzo|Lozzo]] 01:05, 7 October 2007 (MST)<br />
<br />
<br />
Because I wanted to get back to where I was with organising things before people started to re-organise everything. See also the "community-proposal" page. I suppose I went a little overboard as I had to go through just about all the pages under "hardware" again anyway, which I wasn't to happy about in all honesty (I was getting tired, having to put everything back, and obviously didn't gave it enough thought).<br />
<br />
The original idea was to dump hardware into the main categories untill there is a bunch similar and then put them into their own sub-category as well. When I went through all the pages again I felt that would leave the "video" category as good as empty but now I realize I could have just added the tv-cards to both "video" and "tv-cards".<br />
<br />
My thought also was that categories with 1 or 2 pages in them wouldn't be very usefull and spread them out to much (the video category would be almost empty with the tv-cards removed) but now I see that wouldn't be a problem if they remain in the parent categories as well. So I agree with you on putting (at least) the TV-cards category back in, that makes it a lot easier to specificly find them. <br />
<br />
Unless you want to take categories away from pages again, I see no reason to hold fire, we can just add new (sub-)categories to the pages wherever suitable. And if anyone feels that a page really does not belong in a certain category they can just remove it with a little note on the talk page (see Nokia770 for example).<br />
<br>--[[User:Zaerc|Zaerc]] 05:16, 7 October 2007 (MST)<br />
<br />
:Firstly, yes I agree with you that there needs to be a critical mass of articles in a certain area before a sub-category is created.<br />
<br />
:Secondly, yes, I do want to make sure that articles do not appear once in a category and then again ''in a more general category''. This would involve, as you put it, 'taking categories away from pages'. I understand that this is not Wikipedia and I'm not suggesting that we should do everything the same. But the Wikimedia projects have conventions which have been subjected to a large amount of thought and debate and can be very useful guides for less mature documentation projects such as this.<br />
<br />
:Wikipedia sets the de-facto standard for how wikis should be organised - especially when we are using the same software (MediaWiki). Regardless of that, I think that having article A in one category and then a more general category is confusing and runs counter to the intention of how the category function was designed. It makes for general categories which are needlessly cluttered with articles which should be (and are) also categorized more specifically higher up the tree.<br />
<br />
:Having a list of articles in one place (so they are as you claim) may be appropriate for a small number of articles but this is not scalable for a large amount of documentation like we have. To quote directly from the Wikimedia guidelines:<br />
<br />
:''Each page is typically in at least one category. It may be in more, but it may be wise not to put a page in a category and also in a more general category.''[http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide:_Using_Categories#Category_considerations]<br />
<br />
:I do not think you have given a good enough reason to deviate from this. Of course, articles can be in more than one category. You give the examples of phones and orbiters. With the following category structure<br />
<br />
-Hardware<br />
|-Phones<br />
|-Orbiters<br />
<br />
: A device as you describe (which is not exclusively a phone or an orbiter) can appear in both the phone and orbiter category - but ''not'' hardware as this is a more general category. Pleas can we hold fire on further changes in this area until there is more agreement. I will ask others for comment. Cheers [[User:Lozzo|Lozzo]] 06:55, 7 October 2007 (MST)<br />
<br />
===Succinctly===<br />
In my opinion (and following established conventions) this is fine:<br />
<br />
-HARDWARE<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
This is not fine and makes for clutter:<br />
<br />
-HARDWARE --> Cisco smart phone article<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
[[User:Lozzo|Lozzo]] 07:05, 7 October 2007 (MST)<br />
<br />
::A phone is just as much hardware as it is a phone or an orbiter. And it is extremely convenient to have a category listing all the known hardware. As for the other more general categories, they make it easy to quickly find related solutions. Apart from that it is a lot easier to remove tags from pages then to add them, should they prove to be unecessary.<br />
<br />
::I see no reason to comply with policies of unrelated wikis, and: ''but '''it may be wise not to''' put a page in a category and also in a more general category'', does not seems like a very convincing argument. Even if it is an "established convention" elsewhere.<br />
<br />
::I just wish we could focus more on expanding and organizing instead of endless re-organization and debate on how it should be done. And why exactly do we need to have several threads discussing this on my talk page and not the forum or the hardware-category's talk page? --[[User:Zaerc|Zaerc]] 08:45, 7 October 2007 (MST)<br />
<br />
:::Okay I've now moved everything here. Forget other wikis for the time being. There is still obviously some disagreement here which we need to resolve by coming to some kind of consensus decision. Can we ''please'' hang fire on further changes in this area for the time being? [[User:Lozzo|Lozzo]] 10:19, 7 October 2007 (MST)<br />
::::You are completely correct to say "A phone is just as much hardware as it is a phone or an orbiter." But this is accounted for in the example below because both phones and orbiters are '''subclasses''' of hardware. It doesn't need to be repeated again in the hardware category - this is implicit.<br />
<br />
-HARDWARE<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
::::As a compromise, how about we have a list of all hardware as an article in itself? This would surely satisfy your requirement for a complete hardware list in one place? [[User:Lozzo|Lozzo]] 10:24, 7 October 2007 (MST)<br />
<br />
::I'm in favor with Lozzos proposal at the top here, I think this makes sense and also as Lozzo says we could have a long alphabetical list with all hardware that's easy to search through if it's needed. --[[User:Samme|Samme]] 11:03, 7 October 2007 (MST)<br />
<br />
<br />
Unless somebody comes up with some good reasons to remove all the pages describing hardware from the hardware category, I see little reason for me to stop organizing the hardware section as I have been doing since before you came along (no offence intended). I'm really not that interested in acedemic debate on grouping theory, whether something "isn't needed" or "implict" seems hardly worth the discussion. As for pages with lists, that simply does not work, you can find a whole bunch of attempts in the "hardware lists" category. --[[User:Zaerc|Zaerc]] 11:30, 7 October 2007 (MST)<br />
<br />
<br />
:Zaerc, I'm not saying we should necessarily go one way or the other for the time being. But I think it would be reasonable and proper to have a little bit of a discussion with a few of us to get some group consensus before we press on in any particular direction with regards the way we categorize/list things. I'd be very interested to hear your further thoughts on why you believe a hardware list is unworkable.<br />
<br />
:Also, what do you reckon should be the minimum number of articles to justify a category?<br />
<br />
:[[User:Lozzo|Lozzo]] 14:20, 7 October 2007 (MST)<br />
<br />
<br />
::I think the absolute minimum would be one, but ideally the more the merrier. If you look at the [[RCS TXB16]] for example, it is the only thermostat we have (afaik) in the wiki. Still I think it is a good idea to give this device a Thermostats category so that the people looking through automation subcategories (for example) will find it there. And somebody looking for info on that particular device instead will be able to find it in the hardware category without having to go through sub-categories first.<br />
<br />
::Now if you want to make and maintain a seperate list that is fine with me, I'm not having that discussion again. And so far I still haven't seen any good argument to remove all the hardware from the hardware category. --[[User:Zaerc|Zaerc]] 15:53, 7 October 2007 (MST)<br />
<br />
<br />
:::Zaerc, as far as I am aware, you don't have executive fiat on this wiki. With all due respect, what I'm hearing from you at the moment is: "I've decided what's going to happen with regards categorization, I don't care what anyone else says and I'm not going to debate the matter further". I've outlined my arguments at length and in a civil manner. This has included a compromise proposal (supported by Samme) and I do not feel you have given a proper explanation of why you don't think it's workable. You have instead responded by saying you won't discuss the matter further ("I'm not having that discussion again"). [[User:Lozzo|Lozzo]] 11:18, 8 October 2007 (MST)<br />
<br />
<br />
::::You have outlined your opinion over and over, I still see no real arguments why the hardware has to be removed from the hardware category per se. Apart from that, why exactly do I need to go over the hardware-list discussion again? I see no obligation on my part to explain to you why hardware-lists do not work. --[[User:Zaerc|Zaerc]] 05:56, 9 October 2007 (MST)<br />
<br />
<br />
==Lozzo's compromise proposal==<br />
Re-iterating the above...<br />
<br />
<br />
:''Just to point out the obvious, this is no compromise at all.'' --[[User:Zaerc|Zaerc]] 05:56, 9 October 2007 (MST)<br />
<br />
<br />
===Current situation===<br />
# Zaerc wants somewhere where there is "a category listing all the known hardware."<br />
# He has achieved this as follows by listing articles in one category and also in its more general parent category as follows:<br />
<br />
-HARDWARE --> Cisco smart phone article<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
===Disagreement===<br />
#Lozzo believes that this:<br />
##Violates the [http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide:_Using_Categories#Category_considerations generally accepted convention for how categories should be structured]<br />
##Goes against the elegant principle of categories - the whole reason the function was added to MediaWiki<br />
##Makes for very cluttered general categories the further down the category tree you go<br />
##In the more general categories, for example harware, the user is presented with an arbitrary list of product names which do not necessarily describe what a product is. How are we supposed to know what an ''LG 42LB5D'' is or a ''Leadtek DTV1000T'' if they are in one big homogenous general category?<br />
<br />
===Proposed compromise solution===<br />
*'''To satisfy Zaerc's requirement for a single place to list all known hardware, we can maintain a single list article'''. I (lozzo) am very happy to help construct this in partnership with Zaerc. In fact, this would be better than putting all harware in the general hardware category because it would allow notation.<br />
<br />
*The articles should be tagged with categories as follows and according to convention: <br />
<br />
-HARDWARE<br />
|-PHONES --> Cisco smart phone article<br />
|-ORBITERS --> Cisco smart phone article<br />
<br />
This compromise is supported by Lozzo and Samme (see above).<br />
<br />
Please comment below. [[User:Lozzo|Lozzo]] 11:18, 8 October 2007 (MST)<br />
<br />
==Comments==<br />
I am actually in agreement with Zaerc on this one. As the system is now. the Subcategories show up first, so the initial impression is to click the subcategory. I think a list would be to difficult to maintain as more and more people start adding content to the site. I vote for putting the articles in as many categories as they fit, including Hardware. <br />
<br />
Do you know why there is a Category: Hardware List and Hardware?<br />
--[[User:Rwilson131|Rwilson131]] 14:49, 8 October 2007 (MST)<br />
<br />
I still see no valid argument whatsoever to remove all the hardware from the hardware category, no matter how often you repeat your opinions. And "my requirement" is perfectly satisfied the way things are now. --[[User:Zaerc|Zaerc]] 16:08, 8 October 2007 (MST)<br />
<br />
'''''What the hell are you doing [http://wiki.linuxmce.org/index.php?title=LinuxMCE_Wiki_talk:Community_Portal&diff=next&oldid=6575 indenting my comments to be reactions to other comments???]''''' --[[User:Zaerc|Zaerc]] 15:12, 9 October 2007 (MST)<br />
<br />
::Yes, but ''mine isn't''. I am trying to propose a reasonable compromise where we can both achieve what we want. Please find below stuff from RWilson form my talk page. I will respond when I have time. [[User:Lozzo|Lozzo]] 17:03, 8 October 2007 (MST)<br />
<br />
I think we always need to start at the Main Page and determine how is the person most likely going to get to the proper information. Currently, we are confusing ourselves. Take for instance<br />
<br />
Person wants to find out if his system is going to work?(Try and imagine your first visit here were you confused?)<br />
* [[Main Page]]<br />
::The only link for the main page is to<br />
* [[Hardware]] an article about the basics<br />
::Here there are several links to Information about hardware.<br />
**[[What hardware I will need]]<br />
**[[:Category:Hardware]]<br />
::I logical next choose is [[What hardware I will need]]<br />
*[[What hardware I will need]]<br />
::Now this page has several links including [[Tested good hardware]] [[Tested bad hardware]] and [[Suggested hardware]], but the Category at the bottom is [[:Category:Hardware Lists]]<br />
::The [[Suggested hardware]] has items that state they do not work (this should not be there in my opinion)<br />
<br />
I think if we are going to have lists, then there should only be two, Bad Hardware and Suggested Hardware.<br />
Currently we also have [[Recommended Accessories]] which is essentially worthless.<br />
<br />
I can really see no need for [[:Category:Hardware Lists]] as the Categories page is already a list, which is self generated. I am a firm believer in KISS (Keep It Simple Stupid). The software is complicated enough, so our wiki should be simple and reflect the most common problems people are currently facing. ie Display issues, MythTV issues.<br />
Just my two cents worth!<br />
--[[User:Rwilson131|Rwilson131]] 15:01, 8 October 2007 (MST)<br />
<br />
:: I agree with you on this one, it feels to me that this category (Hardware lists and Recommended accessories) isn't necessary at all, I also agree with you that we should keep things simple and also we should make this wiki a simple place to navigate, nopt clutter it up with loads and loads of unnecessary categories etc. --[[User:Samme|Samme]] 00:09, 9 October 2007 (MST)<br />
<br />
:'''A category system is a tree-structure'''. If categories ANTS and SPIDERS are in category CREEPYCRAWLIES then the red ant can be put in the ANT category and it will follow logically that it is ''also in the category CREEPYCRAWLIES''. What you are effectively doing is listing things twice. The MediaWiki category system was never intended to be used in this way - i.e. to create large lists. This is what list articles are for!<br />
<br />
:To pick up on the point made by RWilson, a new user may click on the hardware category. Under the scheme you advocate he will be presented with a page that includes every single piece of hardware entered into the wiki. This includes many brand names and product numbers/codes which will make no sense at all - they didn't to me when I arrived which is why I set about working out what they were and categorizing them (as per nearly every other wiki on the planet). With respect, suggesting that an exhaustive list of hardware will be helpful to a new user is analgous to reading a book by starting at the index: needlessly confusing and overwhelming.<br />
<br />
:'''I am not suggesting that the current lists we have on board are any good''' - they aren't. But that doesn't mean that they have to stay that way. If you want an exhaustive list of hardware then create one in an article. If it has proper sections then it shouldn't take long to keep it up to date - just compare categories with sections in the long list [[User:Lozzo|Lozzo]] 17:50, 8 October 2007 (MST)<br />
<br />
::To emphasise once more, a category is not an "automatically generated list" as has been claimed above; they are two distinct concepts - go and ask anyone on another wiki using the MediaWiki software. If anyone is interested, take a look at this[http://en.wikipedia.org/wiki/Wikipedia:Categories%2C_lists%2C_and_series_boxes]. I am only linking to it because we are using the ''same software'' for our wiki, which is designed to be used in a particular way.<br />
<br />
:::I am not sure I really understand this point as anytime I have ever put something in a category it automatically shows up on the Category's Page. --[[User:Rwilson131|Rwilson131]] 09:07, 9 October 2007 (MST)<br />
<br />
::Another relevant point, each category page can only hold 200 articles before you have to start going through them page by page. [[User:Lozzo|Lozzo]] 18:05, 8 October 2007 (MST)<br />
<br />
:::This is worth noticing, cause I doubt someone will go through endless amount of pages to find there make/model of a tv in the articles listed under hardware category, it's much simple going like "hardware > tv > my model". --[[User:Samme|Samme]] 00:09, 9 October 2007 (MST)<br />
:::This is probably the most noteworthy reason for making this change I have seen. If an actually list solves this problem then I am for a List and taking Items out of the Hardware Section. If this does not fix this issue then leave them alone. --[[User:Rwilson131|Rwilson131]] 09:07, 9 October 2007 (MST)<br />
<br />
<br />
Like I said before, I am not interested in acedemic grouping theory, nor am I interested in how other, totally unrelated wikis are organized (whether they use the same software or not). Please come up with a good reason why all the hardware should be removed from the hardware category, until then I feel there is little use in rehashing your opinions over and over and over again. --[[User:Zaerc|Zaerc]] 04:46, 9 October 2007 (MST)<br />
<br />
<br />
:I have tried to outline my arguments in a clear, detailed, patient way. I have given several reasons why I believe we should change the current system advocated by Zaerc. I am sorry he does not agree or work with me or my compromise proposals but at least I have outlined my ideas at length and tried to explain (again at length) why the current system doesn't work. The arguments given in favour of keeping the status quo are as follows (please let me know if I've missed some off):<br />
<br />
#This is how things were done before up to now<br />
#A big list of hardware is useful, we have decided to use categories to do this and are going to stick with that<br />
<br />
:'''I have proposed a compromise solution where everyone can get what they want''' - we'll have an exhaustive list (which I don't deny is very useful) ''and'' we'll have an elegant clean taxonomy of articles by using the category system as it was intended. I cannot resist commenting that repeatedly describing my comments as "acedemic grouping theory" is a straw man argument and an excuse to not properly engage in a discussion. The onus is not only only on me to come up with something that Zaerc agrees with - he has to defend his position as well. [[User:Lozzo|Lozzo]] 07:00, 9 October 2007 (MST)<br />
<br />
<br />
::'''Your "compromise" is no compromise at all, and certainly not a "solution".''' Just in case you haven't noticed by now, the only one really interested in this discussion is you. --[[User:Zaerc|Zaerc]] 08:24, 9 October 2007 (MST)<br />
<br />
<br />
The more that I think about this topic, the more it seems like we are missing the point. If the way the mediawiki software was designed is to not use the Categories as list then we need to best utilize the software. After all we are trying to educate people on the best way to utilize LinuxMCE. It would not make any sense for us to tell people to do it one way even if the system was not designed that way. <br />
<br />
Personally, I think we need a list of Hardware that works and a list of hardware that does not. How all this is categorized is really semantics. I think that the the admins need to make a decision and go with it. Most of us will follow suit, as this does matter to us, and as admins you will have to figure out how to handle those that do not. I just need to know when I post next time, how you want it done. Let us move on. --[[User:Rwilson131|Rwilson131]] 09:07, 9 October 2007 (MST)<br />
<br />
:Thanks for your comments. I agree that we need lists of hardware that works and does not, and perhaps also a list of hardware broken down by type (TV card, X10 devices etc) so we can see it in one big list. I suppose the debate here is how we achieve this (with categories or lists).<br />
<br />
:You're right, we do need to move on and I hope we can reach a decision - preferably a compromise if one can be found. This is something I feel strongly about but I'm honestly not trying to prolong this discussion needlessly. Thanks again for your thoughts :-) [[User:Lozzo|Lozzo]] 14:13, 9 October 2007 (MST)<br />
<br />
<br />
::I agree that we already have those things, neatly categorized, so can we now finaly please get back to adding ''our'' experience with the hardware ''we'' have? --[[User:Zaerc|Zaerc]] 15:12, 9 October 2007 (MST)<br />
<br />
==Reasons why we shouldn't use lists as categories==<br />
*You can only order articles in a category alphabetically.<br />
*The articles cannot be ordered into sections or subsections to reflect different types of hardware.<br />
*A category with hundreds of items cannot be moved except by editing hundreds of articles.<br />
*After 200 articles you have to keep clicking to view the next page.<br />
*No annotation is possible at all.<br />
*The product code names for electronic hardware are often arcane and give ''no indication whatsoever'' about what the hardware actually does. How is it helpful to have [[RCA HC60RX]] and [[Caddx NX-8E]] in the same category? It isn't even obvious WHAT they are! In fact, one is an alarm panel and the other is a piece of automation equipment. But you certainly wouldn't know this from looking at the root hardware category!<br />
<br />
[[User:Lozzo|Lozzo]] 07:00, 9 October 2007 (MST)<br />
<br />
==Reasons why we should maintain a hardware list==<br />
*The different types of hardware can be ordered in any way which helps user understanding - not just alphabetically but my manufacturer or type for example.<br />
*You can have sections for different types of hardware/manufacturers.<br />
*A list is releatively easy to maintain. Instead of putting <nowiki>[[Category:Hardware]]</nowiki> in the article we simply add in a reference to the new hardware article in the appropriate section of the hardware list.<br />
*You can add additional notation.<br />
*Everything appears on the same page without having to click 'next'<br />
*Lists are much easier to build (fill up) than categories, because entries can be gathered, cut and pasted in from searches and other sources. For example, we could use this to have a list (or section) of hardware without articles in our wiki.<br />
<br />
[[User:Lozzo|Lozzo]] 07:00, 9 October 2007 (MST)<br />
<br />
== Same old, same old ==<br />
<br />
Excuse me but I have things to do besides filling talk pages with endless (not to mention pointless and utterly boring) discussion. --[[User:Zaerc|Zaerc]] 08:24, 9 October 2007 (MST)<br />
<br />
<br />
:I'm not going to be [[Talk:Serial Hack|goaded into a flame war]] no matter how rude you are. You are clearly incapable or unwilling to engage in a constructive way with other editors with whom you have a disagreement. If you "have better things to do" then I suggest you leave this talk page alone until you decided you actually want to engage with the arguments I have put forward. RWilson disagrees with me - do you see him flinging insults around? [[User:Lozzo|Lozzo]] 14:04, 9 October 2007 (MST)<br />
<br />
<br />
::I have already engaged your arguments earlier but all you seem to want to do is rewording your opinions over and over again. If pointing that out is "flinging insults around" then maybe you should just leave the hardware category alone, it was doing just fine without your "help". And yes, it is getting a bit annoying to have to convince new people like you (who aparently have little else to contribute) not to keep taking things away, I for one would rather spend that time and effort adding usefull things instead. --[[User:Zaerc|Zaerc]] 15:49, 9 October 2007 (MST)<br />
<br />
<br />
= Separating development-related stuff into the Trac Wiki =<br />
All,<br />
I suggest to move all development-related pages and information from this wiki to the Trac environment danielk has set up. This would lead to a clear separation between a user wiki (with information on supported hardware, manuals, howtos and so on) and a development wiki (howto build, documentation of sources...). Any comments? --[[User:Chriss|chriss]] 05:04, 20 October 2007 (MST)<br />
<br />
: This is not going to be that simple. Take a look at [[Rip a CD/DVD to the Core]]. I have been working on reorganizing the User's Manual and most of the original pages from Pluto are formated in this manner. One would have to go through every single page and remove the programmer related information and move it to Trac. Certainly there are several pages that can simply be moved, but the vast majority of the Programmer related information co exists on user related information page as well.--[[User:Rwilson131|Rwilson131]] 08:14, 20 October 2007 (MST)<br />
= Where are all of the Wiki Admins =<br />
I have been working on updating the documentation and updating the screenshots. There was all of this discussion, but it has been very quiet lately. I am planning on continuing to update the pages and continue to piece together a working [[User Manual]]. Is there a way that I can get the ability to delete some of the images that I uploaded? I pulled from the wrong directory and I would like to delete the older images as they do not match with the current design of either the orbiters or the LinuxMCE Admin Website. --[[User:Rwilson131|Rwilson131]] 22:08, 2 November 2007 (MST)<br />
:You shouldn't need to delete, just use "Upload a new version of this file"</div>Trouthttp://wiki.linuxmce.org/index.php?title=Aspect_ratio&diff=7238Aspect ratio2007-11-19T13:23:14Z<p>Trout: </p>
<hr />
<div>#REDIRECT [[Aspect Ratio]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=User:Rwilson131&diff=7046User:Rwilson1312007-11-08T04:02:38Z<p>Trout: </p>
<hr />
<div>Man! You make a lot of changes. Thanks!</div>Trouthttp://wiki.linuxmce.org/index.php?title=DVB_Cards&diff=6976DVB Cards2007-11-05T14:06:42Z<p>Trout: don't know why this got lost from the hardware category page</p>
<hr />
<div><br />
== Description of DVB Cards:==<br />
<br />
LMCE uses mythtv as media player and some people use DVB cards as input in Mythtv.<br />
(I will write a tuto for vdr if i manage to put my hands on vdr wrappers.)<br />
<br />
There are different types of DVB cards they differ in the kind of signal / band / compression algorythms and some have mpeg decoders that allow the card to process all the video so the processor is free to do the rest on your host.<br />
<br />
- The DVB-S cards are used to receive satellite signals K Band / PSK QPSK 8PSK etc... <br />
- The DVB-T cards are used to receive terestrial signals VHF/UHF<br />
- The DVB-C cards are used to receive coaxial cable tv<br />
<br />
Those cards should work with lmce as long as they are supported by the Linux kernel.<br />
<br />
First check dmesg | grep dvb should tell you if the card is seen properly and also tell you wich device the card uses (/dev/dvb/adapter0/frontend0 and so forth.)<br />
<br />
In order to use the card you will need to scan for channels.<br />
<br />
To do so you will need to install dvb-utils packages:<br />
<br />
sudo apt-get install dvb-utils<br />
<br />
sudo scan /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2 >channels.conf<br />
<br />
If you dont want any radio or encrypted channels:<br />
<br />
sudo scan /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2 -x0 -t1 >channels.conf<br />
<br />
If you are getting to few channels:<br />
<br />
sudo scan /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2 -x0 -t1 -n >channels.conf<br />
<br />
<br />
Hint: if you can't get any signal lock try to get the frequencies looking on your tv or satellite receiver then input them in the /usr/share/doc/dvb-utils/../..........<br />
<br />
You can even make your own file copying the model in the dvb-x category.<br />
<br />
Once you have populated the channels.conf file you can setup mythtv tu use your card<br />
(mythtv will tell you if it sees the DVB card)<br />
<br />
Then in the channel scan section use the channels.conf method and put the path to your file.<br />
<br />
If mythtv finishes the scan then you can fire up your MD to watch tv.</div>Trouthttp://wiki.linuxmce.org/index.php?title=Current_events&diff=6732Current events2007-10-17T17:29:14Z<p>Trout: </p>
<hr />
<div>Visit the [http://linuxmce.org/smf/index.php?board=350.0 Upcoming features forum] to discuss new features, changes or ideas. If you are willing to offer some cash or other compensation to a developer to get something done right away, visit the [http://linuxmce.org/smf/index.php?board=349.0 Help Wanted forum].<br />
<br />
When a developer has decided to implement some new feature or change, please edit this wiki to add a brief summary including a link to the original forum topic for this new idea, so other users can post to that topic to discuss this, and where you will post updated progress info. Visit the [http://linuxmce.org/wiki/index.php/Contacts Contacts Page] to find developers who can commit your work to the main LinuxMCE branch, or to request svn write access.<br />
<br />
This page lists the features which developers we are working to implement in the next release. There is also a forum dedicated to discussing features here . Please post to this page only those features which have been decided to be included.<br />
<br />
Read about the long-term goals and strategy here: [[History|History of LinuxMCE, why I started this project, and the goals]]<br />
<br />
<br />
----<br />
== Google Summer of Code Ideas: ==<br />
<br />
'''internet radio''' <br />
Integrate internet radio into the existing media menu option so radio stations can be browsed the same way local media can.<br />
<br />
'''internet tv / videos.google / youtube'''<br />
Integrate these online video sources into the existing media menu option so this video can be browsed the same way local media can.<br />
<br />
'''gsd events'''<br />
The embedded Ruby interpretor presently only handles controlling devices; ie processing commands. The same code could be adapted in reverse to respond to events.<br />
<br />
'''Standardized to be included in Ubuntu'''<br />
LinuxMCE still has a lot of non-standard scripts that Pluto wrote for use in commercial, black-box systems, which need to be rewritten in a more standard manner so that LinuxMCE plays nicely by Ubuntu's rules and be accepted into Ubuntu's main repository and included in their build.<br />
<br />
'''Download audio podcast/video podcast'''<br />
A way with the GUI to subscribe to podcasts, and have them automatically downloaded and aggregated with the media in the home. Including playcount so a list of not listened to podcasts can be created.<br />
<br />
'''Capture video from firewire camera'''<br />
The current plug and play detection engine already recognizes firewire digital camcorders. There should be a very rudimentary, simple 'capture' option that appears on screen to do basic video capture and save it to the managed media. Users can use a video editor like Kino for real editing; this is just for quick capture.<br />
<br />
'''Better organize and manage photos'''<br />
The current UI could use some optimization to make it work better for managing photos.<br />
<br />
<br />
== Current Development ==<br />
[[What modules are in development?]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Serial_Hack&diff=6168Talk:Serial Hack2007-10-01T01:30:18Z<p>Trout: /* Trout: Please stop vandalizing this page */</p>
<hr />
<div>When you figure out a better way, edit the article. Until then this is just discussion. [[User:Trout|Trout]] 08:06, 21 September 2007 (MST)<br />
<br />
:When you have something usefull to add for a change, edit the article. Otherwise, quit pestering the people that do --[[User:Zaerc|Zaerc]] 12:59, 21 September 2007 (MST)<br />
<br />
I am at a loss to understand this battle. The original commit was another way to accomplish the same thing. There are a lot pages on this site that have very similar issues. What is the harm in giving people more than one option even if that option is one in the same. If nothing else it offers all of us an opportunity to learn something different. The second option (perl) is another example. Personally I feel both should be left on the page and just remove the editorial commitments as these are truly the things that belong in discussions. <br />
<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Good_practice Good Wiki Practices]<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Behavior_that_is_unacceptable Behavior that is unacceptable]<br />
--[[User:Rwilson131|Rwilson131]] 09:27, 23 September 2007 (MST)<br />
<br />
I'm sure AVJohn is very happy with you pissing all over his page just to prove a point Trout. And how nice of you to make it personal. So thanks for the lessons on properly maintaining a wiki, you're a real champ. --[[User:Zaerc|Zaerc]] 02:50, 24 September 2007 (MST)<br />
<br />
:Keep the articles clean and use the discussion-pages for...ahh, discussions! And when you reply, please indent, it's so much easier to follow a discussion that way. --[[User:Samme|Samme]] 02:58, 24 September 2007 (MST)<br />
<br />
:Zaerc, you keep making it more clear that you don't understand how a wiki works. First of all, I tried to be nice by just moving the discussion piece of the page to the discussion area. This was not acceptable to you, and you moved it back with a nasty comment. I tried again with the same result, and a worse comment from you. So, IMO you are the one who made it personal. Second, when you sait "... all over <strong>his</strong> page", you are completely wrong about page ownership. The page belongs to the wiki and it's not personally AVJohns, this misunderstanding of yours is exactly what caused you to be upset to see "your text" moved to the discussion page. Having the discussion moved to it's correct place is not something to take personally. BTW: you're welcome for the wiki lessons. [[User:Trout|Trout]] 04:50, 24 September 2007 (MST)<br />
<br />
::So I'm the one putting a personal rant aimed at you on that page? Have some respect for the people who actually contribute, because it seems more like all the pages here belong to you. --[[User:Zaerc|Zaerc]] 07:40, 24 September 2007 (MST)<br />
<br />
:::Yes, this is an insult to me "please don't edit pages unless you actually have something to add". I feel that I am adding clarity when I move your comments to the discussion page. You are personally attacking me when you imply I am not adding anything. "go find something usefull to do, instead of pestering people that actually add information" Again another insult, implying that I have nothing better to do than mess with your addition for no purpose. Also discounting my contributions as though they are somehow less important than yours. I don't think that all the pages belong to me and I have stated so. I am sorry if you perceived that, it was not my intent. <br />
:::I really think that the page is better served without different options of editing a file. The page is about detecting serial ports, not how to create a text file. It should be enough to say "create a file like this ..." IMO this would serve the users best. [[User:Trout|Trout]] 09:07, 24 September 2007 (MST)<br />
<br />
::'''Hey hey hey!''' No you have to stop, both of you, we're in this together, work with each other, not against each other, now we end this discussion and continue the work with the wiki - '''and''' from now on discussions goes on to the pages that are designated for discussions so we can stick to the facts in the articles. Do we have a agreement? --[[User:Samme|Samme]] 09:49, 24 September 2007 (MST)<br />
<br />
:::Samme, Of course I'm in agreement, this was my point from the beginning. [[User:Trout|Trout]] 10:57, 24 September 2007 (MST)<br />
<br />
::::You guys make me sick with all your hypocritical bullshit. And then that pathetic excuse that this is to "serve" the users, seems pretty obvious this is '''not''' done in ''their'' best interest. But I guess coming forward to say what it is really about would actually take a pair. --[[User:Zaerc|Zaerc]] 11:56, 25 September 2007 (MST)<br />
<br />
Hi, i took the liberty to add a new page to the wiki [[Editing_Text]] where I put the tricks the two of you offered.<br />
<br />
And I linked to the new page from the appropriate passage within the article...<br />
<br />
I hope, this will end the fight... And I hope I will read a lot from both of you on this wiki in the future.<br />
<br />
Best Regards, [[User:Chewi|Chewi]]<br />
<br />
== Comment about better solutions by AVJohn ==<br />
<br />
I would suggest, that we leave the comment about finding better versions in there.<br />
The reason is that the article describes a hack and AVJohn says in his article that the new script is inferior to the original script.<br />
So the request for other/better solutions is an important notice to<br />
<br />
A) let people know it is only a hack<br />
<br />
B) remind others that have acomplished it a different way to add their version<br />
<br />
C) make other Developers make a "more undirty" workaround<br />
<br />
D) remind actual LMCE-Developers (no offence to AVJohn) to provide an improvement/update that makes the hack unnessasary.<br />
<br />
So I endorse to go back to the previous version for those reasons. Feel free to add your oppinions.<br />
<br />
Best regards, --[[User:Chewi|Chewi]] 07:00, 27 September 2007 (MST)<br />
<br />
<br />
The discussion belongs here IMO. Otherwise it grows out of control into a forum. Not that there's anything wrong with the discussion, but it just doesn't belong on the main page. Think about it from the point of view of someone who just wants to know the best way right now. They don't want to wade through a lot of discussion text to get the answer.<br />
<br />
A) they should know it's a hack by the title<br />
B) someone who's already accomplished it probably either 1) wants to edit the wiki with their knowledge 2) is just checking out how wiki recommends it. The mere fact that it's a wiki is enough encouragement IMO.<br />
C) okay, but they don't want to wade through a pile of blogs to see the best result. They only would want to see the best result (the wiki page) and compare it to what they have in mind.<br />
D) same as C)<br />
[[User:Trout|Trout]] 07:43, 27 September 2007 (MST)<br />
<br />
:''(Never said anything on the main-page ???)'' Basically, you're right with all of your points. But I still think that the extra-encouragement here would be a good thing, as a wiki-page without a comments-section feels like a final statement and feels like allowing editing only by "the inner circle", which is not the case here. This needs the extra-input. This is at least how I feel about wikis. Therefore, I stay with my recommendation. Regards--[[User:Chewi|Chewi]] 08:06, 27 September 2007 (MST)<br />
<br />
::''(I never said anything about main-page either.)'' I said "main page" e.g. There is a main page for every article (the link is labeled 'article') and there is a discussion for every article. That's what I was referring to. I will try to use 'article' now. You can have your opinion about "the inner circle" concept, but I don't feel that way. Also I believe that others know how to use a wiki and that the expectation is user participation. Also, you havn't said anything about the mess it'll make or how to prevent a flame war on the article instead of where it belongs (the discussion) [[User:Trout|Trout]] 08:23, 27 September 2007 (MST)<br />
<br />
:::Ok, that must have been a missunderstanding. Of course I think that discussions about the article itself belong here, just as we are having it now. And I don't want to move that part to the main page. Just for short annotations an area on the mail-article-page ;) is what I prefer. And an area for comments and annotations that does not serve as a forum or discussion-replacement, does not support flame wars. Those can happen everywhere, but I don't see why they should happen here in particular.<br />
<br />
:::I'm still not convinced, but it is not up to me. Let's see, if there are additional oppinions on this. Until then, lets leave it as it is right now, without comments. Best regards --[[User:Chewi|Chewi]] 09:48, 27 September 2007 (MST)<br />
<br />
== does this fix the "serial hack" ? ==<br />
<br />
does this fix the "serial hack" ? [[Blocking Access To Serial Port]] [[User:Trout|Trout]] 12:21, 28 September 2007 (MST)<br />
<br />
== Trout: Please stop vandalizing this page ==<br />
<br />
Somebody cleaned up the mess you made and now you have to spit in his face by continuing to vandalize the page. Your arguments of percieved problems are insignificant and irrelevant. I don't think this is apropriate behavior for a "wiki admin". Please join in on the forum discussion if you feel this is so important. [http://forum.linuxmce.org/index.php?topic=2593.15]. --[[User:Zaerc|Zaerc]] 04:42, 30 September 2007 (MST)<br />
<br />
What specifically are you talking about? I think you are sadly confused. [[User:Trout|Trout]] 10:03, 30 September 2007 (MST)<br />
<br />
:I think that becomes pretty clear in the discussion we are having on the forum. You can also check the page history if you have such a short memory. Meanwhile, please don't edit my comments either. --[[User:Zaerc|Zaerc]] 12:11, 30 September 2007 (MST)<br />
<br />
And yet you continue to chose vandalism over debate by even removing comments here. Please stop it. --[[User:Zaerc|Zaerc]] 16:31, 30 September 2007 (MST)<br />
<br />
You want debate? I have not '''vandalized''' anything. Yet you try to put false comments on the page to make yourself feel superior. The only thing that is clear is that you have a lot of growing up to do. There is no reason for this section on the discussion page or anywhere else, This is more of a discussion between you and me, that doesn't concern anyone else here. If you have a problem with me, I don't really care. I tried numerous times to be kind to you, to no avail. This is a wiki and the content will change whether you like it or not. When you contribute, it becomes the Wiki's text, and doesn't belong to you anymore. The same is true for me and everybody else... and yet you cannot grasp that simple concept. So I recommend that you either contribute in a wiki-community way or not at all. I have nothing against you and I wish you'd accept that your text will change and continue to contribute in spite of it. I'm done having a flame war with you, and I will remove this section of the discussion page soon. [[User:Trout|Trout]] 18:30, 30 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Hauppauge_WinTV-PVR-150_MCE&diff=6140Hauppauge WinTV-PVR-150 MCE2007-09-30T21:55:43Z<p>Trout: </p>
<hr />
<div>* Manufacturer info: http://www.hauppauge.com/pages/products/data_pvr150mce.html<br />
* This card is automatically detected by LinuxMCE and is easily setup via the [[Setup Wizard]]<br />
<br />
===WinTV-PVR-150 includes:===<br />
<br />
* 125 channel cable ready TV tuner<br />
* Composite/s-video input to connect to VCR or camcorders<br />
* High quality MPEG1/MPEG2 video and audio encoder<br />
* dbx-TV stereo decoder (Nicam stereo decoder in Europe)<br />
* IR remote control <br />
<br />
The WinTV-PVR-150's TV tuner and S-Video/composite video inputs are for either [[PAL]] or [[NTSC]].<br />
<br />
===MPEG record specifications:===<br />
* MPEG1 recording at 1150K bits/sec (Video CD data rate)<br />
* MPEG2 record datarates:<br />
**2MBit/sec, 4MBit/sec, 6Mbit/sec, 8Mbit/sec, 12Mbit/sec.<br />
**Selections for DVD Standard play (8MBitsec), DVD Long Play (4MBit/sec) and DVD Extra Long Play (2MBit/sec)<br />
* NTSC format* at 29.97fps: Full D1: 720x480, MPEG1: 352x240<br />
* PAL format* at 25fps: Full D1: 720x576, MPEG1: 352x288<br />
* Audio capture formats: 32/44.1/48 KHz, 16bit stereo, 192/224/384Kbits/sec<br />
* Video digitizer: 10 bits<br />
**Chroma sampling: YUV 4:2:2<br />
**Four line adaptive comb filter for both NTSC and PAL to remove dot crawl<br />
**Fast video locking for security camera applications<br />
* Video file format: .MPG<br />
<br />
===System Requirements:===<br />
* Pentium® III processor 1.2GHz or faster, 128MB RAM and 10GB disk drive minimum recommended<br />
* Free PCI slot<br />
* Sound card<br />
* DVD or CD-RW writer (optional for burning DVDs or Video CD’s)<br />
* VGA card (PCI or AGP) which supports video overlay (NVidia, S3, ATI, etc.) <br />
<br />
===Troubleshooting===<br />
# Currently the ivtv-firmware packages are not being installed by default along with the other ivtv packages, which means that the card is not initialized properly. The fix is simple: Alt-Ctrl-2 into a session and issue the following commands:<br />
apt-get install ivtv-firmware<br />
rmmod ivtv<br />
modprobe ivtv<br />
This should give you a working card<br />
<br />
[[Category: TV tuner cards]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Lozzo&diff=6136User talk:Lozzo2007-09-30T21:53:35Z<p>Trout: lots of progress!</p>
<hr />
<div>Hi Lozzo.<br />
You're doing a lot of great stuff! [[User:Trout|Trout]] 14:53, 30 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Serial_Hack&diff=6123Talk:Serial Hack2007-09-30T20:13:12Z<p>Trout: Removed libelous, non-constructive comments.</p>
<hr />
<div>When you figure out a better way, edit the article. Until then this is just discussion. [[User:Trout|Trout]] 08:06, 21 September 2007 (MST)<br />
<br />
:When you have something usefull to add for a change, edit the article. Otherwise, quit pestering the people that do --[[User:Zaerc|Zaerc]] 12:59, 21 September 2007 (MST)<br />
<br />
I am at a loss to understand this battle. The original commit was another way to accomplish the same thing. There are a lot pages on this site that have very similar issues. What is the harm in giving people more than one option even if that option is one in the same. If nothing else it offers all of us an opportunity to learn something different. The second option (perl) is another example. Personally I feel both should be left on the page and just remove the editorial commitments as these are truly the things that belong in discussions. <br />
<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Good_practice Good Wiki Practices]<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Behavior_that_is_unacceptable Behavior that is unacceptable]<br />
--[[User:Rwilson131|Rwilson131]] 09:27, 23 September 2007 (MST)<br />
<br />
I'm sure AVJohn is very happy with you pissing all over his page just to prove a point Trout. And how nice of you to make it personal. So thanks for the lessons on properly maintaining a wiki, you're a real champ. --[[User:Zaerc|Zaerc]] 02:50, 24 September 2007 (MST)<br />
<br />
:Keep the articles clean and use the discussion-pages for...ahh, discussions! And when you reply, please indent, it's so much easier to follow a discussion that way. --[[User:Samme|Samme]] 02:58, 24 September 2007 (MST)<br />
<br />
:Zaerc, you keep making it more clear that you don't understand how a wiki works. First of all, I tried to be nice by just moving the discussion piece of the page to the discussion area. This was not acceptable to you, and you moved it back with a nasty comment. I tried again with the same result, and a worse comment from you. So, IMO you are the one who made it personal. Second, when you sait "... all over <strong>his</strong> page", you are completely wrong about page ownership. The page belongs to the wiki and it's not personally AVJohns, this misunderstanding of yours is exactly what caused you to be upset to see "your text" moved to the discussion page. Having the discussion moved to it's correct place is not something to take personally. BTW: you're welcome for the wiki lessons. [[User:Trout|Trout]] 04:50, 24 September 2007 (MST)<br />
<br />
::So I'm the one putting a personal rant aimed at you on that page? Have some respect for the people who actually contribute, because it seems more like all the pages here belong to you. --[[User:Zaerc|Zaerc]] 07:40, 24 September 2007 (MST)<br />
<br />
:::Yes, this is an insult to me "please don't edit pages unless you actually have something to add". I feel that I am adding clarity when I move your comments to the discussion page. You are personally attacking me when you imply I am not adding anything. "go find something usefull to do, instead of pestering people that actually add information" Again another insult, implying that I have nothing better to do than mess with your addition for no purpose. Also discounting my contributions as though they are somehow less important than yours. I don't think that all the pages belong to me and I have stated so. I am sorry if you perceived that, it was not my intent. <br />
:::I really think that the page is better served without different options of editing a file. The page is about detecting serial ports, not how to create a text file. It should be enough to say "create a file like this ..." IMO this would serve the users best. [[User:Trout|Trout]] 09:07, 24 September 2007 (MST)<br />
<br />
::'''Hey hey hey!''' No you have to stop, both of you, we're in this together, work with each other, not against each other, now we end this discussion and continue the work with the wiki - '''and''' from now on discussions goes on to the pages that are designated for discussions so we can stick to the facts in the articles. Do we have a agreement? --[[User:Samme|Samme]] 09:49, 24 September 2007 (MST)<br />
<br />
:::Samme, Of course I'm in agreement, this was my point from the beginning. [[User:Trout|Trout]] 10:57, 24 September 2007 (MST)<br />
<br />
::::You guys make me sick with all your hypocritical bullshit. And then that pathetic excuse that this is to "serve" the users, seems pretty obvious this is '''not''' done in ''their'' best interest. But I guess coming forward to say what it is really about would actually take a pair. --[[User:Zaerc|Zaerc]] 11:56, 25 September 2007 (MST)<br />
<br />
Hi, i took the liberty to add a new page to the wiki [[Editing_Text]] where I put the tricks the two of you offered.<br />
<br />
And I linked to the new page from the appropriate passage within the article...<br />
<br />
I hope, this will end the fight... And I hope I will read a lot from both of you on this wiki in the future.<br />
<br />
Best Regards, [[User:Chewi|Chewi]]<br />
<br />
== Comment about better solutions by AVJohn ==<br />
<br />
I would suggest, that we leave the comment about finding better versions in there.<br />
The reason is that the article describes a hack and AVJohn says in his article that the new script is inferior to the original script.<br />
So the request for other/better solutions is an important notice to<br />
<br />
A) let people know it is only a hack<br />
<br />
B) remind others that have acomplished it a different way to add their version<br />
<br />
C) make other Developers make a "more undirty" workaround<br />
<br />
D) remind actual LMCE-Developers (no offence to AVJohn) to provide an improvement/update that makes the hack unnessasary.<br />
<br />
So I endorse to go back to the previous version for those reasons. Feel free to add your oppinions.<br />
<br />
Best regards, --[[User:Chewi|Chewi]] 07:00, 27 September 2007 (MST)<br />
<br />
<br />
The discussion belongs here IMO. Otherwise it grows out of control into a forum. Not that there's anything wrong with the discussion, but it just doesn't belong on the main page. Think about it from the point of view of someone who just wants to know the best way right now. They don't want to wade through a lot of discussion text to get the answer.<br />
<br />
A) they should know it's a hack by the title<br />
B) someone who's already accomplished it probably either 1) wants to edit the wiki with their knowledge 2) is just checking out how wiki recommends it. The mere fact that it's a wiki is enough encouragement IMO.<br />
C) okay, but they don't want to wade through a pile of blogs to see the best result. They only would want to see the best result (the wiki page) and compare it to what they have in mind.<br />
D) same as C)<br />
[[User:Trout|Trout]] 07:43, 27 September 2007 (MST)<br />
<br />
:''(Never said anything on the main-page ???)'' Basically, you're right with all of your points. But I still think that the extra-encouragement here would be a good thing, as a wiki-page without a comments-section feels like a final statement and feels like allowing editing only by "the inner circle", which is not the case here. This needs the extra-input. This is at least how I feel about wikis. Therefore, I stay with my recommendation. Regards--[[User:Chewi|Chewi]] 08:06, 27 September 2007 (MST)<br />
<br />
::''(I never said anything about main-page either.)'' I said "main page" e.g. There is a main page for every article (the link is labeled 'article') and there is a discussion for every article. That's what I was referring to. I will try to use 'article' now. You can have your opinion about "the inner circle" concept, but I don't feel that way. Also I believe that others know how to use a wiki and that the expectation is user participation. Also, you havn't said anything about the mess it'll make or how to prevent a flame war on the article instead of where it belongs (the discussion) [[User:Trout|Trout]] 08:23, 27 September 2007 (MST)<br />
<br />
:::Ok, that must have been a missunderstanding. Of course I think that discussions about the article itself belong here, just as we are having it now. And I don't want to move that part to the main page. Just for short annotations an area on the mail-article-page ;) is what I prefer. And an area for comments and annotations that does not serve as a forum or discussion-replacement, does not support flame wars. Those can happen everywhere, but I don't see why they should happen here in particular.<br />
<br />
:::I'm still not convinced, but it is not up to me. Let's see, if there are additional oppinions on this. Until then, lets leave it as it is right now, without comments. Best regards --[[User:Chewi|Chewi]] 09:48, 27 September 2007 (MST)<br />
<br />
== does this fix the "serial hack" ? ==<br />
<br />
does this fix the "serial hack" ? [[Blocking Access To Serial Port]] [[User:Trout|Trout]] 12:21, 28 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Serial_Hack&diff=6106Talk:Serial Hack2007-09-30T18:04:45Z<p>Trout: Changed Zaerc's libelous heading</p>
<hr />
<div>When you figure out a better way, edit the article. Until then this is just discussion. [[User:Trout|Trout]] 08:06, 21 September 2007 (MST)<br />
<br />
:When you have something usefull to add for a change, edit the article. Otherwise, quit pestering the people that do --[[User:Zaerc|Zaerc]] 12:59, 21 September 2007 (MST)<br />
<br />
I am at a loss to understand this battle. The original commit was another way to accomplish the same thing. There are a lot pages on this site that have very similar issues. What is the harm in giving people more than one option even if that option is one in the same. If nothing else it offers all of us an opportunity to learn something different. The second option (perl) is another example. Personally I feel both should be left on the page and just remove the editorial commitments as these are truly the things that belong in discussions. <br />
<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Good_practice Good Wiki Practices]<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Behavior_that_is_unacceptable Behavior that is unacceptable]<br />
--[[User:Rwilson131|Rwilson131]] 09:27, 23 September 2007 (MST)<br />
<br />
I'm sure AVJohn is very happy with you pissing all over his page just to prove a point Trout. And how nice of you to make it personal. So thanks for the lessons on properly maintaining a wiki, you're a real champ. --[[User:Zaerc|Zaerc]] 02:50, 24 September 2007 (MST)<br />
<br />
:Keep the articles clean and use the discussion-pages for...ahh, discussions! And when you reply, please indent, it's so much easier to follow a discussion that way. --[[User:Samme|Samme]] 02:58, 24 September 2007 (MST)<br />
<br />
:Zaerc, you keep making it more clear that you don't understand how a wiki works. First of all, I tried to be nice by just moving the discussion piece of the page to the discussion area. This was not acceptable to you, and you moved it back with a nasty comment. I tried again with the same result, and a worse comment from you. So, IMO you are the one who made it personal. Second, when you sait "... all over <strong>his</strong> page", you are completely wrong about page ownership. The page belongs to the wiki and it's not personally AVJohns, this misunderstanding of yours is exactly what caused you to be upset to see "your text" moved to the discussion page. Having the discussion moved to it's correct place is not something to take personally. BTW: you're welcome for the wiki lessons. [[User:Trout|Trout]] 04:50, 24 September 2007 (MST)<br />
<br />
::So I'm the one putting a personal rant aimed at you on that page? Have some respect for the people who actually contribute, because it seems more like all the pages here belong to you. --[[User:Zaerc|Zaerc]] 07:40, 24 September 2007 (MST)<br />
<br />
:::Yes, this is an insult to me "please don't edit pages unless you actually have something to add". I feel that I am adding clarity when I move your comments to the discussion page. You are personally attacking me when you imply I am not adding anything. "go find something usefull to do, instead of pestering people that actually add information" Again another insult, implying that I have nothing better to do than mess with your addition for no purpose. Also discounting my contributions as though they are somehow less important than yours. I don't think that all the pages belong to me and I have stated so. I am sorry if you perceived that, it was not my intent. <br />
:::I really think that the page is better served without different options of editing a file. The page is about detecting serial ports, not how to create a text file. It should be enough to say "create a file like this ..." IMO this would serve the users best. [[User:Trout|Trout]] 09:07, 24 September 2007 (MST)<br />
<br />
::'''Hey hey hey!''' No you have to stop, both of you, we're in this together, work with each other, not against each other, now we end this discussion and continue the work with the wiki - '''and''' from now on discussions goes on to the pages that are designated for discussions so we can stick to the facts in the articles. Do we have a agreement? --[[User:Samme|Samme]] 09:49, 24 September 2007 (MST)<br />
<br />
:::Samme, Of course I'm in agreement, this was my point from the beginning. [[User:Trout|Trout]] 10:57, 24 September 2007 (MST)<br />
<br />
::::You guys make me sick with all your hypocritical bullshit. And then that pathetic excuse that this is to "serve" the users, seems pretty obvious this is '''not''' done in ''their'' best interest. But I guess coming forward to say what it is really about would actually take a pair. --[[User:Zaerc|Zaerc]] 11:56, 25 September 2007 (MST)<br />
<br />
Hi, i took the liberty to add a new page to the wiki [[Editing_Text]] where I put the tricks the two of you offered.<br />
<br />
And I linked to the new page from the appropriate passage within the article...<br />
<br />
I hope, this will end the fight... And I hope I will read a lot from both of you on this wiki in the future.<br />
<br />
Best Regards, [[User:Chewi|Chewi]]<br />
<br />
== Comment about better solutions by AVJohn ==<br />
<br />
I would suggest, that we leave the comment about finding better versions in there.<br />
The reason is that the article describes a hack and AVJohn says in his article that the new script is inferior to the original script.<br />
So the request for other/better solutions is an important notice to<br />
<br />
A) let people know it is only a hack<br />
<br />
B) remind others that have acomplished it a different way to add their version<br />
<br />
C) make other Developers make a "more undirty" workaround<br />
<br />
D) remind actual LMCE-Developers (no offence to AVJohn) to provide an improvement/update that makes the hack unnessasary.<br />
<br />
So I endorse to go back to the previous version for those reasons. Feel free to add your oppinions.<br />
<br />
Best regards, --[[User:Chewi|Chewi]] 07:00, 27 September 2007 (MST)<br />
<br />
<br />
The discussion belongs here IMO. Otherwise it grows out of control into a forum. Not that there's anything wrong with the discussion, but it just doesn't belong on the main page. Think about it from the point of view of someone who just wants to know the best way right now. They don't want to wade through a lot of discussion text to get the answer.<br />
<br />
A) they should know it's a hack by the title<br />
B) someone who's already accomplished it probably either 1) wants to edit the wiki with their knowledge 2) is just checking out how wiki recommends it. The mere fact that it's a wiki is enough encouragement IMO.<br />
C) okay, but they don't want to wade through a pile of blogs to see the best result. They only would want to see the best result (the wiki page) and compare it to what they have in mind.<br />
D) same as C)<br />
[[User:Trout|Trout]] 07:43, 27 September 2007 (MST)<br />
<br />
:''(Never said anything on the main-page ???)'' Basically, you're right with all of your points. But I still think that the extra-encouragement here would be a good thing, as a wiki-page without a comments-section feels like a final statement and feels like allowing editing only by "the inner circle", which is not the case here. This needs the extra-input. This is at least how I feel about wikis. Therefore, I stay with my recommendation. Regards--[[User:Chewi|Chewi]] 08:06, 27 September 2007 (MST)<br />
<br />
::''(I never said anything about main-page either.)'' I said "main page" e.g. There is a main page for every article (the link is labeled 'article') and there is a discussion for every article. That's what I was referring to. I will try to use 'article' now. You can have your opinion about "the inner circle" concept, but I don't feel that way. Also I believe that others know how to use a wiki and that the expectation is user participation. Also, you havn't said anything about the mess it'll make or how to prevent a flame war on the article instead of where it belongs (the discussion) [[User:Trout|Trout]] 08:23, 27 September 2007 (MST)<br />
<br />
:::Ok, that must have been a missunderstanding. Of course I think that discussions about the article itself belong here, just as we are having it now. And I don't want to move that part to the main page. Just for short annotations an area on the mail-article-page ;) is what I prefer. And an area for comments and annotations that does not serve as a forum or discussion-replacement, does not support flame wars. Those can happen everywhere, but I don't see why they should happen here in particular.<br />
<br />
:::I'm still not convinced, but it is not up to me. Let's see, if there are additional oppinions on this. Until then, lets leave it as it is right now, without comments. Best regards --[[User:Chewi|Chewi]] 09:48, 27 September 2007 (MST)<br />
<br />
== does this fix the "serial hack" ? ==<br />
<br />
does this fix the "serial hack" ? [[Blocking Access To Serial Port]] [[User:Trout|Trout]] 12:21, 28 September 2007 (MST)<br />
<br />
== Trout: Please stop editing this page ==<br />
<br />
Somebody cleaned up the mess you made and now you have to spit in his face by continuing to vandalize the page. Your arguments of percieved problems are insignificant and irrelevant. I don't think this is apropriate behavior for a "wiki admin". Please join in on the forum discussion if you feel this is so important. [http://forum.linuxmce.org/index.php?topic=2593.15]. --[[User:Zaerc|Zaerc]] 04:42, 30 September 2007 (MST)<br />
<br />
What specifically are you talking about? I think you are sadly confused. [[User:Trout|Trout]] 10:03, 30 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Serial_Hack&diff=6091Talk:Serial Hack2007-09-30T17:03:22Z<p>Trout: /* Trout: Please stop vandalizing this page */</p>
<hr />
<div>When you figure out a better way, edit the article. Until then this is just discussion. [[User:Trout|Trout]] 08:06, 21 September 2007 (MST)<br />
<br />
:When you have something usefull to add for a change, edit the article. Otherwise, quit pestering the people that do --[[User:Zaerc|Zaerc]] 12:59, 21 September 2007 (MST)<br />
<br />
I am at a loss to understand this battle. The original commit was another way to accomplish the same thing. There are a lot pages on this site that have very similar issues. What is the harm in giving people more than one option even if that option is one in the same. If nothing else it offers all of us an opportunity to learn something different. The second option (perl) is another example. Personally I feel both should be left on the page and just remove the editorial commitments as these are truly the things that belong in discussions. <br />
<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Good_practice Good Wiki Practices]<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Behavior_that_is_unacceptable Behavior that is unacceptable]<br />
--[[User:Rwilson131|Rwilson131]] 09:27, 23 September 2007 (MST)<br />
<br />
I'm sure AVJohn is very happy with you pissing all over his page just to prove a point Trout. And how nice of you to make it personal. So thanks for the lessons on properly maintaining a wiki, you're a real champ. --[[User:Zaerc|Zaerc]] 02:50, 24 September 2007 (MST)<br />
<br />
:Keep the articles clean and use the discussion-pages for...ahh, discussions! And when you reply, please indent, it's so much easier to follow a discussion that way. --[[User:Samme|Samme]] 02:58, 24 September 2007 (MST)<br />
<br />
:Zaerc, you keep making it more clear that you don't understand how a wiki works. First of all, I tried to be nice by just moving the discussion piece of the page to the discussion area. This was not acceptable to you, and you moved it back with a nasty comment. I tried again with the same result, and a worse comment from you. So, IMO you are the one who made it personal. Second, when you sait "... all over <strong>his</strong> page", you are completely wrong about page ownership. The page belongs to the wiki and it's not personally AVJohns, this misunderstanding of yours is exactly what caused you to be upset to see "your text" moved to the discussion page. Having the discussion moved to it's correct place is not something to take personally. BTW: you're welcome for the wiki lessons. [[User:Trout|Trout]] 04:50, 24 September 2007 (MST)<br />
<br />
::So I'm the one putting a personal rant aimed at you on that page? Have some respect for the people who actually contribute, because it seems more like all the pages here belong to you. --[[User:Zaerc|Zaerc]] 07:40, 24 September 2007 (MST)<br />
<br />
:::Yes, this is an insult to me "please don't edit pages unless you actually have something to add". I feel that I am adding clarity when I move your comments to the discussion page. You are personally attacking me when you imply I am not adding anything. "go find something usefull to do, instead of pestering people that actually add information" Again another insult, implying that I have nothing better to do than mess with your addition for no purpose. Also discounting my contributions as though they are somehow less important than yours. I don't think that all the pages belong to me and I have stated so. I am sorry if you perceived that, it was not my intent. <br />
:::I really think that the page is better served without different options of editing a file. The page is about detecting serial ports, not how to create a text file. It should be enough to say "create a file like this ..." IMO this would serve the users best. [[User:Trout|Trout]] 09:07, 24 September 2007 (MST)<br />
<br />
::'''Hey hey hey!''' No you have to stop, both of you, we're in this together, work with each other, not against each other, now we end this discussion and continue the work with the wiki - '''and''' from now on discussions goes on to the pages that are designated for discussions so we can stick to the facts in the articles. Do we have a agreement? --[[User:Samme|Samme]] 09:49, 24 September 2007 (MST)<br />
<br />
:::Samme, Of course I'm in agreement, this was my point from the beginning. [[User:Trout|Trout]] 10:57, 24 September 2007 (MST)<br />
<br />
::::You guys make me sick with all your hypocritical bullshit. And then that pathetic excuse that this is to "serve" the users, seems pretty obvious this is '''not''' done in ''their'' best interest. But I guess coming forward to say what it is really about would actually take a pair. --[[User:Zaerc|Zaerc]] 11:56, 25 September 2007 (MST)<br />
<br />
Hi, i took the liberty to add a new page to the wiki [[Editing_Text]] where I put the tricks the two of you offered.<br />
<br />
And I linked to the new page from the appropriate passage within the article...<br />
<br />
I hope, this will end the fight... And I hope I will read a lot from both of you on this wiki in the future.<br />
<br />
Best Regards, [[User:Chewi|Chewi]]<br />
<br />
== Comment about better solutions by AVJohn ==<br />
<br />
I would suggest, that we leave the comment about finding better versions in there.<br />
The reason is that the article describes a hack and AVJohn says in his article that the new script is inferior to the original script.<br />
So the request for other/better solutions is an important notice to<br />
<br />
A) let people know it is only a hack<br />
<br />
B) remind others that have acomplished it a different way to add their version<br />
<br />
C) make other Developers make a "more undirty" workaround<br />
<br />
D) remind actual LMCE-Developers (no offence to AVJohn) to provide an improvement/update that makes the hack unnessasary.<br />
<br />
So I endorse to go back to the previous version for those reasons. Feel free to add your oppinions.<br />
<br />
Best regards, --[[User:Chewi|Chewi]] 07:00, 27 September 2007 (MST)<br />
<br />
<br />
The discussion belongs here IMO. Otherwise it grows out of control into a forum. Not that there's anything wrong with the discussion, but it just doesn't belong on the main page. Think about it from the point of view of someone who just wants to know the best way right now. They don't want to wade through a lot of discussion text to get the answer.<br />
<br />
A) they should know it's a hack by the title<br />
B) someone who's already accomplished it probably either 1) wants to edit the wiki with their knowledge 2) is just checking out how wiki recommends it. The mere fact that it's a wiki is enough encouragement IMO.<br />
C) okay, but they don't want to wade through a pile of blogs to see the best result. They only would want to see the best result (the wiki page) and compare it to what they have in mind.<br />
D) same as C)<br />
[[User:Trout|Trout]] 07:43, 27 September 2007 (MST)<br />
<br />
:''(Never said anything on the main-page ???)'' Basically, you're right with all of your points. But I still think that the extra-encouragement here would be a good thing, as a wiki-page without a comments-section feels like a final statement and feels like allowing editing only by "the inner circle", which is not the case here. This needs the extra-input. This is at least how I feel about wikis. Therefore, I stay with my recommendation. Regards--[[User:Chewi|Chewi]] 08:06, 27 September 2007 (MST)<br />
<br />
::''(I never said anything about main-page either.)'' I said "main page" e.g. There is a main page for every article (the link is labeled 'article') and there is a discussion for every article. That's what I was referring to. I will try to use 'article' now. You can have your opinion about "the inner circle" concept, but I don't feel that way. Also I believe that others know how to use a wiki and that the expectation is user participation. Also, you havn't said anything about the mess it'll make or how to prevent a flame war on the article instead of where it belongs (the discussion) [[User:Trout|Trout]] 08:23, 27 September 2007 (MST)<br />
<br />
:::Ok, that must have been a missunderstanding. Of course I think that discussions about the article itself belong here, just as we are having it now. And I don't want to move that part to the main page. Just for short annotations an area on the mail-article-page ;) is what I prefer. And an area for comments and annotations that does not serve as a forum or discussion-replacement, does not support flame wars. Those can happen everywhere, but I don't see why they should happen here in particular.<br />
<br />
:::I'm still not convinced, but it is not up to me. Let's see, if there are additional oppinions on this. Until then, lets leave it as it is right now, without comments. Best regards --[[User:Chewi|Chewi]] 09:48, 27 September 2007 (MST)<br />
<br />
== does this fix the "serial hack" ? ==<br />
<br />
does this fix the "serial hack" ? [[Blocking Access To Serial Port]] [[User:Trout|Trout]] 12:21, 28 September 2007 (MST)<br />
<br />
== Trout: Please stop vandalizing this page ==<br />
<br />
Somebody cleaned up the mess you made and now you have to spit in his face by continuing to vandalize the page. Your arguments of percieved problems are insignificant and irrelevant. I don't think this is apropriate behavior for a "wiki admin". Please join in on the forum discussion if you feel this is so important. [http://forum.linuxmce.org/index.php?topic=2593.15]. --[[User:Zaerc|Zaerc]] 04:42, 30 September 2007 (MST)<br />
<br />
What specifically are you talking about? I think you are sadly confused. [[User:Trout|Trout]] 10:03, 30 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Template:Sectstub&diff=5906Template:Sectstub2007-09-29T12:54:27Z<p>Trout: Make this template look like the other(s) standard?</p>
<hr />
<div>{| style="background: beige; border: 1px solid #aaa; margin: auto; padding: .2em; width: auto;"<br />
|-<br />
| rowspan=2 style="padding: 4px;" | <br />
| '''This short section requires expansion'''<br />
|}<br />
<br />
<includeonly>[[Category:Articles with sections needing expansion]]</includeonly><br />
<br />
<noinclude><br />
To add this to a very short section use <nowiki>{{sectstub}}</nowiki><br />
</noinclude></div>Trouthttp://wiki.linuxmce.org/index.php?title=TV_Standards&diff=5905TV Standards2007-09-29T12:16:52Z<p>Trout: Wikified!</p>
<hr />
<div>== Continent of Europe and Middle East ==<br />
<br />
* United Kingdom – PAL-I<br />
* Ireland - PAL-I<br />
* Austria – PAL-B<br />
* Belgium – PAL-B<br />
* Bosnia-Herzegovina – PAL-B<br />
* Croatia – PAL-B<br />
* Cyprus – PAL-B<br />
* Denmark – PAL-B<br />
* Finland – PAL-B<br />
* Germany – PAL-B<br />
* Gibraltar – PAL-B<br />
* Greenland – PAL-B<br />
* Iceland – PAL-B<br />
* Israel – PAL-B <br />
* Italy – PAL-B<br />
* Jordan – PAL-B<br />
* Luxembourg – PAL-B<br />
* Maldives – PAL-B<br />
* Malta – PAL-B<br />
* Netherlands – PAL-B<br />
* Norway – PAL-B<br />
* Oman – PAL-B<br />
* Portugal – PAL-B<br />
* Saudi Arabia – PAL-B<br />
* Slovenia – PAL-B<br />
* Spain – PAL-B<br />
* Sweden – PAL-B<br />
* Switzerland – PAL-B<br />
* Syria – PAL-B<br />
* Turkey – PAL-B<br />
* United Arab Emirates – PAL-B<br />
* Yemen – PAL-B<br />
* Romania – PAL-D (V)<br />
<br />
<br />
== Continent of Asia and Oceanic ==<br />
* Hong Kong – PAL-I<br />
* Australia – PAL-B<br />
* Brunei Darussalam – PAL-B<br />
* Cambodia – PAL-B<br />
* India – PAL-B<br />
* Indonesia – PAL-B<br />
* Malaysia – PAL-B<br />
* Nepal – PAL-B<br />
* New Zealand – PAL-B<br />
* Pakistan – PAL-B<br />
* Papua New Guinea – PAL-B<br />
* Singapore – PAL-B<br />
* Sri Lanka – PAL-B<br />
* Thailand – PAL-B<br />
* China – PAL-D<br />
* North Korea – PAL-D (V)<br />
* Guam – NTSC (V)<br />
* Japan – NTSC<br />
* South Korea – NTSC<br />
* Myanmar – NTSC (V)<br />
* Philippines – NTSC<br />
* Taiwan – NTSC (V)<br />
<br />
== Americas and Caribbean ==<br />
* Antigua – NTSC<br />
* Aruba – NTSC<br />
* Bahamas – NTSC (V)<br />
* Barbados – NTSC (V)<br />
* Belize – NTSC (V)<br />
* Bermuda – NTSC (V)<br />
* Bolivia – NTSC (V)<br />
* Canada – NTSC <br />
* Chile – NTSC<br />
* Colombia – NTSC<br />
* Costa Rica – NTSC<br />
* Cuba – NTSC<br />
* Curacao – NTSC<br />
* Dominican Republic – NTSC<br />
* Ecuador – NTSC<br />
* El Salvador – NTSC (V)<br />
* Guatemala – NTSC <br />
* Honduras – NTSC<br />
* Jamaica – NTSC<br />
* Mexico – NTSC<br />
* Nicaragua – NTSC<br />
* Panama – NTSC<br />
* Peru – NTSC<br />
* St. Christopher and Nevis – NTSC (V)<br />
* Suriname – NTSC (V)<br />
* Trinidad/Tobago – NTSC (V)<br />
* United States of America –NTSC<br />
* Venezuela – NTSC<br />
* Virgin Islands – NTSC (V)</div>Trouthttp://wiki.linuxmce.org/index.php?title=NTSC&diff=5904NTSC2007-09-29T12:07:28Z<p>Trout: </p>
<hr />
<div>#REDIRECT [[TV Standards]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=PAL&diff=5903PAL2007-09-29T12:07:08Z<p>Trout: </p>
<hr />
<div>#REDIRECT [[TV Standards]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=Share_IR_Codes&diff=5900Share IR Codes2007-09-29T11:50:28Z<p>Trout: </p>
<hr />
<div>If you don't uncheck "Share my I/R codes with other LinuxMCE users" checkbox from Wizard/Devices/AV Equipment page, the codes you [[Learning/typing_my_own_code|learned or typed]] are sent to our database using the script Share_IRCodes.sh, which use [[SqlCVS]] to send the codes to our central database, so any other users can benefit from them.<br />
<br />
The script is called automatically on each reboot. However, the codes need to be validated by our staff, mostly to prevent accidental submissions.</div>Trouthttp://wiki.linuxmce.org/index.php?title=Generic_Serial_Device&diff=5899Generic Serial Device2007-09-29T11:46:05Z<p>Trout: /* Useful Pages */</p>
<hr />
<div>Generic_Serial_Device (also known as '''GSD''') is a LinuxMCE device that allows end-user to do simple programming for RS232, serial USB (See [[Serial Hack]] for details on getting USB to serial adapters identified properly in the admin panel!) or network connected devices.<br />
:Note : The information is not quite complete because I'm not the original author.<br />
<br />
== Short description ==<br />
It's a standard DCE device, it only can execute commands and send events .<br />
The main idea is instead of programming a device in C++, compile, link with proper libraries you can edit (in a webpage) few lines of code in ruby which will be executed when device receives that command. It exports several objects into ruby so you'll have access to devicedata, device hierarchy, established connection and so on.<br />
<br />
The ruby code for each device template is stored somewhere in ''InfraredGroup_Command'' table. To edit the code go to Wizard> Devices > Generic_Serial_Devices on [[LinuxMCE-admin]] website. You have to add a device from a device template in order to see anything in that page.<br />
<br />
Select the device, and click "RubyCodes" button to be able to edit code that will be executed. <br />
You should be able to see commands that are specified in device template (like ON/OFF/WhateverElse) and a group of ''Internal Commands'' which are used to perform certain actions are to add helper functions.<br />
<br />
If the command you are trying to add doesn't show on first page, go to ''Add/Remove commands'' and add more commands for your device.<br />
<br />
=== Ruby source code ===<br />
<br />
There are 2 forms of ruby code you can write :<br />
* standard ruby code (check [http://www.ruby-lang.org/en/] and [http://poignantguide.net/ruby/] for syntax, references and programming guides)<br />
* short form for '''conn_.Send'''<br />
<$"PWON\r"$><br />
:which simply will send the string ''"PWON\r"'' to device.<br />
<br />
You'll have to quick reload router to get new code. Restarting GSD only will keep old code because the code is supplied by [[Infrared_Plugin]] which caches pluto_main and won't update it's cache without full restart of [[DCERouter]]. With this code it creates a ruby source which will be interpreted by embedded ruby.<br />
<br />
It will create methods called "cmd_CmdIDx" for each command(x) defined in web interface except ''Private_Method_Listing'' which will be inserted in the body of the class directly without wrapping.<br />
<br />
The source usually looks like (''DevID'' is iPK_Device of specific device, ''CmdIDx'' is iPK_Command ) :<br />
<br />
require 'Ruby_Generic_Serial_Device'<br />
class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper<br />
end<br />
class Device_DevID < Ruby_Generic_Serial_Device::RubySerialWrapper<br />
def cmd_CmdID1(paramlist)<br />
@returnParamArray.clear<br />
### WEB CODE for CmdID1 GOES HERE ###<br />
return @returnParamArray<br />
end<br />
def cmd_CmdID2(paramlist)<br />
@returnParamArray.clear<br />
### WEB CODE for CmdID2 GOES HERE ###<br />
return @returnParamArray<br />
end<br />
...<br />
def cmd_ReceiveCommandForChild(cmd)<br />
### Process_Receive Command_For_Child GOES HERE ###<br />
end<br />
...<br />
### Private_Method_Listing GOES HERE ###<br />
...<br />
def initialize()<br />
super<br />
@returnParamArray=Array.new<br />
end<br />
### Generated Setters/Getters goes here (may be empty, but usually looks like below) ###<br />
def data_set(value)<br />
@returnParamArray[19]=value<br />
end<br />
<br />
end<br />
<br />
There might be more then one class definition in that source. This may happen when child device is itself a GSD device.<br />
<br />
=== Command details ===<br />
When the command from DCE arrives it is routed to specific device and ''cmd_XXX'' is run. The commands are run one by one, meaning that you cannot run 2 commands simultaneously. This limitation is implied by embedded ruby interpretor which fails if run from multiple threads.<br />
DCE commands may have return parameters (well known GetVideoFrame), as ruby can return only 1 parameter the ''@returnParamArray'' was added. You can see that in each method we insert '''@returnParamArray.clear''' then the real code and then '''return @returnParamArray'''. Also some setters are generated (like the one from above) for code readability.<br />
<br />
Beside usual DCE command you'll see some ''Internal Commands''. Here goes a small list and what they do:<br />
* '''Private Method Listing''' - used to insert all kind of helpers<br />
* '''Process IDLE''' - method executed once in a while (may be used to keep connection alive, scan for new devices on serial bus)<br />
* '''Process Incoming Data''' - called when some data is available <br />
* '''Process Receive Command For Child''' - called if the device has children and those are pretty dummy (like Lights under CM11), so practically the parent will do the job. As a parameter you have ''cmd'' which is a wrapper for DCEMessage, so you'll have access to deviceId, senderId, commandID and so on.<br />
* '''Process Initialize''' - called when device is starting (to perform handshake with device or some other initialisation required by protocol)<br />
* '''Process Release''' - to close gracefully connection with device (say "good bye" or something)<br />
<br />
== Implementation notes ==<br />
There are several classes that actually need to be touched. Most of the other classes are just for wrapping DCE objects (like Device, Message, Connection and so on) and exporting them into ruby.<br />
<br />
Most important classes :<br />
* '''RubyDCEDeviceNode''' is actually the Device, responsable with initialisation and partially a message handler.<br />
* '''RubyDCEEmbededClass''' is bridge between DeviceNode and ruby, it has ''CallCmdHandler'' which does the real call to ruby and sends back result.<br />
* '''RubyIOManager''' is the one responsible for instantiating RubyDCEDeviceNodes, code retrieval, command handler and serializing ruby calls.<br />
* '''RubyDCECodeSupplier''' gives you the ruby code<br />
* '''RubyCommandWrapper''' a wrapper for Message<br />
* '''GSDMessageProcessing''' is [[Message_Translation|message translator]] which will try to run command if it's implemented without translation.<br />
* '''RubySerialIOConnectionWrapper''' helps to wrap Serial and TCP/IP based connection under same interface, see down the hierarchy the connection you need.<br />
<br />
There are also some files needed for building a library for ruby with SWIG, let them alone, it should work.<br />
<br />
The compilation will give you '''Generic_Serial_Device''' and '''Ruby_Generic_Serial_Device.so''', first file is the binary itself, second file is the bridge library and it will be included by ruby (the request for it is in the first line of the generated source)<br />
<br />
== Known issues ==<br />
<br />
* Only '''ONE''' command can be executed at a time. This is a limitation of embedded ruby, which should be run from one thread only.<br />
* If command expected an answer, it would wait about 20 seconds for the ruby command to complete, and if the command haven't completed yet, it would send an empty response.<br />
* Most of the data are pretty cryptic (like ''device_.devdata_[114]''), you have to look that that number represents (device data id, command id, command parameter id, event id, event parameter id, some other id)<br />
<br />
== Short example ==<br />
For more details about exported classes and available methods check [[GSD_Ruby_Interface]]<br />
<br />
Here is a short example from ''Panasonic IP Camera'':<br />
0:require 'Ruby_Generic_Serial_Device'<br />
1:class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper<br />
2:end<br />
3:class Device_47 < Ruby_Generic_Serial_Device::RubySerialWrapper<br />
4:#### 84 ####################################################################<br />
5:def cmd_84(data, format, disable_aspect_lock, streamid, width, height)<br />
6:@returnParamArray.clear<br />
7:conn_.Reconnect()<br />
8:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]<br />
9:auth_a=Array.new;<br />
10:auth_s.each{|c| auth_a.push(c)}<br />
11:<br />
12:fix_path=device_.devdata_[2];<br />
13:fix_path='/'+fix_path if(fix_path[0]!='/'[0]);<br />
14:<br />
15:s = "GET "+fix_path+" HTTP/1.0\r\n"<br />
16:s+= "Accept: */*\r\n"<br />
17:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"<br />
18:s+= "\r\n"<br />
19:<br />
20:conn_.Send(s)<br />
21:recv=""<br />
22:while(true)<br />
23: buff=conn_.Recv(16384, 5000)<br />
24: if(buff.length() == 0)<br />
25: break<br />
26: end<br />
27: recv = recv + buff<br />
28:end<br />
29:if (recv=~ /^HTTP[^\r\n]+200\sOK.+?\r\n\r\n(.+)$/m)<br />
30: data_set($1)<br />
31: format_set('jpg')<br />
32:end<br />
33:return @returnParamArray<br />
34:end<br />
...<br />
194:#### START SETTERS ####################################################################<br />
195:def initialize()<br />
196:super<br />
197:@returnParamArray=Array.new<br />
198:end<br />
199:def data_set(value)<br />
200:@returnParamArray[19]=value<br />
201:end<br />
202:def format_set(value)<br />
203:@returnParamArray[20]=value<br />
204:end<br />
205:#### END SETTERS ####################################################################<br />
206:end<br />
You can see how command 84 (GetVideoFrame) is implemented:<br />
* it has 6 parameters ''cmd_84(data, format, disable_aspect_lock, streamid, width, height)'', parameters ''data'' and ''format'' are also output parameters<br />
* to set output parameters methods like ''data_set'' and ''format_set'' are automatically generated<br />
* ''device_.devdata_[114]'', ''device_.devdata_[115]'' are the username and password to login into camera <br />
* then it creates HTTP header with basic authorization<br />
* ''device_.devdata_[2]'' is the path to the snapshot (it is configurable because it can change between models)<br />
* it sends the request and waits for the answer<br />
* reads the answer, regexp parse it and gets JPEG content<br />
* sets output parameters<br />
* returns @returnParamArray (the return statement is added automatically)<br />
<br />
<br />
== Example - Adding Clipsal Interface ==<br />
<br />
We can control lights, curtains and climate controls using Clipsal Interface that connects through Serial Port.<br />
<br />
[[Here is a detailed example of how to add Clipsal Interface using Generic Serial Device.|Adding Clipsal Interface using Generic Serial Device]]<br />
<br />
== Useful Pages ==<br />
* [[Serial Hack]] - A quick and dirty hack to fix the USB to Serial adapter problem! (Device not showing the correct block device on the admin panel)<br />
* [[How to add your own GSD device]]<br />
<br />
[[Category: GSD]]<br />
[[Category: LinuxMCE_Devices]]<br />
[[Category: Programmer's Guide]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:User%27s_manual&diff=5897Talk:User's manual2007-09-29T11:42:51Z<p>Trout: what is this page? Should it be renamed?</p>
<hr />
<div>== what is this page? Should it be renamed? ==<br />
<br />
User's manual kindof implies LinuxMCE's user manual... this only talks about DCE... should it be deleted?</div>Trouthttp://wiki.linuxmce.org/index.php?title=What_can_I_do_with_LinuxMCE%3F&diff=5896What can I do with LinuxMCE?2007-09-29T09:23:52Z<p>Trout: /* Home Automation */</p>
<hr />
<div><p>Following is a list of things you can do with LinuxMCE. Each link takes you to a how-to page which has 3 parts: 1) How to set it up, 2) How to use it, 3) Where to find the source code and how it works.</p><br />
<br />
<p>The list is not complete, and many of the topics do not yet have the documentation, and not all documentation pages have screen shots and pictures. Feel free to add your own documentation and commit it into our document tree, like a wiki; there's a how-to for that.</p><br />
<br />
<p>Most people gradually add more and more to LinuxMCE over time, this page will become a comfortable alternative to the full user's manual, allowing you to quickly see what can be done, and how to do it.</p><br />
<p>Everything listed below presently is tested and works even if the documentation is not written, except those items in <i>italics</i> which require modules still in development or only partially complete. Items with an * are coded, and should work, but are not fully tested.</p><br />
<p>[[What modules are in development?]]</p><br />
<br />
==General==<br />
* [[Control LinuxMCE using a Windows device as an Orbiter]]<br><br />
* [[Control LinuxMCE using a Symbian Series 60 mobile phone with Bl]]<br><br />
* [[Control LinuxMCE using other types of mobile phones]]<br><br />
* [[Control LinuxMCE using an Infrared remote]]<br><br />
* [[Add support for new remote controls]]<br><br />
* [[Change the look and feel of the Orbiter]]<br><br />
* [[Create my own skins or GUI for LinuxMCE]]<br><br />
* [[Translate the GUI into another language]]<br><br />
* [[Automatic diskless boot of media directors]]<br><br />
* [[Restrict which users can use use which Orbiters or control w]]<br><br />
Add to/edit the online documentation, wiki-style<br><br />
<br><br />
<br />
==Media==<br />
* [[Have LinuxMCE automatically control the TV and Stereo]]<br><br />
* [[Control the media director's volume using either a receiver]]<br><br />
* [[Use network audio players for a whole-house music solution]]<br><br />
* [[Watch TV using the built-in Myth PVR, and schedule recordings]]<br />
* [[Use a satellite/cable box with the PVR]]<br><br />
* [[Control a TV or cable/satellite box]]<br><br />
* [[Watch a DVD/Listen to a CD]]<br><br />
* [[Rip a CD/DVD to the Core]]<br><br />
* [[Watch/Listen to media stored on the Core]]<br><br />
* [[Play the same media in multiple rooms simultaneously]]<br><br />
* [[Flag media stored on the core as private]]<br><br />
* [[Flag whatever media I am watching now as private]]<br><br />
* [[Catalog media with attributes]]<br><br />
* [[Search for media by attributes using the Orbiters]]<br><br />
* [[Control regular A/V equipment]]<br><br />
* [[Control A/V equipment with RS232/USB/Ethernet]]<br><br />
* [[Make LinuxMCE do something when I start media]]<br><br />
* <i>Upload a pronto file into the Orbiter's pronto emulator</i><br><br />
* [[Have my media follow me]]<br><br />
* [[Make announcements]]<br><br />
<br><br />
<br />
==Home Automation==<br />
* [[Control lights/climate using scenarios]]<br><br />
* [[Control lights or climate with a floorplan]]<br><br />
* [[Adding support for home automation devices]]<br><br />
* [[What if you don't have a driver for my home automation device]]<br><br />
* [[Make things happen at sunrise/sunset]]<br><br />
* [[Make things happen when I enter a room]]<br><br />
* [[Have my lighting or climate settings follow me]]<br><br />
* [[Have external devices control LinuxMCE]]<br><br />
<br />
<br />
<br><br />
<br />
==Security==<br />
* [[Monitor surveillance cameras]]<br><br />
* [[Arm or disarm the alarm using the Orbiters]]<br><br />
* Arm or disarm LinuxMCE's alarm using proximity sensors<br><br />
* [[Automatically take pictures when sensors are disturbed]]<br><br />
* [[Have LinuxMCE notify me of security alerts]]<br><br />
<br><br />
<br />
==PC Computing==<br />
* Have LinuxMCE's screen saver turn my regular TV off when there's no activity and back on automatically, like a PC monitor with power save<br><br />
* Browse web pages on the media directors<br><br />
* <i>Browse web pages on the orbiters</i><br><br />
* <i>Use open office on the media directors</i><br><br />
* <i>Access a KDE/Gnome desktop on the media directors</i><br><br><br />
<br />
==Telecommunications==<br />
* Make phone calls using a VOIP provider<br><br />
* Make phone calls using a regular phone line (POTS), ISDN or T1<br><br />
* Do video conferencing<br></div>Trouthttp://wiki.linuxmce.org/index.php?title=TOC&diff=5895TOC2007-09-29T09:23:13Z<p>Trout: </p>
<hr />
<div>&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Home]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Installation]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Equipment]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[PC Hardware & Peripherals]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Why dual network cards?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Recommended Accessories]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Software]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Building from source]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Kick-Start CD]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Installers]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Windows]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Installing on a new platform]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Network Boot for Media Directors]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Encrypted DVD's]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Wiring Considerations]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Choosing Locations]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Quick Start Guides]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Picking the right components]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Installing the software]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Installing the hardware]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Tell LinuxMCE about your home]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Testing and troubleshooting devices]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Real world example]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Setting up MythTV]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Using LinuxMCE]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[User's Manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Security & Privacy Issues]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[What can I do with LinuxMCE?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control LinuxMCE using a Windows device as an Orbiter]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control LinuxMCE using a Symbian Series 60 mobile phone with Bl]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control LinuxMCE using other types of mobile phones]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control LinuxMCE using an Infrared remote]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Add support for new remote controls]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Automatic diskless boot of media directors]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Change the look and feel of the Orbiter]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Create my own skins or GUI for LinuxMCE]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Translate the GUI into another language]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Use network audio players for a whole-house music solution]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control a TV or cable/satellite box]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Watch a DVD/Listen to a CD]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Have LinuxMCE automatically control the TV and Stereo]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Rip a CD/DVD to the Core]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Watch/Listen to media stored on the Core]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Play the same media in multiple rooms simultaneously]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Search for media by attributes using the Orbiters]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Flag media stored on the core as private]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Flag whatever media I am watching now as private]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Catalog media with attributes]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control regular A/V equipment]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control A/V equipment with RS232/USB/Ethernet]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Make LinuxMCE do something when I start media]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Have my media follow me]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Make announcements]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control the media director's volume using either a receiver]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Use a satellite/cable box with the PVR]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[What modules are in development?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control lights/climate using scenarios]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Control lights or climate with a floorplan]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Make things happen at set times or intervals]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Make things happen when I enter a room]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Have my lighting or climate settings follow me]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Make things happen at sunrise/sunset]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Have external devices control LinuxMCE]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Monitor surveillance cameras]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Arm or disarm the alarm using the Orbiters]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Automatically take pictures when sensors are disturbed]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Have LinuxMCE notify me of security alerts]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Why should I use the LinuxMCE platform for my project?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Overview of the software modules]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[A new concept in collaborative development]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Adding support for home automation devices]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Admin Website]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Wizard Pages]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Basic Info]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Users]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Rooms]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Devices]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Orbiters]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Interfaces]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Devices Security]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Lights]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Media Directors]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Climate]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[AV Devices]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Infrared Codes]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Learning/typing my own code]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[AV Properties]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[TOAD vs Discrete Codes]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Floorplans]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Surveillance Cameras]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Phone Lines]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Phone Extensions]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Scenarios]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Lighting Scenarios]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Climate Scenarios]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Media Scenarios]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Scenarios Security]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Telecom]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Events]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Respond to Events]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Timed Events]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Active sensors]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Security-Video Links]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Notifications]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Settings By Alert Type]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Outside Access]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Advanced Pages]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Device Templates]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[List Page]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Edit Page]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Design Objects]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Packages]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Advanced Pages Devices]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Advanced Pages Scenarios]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Boot Sequence]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Network Settings]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Add Software]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Privacy Settings]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Advanced Pages Events]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[DCE]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Device Status]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Execute Scenarios]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Alert Logs]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Mode Change Logs]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Status]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[View Cameras]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Home Software]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[DCE Router]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[DCE Router Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Command Line Options]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Message Interceptors]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Orbiter]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Orbiter User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Who Am I, Where Am I]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[The Main Menu]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Maps]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Orbiter Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Mobile Orbiter]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Designer]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Designer User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Text Formatting Options]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[sqlCVS]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[sqlCVS User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Naming of Foreign Keys, Indirect Keys, External Keys]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[What do the psc_ fields do?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[What do the psc tables do?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[sqlCVS Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Kick-Start]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Orbiter Symbian]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Orbiter Symbian User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Orbiter Symbian Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[BD - Bidirectional command processor]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[RA - Client/Server Request-Action]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[sql2cpp]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Libraries DCE]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Does the device Implement DCE?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Understanding Controlled Via (aka Parent)]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Categories]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Make a DCE Device in 5 minutes]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[GSD]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Cpp]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Why DCE complements UPNP, XAP, XPL and other standards?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Plain Text DCE Messages]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE_main database]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Orbiter Generator]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[DCE Generator]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[DHCP Plug and Play]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Scripts]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Do I want a dedicated Core?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE DCE Devices]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Bluetooth Dongle]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Bluetooth Dongle User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Bluetooth Dongle Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE App Server]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE App Server User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE App Server Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Disk Drive]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Disk Drive User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Disk Drive Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE GC 100]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE GC 100 User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE GC 100 Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE MythTV Player]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE MythTV Player User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE MythTV Player Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Xine Player]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Xine Player User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Xine Player Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Asterisk]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[AMP Configuration Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Broadvoice]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Free world dialup]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[E-Fon (Switzerland)]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Mozilla Plug-in]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Mozilla Plug-in User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Mozilla Plug-in Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE MythTV Plug-in]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE MythTV Plug-in User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE MythTV Plug-in Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Standard Plug-ins]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Standard Plug-ins User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Standard Plug-ins Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Xine Plug-in]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Xine Plug-in User's manual]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCE Xine Plug-in Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Media Identifiers]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Bang & Olufsen Systems]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[CX88 Blackbird Drivers]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[CX88 Blackbird Drivers Programmer's Guide]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Versions]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Development status for all modules]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[What does an appliance solution like LinuxMCE cost?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Why buy a licensed LinuxMCE product? What's the difference?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Do I need LinuxMCE? Can I use the projects by themselves?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[What if you don't have a driver for my home automation device]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[How are media files organized?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[What scenarios are created automatically?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[I'm a Linux user already. Should I use LinuxMCE's distribution]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[I want my software to run on LinuxMCE but it isn't open source]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Will you host, compile and support the LinuxMCE plug-ins for my]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Open Source Info]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Troubleshooting]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Reset the password for the LinuxMCE Admin site]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[I can't access my media files over the network]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[How do I login to a Linux console?]]<br>&nbsp;&nbsp;&nbsp;&nbsp;[[LinuxMCEVIP]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[Download]]<br>&nbsp;&nbsp;&nbsp;&nbsp;[[Online Documentation]]<br></div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Serial_Hack&diff=5891Talk:Serial Hack2007-09-28T19:21:44Z<p>Trout: does this fix the "serial hack" ?</p>
<hr />
<div>When you figure out a better way, edit the article. Until then this is just discussion. [[User:Trout|Trout]] 08:06, 21 September 2007 (MST)<br />
<br />
:When you have something usefull to add for a change, edit the article. Otherwise, quit pestering the people that do --[[User:Zaerc|Zaerc]] 12:59, 21 September 2007 (MST)<br />
<br />
I am at a loss to understand this battle. The original commit was another way to accomplish the same thing. There are a lot pages on this site that have very similar issues. What is the harm in giving people more than one option even if that option is one in the same. If nothing else it offers all of us an opportunity to learn something different. The second option (perl) is another example. Personally I feel both should be left on the page and just remove the editorial commitments as these are truly the things that belong in discussions. <br />
<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Good_practice Good Wiki Practices]<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Behavior_that_is_unacceptable Behavior that is unacceptable]<br />
--[[User:Rwilson131|Rwilson131]] 09:27, 23 September 2007 (MST)<br />
<br />
I'm sure AVJohn is very happy with you pissing all over his page just to prove a point Trout. And how nice of you to make it personal. So thanks for the lessons on properly maintaining a wiki, you're a real champ. --[[User:Zaerc|Zaerc]] 02:50, 24 September 2007 (MST)<br />
<br />
:Keep the articles clean and use the discussion-pages for...ahh, discussions! And when you reply, please indent, it's so much easier to follow a discussion that way. --[[User:Samme|Samme]] 02:58, 24 September 2007 (MST)<br />
<br />
:Zaerc, you keep making it more clear that you don't understand how a wiki works. First of all, I tried to be nice by just moving the discussion piece of the page to the discussion area. This was not acceptable to you, and you moved it back with a nasty comment. I tried again with the same result, and a worse comment from you. So, IMO you are the one who made it personal. Second, when you sait "... all over <strong>his</strong> page", you are completely wrong about page ownership. The page belongs to the wiki and it's not personally AVJohns, this misunderstanding of yours is exactly what caused you to be upset to see "your text" moved to the discussion page. Having the discussion moved to it's correct place is not something to take personally. BTW: you're welcome for the wiki lessons. [[User:Trout|Trout]] 04:50, 24 September 2007 (MST)<br />
<br />
::So I'm the one putting a personal rant aimed at you on that page? Have some respect for the people who actually contribute, because it seems more like all the pages here belong to you. --[[User:Zaerc|Zaerc]] 07:40, 24 September 2007 (MST)<br />
<br />
:::Yes, this is an insult to me "please don't edit pages unless you actually have something to add". I feel that I am adding clarity when I move your comments to the discussion page. You are personally attacking me when you imply I am not adding anything. "go find something usefull to do, instead of pestering people that actually add information" Again another insult, implying that I have nothing better to do than mess with your addition for no purpose. Also discounting my contributions as though they are somehow less important than yours. I don't think that all the pages belong to me and I have stated so. I am sorry if you perceived that, it was not my intent. <br />
:::I really think that the page is better served without different options of editing a file. The page is about detecting serial ports, not how to create a text file. It should be enough to say "create a file like this ..." IMO this would serve the users best. [[User:Trout|Trout]] 09:07, 24 September 2007 (MST)<br />
<br />
::'''Hey hey hey!''' No you have to stop, both of you, we're in this together, work with each other, not against each other, now we end this discussion and continue the work with the wiki - '''and''' from now on discussions goes on to the pages that are designated for discussions so we can stick to the facts in the articles. Do we have a agreement? --[[User:Samme|Samme]] 09:49, 24 September 2007 (MST)<br />
<br />
:::Samme, Of course I'm in agreement, this was my point from the beginning. [[User:Trout|Trout]] 10:57, 24 September 2007 (MST)<br />
<br />
::::You guys make me sick with all your hypocritical bullshit. And then that pathetic excuse that this is to "serve" the users, seems pretty obvious this is '''not''' done in ''their'' best interest. But I guess coming forward to say what it is really about would actually take a pair. --[[User:Zaerc|Zaerc]] 11:56, 25 September 2007 (MST)<br />
<br />
Hi, i took the liberty to add a new page to the wiki [[Editing_Text]] where I put the tricks the two of you offered.<br />
<br />
And I linked to the new page from the appropriate passage within the article...<br />
<br />
I hope, this will end the fight... And I hope I will read a lot from both of you on this wiki in the future.<br />
<br />
Best Regards, [[User:Chewi|Chewi]]<br />
<br />
== Comment about better solutions by AVJohn ==<br />
<br />
I would suggest, that we leave the comment about finding better versions in there.<br />
The reason is that the article describes a hack and AVJohn says in his article that the new script is inferior to the original script.<br />
So the request for other/better solutions is an important notice to<br />
<br />
A) let people know it is only a hack<br />
<br />
B) remind others that have acomplished it a different way to add their version<br />
<br />
C) make other Developers make a "more undirty" workaround<br />
<br />
D) remind actual LMCE-Developers (no offence to AVJohn) to provide an improvement/update that makes the hack unnessasary.<br />
<br />
So I endorse to go back to the previous version for those reasons. Feel free to add your oppinions.<br />
<br />
Best regards, --[[User:Chewi|Chewi]] 07:00, 27 September 2007 (MST)<br />
<br />
<br />
The discussion belongs here IMO. Otherwise it grows out of control into a forum. Not that there's anything wrong with the discussion, but it just doesn't belong on the main page. Think about it from the point of view of someone who just wants to know the best way right now. They don't want to wade through a lot of discussion text to get the answer.<br />
<br />
A) they should know it's a hack by the title<br />
B) someone who's already accomplished it probably either 1) wants to edit the wiki with their knowledge 2) is just checking out how wiki recommends it. The mere fact that it's a wiki is enough encouragement IMO.<br />
C) okay, but they don't want to wade through a pile of blogs to see the best result. They only would want to see the best result (the wiki page) and compare it to what they have in mind.<br />
D) same as C)<br />
[[User:Trout|Trout]] 07:43, 27 September 2007 (MST)<br />
<br />
:''(Never said anything on the main-page ???)'' Basically, you're right with all of your points. But I still think that the extra-encouragement here would be a good thing, as a wiki-page without a comments-section feels like a final statement and feels like allowing editing only by "the inner circle", which is not the case here. This needs the extra-input. This is at least how I feel about wikis. Therefore, I stay with my recommendation. Regards--[[User:Chewi|Chewi]] 08:06, 27 September 2007 (MST)<br />
<br />
::''(I never said anything about main-page either.)'' I said "main page" e.g. There is a main page for every article (the link is labeled 'article') and there is a discussion for every article. That's what I was referring to. I will try to use 'article' now. You can have your opinion about "the inner circle" concept, but I don't feel that way. Also I believe that others know how to use a wiki and that the expectation is user participation. Also, you havn't said anything about the mess it'll make or how to prevent a flame war on the article instead of where it belongs (the discussion) [[User:Trout|Trout]] 08:23, 27 September 2007 (MST)<br />
<br />
:::Ok, that must have been a missunderstanding. Of course I think that discussions about the article itself belong here, just as we are having it now. And I don't want to move that part to the main page. Just for short annotations an area on the mail-article-page ;) is what I prefer. And an area for comments and annotations that does not serve as a forum or discussion-replacement, does not support flame wars. Those can happen everywhere, but I don't see why they should happen here in particular.<br />
<br />
:::I'm still not convinced, but it is not up to me. Let's see, if there are additional oppinions on this. Until then, lets leave it as it is right now, without comments. Best regards --[[User:Chewi|Chewi]] 09:48, 27 September 2007 (MST)<br />
<br />
== does this fix the "serial hack" ? ==<br />
<br />
does this fix the "serial hack" ? [[Blocking Access To Serial Port]] [[User:Trout|Trout]] 12:21, 28 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Lozzo&diff=5886User talk:Lozzo2007-09-28T18:58:41Z<p>Trout: </p>
<hr />
<div>Hi Lozzo.</div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Video_Screenshots&diff=5867Talk:Video Screenshots2007-09-28T16:54:19Z<p>Trout: </p>
<hr />
<div>what's up with this page?<br />
Should it be deleted? [[User:Trout|Trout]] 09:54, 28 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Text_Formatting_Options&diff=5866Text Formatting Options2007-09-28T16:52:24Z<p>Trout: </p>
<hr />
<div>when the start of a line has a ~ there will be the following tokens between the next ~<br><br />
<br><br />
r right justiy<br><br />
l left justicy<br><br />
c center justify<br><br />
t top align<br><br />
m middle align<br><br />
b bottom align<br><br />
W word wrap<br><br />
B bold<br><br />
I italic<br><br />
U underline<br><br />
X or x means opposite of next char, so XW means no word wrap<br></div>Trouthttp://wiki.linuxmce.org/index.php?title=FiireEngine&diff=5865FiireEngine2007-09-28T10:15:18Z<p>Trout: just redirect...</p>
<hr />
<div>#REDIRECT [[Fiire Engine]].</div>Trouthttp://wiki.linuxmce.org/index.php?title=Upcoming_Features&diff=5847Upcoming Features2007-09-27T17:23:23Z<p>Trout: </p>
<hr />
<div>#REDIRECT [[Current events]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Serial_Hack&diff=5844Talk:Serial Hack2007-09-27T15:23:29Z<p>Trout: /* Comment about better solutions by AVJohn */</p>
<hr />
<div>When you figure out a better way, edit the article. Until then this is just discussion. [[User:Trout|Trout]] 08:06, 21 September 2007 (MST)<br />
<br />
:When you have something usefull to add for a change, edit the article. Otherwise, quit pestering the people that do --[[User:Zaerc|Zaerc]] 12:59, 21 September 2007 (MST)<br />
<br />
I am at a loss to understand this battle. The original commit was another way to accomplish the same thing. There are a lot pages on this site that have very similar issues. What is the harm in giving people more than one option even if that option is one in the same. If nothing else it offers all of us an opportunity to learn something different. The second option (perl) is another example. Personally I feel both should be left on the page and just remove the editorial commitments as these are truly the things that belong in discussions. <br />
<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Good_practice Good Wiki Practices]<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Behavior_that_is_unacceptable Behavior that is unacceptable]<br />
--[[User:Rwilson131|Rwilson131]] 09:27, 23 September 2007 (MST)<br />
<br />
I'm sure AVJohn is very happy with you pissing all over his page just to prove a point Trout. And how nice of you to make it personal. So thanks for the lessons on properly maintaining a wiki, you're a real champ. --[[User:Zaerc|Zaerc]] 02:50, 24 September 2007 (MST)<br />
<br />
:Keep the articles clean and use the discussion-pages for...ahh, discussions! And when you reply, please indent, it's so much easier to follow a discussion that way. --[[User:Samme|Samme]] 02:58, 24 September 2007 (MST)<br />
<br />
:Zaerc, you keep making it more clear that you don't understand how a wiki works. First of all, I tried to be nice by just moving the discussion piece of the page to the discussion area. This was not acceptable to you, and you moved it back with a nasty comment. I tried again with the same result, and a worse comment from you. So, IMO you are the one who made it personal. Second, when you sait "... all over <strong>his</strong> page", you are completely wrong about page ownership. The page belongs to the wiki and it's not personally AVJohns, this misunderstanding of yours is exactly what caused you to be upset to see "your text" moved to the discussion page. Having the discussion moved to it's correct place is not something to take personally. BTW: you're welcome for the wiki lessons. [[User:Trout|Trout]] 04:50, 24 September 2007 (MST)<br />
<br />
::So I'm the one putting a personal rant aimed at you on that page? Have some respect for the people who actually contribute, because it seems more like all the pages here belong to you. --[[User:Zaerc|Zaerc]] 07:40, 24 September 2007 (MST)<br />
<br />
:::Yes, this is an insult to me "please don't edit pages unless you actually have something to add". I feel that I am adding clarity when I move your comments to the discussion page. You are personally attacking me when you imply I am not adding anything. "go find something usefull to do, instead of pestering people that actually add information" Again another insult, implying that I have nothing better to do than mess with your addition for no purpose. Also discounting my contributions as though they are somehow less important than yours. I don't think that all the pages belong to me and I have stated so. I am sorry if you perceived that, it was not my intent. <br />
:::I really think that the page is better served without different options of editing a file. The page is about detecting serial ports, not how to create a text file. It should be enough to say "create a file like this ..." IMO this would serve the users best. [[User:Trout|Trout]] 09:07, 24 September 2007 (MST)<br />
<br />
::'''Hey hey hey!''' No you have to stop, both of you, we're in this together, work with each other, not against each other, now we end this discussion and continue the work with the wiki - '''and''' from now on discussions goes on to the pages that are designated for discussions so we can stick to the facts in the articles. Do we have a agreement? --[[User:Samme|Samme]] 09:49, 24 September 2007 (MST)<br />
<br />
:::Samme, Of course I'm in agreement, this was my point from the beginning. [[User:Trout|Trout]] 10:57, 24 September 2007 (MST)<br />
<br />
::::You guys make me sick with all your hypocritical bullshit. And then that pathetic excuse that this is to "serve" the users, seems pretty obvious this is '''not''' done in ''their'' best interest. But I guess coming forward to say what it is really about would actually take a pair. --[[User:Zaerc|Zaerc]] 11:56, 25 September 2007 (MST)<br />
<br />
Hi, i took the liberty to add a new page to the wiki [[Editing_Text]] where I put the tricks the two of you offered.<br />
<br />
And I linked to the new page from the appropriate passage within the article...<br />
<br />
I hope, this will end the fight... And I hope I will read a lot from both of you on this wiki in the future.<br />
<br />
Best Regards, [[User:Chewi|Chewi]]<br />
<br />
== Comment about better solutions by AVJohn ==<br />
<br />
I would suggest, that we leave the comment about finding better versions in there.<br />
The reason is that the article describes a hack and AVJohn says in his article that the new script is inferior to the original script.<br />
So the request for other/better solutions is an important notice to<br />
<br />
A) let people know it is only a hack<br />
<br />
B) remind others that have acomplished it a different way to add their version<br />
<br />
C) make other Developers make a "more undirty" workaround<br />
<br />
D) remind actual LMCE-Developers (no offence to AVJohn) to provide an improvement/update that makes the hack unnessasary.<br />
<br />
So I endorse to go back to the previous version for those reasons. Feel free to add your oppinions.<br />
<br />
Best regards, --[[User:Chewi|Chewi]] 07:00, 27 September 2007 (MST)<br />
<br />
<br />
The discussion belongs here IMO. Otherwise it grows out of control into a forum. Not that there's anything wrong with the discussion, but it just doesn't belong on the main page. Think about it from the point of view of someone who just wants to know the best way right now. They don't want to wade through a lot of discussion text to get the answer.<br />
<br />
A) they should know it's a hack by the title<br />
B) someone who's already accomplished it probably either 1) wants to edit the wiki with their knowledge 2) is just checking out how wiki recommends it. The mere fact that it's a wiki is enough encouragement IMO.<br />
C) okay, but they don't want to wade through a pile of blogs to see the best result. They only would want to see the best result (the wiki page) and compare it to what they have in mind.<br />
D) same as C)<br />
[[User:Trout|Trout]] 07:43, 27 September 2007 (MST)<br />
<br />
:''(Never said anything on the main-page ???)'' Basically, you're right with all of your points. But I still think that the extra-encouragement here would be a good thing, as a wiki-page without a comments-section feels like a final statement and feels like allowing editing only by "the inner circle", which is not the case here. This needs the extra-input. This is at least how I feel about wikis. Therefore, I stay with my recommendation. Regards--[[User:Chewi|Chewi]] 08:06, 27 September 2007 (MST)<br />
<br />
::''(I never said anything about main-page either.)'' I said "main page" e.g. There is a main page for every article (the link is labeled 'article') and there is a discussion for every article. That's what I was referring to. I will try to use 'article' now. You can have your opinion about "the inner circle" concept, but I don't feel that way. Also I believe that others know how to use a wiki and that the expectation is user participation. Also, you havn't said anything about the mess it'll make or how to prevent a flame war on the article instead of where it belongs (the discussion) [[User:Trout|Trout]] 08:23, 27 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Serial_Hack&diff=5841Talk:Serial Hack2007-09-27T14:43:34Z<p>Trout: /* Comment about better solutions by AVJohn */</p>
<hr />
<div>When you figure out a better way, edit the article. Until then this is just discussion. [[User:Trout|Trout]] 08:06, 21 September 2007 (MST)<br />
<br />
:When you have something usefull to add for a change, edit the article. Otherwise, quit pestering the people that do --[[User:Zaerc|Zaerc]] 12:59, 21 September 2007 (MST)<br />
<br />
I am at a loss to understand this battle. The original commit was another way to accomplish the same thing. There are a lot pages on this site that have very similar issues. What is the harm in giving people more than one option even if that option is one in the same. If nothing else it offers all of us an opportunity to learn something different. The second option (perl) is another example. Personally I feel both should be left on the page and just remove the editorial commitments as these are truly the things that belong in discussions. <br />
<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Good_practice Good Wiki Practices]<br />
*[http://en.wikipedia.org/wiki/Wikipedia:Talk_page_guidelines#Behavior_that_is_unacceptable Behavior that is unacceptable]<br />
--[[User:Rwilson131|Rwilson131]] 09:27, 23 September 2007 (MST)<br />
<br />
I'm sure AVJohn is very happy with you pissing all over his page just to prove a point Trout. And how nice of you to make it personal. So thanks for the lessons on properly maintaining a wiki, you're a real champ. --[[User:Zaerc|Zaerc]] 02:50, 24 September 2007 (MST)<br />
<br />
:Keep the articles clean and use the discussion-pages for...ahh, discussions! And when you reply, please indent, it's so much easier to follow a discussion that way. --[[User:Samme|Samme]] 02:58, 24 September 2007 (MST)<br />
<br />
:Zaerc, you keep making it more clear that you don't understand how a wiki works. First of all, I tried to be nice by just moving the discussion piece of the page to the discussion area. This was not acceptable to you, and you moved it back with a nasty comment. I tried again with the same result, and a worse comment from you. So, IMO you are the one who made it personal. Second, when you sait "... all over <strong>his</strong> page", you are completely wrong about page ownership. The page belongs to the wiki and it's not personally AVJohns, this misunderstanding of yours is exactly what caused you to be upset to see "your text" moved to the discussion page. Having the discussion moved to it's correct place is not something to take personally. BTW: you're welcome for the wiki lessons. [[User:Trout|Trout]] 04:50, 24 September 2007 (MST)<br />
<br />
::So I'm the one putting a personal rant aimed at you on that page? Have some respect for the people who actually contribute, because it seems more like all the pages here belong to you. --[[User:Zaerc|Zaerc]] 07:40, 24 September 2007 (MST)<br />
<br />
:::Yes, this is an insult to me "please don't edit pages unless you actually have something to add". I feel that I am adding clarity when I move your comments to the discussion page. You are personally attacking me when you imply I am not adding anything. "go find something usefull to do, instead of pestering people that actually add information" Again another insult, implying that I have nothing better to do than mess with your addition for no purpose. Also discounting my contributions as though they are somehow less important than yours. I don't think that all the pages belong to me and I have stated so. I am sorry if you perceived that, it was not my intent. <br />
:::I really think that the page is better served without different options of editing a file. The page is about detecting serial ports, not how to create a text file. It should be enough to say "create a file like this ..." IMO this would serve the users best. [[User:Trout|Trout]] 09:07, 24 September 2007 (MST)<br />
<br />
::'''Hey hey hey!''' No you have to stop, both of you, we're in this together, work with each other, not against each other, now we end this discussion and continue the work with the wiki - '''and''' from now on discussions goes on to the pages that are designated for discussions so we can stick to the facts in the articles. Do we have a agreement? --[[User:Samme|Samme]] 09:49, 24 September 2007 (MST)<br />
<br />
:::Samme, Of course I'm in agreement, this was my point from the beginning. [[User:Trout|Trout]] 10:57, 24 September 2007 (MST)<br />
<br />
::::You guys make me sick with all your hypocritical bullshit. And then that pathetic excuse that this is to "serve" the users, seems pretty obvious this is '''not''' done in ''their'' best interest. But I guess coming forward to say what it is really about would actually take a pair. --[[User:Zaerc|Zaerc]] 11:56, 25 September 2007 (MST)<br />
<br />
Hi, i took the liberty to add a new page to the wiki [[Editing_Text]] where I put the tricks the two of you offered.<br />
<br />
And I linked to the new page from the appropriate passage within the article...<br />
<br />
I hope, this will end the fight... And I hope I will read a lot from both of you on this wiki in the future.<br />
<br />
Best Regards, [[User:Chewi|Chewi]]<br />
<br />
== Comment about better solutions by AVJohn ==<br />
<br />
I would suggest, that we leave the comment about finding better versions in there.<br />
The reason is that the article describes a hack and AVJohn says in his article that the new script is inferior to the original script.<br />
So the request for other/better solutions is an important notice to<br />
<br />
A) let people know it is only a hack<br />
<br />
B) remind others that have acomplished it a different way to add their version<br />
<br />
C) make other Developers make a "more undirty" workaround<br />
<br />
D) remind actual LMCE-Developers (no offence to AVJohn) to provide an improvement/update that makes the hack unnessasary.<br />
<br />
So I endorse to go back to the previous version for those reasons. Feel free to add your oppinions.<br />
<br />
Best regards, --[[User:Chewi|Chewi]] 07:00, 27 September 2007 (MST)<br />
<br />
<br />
The discussion belongs here IMO. Otherwise it grows out of control into a forum. Not that there's anything wrong with the discussion, but it just doesn't belong on the main page. Think about it from the point of view of someone who just wants to know the best way right now. They don't want to wade through a lot of discussion text to get the answer.<br />
<br />
A) they should know it's a hack by the title<br />
B) someone who's already accomplished it probably either 1) wants to edit the wiki with their knowledge 2) is just checking out how wiki recommends it. The mere fact that it's a wiki is enough encouragement IMO.<br />
C) okay, but they don't want to wade through a pile of blogs to see the best result. They only would want to see the best result (the wiki page) and compare it to what they have in mind.<br />
D) same as C)<br />
[[User:Trout|Trout]] 07:43, 27 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Serial_Hack&diff=5838Serial Hack2007-09-27T13:18:35Z<p>Trout: don't need to ask for more trouble on the main page.</p>
<hr />
<div>== Serial List Hack ==<br />
In some situations, (which, I might add are becoming more and more common now) a core or core/hybrid may not have enough, or indeed, any serial ports for automation kit such as the [[X10]] modules to jack into.<br />
<br />
In these cases a [[USB-to-Serial converter]] may be used, but LinuxMCE does not list these correctly in its admin pages. This is due to the script "/usr/pluto/bin/ListSerialPorts.sh" which creates the list of serial ports, not giving the correct path (usually /dev/ttyUSB#, where # is a number).<br />
<br />
A simple replacement, which, while inferior to the current script in that it does not detect the ports in use, does correctly list all serial ports, both USB and normal serial. However, it requires the 'tree' command, so:<br />
<br />
<br />
<pre>sudo apt-get install tree</pre><br />
<br />
<br />
Once that has completed, tree will have been installed, and we can use its '-fi' mode to produce full paths, then it is just a simple matter of removing the origional ListSerialPorts.sh file and writing our own, I use [[vim]] for this, but any other terminal or graphical text editor will do the job (see [[Editing_Text]]):<br />
<br />
<br />
<pre><br />
sudo rm /usr/pluto/bin/ListSerialPorts.sh<br />
sudo vim /usr/pluto/bin/ListSerialPorts.sh<br />
</pre><br />
<br />
<br />
Now that [[vim]] is open, enter the following:<br />
<br />
<br />
<pre><br />
#!/bin/bash<br />
<br />
tree -fi /dev | grep ttyS<br />
tree -fi /dev | grep ttyUSB<br />
</pre><br />
<br />
<br />
[[Category: GSD]]<br />
[[Category: LinuxMCE_Devices]]<br />
[[Category: Programmer's Guide]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=Backend&diff=5825Backend2007-09-27T10:51:57Z<p>Trout: if it's aka, it should be a redirect</p>
<hr />
<div>#REDIRECT [[Core]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=The_backend&diff=5824The backend2007-09-27T10:51:32Z<p>Trout: if it's aka, it should be a redirect</p>
<hr />
<div>#REDIRECT [[Core]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=User:Avajon&diff=5717User:Avajon2007-09-26T17:15:15Z<p>Trout: </p>
<hr />
<div>Your english is not that bad, it's actually pretty good !</div>Trouthttp://wiki.linuxmce.org/index.php?title=Getting_Started&diff=5715Getting Started2007-09-26T09:55:30Z<p>Trout: /* A Dealer Core */</p>
<hr />
<div>==Equipment: Picking The Right Components==<br />
<br />
''See also: [[Tested good hardware]] and [[Tested bad hardware]]''<br />
<br />
===The Core===<br />
<br />
Most important, is the "[[core]]". This is the main LinuxMCE server that runs all the applications. The commercial version uses a high-end server with RAID-5 storage. You'll probably be able to get by with a good Pentium 4, at least 80 GB of storage and two network cards (Gigabit ideally).<br />
<br />
It would be best to use a dedicated core, which means you'll end up putting this computer somewhere out of the way and not connecting a monitor to it. If you are using only one computer for your system, then you've chosen the "hybrid" system, which means that your core will also be your media player. You'll definitely need a monitor or TV for this system!<br />
<br />
===Media Directors===<br />
<br />
Note that each [[media director]] will need a [[Bluetooth dongle]] if you want to use a Bluetooth mobile phone as the remote in that area. To control your a/v equipment using [[infrared]], you will need an interface module (global cache [[gc100]]). This interface module also gives you extra serial ports. So, in this example, the TV is controlled by [[infrared]], and the receiver by RS232.<br />
<br />
''See also: [[Sound Cards]] and [[Network_Boot_for_Media_Directors]]''<br />
<br />
===Orbiters===<br />
<br />
===Network Attached Storage===<br />
<br />
An alternative to having a lot of storage space in the core is to have a small hard drive for the core and store all your files on a [[Network Attached Storage|network attached storage]] (or NAS) server. The [[Buffalo TeraStation]] is 1.0 TeraByte RAID-5 and under $1K(US). Having a NAS will allow you to not lose your precious media files. You'll likely want the larger storage for your collection of music and videos. Keep in mind that your LinuxMCE system can also record TV shows (using MythTV) and video from your security cameras (using Motion).<br />
<br />
===Additional Devices===<br />
<br />
''See also [[Recommended Accessories]]''<br />
<br />
Optionally, you may want the aforementioned home automation devices for controlling your lights. Also, optionally, you may want security cameras, plasma screen TV, a streaming media music player such as the [[Squeezebox]], an alarm system with a serial interface, etc. Some of these devices need ''another'' device called a [[gc100]]. This allows devices that communicate using a serial port (good alarm panels) or [[infrared]] (like your TV) to connect to the network and talk with your LinuxMCE core.<br />
<br />
===Location Considerations===<br />
<br />
This section has been moved to [[Choosing Locations]].<br />
<br />
===Wiring Considerations===<br />
<br />
''Main article: [[Wiring Considerations]]''<br />
<br />
Once LinuxMCE is installed, just treat it like an appliance--plug it in, turn it on, and leave it alone. The great news is that don't need to install any software on the media PCs that will be used as media directors. You can leave whatever operating system is on there, such as Windows, untouched-they will do a [[Network Boot for Media Directors]] when you want to use them as a Media Director.<br />
<br />
The only special requirement is that the LinuxMCE Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). In our Core, we provide [[Why dual network cards?|dual network cards]] one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.<br />
<br />
==Setting Up The Hardware==<br />
<br />
There are many ways to install LinuxMCE, and lots of options for equipment. However, the key components in a LinuxMCE system are the Core (the PC acting as the master server), Media Directors (media PC's connected to your TV's), and Orbiters (remote controls-web pads, pda's, mobile phones, etc.).<br />
<br />
===A Dealer Core===<br />
<br />
<p>If you buy from a Pro dealer, they will come to your home, analyze your situation, and make the decision with you. They will offer a complete, custom-installed solution.</p><br />
<p>If you buy from regular dealer, the first thing you will need to get is 1 Core. This is the brains behind the whole system, and it must run 24/7 since it will be providing all the services in your home, like the DHCP, security system, media server, phones, etc. Also, all the media in the home (movies, music, etc.) will be stored on the Core. Most dealers sell Cores that are commercial servers with massive storage and full redundancy so they will run non-stop without incident. Since these Cores are often bulky, they are normally tucked away in a wiring closet or equipment rack. However, you can also hook the Core up to your TV and use it as your first media director--we call this a hybrid. Prices for Cores vary from under $1,000 for a basic Pentium PC, up to $7,000+ for a dual Xeon model with 4TB of storage. See our [[***Core comparison***]] guide for help deciding.</p><br />
<p>Then for each TV area where you want media you will need a media director. It's easy to add or remove media directors at any time. See our [[***media director comparison guide***]].</p><br />
<p>For Orbiters you can either buy touch-screen tablets from a LinuxMCE dealer [[***comparison guide***]]. Be sure to get a Bluetooth-enabled Symbian http://www.series60.com phone from your local mobile phone carrier--they make great remote controls.</p><br />
<br />
<p>Also view our http://www.linuxmce.org/wiki/index.php/LinuxMCE:Compability to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.</p><br />
<br />
=== I will use my own PC's ===<br />
<br />
<p><b>First a warning</b> LinuxMCE is Linux-based, but don't worry. Sometimes drivers are not available for Linux as soon as they are for Windows. Particularly, if you bought some new, exotic hardware there may not be drivers. If you're looking to get some new hardware to run LinuxMCE you may want to check sites like http://www.linuxcompatible.org to be sure it's supported under Linux before you buy. Or maybe post a "will this work?" message in our forum. If you already have the hardware it can't hurt to try.</p><br />
<br />
<p>You will need one PC to run the <b>Core</b> software. Although you could install the Core on top of your existing Windows/Linux o/s, or build from source, it will be tricky and you will miss out on a lot of features. You really needs to use our own distribution because, in addition to our own software, LinuxMCE also includes lots of other open source projects, like Asterisk, Firefox, Xine, VideoLan, etc. We built "wrappers" for all of them which is how we get them all to work together seamlessly. For example, if you start watching a movie in 1 room, LinuxMCE will use Xine on that local media director. Use the orbiter to move that movie to 2 rooms, and LinuxMCE seamlessly detects the network capabilities (multi-cast switch, etc.), moves the video source to the Core using VideoLan, broadcasts to both rooms, uses VLC to do the rendering and changes the UI on the remote controls. If you use the vanilla packages from, say Fedora, none of that will work. Plus, a lot of LinuxMCE's more advanced, kernel-level modules, like plug-and-play, bandwidth shaping to ensure your phone calls are clear, network boot, and so on may not work on other Linux distributions and definitely cannot be done under Windows.</p><br />
<br />
<p>Note this PC should always be left on since it becomes the 'brains' for the whole house and all the other pieces won't function unless they can find the <b>Core</b>. In our commercial product, the Core is a fail-safe, redundant server.</p><br />
<br />
<p>There is only <b>one special requirement</b>. The Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). If you have another DHCP server (like a cable/dsl modem), we recommend your Core have dual network cards: one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.</p><br />
<br />
<p>You can also put other cards in the Core, such as analog phone line interfaces from www.digium.com for the phone system or analog video capture cards for surveillance cameras. You can put the PVR/satellite capture cards in the individual media PC's, or you can put several in the Core, which will share the video throughout the house.</p><br />
<br />
<p>Wherever you have a TV/Stereo you can use a PC or thin-client as the Media Director--it doesn't need to be on all the time and there's no software to install since they will network boot off the Core. Just be sure it has a good Linux-compatible sound card, a Linux-compatible video card, supports PXE network boot (nearly all recent motherboards do), and--optionally--a PVR card. To use the Bluetooth mobile phones as remote controls, add a USB Bluetooth Dongle for each media director (around $25). All the media directors will report the signal strengths of all the mobile phones--this is how the Core figures out what room you're in. Since all resources in the whole house are shared, you will be able to control any device in any room from anywhere--as long as you're within Bluetooth range of any media director (about 10m or 30feet), you will have control over everything in the house. You can also use low-cost network audio players, like the Squeeze Box, wherever you want to add music.</p><br />
<br />
<p>To control the system, you can use the PC's mouse and keyboard, or an infrared remote, or run the Orbiter software on your mobile phones, webpads and PDA's.</p><br />
<br />
Also view our [[tested good hardware]] to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.<br />
<br />
===A Dedicated Core===<br />
<br />
<p>The Core is the central point of the Linux MCE system and runs applications and daemons needed for the other devices to exchange messages. A dedicated core will run only the backed applications and will not provide any fronted except the web interface, this means you won't act as a media center. You'll need to use Media Directors to be able to play movies, listen to music and watch TV. This kind of setup is recommended when you have lot of extra devices, this way the back end applications will have full access to Core's resources.</p><br><br />
<br />
[[Image:Diagram1.jpg|200px]]<br />
<br />
===A Dedicated Hybrid===<br />
<br />
A "hybrid" just means the computer that is running is the "Core" software is also running the "Media Director" software-you use the Core as a Media Director. The only reason we don't recommend this in our high-end installations is because a computer suitable for a Core is usually a pretty massive box with major hard drive capacity and rather noisy, so it's shoved away in the wiring closet, rather than sitting next to a TV like a Media Director would. However, you can use a regular PC as the Core + Media Director (Hybrid) also. Just remember that it will need to always be on since the Core software is what controls everything in the house.<br />
<br />
[[Image:Diagram2.jpg|200px]]<br />
<br />
Be sure you complete the installation of your Core/Hybrid before trying to boot the media directors.<br />
<br />
==Installation==<br />
<br />
===Pre-installation Setup===<br />
<br />
'''Note:''' During the installation, you may have some difficulties that can be avoided by following the advice below:<br />
<br />
# Make sure you have an Internet connection prior to starting! After LinuxMCE installs, it will need to access the Internet and download the latest patches. (More often than not, you want this!)<br />
# Confused about which internet adapter should be your "main" when that option is given to you during the install? Just click on one. You have a 50/50 chance of getting it right. You can easily change it later in the [[LinuxMCE-Website Admin]] pages by selecting "Advanced -> Network -> Network Settings" from the drop-down and clicking "Swap Interfaces".<br />
# Use the core's DHCP server to give machines on your network a dynamic IP address. Turn off the DHCP server on any other devices you may have on your network! <i>This is very important!</i> You probably already have your home router giving out addresses. Check the configuration and turn that feature off. LinuxMCE uses the DHCP requests from machines that come online to figure out what they are and what to do with them.<br />
# A map of your home. This is actually a very important step because LinuxMCE seems to need the map to properly finish the installation of some devices. It is easy to create a map using any drawing software or just draw one by hand and scan it. You don't need anything fancy, just some squares representing your different rooms. If the file is too big, LinuxMCE will scale it to fit. You can always upload a new map later on when you feel like being more creative. You can also make multiple maps, say, one for each floor or section of your house. This will all make more sense later when you get into configuring the devices.<br />
<br />
===Download===<br />
Download the Kubuntu installer and optional packages ISO from [http://linuxmce.org/wiki/index.php/Download_Instructions here].<br />
<br />
===Software Installation===<br />
<br />
You can find Steps for installing Linux MCE on a Kubuntu 7.04 system [http://wiki.linuxmce.org/index.php/Installation_Guide here].<br />
<br />
===Finalize The Install===<br />
<br />
<p>After you have set everything up, you should do a full reboot of the "LinuxMCE universe", meaning rebooting the Core/Hybrid plus any media directors.<br />
You can do this by choosing "Restart" from the LinuxMCE Admin site wizard (the last option), or from any orbiter or media director by clicking the LinuxMCE logo on the main menu and choosing "Reboot Core".</p><br />
<p>If your media directors support both software power off and wake on lan, the core will turn them off before it reboots itself, and will turn them back on when it has finished booting up. If not, you may need to reboot the media directors manually by cycling power on them. Note that you should not turn the media directors on until the Core/Hybrid has finished booting up.</p><br />
<br />
==Configuration==<br />
<br />
===Tell LinuxMCE About Your Home===<br />
<br />
[[Tell LinuxMCE about your home]] shows you how to use our LinuxMCE Admin wizard. In about 2 hours you can have everything setup--the whole-house media server, full control all your lights, climate, and tv/hi-fi gear, the phone system, follow-me, everything. It's quick, painless, and non-technical.<br />
<br />
===Adding Other Devices===<br />
<br />
If you chose a "Core", not being used as a Media Director, then it will boot up and you will see a simple menu like this:<br><br />
[[Image:Console.jpg|200px]]<br />
<em>LinuxMCE Core; After boot-up menu</em><br><br><br />
<p>You don't need to do anything. Your Core is up and running. Just make note of the IP address - you will need it to configure the system. </p><br />
<p>If you chose a "Hybrid", that is you are using your Core as a Media Director, it will boot up to the same welcome menu as any media director. Note that the welcome menu will appear on the first boot. After that, it will boot to the normal main menu, however, you can click the LinuxMCE logo in the lower left corner of the main menu to see the advanced options, including all the buttons on the welcome menu.</p><br><br />
[[Image:Welcome.jpg|200px]]<br />
<br />
<p>You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]<br />
Since the Hybrid + Media Directors have one built in, you can just click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/linuxmce_admin where myip is the IP address of the<br />
Core/Hybrid. <br />
Login then click [[Wizard Pages|Wizard]]. You will see the following screen.</p><br />
[[Image:Wizard.jpg|200px]]<br />
<br />
<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers. <br />
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.</p><br />
<p><b>EXAMPLE: Adding other devices</b></p><p>Example:<br />
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some tv's and stereo's to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.<br />
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p><br />
<br />
<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].<br />
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the tv's and stereo's it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].<br />
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].<br />
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used with an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p><br />
<p>Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.<br />
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your tv's and stereo's on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p><br />
<br />
<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel. <br />
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p><br />
<br />
<p>Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.</p><br />
<br />
===Scenarios, Events & Security===<br />
<br />
<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p><br />
<br />
===Configuring Myth TV===<br />
<br />
This section has been moved to [[Setting up MythTV]].<br />
<br />
===Upload Your Media===<br />
<br />
<p>There will also be Microsoft Windows compatible network shares on the Core or Hybrid (uses Samba) . There is a "public" share for putting all files that the whole family can share--movies, music, etc. And there is a private share for each family member. To access these network shares in Windows, choose Start, Run, and type \\ plus the IP address of the Core or hybrid. <br />
<br />
For example: \\192.168.80.1 Note that if you add new family members, their network share will not be available until after you reboot the Core/Hybrid. Once you copy your media into the appropriate folder, you can go into the LinuxMCE Admin site, choose "Files &amp; Media" and "Media Files Sync" to be sure your media is in the database, add attributes (artist, actor, etc.), and choose cover art.</p><br />
<br />
==Using LinuxMCE==<br />
<br />
This section has been moved to [[Using LinuxMCE]]. In 10 minutes you'll be up to speed and using all of LinuxMCE's features.<br />
<br />
<p><b>Using LinuxMCE with an Orbiter</b></p><br />
<p>Orbiter is just our way of saying remote control. All the Media Directors run an on-screen Orbiter, like the one below. Choose options on the on-screen orbiter with a keyboard/mouse attached to the media director, or with an infrared remote control. The Orbiter software runs on Linux, Windows and Windows CE, and can also be run on webpads and PDA's.<br />
Either way, it works exactly the same.</p><p>Below is the main menu. In the lower right are the [[Who Am I, Where Am I|'who' and 'where']] buttons. This indicates what room you are in, or want to control, and which family member is using the Orbiter. <br />
<br />
Touch either button if this isn't correct. Even if you are using an on-screen orbiter on the media director in the Living Room, for example, you can still change the location to the Bedroom. That means you would be using the Media Director in the Living Room as a remote control for the devices in the bedroom. Normally you don't change the location for an on-screen orbiter, since that device stays in a fixed place, but you do when you have a wireless web pad or pda you carry around.</p><br />
<br />
<p>The icons on the left all lead to a [[maps]], or floorplan, of your house showing your lighting, media, climate, telecom and security devices. Next to each of the floorplan icons are the scenarios for that category and the given room. In the scenarios section of the LinuxMCE Admin web site you create the scenarios for each room. You can have a lighting scenario called 'entertaining guests' that sets some lights, plays some background music, unlocks the door, and so on.<br />
<br><br />
[[Image:Main-menu.jpg|200px]]<br />
<br />
[[Image:Litscen.jpg|200px]]<br><br />
<br />
<p><b>NOTE:</b><br />
Many orbiters have relatively slow processors (like PDA's and phones) and may be running on slow wi-fi connections. So, the orbiters do not retrieve the large, full-size graphics, scaling them, drawing the text, and rendering everything on the fly. <br />
<br />
Rather all the graphics on your Orbiter are pre-scaled and pre-rendered by OrbiterGen. This means that if you add new scenarios or devices, or change floorplans or skins, you won't see them immediately on the Orbiter. You must go to the 'Advanced<br />
Options' page by clicking the LinuxMCE logo on the main menu, and choose 'Regenerate this Orbiter'. You'll be asked to wait about 60 seconds or so while the renderer creates new graphics, and then the Orbiter will reload.</p><br />
<br />
<p><b>Using your system with a Mobile Orbiter</b></p><br />
<p>Unless you turned off the "Auto Detect new Bluetooth Phones" option for the Media Director, compatible Bluetooth Mobile phones will automatically be detected when they are within range of any Media Director if they have Bluetooth turned on. A message will appear on all the Orbiters asking if it's a phone, and if so, to whom it belongs. Be sure you add your family members to the LinuxMCE Admin web site before doing this. Also, you may need to turn on the TV to see the message on the on-screen orbiter.</p><br />
<br />
<p>If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.</p><p>The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" button. The "who" is determined when you chose to install the software. That family member is assumed to always be the user. And the "where" is automatic-whenever you come within range of a media director it will automatically switch to the correct location. You can press the button under the location if you want to control a location other than the one you are in.</p><br />
<br />
<p>Since the display is smaller, rather than showing all the scenarios on the main menu, you must first choose the category, like lighting, and then choose the scenario from the sub menu that appears. You can also hold the category to toggle 'follow-me' mode, indicated with a red F. So, if you hold down the 2 button, a red F appears for media. Now as you move around the house your media will follow you. All 5 categories have follow-me. <a<br />
href="http://linuxmce.org/index.php?section=how_LinuxMCE_works">Screen shots of the Mobile Orbiter</a> / [[User's manual]]</p><br />
<br />
==Troubleshooting==<br />
<br />
[[Testing_and_troubleshooting_devices]]<br />
<br />
<p>[[Development status for all modules|What works and what doesn't?]]</p><br />
<br />
<p>If you don't know Linux at all, you can go into the LinuxMCE Admin website and choose [[Outside Access]], and check the box to get outside assistance from LinuxMCE. You will pick a password you will give one of our tech support staff. When you do, your system will make a secure, encrypted connection back to our support staff giving us temporary access to your system. The connection is closed as soon as you uncheck the box. Without checking that box, nobody at LinuxMCE will have any access to your system.</p><br />
<br />
<p>This troubleshooting guide assumes some basic knowledge of Linux. In LinuxMCE, everything is a device. In the LinuxMCE Admin web site, you can choose [[Devices]], to see a list of all the devices in your installation. We recommend you don't make changes here - you can break things! The top level device is usually a computer, either the core or a hybrid or an orbiter. All the logs for the devices on that computer are stored in /var/log/pluto. You can ssh in to the core using the root password you chose, and from there, you can ssh to all the media directors-shared keys were automatically setup.</p><br />
<p>All current activity is logged in the file that ends in ".newlog". After a device crashes, its logs are moved into<br />
the ".log" directory. At bootup, all logs are archived into /var/log/pluto/archives.</p><br />
<br />
<p>All DCE devices are running in separate screen sessions. Type "screen -ls" to see all active screen sessions,<br />
and "screen -r PID" where PID is the id you saw in the -ls list to attach to the screen session. There is not much for you to do or see though since all the output on stderr and stdout is going into the logs. DCERouter is running the same way on your core or hybrid.</p><br />
<br />
<p>At bootup, all the scripts listed in the LinuxMCE Admin website under [[Boot Sequence]] are run. If any programs crash, a core dump file is put in /usr/pluto/coredump. At each reboot, any core dumps are archived with the log files in /var/log/pluto/archives. A database dump/configuration snapshot are also put in each archive. Archives are deleted after 5 days.</p><br />
<br />
<p>If you're a programmer, you can also check out our [[Programmer's Guide]]. If you want to learn about writing DCE Devices, see the [[DCE]].<br />
</p><br />
<br />
<br />
''Note:''<br />
<p>We had to leave some basic features out of the free version due to licensing issues. See [http://www.geocities.com/medencid/index.html here] for a list. If you purchase a pre-built LinuxMCE system, some or all of these technologies may be licensed and the license fee built into the purchase price. Before contacting LinuxMCE support to ask why something doesn't work, please refer to that site so you know what features were left out intentionally. Note that LinuxMCE does not encourage, endorse or support users adding 3rd party modules, nor did LinuxMCE develop those modules. If you choose to add 3rd party modules we suggest you first confirm they are legal in your area.</p></div>Trouthttp://wiki.linuxmce.org/index.php?title=Getting_Started&diff=5714Getting Started2007-09-26T09:53:27Z<p>Trout: /* A Dealer Core */</p>
<hr />
<div>==Equipment: Picking The Right Components==<br />
<br />
''See also: [[Tested good hardware]] and [[Tested bad hardware]]''<br />
<br />
===The Core===<br />
<br />
Most important, is the "[[core]]". This is the main LinuxMCE server that runs all the applications. The commercial version uses a high-end server with RAID-5 storage. You'll probably be able to get by with a good Pentium 4, at least 80 GB of storage and two network cards (Gigabit ideally).<br />
<br />
It would be best to use a dedicated core, which means you'll end up putting this computer somewhere out of the way and not connecting a monitor to it. If you are using only one computer for your system, then you've chosen the "hybrid" system, which means that your core will also be your media player. You'll definitely need a monitor or TV for this system!<br />
<br />
===Media Directors===<br />
<br />
Note that each [[media director]] will need a [[Bluetooth dongle]] if you want to use a Bluetooth mobile phone as the remote in that area. To control your a/v equipment using [[infrared]], you will need an interface module (global cache [[gc100]]). This interface module also gives you extra serial ports. So, in this example, the TV is controlled by [[infrared]], and the receiver by RS232.<br />
<br />
''See also: [[Sound Cards]] and [[Network_Boot_for_Media_Directors]]''<br />
<br />
===Orbiters===<br />
<br />
===Network Attached Storage===<br />
<br />
An alternative to having a lot of storage space in the core is to have a small hard drive for the core and store all your files on a [[Network Attached Storage|network attached storage]] (or NAS) server. The [[Buffalo TeraStation]] is 1.0 TeraByte RAID-5 and under $1K(US). Having a NAS will allow you to not lose your precious media files. You'll likely want the larger storage for your collection of music and videos. Keep in mind that your LinuxMCE system can also record TV shows (using MythTV) and video from your security cameras (using Motion).<br />
<br />
===Additional Devices===<br />
<br />
''See also [[Recommended Accessories]]''<br />
<br />
Optionally, you may want the aforementioned home automation devices for controlling your lights. Also, optionally, you may want security cameras, plasma screen TV, a streaming media music player such as the [[Squeezebox]], an alarm system with a serial interface, etc. Some of these devices need ''another'' device called a [[gc100]]. This allows devices that communicate using a serial port (good alarm panels) or [[infrared]] (like your TV) to connect to the network and talk with your LinuxMCE core.<br />
<br />
===Location Considerations===<br />
<br />
This section has been moved to [[Choosing Locations]].<br />
<br />
===Wiring Considerations===<br />
<br />
''Main article: [[Wiring Considerations]]''<br />
<br />
Once LinuxMCE is installed, just treat it like an appliance--plug it in, turn it on, and leave it alone. The great news is that don't need to install any software on the media PCs that will be used as media directors. You can leave whatever operating system is on there, such as Windows, untouched-they will do a [[Network Boot for Media Directors]] when you want to use them as a Media Director.<br />
<br />
The only special requirement is that the LinuxMCE Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). In our Core, we provide [[Why dual network cards?|dual network cards]] one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.<br />
<br />
==Setting Up The Hardware==<br />
<br />
There are many ways to install LinuxMCE, and lots of options for equipment. However, the key components in a LinuxMCE system are the Core (the PC acting as the master server), Media Directors (media PC's connected to your TV's), and Orbiters (remote controls-web pads, pda's, mobile phones, etc.).<br />
<br />
===A Dealer Core===<br />
<br />
<p>If you buy from a Pro dealer, they will come to your home, analyze your situation, and make the decision with you. They will offer a complete, custom-installed solution.</p><br />
<p>If you buy from regular dealer, the first thing you will need to get is 1 Core. This is the brains behind the whole system, and it must run 24/7 since it will be providing all the services in your home, like the DHCP, security system, media server, phones, etc. Also, all the media in the home (movies, music, etc.) will be stored on the Core. Most dealers sell Cores that are commercial servers with massive storage and full redundancy so they will run non-stop without incident. Since these Cores are often bulky, they are normally tucked away in a wiring closet or equipment rack. However, you can also hook the Core up to your TV and use it as your first media director--we call this a hybrid. Prices for Cores vary from under $1,000 for a basic Pentium PC, up to $7,000+ for a dual Xeon model with 4TB of storage. See our ***Core comparison*** guide for help deciding.</p><br />
<p>Then for each TV area where you want media you will need a media director. It's easy to add or remove media directors at any time. See our ***media director comparison guide***.</p><br />
<p>For Orbiters you can either buy touch-screen tablets from a LinuxMCE dealer ***comparison guide***. Be sure to get a Bluetooth-enabled Symbian http://www.series60.com phone from your local mobile phone carrier--they make great remote controls.</p><br />
<br />
<p>Also view our http://www.linuxmce.org/wiki/index.php/LinuxMCE:Compability to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.</p><br />
<br />
=== I will use my own PC's ===<br />
<br />
<p><b>First a warning</b> LinuxMCE is Linux-based, but don't worry. Sometimes drivers are not available for Linux as soon as they are for Windows. Particularly, if you bought some new, exotic hardware there may not be drivers. If you're looking to get some new hardware to run LinuxMCE you may want to check sites like http://www.linuxcompatible.org to be sure it's supported under Linux before you buy. Or maybe post a "will this work?" message in our forum. If you already have the hardware it can't hurt to try.</p><br />
<br />
<p>You will need one PC to run the <b>Core</b> software. Although you could install the Core on top of your existing Windows/Linux o/s, or build from source, it will be tricky and you will miss out on a lot of features. You really needs to use our own distribution because, in addition to our own software, LinuxMCE also includes lots of other open source projects, like Asterisk, Firefox, Xine, VideoLan, etc. We built "wrappers" for all of them which is how we get them all to work together seamlessly. For example, if you start watching a movie in 1 room, LinuxMCE will use Xine on that local media director. Use the orbiter to move that movie to 2 rooms, and LinuxMCE seamlessly detects the network capabilities (multi-cast switch, etc.), moves the video source to the Core using VideoLan, broadcasts to both rooms, uses VLC to do the rendering and changes the UI on the remote controls. If you use the vanilla packages from, say Fedora, none of that will work. Plus, a lot of LinuxMCE's more advanced, kernel-level modules, like plug-and-play, bandwidth shaping to ensure your phone calls are clear, network boot, and so on may not work on other Linux distributions and definitely cannot be done under Windows.</p><br />
<br />
<p>Note this PC should always be left on since it becomes the 'brains' for the whole house and all the other pieces won't function unless they can find the <b>Core</b>. In our commercial product, the Core is a fail-safe, redundant server.</p><br />
<br />
<p>There is only <b>one special requirement</b>. The Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). If you have another DHCP server (like a cable/dsl modem), we recommend your Core have dual network cards: one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.</p><br />
<br />
<p>You can also put other cards in the Core, such as analog phone line interfaces from www.digium.com for the phone system or analog video capture cards for surveillance cameras. You can put the PVR/satellite capture cards in the individual media PC's, or you can put several in the Core, which will share the video throughout the house.</p><br />
<br />
<p>Wherever you have a TV/Stereo you can use a PC or thin-client as the Media Director--it doesn't need to be on all the time and there's no software to install since they will network boot off the Core. Just be sure it has a good Linux-compatible sound card, a Linux-compatible video card, supports PXE network boot (nearly all recent motherboards do), and--optionally--a PVR card. To use the Bluetooth mobile phones as remote controls, add a USB Bluetooth Dongle for each media director (around $25). All the media directors will report the signal strengths of all the mobile phones--this is how the Core figures out what room you're in. Since all resources in the whole house are shared, you will be able to control any device in any room from anywhere--as long as you're within Bluetooth range of any media director (about 10m or 30feet), you will have control over everything in the house. You can also use low-cost network audio players, like the Squeeze Box, wherever you want to add music.</p><br />
<br />
<p>To control the system, you can use the PC's mouse and keyboard, or an infrared remote, or run the Orbiter software on your mobile phones, webpads and PDA's.</p><br />
<br />
Also view our [[tested good hardware]] to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.<br />
<br />
===A Dedicated Core===<br />
<br />
<p>The Core is the central point of the Linux MCE system and runs applications and daemons needed for the other devices to exchange messages. A dedicated core will run only the backed applications and will not provide any fronted except the web interface, this means you won't act as a media center. You'll need to use Media Directors to be able to play movies, listen to music and watch TV. This kind of setup is recommended when you have lot of extra devices, this way the back end applications will have full access to Core's resources.</p><br><br />
<br />
[[Image:Diagram1.jpg|200px]]<br />
<br />
===A Dedicated Hybrid===<br />
<br />
A "hybrid" just means the computer that is running is the "Core" software is also running the "Media Director" software-you use the Core as a Media Director. The only reason we don't recommend this in our high-end installations is because a computer suitable for a Core is usually a pretty massive box with major hard drive capacity and rather noisy, so it's shoved away in the wiring closet, rather than sitting next to a TV like a Media Director would. However, you can use a regular PC as the Core + Media Director (Hybrid) also. Just remember that it will need to always be on since the Core software is what controls everything in the house.<br />
<br />
[[Image:Diagram2.jpg|200px]]<br />
<br />
Be sure you complete the installation of your Core/Hybrid before trying to boot the media directors.<br />
<br />
==Installation==<br />
<br />
===Pre-installation Setup===<br />
<br />
'''Note:''' During the installation, you may have some difficulties that can be avoided by following the advice below:<br />
<br />
# Make sure you have an Internet connection prior to starting! After LinuxMCE installs, it will need to access the Internet and download the latest patches. (More often than not, you want this!)<br />
# Confused about which internet adapter should be your "main" when that option is given to you during the install? Just click on one. You have a 50/50 chance of getting it right. You can easily change it later in the [[LinuxMCE-Website Admin]] pages by selecting "Advanced -> Network -> Network Settings" from the drop-down and clicking "Swap Interfaces".<br />
# Use the core's DHCP server to give machines on your network a dynamic IP address. Turn off the DHCP server on any other devices you may have on your network! <i>This is very important!</i> You probably already have your home router giving out addresses. Check the configuration and turn that feature off. LinuxMCE uses the DHCP requests from machines that come online to figure out what they are and what to do with them.<br />
# A map of your home. This is actually a very important step because LinuxMCE seems to need the map to properly finish the installation of some devices. It is easy to create a map using any drawing software or just draw one by hand and scan it. You don't need anything fancy, just some squares representing your different rooms. If the file is too big, LinuxMCE will scale it to fit. You can always upload a new map later on when you feel like being more creative. You can also make multiple maps, say, one for each floor or section of your house. This will all make more sense later when you get into configuring the devices.<br />
<br />
===Download===<br />
Download the Kubuntu installer and optional packages ISO from [http://linuxmce.org/wiki/index.php/Download_Instructions here].<br />
<br />
===Software Installation===<br />
<br />
You can find Steps for installing Linux MCE on a Kubuntu 7.04 system [http://wiki.linuxmce.org/index.php/Installation_Guide here].<br />
<br />
===Finalize The Install===<br />
<br />
<p>After you have set everything up, you should do a full reboot of the "LinuxMCE universe", meaning rebooting the Core/Hybrid plus any media directors.<br />
You can do this by choosing "Restart" from the LinuxMCE Admin site wizard (the last option), or from any orbiter or media director by clicking the LinuxMCE logo on the main menu and choosing "Reboot Core".</p><br />
<p>If your media directors support both software power off and wake on lan, the core will turn them off before it reboots itself, and will turn them back on when it has finished booting up. If not, you may need to reboot the media directors manually by cycling power on them. Note that you should not turn the media directors on until the Core/Hybrid has finished booting up.</p><br />
<br />
==Configuration==<br />
<br />
===Tell LinuxMCE About Your Home===<br />
<br />
[[Tell LinuxMCE about your home]] shows you how to use our LinuxMCE Admin wizard. In about 2 hours you can have everything setup--the whole-house media server, full control all your lights, climate, and tv/hi-fi gear, the phone system, follow-me, everything. It's quick, painless, and non-technical.<br />
<br />
===Adding Other Devices===<br />
<br />
If you chose a "Core", not being used as a Media Director, then it will boot up and you will see a simple menu like this:<br><br />
[[Image:Console.jpg|200px]]<br />
<em>LinuxMCE Core; After boot-up menu</em><br><br><br />
<p>You don't need to do anything. Your Core is up and running. Just make note of the IP address - you will need it to configure the system. </p><br />
<p>If you chose a "Hybrid", that is you are using your Core as a Media Director, it will boot up to the same welcome menu as any media director. Note that the welcome menu will appear on the first boot. After that, it will boot to the normal main menu, however, you can click the LinuxMCE logo in the lower left corner of the main menu to see the advanced options, including all the buttons on the welcome menu.</p><br><br />
[[Image:Welcome.jpg|200px]]<br />
<br />
<p>You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]<br />
Since the Hybrid + Media Directors have one built in, you can just click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/linuxmce_admin where myip is the IP address of the<br />
Core/Hybrid. <br />
Login then click [[Wizard Pages|Wizard]]. You will see the following screen.</p><br />
[[Image:Wizard.jpg|200px]]<br />
<br />
<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers. <br />
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.</p><br />
<p><b>EXAMPLE: Adding other devices</b></p><p>Example:<br />
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some tv's and stereo's to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.<br />
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p><br />
<br />
<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].<br />
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the tv's and stereo's it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].<br />
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].<br />
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used with an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p><br />
<p>Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.<br />
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your tv's and stereo's on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p><br />
<br />
<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel. <br />
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p><br />
<br />
<p>Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.</p><br />
<br />
===Scenarios, Events & Security===<br />
<br />
<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p><br />
<br />
===Configuring Myth TV===<br />
<br />
This section has been moved to [[Setting up MythTV]].<br />
<br />
===Upload Your Media===<br />
<br />
<p>There will also be Microsoft Windows compatible network shares on the Core or Hybrid (uses Samba) . There is a "public" share for putting all files that the whole family can share--movies, music, etc. And there is a private share for each family member. To access these network shares in Windows, choose Start, Run, and type \\ plus the IP address of the Core or hybrid. <br />
<br />
For example: \\192.168.80.1 Note that if you add new family members, their network share will not be available until after you reboot the Core/Hybrid. Once you copy your media into the appropriate folder, you can go into the LinuxMCE Admin site, choose "Files &amp; Media" and "Media Files Sync" to be sure your media is in the database, add attributes (artist, actor, etc.), and choose cover art.</p><br />
<br />
==Using LinuxMCE==<br />
<br />
This section has been moved to [[Using LinuxMCE]]. In 10 minutes you'll be up to speed and using all of LinuxMCE's features.<br />
<br />
<p><b>Using LinuxMCE with an Orbiter</b></p><br />
<p>Orbiter is just our way of saying remote control. All the Media Directors run an on-screen Orbiter, like the one below. Choose options on the on-screen orbiter with a keyboard/mouse attached to the media director, or with an infrared remote control. The Orbiter software runs on Linux, Windows and Windows CE, and can also be run on webpads and PDA's.<br />
Either way, it works exactly the same.</p><p>Below is the main menu. In the lower right are the [[Who Am I, Where Am I|'who' and 'where']] buttons. This indicates what room you are in, or want to control, and which family member is using the Orbiter. <br />
<br />
Touch either button if this isn't correct. Even if you are using an on-screen orbiter on the media director in the Living Room, for example, you can still change the location to the Bedroom. That means you would be using the Media Director in the Living Room as a remote control for the devices in the bedroom. Normally you don't change the location for an on-screen orbiter, since that device stays in a fixed place, but you do when you have a wireless web pad or pda you carry around.</p><br />
<br />
<p>The icons on the left all lead to a [[maps]], or floorplan, of your house showing your lighting, media, climate, telecom and security devices. Next to each of the floorplan icons are the scenarios for that category and the given room. In the scenarios section of the LinuxMCE Admin web site you create the scenarios for each room. You can have a lighting scenario called 'entertaining guests' that sets some lights, plays some background music, unlocks the door, and so on.<br />
<br><br />
[[Image:Main-menu.jpg|200px]]<br />
<br />
[[Image:Litscen.jpg|200px]]<br><br />
<br />
<p><b>NOTE:</b><br />
Many orbiters have relatively slow processors (like PDA's and phones) and may be running on slow wi-fi connections. So, the orbiters do not retrieve the large, full-size graphics, scaling them, drawing the text, and rendering everything on the fly. <br />
<br />
Rather all the graphics on your Orbiter are pre-scaled and pre-rendered by OrbiterGen. This means that if you add new scenarios or devices, or change floorplans or skins, you won't see them immediately on the Orbiter. You must go to the 'Advanced<br />
Options' page by clicking the LinuxMCE logo on the main menu, and choose 'Regenerate this Orbiter'. You'll be asked to wait about 60 seconds or so while the renderer creates new graphics, and then the Orbiter will reload.</p><br />
<br />
<p><b>Using your system with a Mobile Orbiter</b></p><br />
<p>Unless you turned off the "Auto Detect new Bluetooth Phones" option for the Media Director, compatible Bluetooth Mobile phones will automatically be detected when they are within range of any Media Director if they have Bluetooth turned on. A message will appear on all the Orbiters asking if it's a phone, and if so, to whom it belongs. Be sure you add your family members to the LinuxMCE Admin web site before doing this. Also, you may need to turn on the TV to see the message on the on-screen orbiter.</p><br />
<br />
<p>If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.</p><p>The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" button. The "who" is determined when you chose to install the software. That family member is assumed to always be the user. And the "where" is automatic-whenever you come within range of a media director it will automatically switch to the correct location. You can press the button under the location if you want to control a location other than the one you are in.</p><br />
<br />
<p>Since the display is smaller, rather than showing all the scenarios on the main menu, you must first choose the category, like lighting, and then choose the scenario from the sub menu that appears. You can also hold the category to toggle 'follow-me' mode, indicated with a red F. So, if you hold down the 2 button, a red F appears for media. Now as you move around the house your media will follow you. All 5 categories have follow-me. <a<br />
href="http://linuxmce.org/index.php?section=how_LinuxMCE_works">Screen shots of the Mobile Orbiter</a> / [[User's manual]]</p><br />
<br />
==Troubleshooting==<br />
<br />
[[Testing_and_troubleshooting_devices]]<br />
<br />
<p>[[Development status for all modules|What works and what doesn't?]]</p><br />
<br />
<p>If you don't know Linux at all, you can go into the LinuxMCE Admin website and choose [[Outside Access]], and check the box to get outside assistance from LinuxMCE. You will pick a password you will give one of our tech support staff. When you do, your system will make a secure, encrypted connection back to our support staff giving us temporary access to your system. The connection is closed as soon as you uncheck the box. Without checking that box, nobody at LinuxMCE will have any access to your system.</p><br />
<br />
<p>This troubleshooting guide assumes some basic knowledge of Linux. In LinuxMCE, everything is a device. In the LinuxMCE Admin web site, you can choose [[Devices]], to see a list of all the devices in your installation. We recommend you don't make changes here - you can break things! The top level device is usually a computer, either the core or a hybrid or an orbiter. All the logs for the devices on that computer are stored in /var/log/pluto. You can ssh in to the core using the root password you chose, and from there, you can ssh to all the media directors-shared keys were automatically setup.</p><br />
<p>All current activity is logged in the file that ends in ".newlog". After a device crashes, its logs are moved into<br />
the ".log" directory. At bootup, all logs are archived into /var/log/pluto/archives.</p><br />
<br />
<p>All DCE devices are running in separate screen sessions. Type "screen -ls" to see all active screen sessions,<br />
and "screen -r PID" where PID is the id you saw in the -ls list to attach to the screen session. There is not much for you to do or see though since all the output on stderr and stdout is going into the logs. DCERouter is running the same way on your core or hybrid.</p><br />
<br />
<p>At bootup, all the scripts listed in the LinuxMCE Admin website under [[Boot Sequence]] are run. If any programs crash, a core dump file is put in /usr/pluto/coredump. At each reboot, any core dumps are archived with the log files in /var/log/pluto/archives. A database dump/configuration snapshot are also put in each archive. Archives are deleted after 5 days.</p><br />
<br />
<p>If you're a programmer, you can also check out our [[Programmer's Guide]]. If you want to learn about writing DCE Devices, see the [[DCE]].<br />
</p><br />
<br />
<br />
''Note:''<br />
<p>We had to leave some basic features out of the free version due to licensing issues. See [http://www.geocities.com/medencid/index.html here] for a list. If you purchase a pre-built LinuxMCE system, some or all of these technologies may be licensed and the license fee built into the purchase price. Before contacting LinuxMCE support to ask why something doesn't work, please refer to that site so you know what features were left out intentionally. Note that LinuxMCE does not encourage, endorse or support users adding 3rd party modules, nor did LinuxMCE develop those modules. If you choose to add 3rd party modules we suggest you first confirm they are legal in your area.</p></div>Trouthttp://wiki.linuxmce.org/index.php?title=Getting_Started&diff=5713Getting Started2007-09-26T09:49:37Z<p>Trout: /* Additional Devices */</p>
<hr />
<div>==Equipment: Picking The Right Components==<br />
<br />
''See also: [[Tested good hardware]] and [[Tested bad hardware]]''<br />
<br />
===The Core===<br />
<br />
Most important, is the "[[core]]". This is the main LinuxMCE server that runs all the applications. The commercial version uses a high-end server with RAID-5 storage. You'll probably be able to get by with a good Pentium 4, at least 80 GB of storage and two network cards (Gigabit ideally).<br />
<br />
It would be best to use a dedicated core, which means you'll end up putting this computer somewhere out of the way and not connecting a monitor to it. If you are using only one computer for your system, then you've chosen the "hybrid" system, which means that your core will also be your media player. You'll definitely need a monitor or TV for this system!<br />
<br />
===Media Directors===<br />
<br />
Note that each [[media director]] will need a [[Bluetooth dongle]] if you want to use a Bluetooth mobile phone as the remote in that area. To control your a/v equipment using [[infrared]], you will need an interface module (global cache [[gc100]]). This interface module also gives you extra serial ports. So, in this example, the TV is controlled by [[infrared]], and the receiver by RS232.<br />
<br />
''See also: [[Sound Cards]] and [[Network_Boot_for_Media_Directors]]''<br />
<br />
===Orbiters===<br />
<br />
===Network Attached Storage===<br />
<br />
An alternative to having a lot of storage space in the core is to have a small hard drive for the core and store all your files on a [[Network Attached Storage|network attached storage]] (or NAS) server. The [[Buffalo TeraStation]] is 1.0 TeraByte RAID-5 and under $1K(US). Having a NAS will allow you to not lose your precious media files. You'll likely want the larger storage for your collection of music and videos. Keep in mind that your LinuxMCE system can also record TV shows (using MythTV) and video from your security cameras (using Motion).<br />
<br />
===Additional Devices===<br />
<br />
''See also [[Recommended Accessories]]''<br />
<br />
Optionally, you may want the aforementioned home automation devices for controlling your lights. Also, optionally, you may want security cameras, plasma screen TV, a streaming media music player such as the [[Squeezebox]], an alarm system with a serial interface, etc. Some of these devices need ''another'' device called a [[gc100]]. This allows devices that communicate using a serial port (good alarm panels) or [[infrared]] (like your TV) to connect to the network and talk with your LinuxMCE core.<br />
<br />
===Location Considerations===<br />
<br />
This section has been moved to [[Choosing Locations]].<br />
<br />
===Wiring Considerations===<br />
<br />
''Main article: [[Wiring Considerations]]''<br />
<br />
Once LinuxMCE is installed, just treat it like an appliance--plug it in, turn it on, and leave it alone. The great news is that don't need to install any software on the media PCs that will be used as media directors. You can leave whatever operating system is on there, such as Windows, untouched-they will do a [[Network Boot for Media Directors]] when you want to use them as a Media Director.<br />
<br />
The only special requirement is that the LinuxMCE Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). In our Core, we provide [[Why dual network cards?|dual network cards]] one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.<br />
<br />
==Setting Up The Hardware==<br />
<br />
There are many ways to install LinuxMCE, and lots of options for equipment. However, the key components in a LinuxMCE system are the Core (the PC acting as the master server), Media Directors (media PC's connected to your TV's), and Orbiters (remote controls-web pads, pda's, mobile phones, etc.).<br />
<br />
===A Dealer Core===<br />
<br />
<p>If you buy from a Pro dealer, they will come to your home, analyze your situation, and make the decision with you. They will offer a complete, custom-installed solution.</p><br />
<p>If you buy from regular dealer, the first thing you will need to get is 1 Core. This is the brains behind the whole system, and it must run 24/7 since it will be providing all the services in your home, like the security system, media server, phones, etc. Also, all the media in the home (movies, music, etc.) will be stored on the Core. Most dealers sell Cores that are commercial servers with massive storage and full redundancy so they will run non-stop without incident. Since these Cores are often bulky, they are normally tucked away in a wiring closet or equipment rack. However, you can also hook the Core up to your TV and use it as your first media director--we call this a hybrid. Prices for Cores vary from under $1,000 for a basic Pentium PC, up to $7,000+ for a dual Xeon model with 4TB of storage. See our ***Core comparison*** guide for help deciding.</p><br />
<p>Then for each TV area where you want media you will need a media director. It's easy to add or remove media directors at any time. See our ***media director comparison guide***.</p><br />
<p>For Orbiters you can either buy touch-screen tablets from a LinuxMCE dealer ***comparison guide***. Be sure to get a Bluetooth-enabled Symbian http://www.series60.com phone from your local mobile phone carrier--they make great remote controls.</p><br />
<br />
<p>Also view our http://www.linuxmce.org/wiki/index.php/LinuxMCE:Compability to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.</p><br />
<br />
=== I will use my own PC's ===<br />
<br />
<p><b>First a warning</b> LinuxMCE is Linux-based, but don't worry. Sometimes drivers are not available for Linux as soon as they are for Windows. Particularly, if you bought some new, exotic hardware there may not be drivers. If you're looking to get some new hardware to run LinuxMCE you may want to check sites like http://www.linuxcompatible.org to be sure it's supported under Linux before you buy. Or maybe post a "will this work?" message in our forum. If you already have the hardware it can't hurt to try.</p><br />
<br />
<p>You will need one PC to run the <b>Core</b> software. Although you could install the Core on top of your existing Windows/Linux o/s, or build from source, it will be tricky and you will miss out on a lot of features. You really needs to use our own distribution because, in addition to our own software, LinuxMCE also includes lots of other open source projects, like Asterisk, Firefox, Xine, VideoLan, etc. We built "wrappers" for all of them which is how we get them all to work together seamlessly. For example, if you start watching a movie in 1 room, LinuxMCE will use Xine on that local media director. Use the orbiter to move that movie to 2 rooms, and LinuxMCE seamlessly detects the network capabilities (multi-cast switch, etc.), moves the video source to the Core using VideoLan, broadcasts to both rooms, uses VLC to do the rendering and changes the UI on the remote controls. If you use the vanilla packages from, say Fedora, none of that will work. Plus, a lot of LinuxMCE's more advanced, kernel-level modules, like plug-and-play, bandwidth shaping to ensure your phone calls are clear, network boot, and so on may not work on other Linux distributions and definitely cannot be done under Windows.</p><br />
<br />
<p>Note this PC should always be left on since it becomes the 'brains' for the whole house and all the other pieces won't function unless they can find the <b>Core</b>. In our commercial product, the Core is a fail-safe, redundant server.</p><br />
<br />
<p>There is only <b>one special requirement</b>. The Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). If you have another DHCP server (like a cable/dsl modem), we recommend your Core have dual network cards: one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.</p><br />
<br />
<p>You can also put other cards in the Core, such as analog phone line interfaces from www.digium.com for the phone system or analog video capture cards for surveillance cameras. You can put the PVR/satellite capture cards in the individual media PC's, or you can put several in the Core, which will share the video throughout the house.</p><br />
<br />
<p>Wherever you have a TV/Stereo you can use a PC or thin-client as the Media Director--it doesn't need to be on all the time and there's no software to install since they will network boot off the Core. Just be sure it has a good Linux-compatible sound card, a Linux-compatible video card, supports PXE network boot (nearly all recent motherboards do), and--optionally--a PVR card. To use the Bluetooth mobile phones as remote controls, add a USB Bluetooth Dongle for each media director (around $25). All the media directors will report the signal strengths of all the mobile phones--this is how the Core figures out what room you're in. Since all resources in the whole house are shared, you will be able to control any device in any room from anywhere--as long as you're within Bluetooth range of any media director (about 10m or 30feet), you will have control over everything in the house. You can also use low-cost network audio players, like the Squeeze Box, wherever you want to add music.</p><br />
<br />
<p>To control the system, you can use the PC's mouse and keyboard, or an infrared remote, or run the Orbiter software on your mobile phones, webpads and PDA's.</p><br />
<br />
Also view our [[tested good hardware]] to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.<br />
<br />
===A Dedicated Core===<br />
<br />
<p>The Core is the central point of the Linux MCE system and runs applications and daemons needed for the other devices to exchange messages. A dedicated core will run only the backed applications and will not provide any fronted except the web interface, this means you won't act as a media center. You'll need to use Media Directors to be able to play movies, listen to music and watch TV. This kind of setup is recommended when you have lot of extra devices, this way the back end applications will have full access to Core's resources.</p><br><br />
<br />
[[Image:Diagram1.jpg|200px]]<br />
<br />
===A Dedicated Hybrid===<br />
<br />
A "hybrid" just means the computer that is running is the "Core" software is also running the "Media Director" software-you use the Core as a Media Director. The only reason we don't recommend this in our high-end installations is because a computer suitable for a Core is usually a pretty massive box with major hard drive capacity and rather noisy, so it's shoved away in the wiring closet, rather than sitting next to a TV like a Media Director would. However, you can use a regular PC as the Core + Media Director (Hybrid) also. Just remember that it will need to always be on since the Core software is what controls everything in the house.<br />
<br />
[[Image:Diagram2.jpg|200px]]<br />
<br />
Be sure you complete the installation of your Core/Hybrid before trying to boot the media directors.<br />
<br />
==Installation==<br />
<br />
===Pre-installation Setup===<br />
<br />
'''Note:''' During the installation, you may have some difficulties that can be avoided by following the advice below:<br />
<br />
# Make sure you have an Internet connection prior to starting! After LinuxMCE installs, it will need to access the Internet and download the latest patches. (More often than not, you want this!)<br />
# Confused about which internet adapter should be your "main" when that option is given to you during the install? Just click on one. You have a 50/50 chance of getting it right. You can easily change it later in the [[LinuxMCE-Website Admin]] pages by selecting "Advanced -> Network -> Network Settings" from the drop-down and clicking "Swap Interfaces".<br />
# Use the core's DHCP server to give machines on your network a dynamic IP address. Turn off the DHCP server on any other devices you may have on your network! <i>This is very important!</i> You probably already have your home router giving out addresses. Check the configuration and turn that feature off. LinuxMCE uses the DHCP requests from machines that come online to figure out what they are and what to do with them.<br />
# A map of your home. This is actually a very important step because LinuxMCE seems to need the map to properly finish the installation of some devices. It is easy to create a map using any drawing software or just draw one by hand and scan it. You don't need anything fancy, just some squares representing your different rooms. If the file is too big, LinuxMCE will scale it to fit. You can always upload a new map later on when you feel like being more creative. You can also make multiple maps, say, one for each floor or section of your house. This will all make more sense later when you get into configuring the devices.<br />
<br />
===Download===<br />
Download the Kubuntu installer and optional packages ISO from [http://linuxmce.org/wiki/index.php/Download_Instructions here].<br />
<br />
===Software Installation===<br />
<br />
You can find Steps for installing Linux MCE on a Kubuntu 7.04 system [http://wiki.linuxmce.org/index.php/Installation_Guide here].<br />
<br />
===Finalize The Install===<br />
<br />
<p>After you have set everything up, you should do a full reboot of the "LinuxMCE universe", meaning rebooting the Core/Hybrid plus any media directors.<br />
You can do this by choosing "Restart" from the LinuxMCE Admin site wizard (the last option), or from any orbiter or media director by clicking the LinuxMCE logo on the main menu and choosing "Reboot Core".</p><br />
<p>If your media directors support both software power off and wake on lan, the core will turn them off before it reboots itself, and will turn them back on when it has finished booting up. If not, you may need to reboot the media directors manually by cycling power on them. Note that you should not turn the media directors on until the Core/Hybrid has finished booting up.</p><br />
<br />
==Configuration==<br />
<br />
===Tell LinuxMCE About Your Home===<br />
<br />
[[Tell LinuxMCE about your home]] shows you how to use our LinuxMCE Admin wizard. In about 2 hours you can have everything setup--the whole-house media server, full control all your lights, climate, and tv/hi-fi gear, the phone system, follow-me, everything. It's quick, painless, and non-technical.<br />
<br />
===Adding Other Devices===<br />
<br />
If you chose a "Core", not being used as a Media Director, then it will boot up and you will see a simple menu like this:<br><br />
[[Image:Console.jpg|200px]]<br />
<em>LinuxMCE Core; After boot-up menu</em><br><br><br />
<p>You don't need to do anything. Your Core is up and running. Just make note of the IP address - you will need it to configure the system. </p><br />
<p>If you chose a "Hybrid", that is you are using your Core as a Media Director, it will boot up to the same welcome menu as any media director. Note that the welcome menu will appear on the first boot. After that, it will boot to the normal main menu, however, you can click the LinuxMCE logo in the lower left corner of the main menu to see the advanced options, including all the buttons on the welcome menu.</p><br><br />
[[Image:Welcome.jpg|200px]]<br />
<br />
<p>You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]<br />
Since the Hybrid + Media Directors have one built in, you can just click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/linuxmce_admin where myip is the IP address of the<br />
Core/Hybrid. <br />
Login then click [[Wizard Pages|Wizard]]. You will see the following screen.</p><br />
[[Image:Wizard.jpg|200px]]<br />
<br />
<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers. <br />
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.</p><br />
<p><b>EXAMPLE: Adding other devices</b></p><p>Example:<br />
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some tv's and stereo's to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.<br />
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p><br />
<br />
<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].<br />
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the tv's and stereo's it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].<br />
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].<br />
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used with an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p><br />
<p>Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.<br />
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your tv's and stereo's on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p><br />
<br />
<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel. <br />
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p><br />
<br />
<p>Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.</p><br />
<br />
===Scenarios, Events & Security===<br />
<br />
<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p><br />
<br />
===Configuring Myth TV===<br />
<br />
This section has been moved to [[Setting up MythTV]].<br />
<br />
===Upload Your Media===<br />
<br />
<p>There will also be Microsoft Windows compatible network shares on the Core or Hybrid (uses Samba) . There is a "public" share for putting all files that the whole family can share--movies, music, etc. And there is a private share for each family member. To access these network shares in Windows, choose Start, Run, and type \\ plus the IP address of the Core or hybrid. <br />
<br />
For example: \\192.168.80.1 Note that if you add new family members, their network share will not be available until after you reboot the Core/Hybrid. Once you copy your media into the appropriate folder, you can go into the LinuxMCE Admin site, choose "Files &amp; Media" and "Media Files Sync" to be sure your media is in the database, add attributes (artist, actor, etc.), and choose cover art.</p><br />
<br />
==Using LinuxMCE==<br />
<br />
This section has been moved to [[Using LinuxMCE]]. In 10 minutes you'll be up to speed and using all of LinuxMCE's features.<br />
<br />
<p><b>Using LinuxMCE with an Orbiter</b></p><br />
<p>Orbiter is just our way of saying remote control. All the Media Directors run an on-screen Orbiter, like the one below. Choose options on the on-screen orbiter with a keyboard/mouse attached to the media director, or with an infrared remote control. The Orbiter software runs on Linux, Windows and Windows CE, and can also be run on webpads and PDA's.<br />
Either way, it works exactly the same.</p><p>Below is the main menu. In the lower right are the [[Who Am I, Where Am I|'who' and 'where']] buttons. This indicates what room you are in, or want to control, and which family member is using the Orbiter. <br />
<br />
Touch either button if this isn't correct. Even if you are using an on-screen orbiter on the media director in the Living Room, for example, you can still change the location to the Bedroom. That means you would be using the Media Director in the Living Room as a remote control for the devices in the bedroom. Normally you don't change the location for an on-screen orbiter, since that device stays in a fixed place, but you do when you have a wireless web pad or pda you carry around.</p><br />
<br />
<p>The icons on the left all lead to a [[maps]], or floorplan, of your house showing your lighting, media, climate, telecom and security devices. Next to each of the floorplan icons are the scenarios for that category and the given room. In the scenarios section of the LinuxMCE Admin web site you create the scenarios for each room. You can have a lighting scenario called 'entertaining guests' that sets some lights, plays some background music, unlocks the door, and so on.<br />
<br><br />
[[Image:Main-menu.jpg|200px]]<br />
<br />
[[Image:Litscen.jpg|200px]]<br><br />
<br />
<p><b>NOTE:</b><br />
Many orbiters have relatively slow processors (like PDA's and phones) and may be running on slow wi-fi connections. So, the orbiters do not retrieve the large, full-size graphics, scaling them, drawing the text, and rendering everything on the fly. <br />
<br />
Rather all the graphics on your Orbiter are pre-scaled and pre-rendered by OrbiterGen. This means that if you add new scenarios or devices, or change floorplans or skins, you won't see them immediately on the Orbiter. You must go to the 'Advanced<br />
Options' page by clicking the LinuxMCE logo on the main menu, and choose 'Regenerate this Orbiter'. You'll be asked to wait about 60 seconds or so while the renderer creates new graphics, and then the Orbiter will reload.</p><br />
<br />
<p><b>Using your system with a Mobile Orbiter</b></p><br />
<p>Unless you turned off the "Auto Detect new Bluetooth Phones" option for the Media Director, compatible Bluetooth Mobile phones will automatically be detected when they are within range of any Media Director if they have Bluetooth turned on. A message will appear on all the Orbiters asking if it's a phone, and if so, to whom it belongs. Be sure you add your family members to the LinuxMCE Admin web site before doing this. Also, you may need to turn on the TV to see the message on the on-screen orbiter.</p><br />
<br />
<p>If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.</p><p>The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" button. The "who" is determined when you chose to install the software. That family member is assumed to always be the user. And the "where" is automatic-whenever you come within range of a media director it will automatically switch to the correct location. You can press the button under the location if you want to control a location other than the one you are in.</p><br />
<br />
<p>Since the display is smaller, rather than showing all the scenarios on the main menu, you must first choose the category, like lighting, and then choose the scenario from the sub menu that appears. You can also hold the category to toggle 'follow-me' mode, indicated with a red F. So, if you hold down the 2 button, a red F appears for media. Now as you move around the house your media will follow you. All 5 categories have follow-me. <a<br />
href="http://linuxmce.org/index.php?section=how_LinuxMCE_works">Screen shots of the Mobile Orbiter</a> / [[User's manual]]</p><br />
<br />
==Troubleshooting==<br />
<br />
[[Testing_and_troubleshooting_devices]]<br />
<br />
<p>[[Development status for all modules|What works and what doesn't?]]</p><br />
<br />
<p>If you don't know Linux at all, you can go into the LinuxMCE Admin website and choose [[Outside Access]], and check the box to get outside assistance from LinuxMCE. You will pick a password you will give one of our tech support staff. When you do, your system will make a secure, encrypted connection back to our support staff giving us temporary access to your system. The connection is closed as soon as you uncheck the box. Without checking that box, nobody at LinuxMCE will have any access to your system.</p><br />
<br />
<p>This troubleshooting guide assumes some basic knowledge of Linux. In LinuxMCE, everything is a device. In the LinuxMCE Admin web site, you can choose [[Devices]], to see a list of all the devices in your installation. We recommend you don't make changes here - you can break things! The top level device is usually a computer, either the core or a hybrid or an orbiter. All the logs for the devices on that computer are stored in /var/log/pluto. You can ssh in to the core using the root password you chose, and from there, you can ssh to all the media directors-shared keys were automatically setup.</p><br />
<p>All current activity is logged in the file that ends in ".newlog". After a device crashes, its logs are moved into<br />
the ".log" directory. At bootup, all logs are archived into /var/log/pluto/archives.</p><br />
<br />
<p>All DCE devices are running in separate screen sessions. Type "screen -ls" to see all active screen sessions,<br />
and "screen -r PID" where PID is the id you saw in the -ls list to attach to the screen session. There is not much for you to do or see though since all the output on stderr and stdout is going into the logs. DCERouter is running the same way on your core or hybrid.</p><br />
<br />
<p>At bootup, all the scripts listed in the LinuxMCE Admin website under [[Boot Sequence]] are run. If any programs crash, a core dump file is put in /usr/pluto/coredump. At each reboot, any core dumps are archived with the log files in /var/log/pluto/archives. A database dump/configuration snapshot are also put in each archive. Archives are deleted after 5 days.</p><br />
<br />
<p>If you're a programmer, you can also check out our [[Programmer's Guide]]. If you want to learn about writing DCE Devices, see the [[DCE]].<br />
</p><br />
<br />
<br />
''Note:''<br />
<p>We had to leave some basic features out of the free version due to licensing issues. See [http://www.geocities.com/medencid/index.html here] for a list. If you purchase a pre-built LinuxMCE system, some or all of these technologies may be licensed and the license fee built into the purchase price. Before contacting LinuxMCE support to ask why something doesn't work, please refer to that site so you know what features were left out intentionally. Note that LinuxMCE does not encourage, endorse or support users adding 3rd party modules, nor did LinuxMCE develop those modules. If you choose to add 3rd party modules we suggest you first confirm they are legal in your area.</p></div>Trouthttp://wiki.linuxmce.org/index.php?title=Getting_Started&diff=5712Getting Started2007-09-26T09:48:29Z<p>Trout: /* Media Directors */</p>
<hr />
<div>==Equipment: Picking The Right Components==<br />
<br />
''See also: [[Tested good hardware]] and [[Tested bad hardware]]''<br />
<br />
===The Core===<br />
<br />
Most important, is the "[[core]]". This is the main LinuxMCE server that runs all the applications. The commercial version uses a high-end server with RAID-5 storage. You'll probably be able to get by with a good Pentium 4, at least 80 GB of storage and two network cards (Gigabit ideally).<br />
<br />
It would be best to use a dedicated core, which means you'll end up putting this computer somewhere out of the way and not connecting a monitor to it. If you are using only one computer for your system, then you've chosen the "hybrid" system, which means that your core will also be your media player. You'll definitely need a monitor or TV for this system!<br />
<br />
===Media Directors===<br />
<br />
Note that each [[media director]] will need a [[Bluetooth dongle]] if you want to use a Bluetooth mobile phone as the remote in that area. To control your a/v equipment using [[infrared]], you will need an interface module (global cache [[gc100]]). This interface module also gives you extra serial ports. So, in this example, the TV is controlled by [[infrared]], and the receiver by RS232.<br />
<br />
''See also: [[Sound Cards]] and [[Network_Boot_for_Media_Directors]]''<br />
<br />
===Orbiters===<br />
<br />
===Network Attached Storage===<br />
<br />
An alternative to having a lot of storage space in the core is to have a small hard drive for the core and store all your files on a [[Network Attached Storage|network attached storage]] (or NAS) server. The [[Buffalo TeraStation]] is 1.0 TeraByte RAID-5 and under $1K(US). Having a NAS will allow you to not lose your precious media files. You'll likely want the larger storage for your collection of music and videos. Keep in mind that your LinuxMCE system can also record TV shows (using MythTV) and video from your security cameras (using Motion).<br />
<br />
===Additional Devices===<br />
<br />
''See also [[Recommended Accessories]]''<br />
<br />
Optionally, you may want the aforementioned home automation devices for controlling your lights. Also, optionally, you may want security cameras, plasma screen TV, a streaming media music player such as the [[Squeezebox]], an alarm system with a serial interface, etc. Some of these devices need ''another'' device called a [[gc100]]. This allows devices that communicate using a serial port (good alarm panels) or infrared (like your TV) to connect to the network and talk with your LinuxMCE core.<br />
<br />
===Location Considerations===<br />
<br />
This section has been moved to [[Choosing Locations]].<br />
<br />
===Wiring Considerations===<br />
<br />
''Main article: [[Wiring Considerations]]''<br />
<br />
Once LinuxMCE is installed, just treat it like an appliance--plug it in, turn it on, and leave it alone. The great news is that don't need to install any software on the media PCs that will be used as media directors. You can leave whatever operating system is on there, such as Windows, untouched-they will do a [[Network Boot for Media Directors]] when you want to use them as a Media Director.<br />
<br />
The only special requirement is that the LinuxMCE Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). In our Core, we provide [[Why dual network cards?|dual network cards]] one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.<br />
<br />
==Setting Up The Hardware==<br />
<br />
There are many ways to install LinuxMCE, and lots of options for equipment. However, the key components in a LinuxMCE system are the Core (the PC acting as the master server), Media Directors (media PC's connected to your TV's), and Orbiters (remote controls-web pads, pda's, mobile phones, etc.).<br />
<br />
===A Dealer Core===<br />
<br />
<p>If you buy from a Pro dealer, they will come to your home, analyze your situation, and make the decision with you. They will offer a complete, custom-installed solution.</p><br />
<p>If you buy from regular dealer, the first thing you will need to get is 1 Core. This is the brains behind the whole system, and it must run 24/7 since it will be providing all the services in your home, like the security system, media server, phones, etc. Also, all the media in the home (movies, music, etc.) will be stored on the Core. Most dealers sell Cores that are commercial servers with massive storage and full redundancy so they will run non-stop without incident. Since these Cores are often bulky, they are normally tucked away in a wiring closet or equipment rack. However, you can also hook the Core up to your TV and use it as your first media director--we call this a hybrid. Prices for Cores vary from under $1,000 for a basic Pentium PC, up to $7,000+ for a dual Xeon model with 4TB of storage. See our ***Core comparison*** guide for help deciding.</p><br />
<p>Then for each TV area where you want media you will need a media director. It's easy to add or remove media directors at any time. See our ***media director comparison guide***.</p><br />
<p>For Orbiters you can either buy touch-screen tablets from a LinuxMCE dealer ***comparison guide***. Be sure to get a Bluetooth-enabled Symbian http://www.series60.com phone from your local mobile phone carrier--they make great remote controls.</p><br />
<br />
<p>Also view our http://www.linuxmce.org/wiki/index.php/LinuxMCE:Compability to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.</p><br />
<br />
=== I will use my own PC's ===<br />
<br />
<p><b>First a warning</b> LinuxMCE is Linux-based, but don't worry. Sometimes drivers are not available for Linux as soon as they are for Windows. Particularly, if you bought some new, exotic hardware there may not be drivers. If you're looking to get some new hardware to run LinuxMCE you may want to check sites like http://www.linuxcompatible.org to be sure it's supported under Linux before you buy. Or maybe post a "will this work?" message in our forum. If you already have the hardware it can't hurt to try.</p><br />
<br />
<p>You will need one PC to run the <b>Core</b> software. Although you could install the Core on top of your existing Windows/Linux o/s, or build from source, it will be tricky and you will miss out on a lot of features. You really needs to use our own distribution because, in addition to our own software, LinuxMCE also includes lots of other open source projects, like Asterisk, Firefox, Xine, VideoLan, etc. We built "wrappers" for all of them which is how we get them all to work together seamlessly. For example, if you start watching a movie in 1 room, LinuxMCE will use Xine on that local media director. Use the orbiter to move that movie to 2 rooms, and LinuxMCE seamlessly detects the network capabilities (multi-cast switch, etc.), moves the video source to the Core using VideoLan, broadcasts to both rooms, uses VLC to do the rendering and changes the UI on the remote controls. If you use the vanilla packages from, say Fedora, none of that will work. Plus, a lot of LinuxMCE's more advanced, kernel-level modules, like plug-and-play, bandwidth shaping to ensure your phone calls are clear, network boot, and so on may not work on other Linux distributions and definitely cannot be done under Windows.</p><br />
<br />
<p>Note this PC should always be left on since it becomes the 'brains' for the whole house and all the other pieces won't function unless they can find the <b>Core</b>. In our commercial product, the Core is a fail-safe, redundant server.</p><br />
<br />
<p>There is only <b>one special requirement</b>. The Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). If you have another DHCP server (like a cable/dsl modem), we recommend your Core have dual network cards: one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.</p><br />
<br />
<p>You can also put other cards in the Core, such as analog phone line interfaces from www.digium.com for the phone system or analog video capture cards for surveillance cameras. You can put the PVR/satellite capture cards in the individual media PC's, or you can put several in the Core, which will share the video throughout the house.</p><br />
<br />
<p>Wherever you have a TV/Stereo you can use a PC or thin-client as the Media Director--it doesn't need to be on all the time and there's no software to install since they will network boot off the Core. Just be sure it has a good Linux-compatible sound card, a Linux-compatible video card, supports PXE network boot (nearly all recent motherboards do), and--optionally--a PVR card. To use the Bluetooth mobile phones as remote controls, add a USB Bluetooth Dongle for each media director (around $25). All the media directors will report the signal strengths of all the mobile phones--this is how the Core figures out what room you're in. Since all resources in the whole house are shared, you will be able to control any device in any room from anywhere--as long as you're within Bluetooth range of any media director (about 10m or 30feet), you will have control over everything in the house. You can also use low-cost network audio players, like the Squeeze Box, wherever you want to add music.</p><br />
<br />
<p>To control the system, you can use the PC's mouse and keyboard, or an infrared remote, or run the Orbiter software on your mobile phones, webpads and PDA's.</p><br />
<br />
Also view our [[tested good hardware]] to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.<br />
<br />
===A Dedicated Core===<br />
<br />
<p>The Core is the central point of the Linux MCE system and runs applications and daemons needed for the other devices to exchange messages. A dedicated core will run only the backed applications and will not provide any fronted except the web interface, this means you won't act as a media center. You'll need to use Media Directors to be able to play movies, listen to music and watch TV. This kind of setup is recommended when you have lot of extra devices, this way the back end applications will have full access to Core's resources.</p><br><br />
<br />
[[Image:Diagram1.jpg|200px]]<br />
<br />
===A Dedicated Hybrid===<br />
<br />
A "hybrid" just means the computer that is running is the "Core" software is also running the "Media Director" software-you use the Core as a Media Director. The only reason we don't recommend this in our high-end installations is because a computer suitable for a Core is usually a pretty massive box with major hard drive capacity and rather noisy, so it's shoved away in the wiring closet, rather than sitting next to a TV like a Media Director would. However, you can use a regular PC as the Core + Media Director (Hybrid) also. Just remember that it will need to always be on since the Core software is what controls everything in the house.<br />
<br />
[[Image:Diagram2.jpg|200px]]<br />
<br />
Be sure you complete the installation of your Core/Hybrid before trying to boot the media directors.<br />
<br />
==Installation==<br />
<br />
===Pre-installation Setup===<br />
<br />
'''Note:''' During the installation, you may have some difficulties that can be avoided by following the advice below:<br />
<br />
# Make sure you have an Internet connection prior to starting! After LinuxMCE installs, it will need to access the Internet and download the latest patches. (More often than not, you want this!)<br />
# Confused about which internet adapter should be your "main" when that option is given to you during the install? Just click on one. You have a 50/50 chance of getting it right. You can easily change it later in the [[LinuxMCE-Website Admin]] pages by selecting "Advanced -> Network -> Network Settings" from the drop-down and clicking "Swap Interfaces".<br />
# Use the core's DHCP server to give machines on your network a dynamic IP address. Turn off the DHCP server on any other devices you may have on your network! <i>This is very important!</i> You probably already have your home router giving out addresses. Check the configuration and turn that feature off. LinuxMCE uses the DHCP requests from machines that come online to figure out what they are and what to do with them.<br />
# A map of your home. This is actually a very important step because LinuxMCE seems to need the map to properly finish the installation of some devices. It is easy to create a map using any drawing software or just draw one by hand and scan it. You don't need anything fancy, just some squares representing your different rooms. If the file is too big, LinuxMCE will scale it to fit. You can always upload a new map later on when you feel like being more creative. You can also make multiple maps, say, one for each floor or section of your house. This will all make more sense later when you get into configuring the devices.<br />
<br />
===Download===<br />
Download the Kubuntu installer and optional packages ISO from [http://linuxmce.org/wiki/index.php/Download_Instructions here].<br />
<br />
===Software Installation===<br />
<br />
You can find Steps for installing Linux MCE on a Kubuntu 7.04 system [http://wiki.linuxmce.org/index.php/Installation_Guide here].<br />
<br />
===Finalize The Install===<br />
<br />
<p>After you have set everything up, you should do a full reboot of the "LinuxMCE universe", meaning rebooting the Core/Hybrid plus any media directors.<br />
You can do this by choosing "Restart" from the LinuxMCE Admin site wizard (the last option), or from any orbiter or media director by clicking the LinuxMCE logo on the main menu and choosing "Reboot Core".</p><br />
<p>If your media directors support both software power off and wake on lan, the core will turn them off before it reboots itself, and will turn them back on when it has finished booting up. If not, you may need to reboot the media directors manually by cycling power on them. Note that you should not turn the media directors on until the Core/Hybrid has finished booting up.</p><br />
<br />
==Configuration==<br />
<br />
===Tell LinuxMCE About Your Home===<br />
<br />
[[Tell LinuxMCE about your home]] shows you how to use our LinuxMCE Admin wizard. In about 2 hours you can have everything setup--the whole-house media server, full control all your lights, climate, and tv/hi-fi gear, the phone system, follow-me, everything. It's quick, painless, and non-technical.<br />
<br />
===Adding Other Devices===<br />
<br />
If you chose a "Core", not being used as a Media Director, then it will boot up and you will see a simple menu like this:<br><br />
[[Image:Console.jpg|200px]]<br />
<em>LinuxMCE Core; After boot-up menu</em><br><br><br />
<p>You don't need to do anything. Your Core is up and running. Just make note of the IP address - you will need it to configure the system. </p><br />
<p>If you chose a "Hybrid", that is you are using your Core as a Media Director, it will boot up to the same welcome menu as any media director. Note that the welcome menu will appear on the first boot. After that, it will boot to the normal main menu, however, you can click the LinuxMCE logo in the lower left corner of the main menu to see the advanced options, including all the buttons on the welcome menu.</p><br><br />
[[Image:Welcome.jpg|200px]]<br />
<br />
<p>You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]<br />
Since the Hybrid + Media Directors have one built in, you can just click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/linuxmce_admin where myip is the IP address of the<br />
Core/Hybrid. <br />
Login then click [[Wizard Pages|Wizard]]. You will see the following screen.</p><br />
[[Image:Wizard.jpg|200px]]<br />
<br />
<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers. <br />
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.</p><br />
<p><b>EXAMPLE: Adding other devices</b></p><p>Example:<br />
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some tv's and stereo's to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.<br />
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p><br />
<br />
<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].<br />
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the tv's and stereo's it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].<br />
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].<br />
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used with an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p><br />
<p>Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.<br />
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your tv's and stereo's on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p><br />
<br />
<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel. <br />
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p><br />
<br />
<p>Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.</p><br />
<br />
===Scenarios, Events & Security===<br />
<br />
<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p><br />
<br />
===Configuring Myth TV===<br />
<br />
This section has been moved to [[Setting up MythTV]].<br />
<br />
===Upload Your Media===<br />
<br />
<p>There will also be Microsoft Windows compatible network shares on the Core or Hybrid (uses Samba) . There is a "public" share for putting all files that the whole family can share--movies, music, etc. And there is a private share for each family member. To access these network shares in Windows, choose Start, Run, and type \\ plus the IP address of the Core or hybrid. <br />
<br />
For example: \\192.168.80.1 Note that if you add new family members, their network share will not be available until after you reboot the Core/Hybrid. Once you copy your media into the appropriate folder, you can go into the LinuxMCE Admin site, choose "Files &amp; Media" and "Media Files Sync" to be sure your media is in the database, add attributes (artist, actor, etc.), and choose cover art.</p><br />
<br />
==Using LinuxMCE==<br />
<br />
This section has been moved to [[Using LinuxMCE]]. In 10 minutes you'll be up to speed and using all of LinuxMCE's features.<br />
<br />
<p><b>Using LinuxMCE with an Orbiter</b></p><br />
<p>Orbiter is just our way of saying remote control. All the Media Directors run an on-screen Orbiter, like the one below. Choose options on the on-screen orbiter with a keyboard/mouse attached to the media director, or with an infrared remote control. The Orbiter software runs on Linux, Windows and Windows CE, and can also be run on webpads and PDA's.<br />
Either way, it works exactly the same.</p><p>Below is the main menu. In the lower right are the [[Who Am I, Where Am I|'who' and 'where']] buttons. This indicates what room you are in, or want to control, and which family member is using the Orbiter. <br />
<br />
Touch either button if this isn't correct. Even if you are using an on-screen orbiter on the media director in the Living Room, for example, you can still change the location to the Bedroom. That means you would be using the Media Director in the Living Room as a remote control for the devices in the bedroom. Normally you don't change the location for an on-screen orbiter, since that device stays in a fixed place, but you do when you have a wireless web pad or pda you carry around.</p><br />
<br />
<p>The icons on the left all lead to a [[maps]], or floorplan, of your house showing your lighting, media, climate, telecom and security devices. Next to each of the floorplan icons are the scenarios for that category and the given room. In the scenarios section of the LinuxMCE Admin web site you create the scenarios for each room. You can have a lighting scenario called 'entertaining guests' that sets some lights, plays some background music, unlocks the door, and so on.<br />
<br><br />
[[Image:Main-menu.jpg|200px]]<br />
<br />
[[Image:Litscen.jpg|200px]]<br><br />
<br />
<p><b>NOTE:</b><br />
Many orbiters have relatively slow processors (like PDA's and phones) and may be running on slow wi-fi connections. So, the orbiters do not retrieve the large, full-size graphics, scaling them, drawing the text, and rendering everything on the fly. <br />
<br />
Rather all the graphics on your Orbiter are pre-scaled and pre-rendered by OrbiterGen. This means that if you add new scenarios or devices, or change floorplans or skins, you won't see them immediately on the Orbiter. You must go to the 'Advanced<br />
Options' page by clicking the LinuxMCE logo on the main menu, and choose 'Regenerate this Orbiter'. You'll be asked to wait about 60 seconds or so while the renderer creates new graphics, and then the Orbiter will reload.</p><br />
<br />
<p><b>Using your system with a Mobile Orbiter</b></p><br />
<p>Unless you turned off the "Auto Detect new Bluetooth Phones" option for the Media Director, compatible Bluetooth Mobile phones will automatically be detected when they are within range of any Media Director if they have Bluetooth turned on. A message will appear on all the Orbiters asking if it's a phone, and if so, to whom it belongs. Be sure you add your family members to the LinuxMCE Admin web site before doing this. Also, you may need to turn on the TV to see the message on the on-screen orbiter.</p><br />
<br />
<p>If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.</p><p>The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" button. The "who" is determined when you chose to install the software. That family member is assumed to always be the user. And the "where" is automatic-whenever you come within range of a media director it will automatically switch to the correct location. You can press the button under the location if you want to control a location other than the one you are in.</p><br />
<br />
<p>Since the display is smaller, rather than showing all the scenarios on the main menu, you must first choose the category, like lighting, and then choose the scenario from the sub menu that appears. You can also hold the category to toggle 'follow-me' mode, indicated with a red F. So, if you hold down the 2 button, a red F appears for media. Now as you move around the house your media will follow you. All 5 categories have follow-me. <a<br />
href="http://linuxmce.org/index.php?section=how_LinuxMCE_works">Screen shots of the Mobile Orbiter</a> / [[User's manual]]</p><br />
<br />
==Troubleshooting==<br />
<br />
[[Testing_and_troubleshooting_devices]]<br />
<br />
<p>[[Development status for all modules|What works and what doesn't?]]</p><br />
<br />
<p>If you don't know Linux at all, you can go into the LinuxMCE Admin website and choose [[Outside Access]], and check the box to get outside assistance from LinuxMCE. You will pick a password you will give one of our tech support staff. When you do, your system will make a secure, encrypted connection back to our support staff giving us temporary access to your system. The connection is closed as soon as you uncheck the box. Without checking that box, nobody at LinuxMCE will have any access to your system.</p><br />
<br />
<p>This troubleshooting guide assumes some basic knowledge of Linux. In LinuxMCE, everything is a device. In the LinuxMCE Admin web site, you can choose [[Devices]], to see a list of all the devices in your installation. We recommend you don't make changes here - you can break things! The top level device is usually a computer, either the core or a hybrid or an orbiter. All the logs for the devices on that computer are stored in /var/log/pluto. You can ssh in to the core using the root password you chose, and from there, you can ssh to all the media directors-shared keys were automatically setup.</p><br />
<p>All current activity is logged in the file that ends in ".newlog". After a device crashes, its logs are moved into<br />
the ".log" directory. At bootup, all logs are archived into /var/log/pluto/archives.</p><br />
<br />
<p>All DCE devices are running in separate screen sessions. Type "screen -ls" to see all active screen sessions,<br />
and "screen -r PID" where PID is the id you saw in the -ls list to attach to the screen session. There is not much for you to do or see though since all the output on stderr and stdout is going into the logs. DCERouter is running the same way on your core or hybrid.</p><br />
<br />
<p>At bootup, all the scripts listed in the LinuxMCE Admin website under [[Boot Sequence]] are run. If any programs crash, a core dump file is put in /usr/pluto/coredump. At each reboot, any core dumps are archived with the log files in /var/log/pluto/archives. A database dump/configuration snapshot are also put in each archive. Archives are deleted after 5 days.</p><br />
<br />
<p>If you're a programmer, you can also check out our [[Programmer's Guide]]. If you want to learn about writing DCE Devices, see the [[DCE]].<br />
</p><br />
<br />
<br />
''Note:''<br />
<p>We had to leave some basic features out of the free version due to licensing issues. See [http://www.geocities.com/medencid/index.html here] for a list. If you purchase a pre-built LinuxMCE system, some or all of these technologies may be licensed and the license fee built into the purchase price. Before contacting LinuxMCE support to ask why something doesn't work, please refer to that site so you know what features were left out intentionally. Note that LinuxMCE does not encourage, endorse or support users adding 3rd party modules, nor did LinuxMCE develop those modules. If you choose to add 3rd party modules we suggest you first confirm they are legal in your area.</p></div>Trouthttp://wiki.linuxmce.org/index.php?title=EIB/KNX&diff=5711EIB/KNX2007-09-26T09:44:21Z<p>Trout: /* Problems */</p>
<hr />
<div>KNX (EIB) is a standardised (EN 50090,ISO/IEC 14543), OSI-based network communications protocol for intelligent buildings. KNX is the successor to, and convergence of, three previous standards: the European Home Systems Protocol (EHS), BatiBUS, and the European Installation Bus (EIB).<br />
<br />
The KNX standard is administered by the Konnex Association. [http://www.konnex.org konnex.org]<br />
<br />
<br />
== How to install and use EIB ==<br />
<br />
Connect your Core-Server with a serial cable to the EIB. Your BUS Connector has to have the FT1.2Protocol. (like [http://http://www.eibmarkt.com/cgi-bin/eibmarkt.storefront/46f9364200e19a48274450f3362b0652/Product/View/N434019 this]. You can use it from any Company (Gira, Berker, Siemens, ... ) but it is very important to have the correct protocol. (I bought the wrong one). <br />
When you have connect it you have to add the EIB Interface in the WebAdmin. Go to Devices-->Interface and choose EIB, select the correct COM-Port, do a reload - router and you are ready to use it.<br />
You can also go in a console and look into the log file (DeviceID_EIB.log) to see if everything works fine. <br />
<br />
== How to add devices ==<br />
<br />
In the Webadmin you have on the left side new menu buttons for Lights, Drapes, Sensors and Thermostats. At first you have to add the groupadresses. You have to upload a file with the correct information about your System. The format is:<br />
<br />
<pre><br />
"LichtARschalt"/"0"/"0"/"1"<br />
"Licht-SZ-schalt"/"0"/"0"/"10"<br />
"Licht-SZ-dimm"/"0"/"0"/"11"<br />
"Licht-SZ-wert"/"0"/"0"/"12"<br />
</pre><br />
<br />
=== Lights ===<br />
<br />
Goto EIB Lights on the Webadmin. Give the Name of your Light and choose if it is dimmable or not. Click on the "Pick" Button -> choose the correct groupaddress for on/off and dim. In Webadmin->Lights you can add the room and type of your light. After that you can put the EIB light on the floorplan. <br />
<br />
=== Thermostats ===<br />
<br />
In my house the thermostats have two states (cold and warm). I don't want to change the temperature with LinuxMCE, i only want to turn on and off the heating. When the temperature is reached the EIB turns off the heating by itself. <br />
So, what did i do? <br />
At first i allowed my thermostat to change the state (on/off) by the bus and gave it a groupaddress (like 2/0/10)<br />
I go to the Webadmin->Scenarios->Climate and create for every room two scenarios (on and off). Then go to the Webadmin->Advanced->Configuration->Scenarios-Climate and choose the first Scenario. Add the EIB Device and the Command EIB_Write. <br />
Now you have to insert the groupaddress, data string and data type. Insert the groupaddress (2/0/10), the data string (1=on, 2=off) and for the data type put 6 in the field. Press save and you can test it. <br />
<br />
This is a lot of work, but so you can write a very small php-page to execute one of the scenarios. That's very comfortable because you can turn on and off the heating from anywhere with the browser of a mobile phone.<br />
<br />
=== Drapes ===<br />
<br />
It's the same as the thermostats. I don't use the EIB-Drapes, I create my own scenarios and send the commands with EIB_Write to the bus. This works very well.<br />
<br />
=== Sensors ===<br />
<br />
I don't really have sensors. I only tried to create a sensor that is a light-switch. Every time I turn on the light the sensor was tripped and the Commands were executed.<br />
<br />
== Problems ==<br />
<br />
=== How to send the Time on the bus? ===<br />
<br />
I want to send the system time of the server every ten minutes to the bus. The reason is, the internal clocks of the thermostats don't have a real clock, so they need the correct time/date every hour to synchronize. <br />
Has anyone tried this???<br />
<br />
=== Can't read from the bus ===<br />
<br />
I want to read data from the bus. Like how warm is it in the rooms or is a light on or off. <br />
I think this function isn't implemented yet... I will try to implement it, but i don't know how to build a working development system.</div>Trouthttp://wiki.linuxmce.org/index.php?title=EIB/KNX&diff=5710EIB/KNX2007-09-26T09:43:05Z<p>Trout: /* How to add devices */</p>
<hr />
<div>KNX (EIB) is a standardised (EN 50090,ISO/IEC 14543), OSI-based network communications protocol for intelligent buildings. KNX is the successor to, and convergence of, three previous standards: the European Home Systems Protocol (EHS), BatiBUS, and the European Installation Bus (EIB).<br />
<br />
The KNX standard is administered by the Konnex Association. [http://www.konnex.org konnex.org]<br />
<br />
<br />
== How to install and use EIB ==<br />
<br />
Connect your Core-Server with a serial cable to the EIB. Your BUS Connector has to have the FT1.2Protocol. (like [http://http://www.eibmarkt.com/cgi-bin/eibmarkt.storefront/46f9364200e19a48274450f3362b0652/Product/View/N434019 this]. You can use it from any Company (Gira, Berker, Siemens, ... ) but it is very important to have the correct protocol. (I bought the wrong one). <br />
When you have connect it you have to add the EIB Interface in the WebAdmin. Go to Devices-->Interface and choose EIB, select the correct COM-Port, do a reload - router and you are ready to use it.<br />
You can also go in a console and look into the log file (DeviceID_EIB.log) to see if everything works fine. <br />
<br />
== How to add devices ==<br />
<br />
In the Webadmin you have on the left side new menu buttons for Lights, Drapes, Sensors and Thermostats. At first you have to add the groupadresses. You have to upload a file with the correct information about your System. The format is:<br />
<br />
<pre><br />
"LichtARschalt"/"0"/"0"/"1"<br />
"Licht-SZ-schalt"/"0"/"0"/"10"<br />
"Licht-SZ-dimm"/"0"/"0"/"11"<br />
"Licht-SZ-wert"/"0"/"0"/"12"<br />
</pre><br />
<br />
=== Lights ===<br />
<br />
Goto EIB Lights on the Webadmin. Give the Name of your Light and choose if it is dimmable or not. Click on the "Pick" Button -> choose the correct groupaddress for on/off and dim. In Webadmin->Lights you can add the room and type of your light. After that you can put the EIB light on the floorplan. <br />
<br />
=== Thermostats ===<br />
<br />
In my house the thermostats have two states (cold and warm). I don't want to change the temperature with LinuxMCE, i only want to turn on and off the heating. When the temperature is reached the EIB turns off the heating by itself. <br />
So, what did i do? <br />
At first i allowed my thermostat to change the state (on/off) by the bus and gave it a groupaddress (like 2/0/10)<br />
I go to the Webadmin->Scenarios->Climate and create for every room two scenarios (on and off). Then go to the Webadmin->Advanced->Configuration->Scenarios-Climate and choose the first Scenario. Add the EIB Device and the Command EIB_Write. <br />
Now you have to insert the groupaddress, data string and data type. Insert the groupaddress (2/0/10), the data string (1=on, 2=off) and for the data type put 6 in the field. Press save and you can test it. <br />
<br />
This is a lot of work, but so you can write a very small php-page to execute one of the scenarios. That's very comfortable because you can turn on and off the heating from anywhere with the browser of a mobile phone.<br />
<br />
=== Drapes ===<br />
<br />
It's the same as the thermostats. I don't use the EIB-Drapes, I create my own scenarios and send the commands with EIB_Write to the bus. This works very well.<br />
<br />
=== Sensors ===<br />
<br />
I don't really have sensors. I only tried to create a sensor that is a light-switch. Every time I turn on the light the sensor was tripped and the Commands were executed.<br />
<br />
== Problems ==<br />
<br />
=== How to send the Time on the bus? ===<br />
<br />
I want to send the system time of the server every ten minutes to the bus. The reason is, the internal clocks of the thermostats don't have a real clock, so they need the correct time/date every hour to synchronize. <br />
Has anyone tried this???<br />
<br />
=== Can't read from the bus ===<br />
<br />
I want to read data from the bus. Like how warm is it in the rooms or is a light on or off. <br />
I think this function isn't implemented yet?!?!? I would try to implement it, but i don't know how to build a working development system.<br />
<br />
<br />
<br />
sorry for the bad english :)</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=5702User talk:Samme2007-09-26T00:31:33Z<p>Trout: /* Needs to be fixed */</p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now. [[User:Trout|Trout]] 17:23, 24 September 2007 (MST)<br />
::::How about that admin access for me? [[User:Trout|Trout]] 12:44, 25 September 2007 (MST)<br />
:::::Please block all the spammers. I've set a category on them Categories: Spammer [[User:Trout|Trout]] 17:30, 25 September 2007 (MST)<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)<br />
<br />
::This was just the first step, I'm thinking of implementing some other measures too. --[[User:Samme|Samme]] 23:18, 24 September 2007 (MST)<br />
<br />
== Needs to be fixed ==<br />
<br />
{{NeedsToBeFixed}}<br />
<br />
Every page needs to be fixed. This is not helpful unless you say how it is to be fixed. [[User:Trout|Trout]] 09:56, 25 September 2007 (MST)<br />
<br />
If <strong>categorization</strong> is one issue and <strong>weak content</strong> is another, maybe we could have two or more different ones. [[User:Trout|Trout]] 10:55, 25 September 2007 (MST)<br />
<br />
:Good point, what I mean the most with those are that they need to be categorized and wikified and often make them more readable. Maybe we should start by setting up some guidelines how articles should look etc? What do you think? Maybe we could somehow gather the ones that edit the wiki most and agree on some rules/guidelines, maybe via irc? --[[User:Samme|Samme]] 13:44, 25 September 2007 (MST)<br />
<br />
::IRC is fine. server/room/time ? [[User:Trout|Trout]] 17:31, 25 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=5701User talk:Samme2007-09-26T00:30:38Z<p>Trout: </p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now. [[User:Trout|Trout]] 17:23, 24 September 2007 (MST)<br />
::::How about that admin access for me? [[User:Trout|Trout]] 12:44, 25 September 2007 (MST)<br />
:::::Please block all the spammers. I've set a category on them Categories: Spammer [[User:Trout|Trout]] 17:30, 25 September 2007 (MST)<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)<br />
<br />
::This was just the first step, I'm thinking of implementing some other measures too. --[[User:Samme|Samme]] 23:18, 24 September 2007 (MST)<br />
<br />
== Needs to be fixed ==<br />
<br />
{{NeedsToBeFixed}}<br />
<br />
Every page needs to be fixed. This is not helpful unless you say how it is to be fixed. [[User:Trout|Trout]] 09:56, 25 September 2007 (MST)<br />
<br />
If <strong>categorization</strong> is one issue and <strong>weak content</strong> is another, maybe we could have two or more different ones. [[User:Trout|Trout]] 10:55, 25 September 2007 (MST)<br />
<br />
:Good point, what I mean the most with those are that they need to be categorized and wikified and often make them more readable. Maybe we should start by setting up some guidelines how articles should look etc? What do you think? Maybe we could somehow gather the ones that edit the wiki most and agree on some rules/guidelines, maybe via irc? --[[User:Samme|Samme]] 13:44, 25 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=5696User talk:Samme2007-09-25T19:44:41Z<p>Trout: /* If you're the wiki admin, block the spammers */</p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now. [[User:Trout|Trout]] 17:23, 24 September 2007 (MST)<br />
::::How about that admin access for me? [[User:Trout|Trout]] 12:44, 25 September 2007 (MST)<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)<br />
<br />
::This was just the first step, I'm thinking of implementing some other measures too. --[[User:Samme|Samme]] 23:18, 24 September 2007 (MST)<br />
<br />
== Needs to be fixed ==<br />
<br />
{{NeedsToBeFixed}}<br />
<br />
Every page needs to be fixed. This is not helpful unless you say how it is to be fixed. [[User:Trout|Trout]] 09:56, 25 September 2007 (MST)<br />
<br />
If <strong>categorization</strong> is one issue and <strong>weak content</strong> is another, maybe we could have two or more different ones. [[User:Trout|Trout]] 10:55, 25 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=5694User talk:Samme2007-09-25T17:55:14Z<p>Trout: /* Needs to be fixed */</p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now. [[User:Trout|Trout]] 17:23, 24 September 2007 (MST)<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)<br />
<br />
::This was just the first step, I'm thinking of implementing some other measures too. --[[User:Samme|Samme]] 23:18, 24 September 2007 (MST)<br />
<br />
== Needs to be fixed ==<br />
<br />
{{NeedsToBeFixed}}<br />
<br />
Every page needs to be fixed. This is not helpful unless you say how it is to be fixed. [[User:Trout|Trout]] 09:56, 25 September 2007 (MST)<br />
<br />
If <strong>categorization</strong> is one issue and <strong>weak content</strong> is another, maybe we could have two or more different ones. [[User:Trout|Trout]] 10:55, 25 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=5692User talk:Samme2007-09-25T16:56:50Z<p>Trout: Needs to be fixed</p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now. [[User:Trout|Trout]] 17:23, 24 September 2007 (MST)<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)<br />
<br />
::This was just the first step, I'm thinking of implementing some other measures too. --[[User:Samme|Samme]] 23:18, 24 September 2007 (MST)<br />
<br />
== Needs to be fixed ==<br />
<br />
{{NeedsToBeFixed}}<br />
<br />
Every page needs to be fixed. This is not helpful unless you say how it is to be fixed. [[User:Trout|Trout]] 09:56, 25 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=Motorola_KRZR&diff=5689Motorola KRZR2007-09-25T11:56:24Z<p>Trout: help this phone along</p>
<hr />
<div>[[Image:Krzr.jpg]]<br />
<br />
This is a super popular phone from Motorola.<br />
<br />
This phone currently does not work at all.<br />
<br />
[[Category: Hardware]]<br />
[[Category: Phones]]</div>Trouthttp://wiki.linuxmce.org/index.php?title=File:Krzr.jpg&diff=5688File:Krzr.jpg2007-09-25T11:54:46Z<p>Trout: </p>
<hr />
<div></div>Trouthttp://wiki.linuxmce.org/index.php?title=Talk:Motorola_KRZR&diff=5687Talk:Motorola KRZR2007-09-25T11:52:21Z<p>Trout: why delete hardware pages?</p>
<hr />
<div>Why would a hardware page be deleted?<br />
The only reason I can think of is that the hardware doesn't exist. And this is not the case for this device.</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=5672User talk:Samme2007-09-25T00:23:12Z<p>Trout: /* If you're the wiki admin, block the spammers */</p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now. [[User:Trout|Trout]] 17:23, 24 September 2007 (MST)<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)</div>Trouthttp://wiki.linuxmce.org/index.php?title=User_talk:Samme&diff=5671User talk:Samme2007-09-25T00:22:57Z<p>Trout: /* If you're the wiki admin, block the spammers */</p>
<hr />
<div>*If you want to add a new '''topic''', '''[http://wiki.linuxmce.com/index.php?title=User_talk:Samme&action=edit&section=new click here]'''.<br />
*If you want to '''add a post''', click on [<font color="blue">edit</font>] by the header of the topic.<br />
*'''Sign''' your post with 4 tilde <nowiki>~~~~</nowiki> <br />
*'''Preview''' before you submit!<br />
<br />
<br />
<br />
== If you're the wiki admin, block the spammers ==<br />
<br />
The spammers are running wild on this wiki. Ban them from doing it. [[User:Trout|Trout]] 15:14, 14 September 2007 (MST)<br />
<br />
:I'm working on it. Please do sign when you leave a message. You know how, don't you? [[User:Samme|Samme]] 15:52, 14 September 2007 (MST)<br />
<br />
:Yes, of course I know how to sign comments. If you need help with admin, I volunteer. [[User:Trout|Trout]] 11:32, 15 September 2007 (MST)<br />
::Good, then as soon as I get admin rights from Paul I'll also add you as admin. [[User:Samme|Samme]] 13:59, 15 September 2007 (MST)<br />
:::Okay, it looks like you've got it now.<br />
<br />
:What's the hold up? We need some spammers banned. People are getting frustrated. Look at the decline in participation. Tired of dealing with spammers. [[User:Trout|Trout]] 09:26, 18 September 2007 (MST)<br />
<br />
::I know Trout, but I haven't got any response from Paul yet regarding admin-rights, as soon as we get them then we can start cleaning up. [[User:Samme|Samme]] 09:39, 18 September 2007 (MST)<br />
<br />
:Yeah! Thanks for blocking the spammers! [[User:Trout|Trout]] 05:37, 24 September 2007 (MST)</div>Trout