<?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>Windows Software &#8211; Tomas&#039; log of stuff</title>
	<atom:link href="https://blog.fjetland.com/category/technology/windows-software/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.fjetland.com</link>
	<description>Notes from the sysadmin trenches, on hobby photography, and anything else that comes to mind</description>
	<lastBuildDate>Wed, 15 Jun 2022 19:08:31 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Connecting VS Code directly to Photon OS 4</title>
		<link>https://blog.fjetland.com/2022/06/connecting-vs-code-directly-to-photon-os-4/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=connecting-vs-code-directly-to-photon-os-4</link>
					<comments>https://blog.fjetland.com/2022/06/connecting-vs-code-directly-to-photon-os-4/#respond</comments>
		
		<dc:creator><![CDATA[tomasf]]></dc:creator>
		<pubDate>Wed, 15 Jun 2022 19:05:52 +0000</pubDate>
				<category><![CDATA[Containers]]></category>
		<category><![CDATA[Windows Software]]></category>
		<category><![CDATA[docker]]></category>
		<category><![CDATA[photon os]]></category>
		<category><![CDATA[system administration]]></category>
		<category><![CDATA[vs code]]></category>
		<guid isPermaLink="false">http://blog.fjetland.com/?p=1441</guid>

					<description><![CDATA[Tweaking Photon OS to allow VS Code to connect to it over ssh]]></description>
										<content:encoded><![CDATA[<div class="wp-block-image">
<figure class="aligncenter size-large"><img fetchpriority="high" decoding="async" width="1024" height="536" src="http://blog.fjetland.com/wp-content/uploads/2022/06/vscode-1024x536.png" alt="" class="wp-image-1442" srcset="https://blog.fjetland.com/wp-content/uploads/2022/06/vscode-1024x536.png 1024w, https://blog.fjetland.com/wp-content/uploads/2022/06/vscode-300x157.png 300w, https://blog.fjetland.com/wp-content/uploads/2022/06/vscode-768x402.png 768w, https://blog.fjetland.com/wp-content/uploads/2022/06/vscode.png 1200w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure></div>


<p>This is just a quick update to <a href="http://blog.fjetland.com/2022/05/setting-up-photon-os-4-as-a-docker-host-vm-on-vsphere-7/" data-type="post" data-id="1401">my setting up Photon OS as a docker host</a> post. I use <a href="https://code.visualstudio.com/" data-type="URL" data-id="https://code.visualstudio.com/" target="_blank" rel="noopener">VS Code</a> to both (try to) write code and edit configuration files, such as YAML files for Docker Compose. So to make configuring containers faster and easier, I&#8217;d like to be able to edit the files directly on the Photon VM using VS Code with the <a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack" target="_blank" rel="noopener">Remote Development pack</a> on my desktop.</p>



<p>To do this, VS Code wants to deploy a small component on the destination server, and that doesn&#8217;t run entirely smoothly on Photon OS minimal out of the box due to its small footprint. So here&#8217;s what I need to adjust.</p>



<p>First, it needs tar to untar the addon, so</p>



<pre class="wp-block-code"><code>tdnf -y install tar</code></pre>



<p>Next, the sshd demon needs to allow TCP forwarding, which it doesn&#8217;t out of the box.</p>



<pre class="wp-block-code"><code>sed -i "s/AllowTcpForwarding no/AllowTcpForwarding yes/g" /etc/ssh/sshd_config</code></pre>



<p>Then restart the sshd, and we&#8217;re good to go!</p>



<pre class="wp-block-code"><code>systemctl restart sshd</code></pre>



<p>And then VS Code is ready to connect straight to the Photon OS VM! If you remembered to install the extensions, obviously&#8230;</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.fjetland.com/2022/06/connecting-vs-code-directly-to-photon-os-4/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Blast from the past: PicaView returns</title>
		<link>https://blog.fjetland.com/2015/03/blast-from-the-past-picaview-returns/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=blast-from-the-past-picaview-returns</link>
					<comments>https://blog.fjetland.com/2015/03/blast-from-the-past-picaview-returns/#comments</comments>
		
		<dc:creator><![CDATA[tomasf]]></dc:creator>
		<pubDate>Sun, 08 Mar 2015 22:16:27 +0000</pubDate>
				<category><![CDATA[Photography Software]]></category>
		<category><![CDATA[Windows Software]]></category>
		<category><![CDATA[image management]]></category>
		<category><![CDATA[photography utilities]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[Windows]]></category>
		<guid isPermaLink="false">http://blog.fjetland.com/?p=27</guid>

					<description><![CDATA[I use a lot of utilities. Up through the years I&#8217;ve registered many dozens of small and not so small shareware and otherwise distributed utilities. One of the earliest ones I actually paid for&#46;&#46;&#46;]]></description>
										<content:encoded><![CDATA[<p>I use a lot of utilities. Up through the years I&#8217;ve registered many dozens of small and not so small shareware and otherwise distributed utilities. One of the earliest ones I actually paid for was back in the Windows 3.11 days, and it was <a href="http://en.wikipedia.org/wiki/ACDSee" target="_blank" rel="noopener">ACDSee</a>, a fast image browser with an amazing file format support. Back in those days, pretty much every program that used images had its own format, and pretty much everyone that worked with images had their own preference that they would send out images in. It was a mess.</p>
<p>Until ACDSee came around.</p>
<p>It wasn&#8217;t the first. And it wasn&#8217;t free. But it was small, comprehensive and it was FAST.</p>
<p>There&#8217;s been many updates to ACDSee, and unfortunately most of them have not been for the better according to many of us long time users. But for a while ACD Systems also developed some interesting smaller utilities to make images more accessible in Windows, such as Image Fox (which would tag a preview box beside any standard Windows Save or Open dialog), mPowerTools, etc. But my favorite companion to ACDSee was always PicaView, an Explorer shell extension that would let you right click any image in explorer and get a preview right in the context drop down menu with quick access to essential image data and functions. Unfortunately most of these utilities were discontinued long ago, some naturally because of improvements in Windows or in competing products, but when PicaView went away it always felt like there was an unfilled space.</p>
<p>I&#8217;ve kept my ACDSee licenses reasonably updated through all these 20 years, skipping a version now and then. I even ran the big brother <a href="http://www.acdsee.com/en/products/acdsee-pro-8" target="_blank" rel="noopener">ACDSee Pro</a> for a few years. But for the last few years I&#8217;ve felt that they&#8217;ve released new versions every autumn just to boost sales, with little or no benefit to us fans of the core functionality. If anything the &#8220;image browser&#8221; functionality kept getting slower and slower.</p>
<p>So when a friend pinged me and said he thought the latest version 18 was faster with our 36 megapixel raw files, I was still back at version 15 and had stopped paying attention to what they were up to. I decided to give it a try. And while it does seem faster, the big surprise was the return of an old friend; <a href="http://www.acdsee.com/en/products/acdsee-18/whats-new" target="_blank" rel="noopener">PicaView is back</a> as a feature of <a href="http://www.acdsee.com/en/products/acdsee-18" target="_blank" rel="noopener">ACDSee 18</a>! And there was much rejoicing.</p>
<p>So what&#8217;s all the fuss about? Here&#8217;s a folder of raw files from my trip last year to Kenya. Normally I&#8217;d find my way around my raw files from within Lightroom, but sometimes I need to browse through them just quick on the road before they&#8217;re imported, or I&#8217;m accessing my drive from another PC. In these cases both ACDSee and Picaview comes in handy. PicaView lets me see a more detailed preview of the image <em>and</em> the essential shooting data without leaving the Explorer interface.</p>
<p><div id="attachment_31" style="width: 1040px" class="wp-caption alignright"><a href="http://blog.fjetland.com/wp-content/uploads/2015/03/PicaView_v18.png" data-rel="lightbox-gallery-IQgd3Kr2" data-rl_title="PicaView previewing a RAW file from a Nikon D810" data-rl_caption="" title="PicaView previewing a RAW file from a Nikon D810"><img decoding="async" aria-describedby="caption-attachment-31" class="size-full wp-image-31" src="http://blog.fjetland.com/wp-content/uploads/2015/03/PicaView_v18.png" alt="PicaView previewing a RAW file from a Nikon D810" width="1030" height="978" /></a><p id="caption-attachment-31" class="wp-caption-text">PicaView previewing a RAW file from a Nikon D810</p></div></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.fjetland.com/2015/03/blast-from-the-past-picaview-returns/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
