<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "Any known issues with QRecall under Big Sur?"]]></title>
		<link>https://forums.qrecall.com/posts/list/2.page</link>
		<description><![CDATA[Latest messages posted in the topic "Any known issues with QRecall under Big Sur?"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>Any known issues with QRecall under Big Sur?</title>
				<description><![CDATA[ I just installed Big Sur and want to know if it's been tested]]></description>
				<guid isPermaLink="true">https://forums.qrecall.com/posts/preList/2351/5935.page</guid>
				<link>https://forums.qrecall.com/posts/preList/2351/5935.page</link>
				<pubDate><![CDATA[Tue, 17 Nov 2020 16:25:57]]> GMT</pubDate>
				<author><![CDATA[ Ernest Ashford]]></author>
			</item>
			<item>
				<title>Re:Any known issues with QRecall under Big Sur?</title>
				<description><![CDATA[ QRecall 2.2 has been tested under Big Sur and appears to be generally functional. We're performed hundreds of captures here at QRecall central. <br> <br>There may be some odd issues with the layers.index file (see the earlier thread), which we're looking into. But for now it appears that repairing the archive will resolve the issue (and this issue does not involve any data loss). <br> <br>As mentioned in the [url=http://www.qrecall.com/release/?version=2.2.8]2.2.8 release notes[/url], there are a few minor cosmetic issues, most of which are being dealt with in QRecall 3.0 (which has not been released yet).]]></description>
				<guid isPermaLink="true">https://forums.qrecall.com/posts/preList/2351/5937.page</guid>
				<link>https://forums.qrecall.com/posts/preList/2351/5937.page</link>
				<pubDate><![CDATA[Tue, 17 Nov 2020 16:31:19]]> GMT</pubDate>
				<author><![CDATA[ James Bucanek]]></author>
			</item>
	</channel>
</rss>