<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Lynxworks &#187; Howto</title>
	<atom:link href="http://blog.lynxworks.eu/tag/howto/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.lynxworks.eu</link>
	<description>I don&#039;t think there are any dragons here</description>
	<lastBuildDate>Sat, 31 Mar 2012 12:42:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Repair Samsung NC10 MBR</title>
		<link>http://blog.lynxworks.eu/2011/10/repair-samsung-nc10-mbr/</link>
		<comments>http://blog.lynxworks.eu/2011/10/repair-samsung-nc10-mbr/#comments</comments>
		<pubDate>Sun, 16 Oct 2011 11:07:35 +0000</pubDate>
		<dc:creator>Dougie</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Misc]]></category>
		<category><![CDATA[Fix]]></category>
		<category><![CDATA[Howto]]></category>
		<category><![CDATA[MBR]]></category>
		<category><![CDATA[NC10]]></category>
		<category><![CDATA[Recovery]]></category>
		<category><![CDATA[Samsung]]></category>

		<guid isPermaLink="false">http://blog.lynxworks.eu/?p=1966</guid>
		<description><![CDATA[Repair the Samsung NC10's MBR - returning the F4 recovery option. <a href="http://blog.lynxworks.eu/2011/10/repair-samsung-nc10-mbr/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I removed Ubuntu from a Samsung NC10 yesterday, now the F4 recovery option doesn&#8217;t work. Please excuse the lack of screen shots on this Howto but I couldn&#8217;t think how to capture from the recovery manager and camera shots look rubbish.</p>
<p>It would appear that Samsung uses a custom Master Boot Record (MBR) &#8211; so for Grub all is well because you can choose to boot into the recovery partition and away you go. However if you have followed any of the usual guides to removing grub (such as running an XP CD to a recovery console and typing fixmbr) F4 will not launch the restore tool.</p>
<p><a href="http://www.sysresccd.org/Main_Page">System Rescue CD</a> is a great tool to have handy on a USB key. You can, so booting into it run this command:</p>
<pre class="brush: bash; gutter: true">fdisk /dev/sda</pre>
<p>Now pressing &#8220;p&#8221; should show you that the recovery partition is 1, so type &#8220;a&#8221; then &#8220;2&#8243;, &#8220;a&#8221; then &#8220;1&#8243; to make it bootable. Now write the partition table by typing &#8220;w&#8221; then reboot. At this point you will boot into the recovery manager and be able to recover but the F4 key will not still not be available at boot and of course trying to create a backup will not work either (as Windows will be booted on restart).</p>
<p>Once Samsung Recovery Manager III has loaded up, press Ctrl+Alt+F10 &#8211; I had no idea there was a management mode until I read this <a href="http://www.sammynetbook.com/forum/threads/11440-Recovery-Partition-rebuild-with-F4-key-enable">page</a> (French) but be aware its only available from the recovery partition. It asks for a password &#8211; &#8220;secos&#8221; (without the quotes). Once in management mode, click the &#8220;Image&#8221; tab and select &#8220;Export&#8221; then &#8220;Select Location&#8221;, I used &#8220;D:\&#8221;. Click &#8220;Start&#8221; and accept the dialogue box that comes up. This is a backup of the recovery partition.</p>
<p>Once this stage is finished, select the &#8220;Tools&#8221; tab, insert a spare USB stick and click &#8220;Admin Tool USB&#8221;. It will format the USB stick and then install some utilities. It takes a couple of minutes. Once finished click the close button in the top right and it&#8217;ll ask if the computer should be turned off &#8211; say yes.</p>
<p>Boot with the USB key we just made, bringing you to a completely different recovery menu. Click &#8220;MBR Fix&#8221; and then close the application.</p>
<p>Now when you reboot you&#8217;ll notice that the MBR has been repaired and F4 once again boots into Recovery Manager III.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lynxworks.eu/2011/10/repair-samsung-nc10-mbr/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Compaq CQ10 failed BIOS update</title>
		<link>http://blog.lynxworks.eu/2011/10/compaq-cq10-failed-bios-update/</link>
		<comments>http://blog.lynxworks.eu/2011/10/compaq-cq10-failed-bios-update/#comments</comments>
		<pubDate>Fri, 14 Oct 2011 21:46:24 +0000</pubDate>
		<dc:creator>Dougie</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Compaq]]></category>
		<category><![CDATA[Fix]]></category>
		<category><![CDATA[Howto]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[Netbook]]></category>

		<guid isPermaLink="false">http://blog.lynxworks.eu/?p=1961</guid>
		<description><![CDATA[A friend brought me a Compaq CQ10 over earlier. It seems it lost power during a Softpaq BIOS update. Initially the screen was booting to the HP BIOS recovery screen, attempting to rewrite and failing around 10%. I tried a &#8230; <a href="http://blog.lynxworks.eu/2011/10/compaq-cq10-failed-bios-update/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>A friend brought me a Compaq CQ10 over earlier. It seems it lost power during a Softpaq BIOS update. Initially the screen was booting to the HP BIOS recovery screen, attempting to rewrite and failing around 10%. I tried a few things and nothing worked, until the owner mentioned they&#8217;d upgraded the RAM.</p>
<p>Sure enough, it was a different size and type to the original specification so I refitted a 1 Gb 666MHz stick I had lying around from a previous upgrade and rebooted.</p>
<p>This time we re-flashed, verified and rebooted. Then it kept repeating this cycle so I took off the back panel (use the orange latch visible when the battery is removed) and removed the CMOS battery. After a short pause (30 seconds or so) I put it back and rebooted. This time there was an error message about the CMOS settings (unsurprisingly) and it rebooted.</p>
<p>However this time we got the Compaq BIOS boot screen, so I hit the escape key to enter BIOS. Then hit F9 to load default values, accept it and hit F10 to save values and hey presto the system is back up and running.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lynxworks.eu/2011/10/compaq-cq10-failed-bios-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bash</title>
		<link>http://blog.lynxworks.eu/2010/09/bash/</link>
		<comments>http://blog.lynxworks.eu/2010/09/bash/#comments</comments>
		<pubDate>Sat, 18 Sep 2010 10:13:12 +0000</pubDate>
		<dc:creator>Dougie</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[Howto]]></category>
		<category><![CDATA[Planet Ubuntu]]></category>

		<guid isPermaLink="false">http://blog.lynxworks.eu/?p=1412</guid>
		<description><![CDATA[Two things that improve my bash productivity &#8211; stopping the cursor keys inserting characters in vim and history search in bash. Edit ~/.vimrc or /etc/vim/vimrc (for system wide) and add turn off vi compatibility: set nocompatible The latter can be &#8230; <a href="http://blog.lynxworks.eu/2010/09/bash/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Two things that improve my bash productivity &#8211; stopping the cursor keys inserting characters in vim and history search in bash.</p>
<p>Edit ~/.vimrc or /etc/vim/vimrc (for system wide) and add turn off vi compatibility:</p>
<p><code>set nocompatible</code></p>
<p>The latter can be improved by editing ~/.inputrc (or /etc/inputrc for everyone). Pressing the up key scrolls through all the commands you&#8217;ve typed but by adding:</p>
<p><code>"\e[A":history-search-backward<br />
"\e[B":history-search-forward</code></p>
<p>You can type the first letter or two and get the command you need, so if you typed &#8220;mysql -u root -p&#8221; last Tuesday but can&#8217;t remember the options, typing &#8220;my&#8221; and pressing the up key will find it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lynxworks.eu/2010/09/bash/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Watch TV with VLC and a Freecom DVB-T Stick</title>
		<link>http://blog.lynxworks.eu/2009/08/watch-tv-with-vlc-and-a-freecom-dvb-t-stick/</link>
		<comments>http://blog.lynxworks.eu/2009/08/watch-tv-with-vlc-and-a-freecom-dvb-t-stick/#comments</comments>
		<pubDate>Fri, 14 Aug 2009 22:43:52 +0000</pubDate>
		<dc:creator>Dougie</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[Arch Linux]]></category>
		<category><![CDATA[Howto]]></category>
		<category><![CDATA[Planet Ubuntu]]></category>

		<guid isPermaLink="false">http://blog.lynxworks.eu/?p=850</guid>
		<description><![CDATA[One of the things I need my Aspire One to do is watch TV.  When you&#8217;re away, it&#8217;s nice to be able to watch a little TV.  I bought a Freecom DVB-T USB stick years ago and have always had &#8230; <a href="http://blog.lynxworks.eu/2009/08/watch-tv-with-vlc-and-a-freecom-dvb-t-stick/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<br />
<b>Warning</b>:  fopen(http://blog.lynxworks.eu/http://blog.lynxworks.eu/wp-content/uploads/2009/08/vlc-interface2.png) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: HTTP request failed! HTTP/1.0 404 Not Found
 in <b>/mounted-storage/home101a/sub008/sc40807-MNUP/blog/wp-content/plugins/hungred-image-fit/hungred-image-fit.php</b> on line <b>318</b><br />
Invalid file stream.
