The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
And the first issue you are going to face is , your PI will not boot with wireless KB and mouse unless you have purchased a branded micro USB power adapter. Apple iPad, Nexus and iPhone adapters are the only products worked for me.
Also avoid Microsoft wireless keyboard-mouse combo. If you are using more USBs , ensure to buy a quality powered USB hub.
Power is the issue that takes your skin out while working with PI. All the best.
Good point, I originally used an old Logitech G15 usb keyboard I had lyring around, unfortunately it had an LCD screen and back lit keyboard. needless to say, it didn't play well with the Pi due to power constraints.
I have two (both model B version 2). You don't need a keyboard/mouse/monitor for each one once you have the network set up. Headless operation from your Windows/Ubuntu machine works as well or better than direct connection to HDMI... but you have to do it the hard way initially to build the boot disk (SD card) and set up the network.
I also bought the 5V micro USB charger from the vendor (Newark), by which I avoided an entire class of problems. I understand from the masses that the main problems with the RPi involve power.
I am also building a project where I will run it headless off network and built my own power supply, which works fine. It is not power hungry but needs at least 700 mA, which most phone chargers do not supply.
Have fun with it! I haven't run out of things to do with it yet...
I have no problem with Microsoft innovating. I have a huge problem with them single handedly being responsible for so much pain because of trident. Lets settle n a single engine and innovate around that. (And while you're at it ditch gecko. )
The one built in to the core library is WebKit, and the Trident and Gecko ones are external addins, and won't be installed by default (if I can ever get VS/WiX/etc. to cooperate with me and actually build.)
They also will likely not be implemented until after version 1.0.
The WebKit (Awesomium) version I am using is the latest beta/RC, so it is kinda buggy at times.
Some of the error 'messages' I encountered:
* 'Internal Epic Fail Error' <--- likely my favorite.
* 'The Daily WTF needs THIS code.
X| X| X|
* 404 Brain Not Found.
* [Nasty Words Removed] code!
We're upgrading and reconfiguring our load balancers as a final step in the changes we made over the break. During this time there could be some small outages, but it should all be done by lunchtime, US Eastern