Hi, Toomas,

first of, thanks for the answers!

1. Works like a charm to use the backup utility for FeedReader Connect. I had to copy the two files gbak.exe and gfix.exe, too. Other than that it's excellent!
2. Actually in my FeedReader Connect there is no Synchronize! option in the Tools menu. Here's how I've set it up. In the Tools menu I used the FeedReader Connect Control Panel to save my FTP server's login data. Address, user name and password are stored there. Afterwards I right-clicked every single feed and set the FeedReader Connect options for them. I used the same folder on the FTP server for all of my feeds. I also checked the Enable Feed Uploader checkbox for every feed. That's it. Then I just started using FeedReader Connect as usual.
   • New articles arrived, I read some of them and eventually I closed the tool.
   • When I opened it on the other machine the articles hadn't updated. They were still all in the same state I left them in. Some were read, some unread.
   • I tested a litte more and found that it seems random which version gets uploaded to the FTP server. Actually sometimes a read article appears as read even on the other machine. However, I can't find the reason why this doesn't always work
   • Aside from the read/unread status there's another strange bahavior: when I force a manual upload (i.e. right-click a feed and hit Trigger feed upload) I doesn't necessarily appear in the Event Viewer. Sometimes it shows up and the next time the Event Viewer is just empty.
3. Thanks for explaning that. Now I get the difference between the archive and the database. At least I hope that I understand the difference. If I get this right the archive says how many articles are displayed for every feed. So an archive size of 50 will let me see up to 50 articles for every feed. When the 51st arrives the oldest article is cut off. However, internally it still remains in the database. That's why the FDB database file get's bigger and bigger over time. The articles are still there even if I don't see them anymore. That's where the backup utility comes in handy to reduce the FDB file's size. Is that about right?
4. See 3

Now I quite get how you are using "the synchronization" :). Problem is that feeds are not uploaded to server every time you change readstatus of some of your articles. This feed upload is not meant to be used this way although it's possible. In latest versions normal Feedreader has Synchronize option that allows you to send to server all read states. And in other Feedreader you will then download them and readstates are applied automatically.

About archive size - if article will be 51th then it's contents will be deleted but article row still stays in database. Now this Backup Application will delete those empty rows. In latest 3.12 it's already done automatically on every application start. In older version you had to use Backup Utility to do this.

But to be honest it's quite hard to compare 3.08 and 3.12. There are quite a lot of things changed and made better in 3.12.

Hi, Toomas,

I see why the synchronization didn't work the way I expected. I've tried the regular FeedReader instead of FeedReader Connect, too.

However, the regular FeedReader uploads the whole FDB file at once when I use its Synchronize! function. With my connection speed and with an FDB file size of about 5 MByte it takes 40 seconds to upload the FDB file. Now even with the backup utility I didn't find a way to make the FDB file smaller than 5 MByte. Let alone much smaller - like for example 500 kByte. It just wasn't possible.

• FeedReader is slow but it synchronizes the read/unread status.
• FeedReader Connect ist fast but it does not necessarily synchronize the read/unread status.

How can I use both speed and read/unread synchronization together? You said that FeedReader Connect is not meant to be used the way I used it even if it's possible. How can I make both features work together so that FeedReader Connect synchronizes the read/unread status? What would you suggest?

Greetings,

Sven

Something is wrong here with Feedreader synchronization. :) Feedreader does not upload whole FDB file. It uploads only the read state. For example in case of 60 days of reading state history this file is 270 kb (in my case). But it's not needed to synchronize 60 days. It's enough to synchronize 3 days if you sync every day. This is not article age but history of reading state change. So it uploads 3 days of your "actions". In my case it takes 1 minute to complete sync in case of 60 days.

Maybe you had some settings wrong in Feedreader Synchronization Options. You can play around with them (different FTP settings).

BTW. What's your computers characteristics? And how many feeds you have subscribed?

I feel like Homer Simpson realizing he totally fucked something up. I was totally wrong.

FeedReader works as you described. It synchronizes the read state when I hit the Synchronize! button.

Back in the days when I tested FeedReader for the first time I wasn't happy with the Synchronize! function for whatever reason. I don't remember why I wasn't happy with it. I switched to manually uploading the FDB file every time I quit FeedReader. So that's why I was convinced that Synchronize! uploads the whole FDB file. I just had it remembered incorrectly.

It pretty much works how I like it. Now two questions popped up:

1. Can I let the synchronization run completely in the background when I start FeedReader and when I quit FeedReader? So that I don't have to open the menu and do it by myself. No pop-up, no buttons, just all automatically in the background. Is that possible? Is there such an option?
2. How can I synchronize the feed addresses together with the read states? When I add a feed on one machine I have to add it manually on the other machine, too. How can I change the synchronization so that it includes the list of feed addresses?

Greetings,

Sven

PS: here are some of my machine's specifications:

• Windows XP Professional with Service Pack 2
• All security updates installed
• If it matters: an Intel Pentium 4 with 3 GHz
• 1 GByte RAM

Oh and I've subscribed to 34 feeds.

If you add skipvercheck=yes to feedreader.ini in [misc] section then Feedreader will not search for updates any more.

What comes to new version of Feedreader Connect then this demo version will stay the same as it is at the moment. In our opinion it's enough to test version out. But in some days we will make Feedreader Connect available for purchase. It will be based on 3.12 and will quite always be up to date in the future. Also it removes the limitations that are available in demo right now.

Greetings
Toomas

Thanks for the hint about changing the INI file. I did that and so far it works perfectly.

Thanks, even it works fine for me
regards
Nude Female Paintings

Very good site, excellent content, I will recommend to my group of readers in the university, I found very interesting article on the internet, including this ... I will leave an input ----> The Antique Autos are considerate real treasures and many people pay a lot for them,? the quality of a good antique autos especially the classic ford cars represent many money, are a exception of the rule because can have higher prices in the market, the antique autos are a good option for some part of the society like the classic ford cars too, that meaning power, and position in a society that every day need it more of course, and the antique cars or classic ford cars like for example the Buick classic, the classic corvettes.
More info at: http://www.antique-classiccars.com/

Treatment for impotence
Impotence is not an extremely grave thing, even though it can be extremely harmful to a man's self-esteem and confidence. On the other hand, if you are a man that experiences from impotence, not considering of how old you are, you be supposed to know that there are things that you can do in order to help yourself out with this problem