Hi guys,
today the portable app manager notified me the availability of an upgrade for my portable kitty (to 0.63.1.4). I did it, as I've already done it a lot of times before... and lost all my settings. Very very very bad! 
First of all I want you to know I love your software and also I had a backup copy from which I restored my settings (or I'd have really been lost), but this bothered me anyway. I just hope this won't happen again, it's really unfair. Please.
Thank you for your work and bye.
J.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Sorry to hear about that. Sadly, it looks like KiTTY will lose its INI and log files (but not its Commands, Folders, Launcher, Sessions, Sessions_Commands, and SSHHostKeys) if you improperly exit and then upgrade without running it first so it can recover. I've updated most apps to even recover from this sort of situation, but it looks like KiTTY's installer isn't yet set to manually preserve an INI left in its App directory. I'll have that updated for the next release.
For background, an improper exit occurs when the PC crashes, when the drive is ejected or shorted while the app is running, or when Windows is shut down while the app is running. That's why the app will warn you it was improperly shut down on next run and why the platform has a function built in to ensure all your apps are properly closed (politely without crashing) on exit.
Sometimes, the impossible can become possible, if you're awesome!
I have that included now in my packaging template (FilesToPreserve for kitty.ini and putty.log). Sorry for overlooking that.
Should I do a Revision 2 for 0.63.1.4 (and what PackageVersion should I choose then - 0.63.1.42? but that could interfere with 0.63.1.5) or should I wait for the next base app's update. There is this crashing error still lurking around...
You can include it in the .5 pack that was just released.
Sometimes, the impossible can become possible, if you're awesome!
Thanks, just got the update notification. It'll be ready in a few minutes (it's 4:00 a.m. here, should do something about my sleep disorder. ;))
Hi John,
thank you for your reply.
Sorry, maybe I wasn't accurate enough when I tried to explain my issue.
As far as I know I didn't do any improper exit. Besides, I hadn't lost the ini and log files, but the "Sessions" folder with the configuration of all the servers of mine.
It's usually stored in "Data" when the app isn't active and moved in "App/Kitty" when it is. After the upgrade it wasn't present in any of them. If I hadn't backed it up previously I'd been lost.
That's specifically configured to be preserved if it's not moved back and forth. If it got lost, the first thing I'd explore is errors on the drive. Moving back and forth and 'preserving' within the installer is accomplished just via simple rename Windows API calls. Nothing more complicated than that. And there's no command anywhere to delete that folder.
Sometimes, the impossible can become possible, if you're awesome!
I just found one scenario, where this happens:
If
kitty_portable.exeis run directly from theApp\KiTTYdirectory and then closed, a defaultSessionsfolder - containing theDefault%20Settings- is created.A subsequent launch of
KiTTYPortable.exeeither standalone or from the Menu replaces the savedSessionsfolder in Data with the new (empty) one - despite the description in the launcher manual:Is this a bug or did I overlook something?
-edit-
I finally got the
configdiroption working. (I thought too complicated before and KiTTY can be called the worst documented app I know...)Please hold back the update until I figured it out completely. That should prevent all the above problems...
I have (presumably) the same problem, possibly with even stranger behavior.
I had a whole bunch of saved connections that disappeared a few days ago, possibly when I last upgraded, but I didn't notice the coincidence.
Now:
1) if I start KiTTY fresh from PortableApps start menu I have all my connections.
2) if I try a second connection they seem to be gone.
3) if I use the window menu (click on the icon on the top left of window decoration) and select "Saved Sessions" they are all there
4) ... , but if I select one of them KiTTY fails and drops me into the empty "KiTTY Configuration" window.
Problem seems to be the new KiTTY may save its things in ...\PortableApps\KiTTYPortable\App\KiTTY\Sessions instead of the "normal" (read: "old behavior") ...\PortableApps\KiTTYPortable\Data\Sessions.
I do not know why this happens and which is the "right" place, but synchronizing the two dirs cured the symptoms for me.
Someone with more insight into the PortableApps structure should have a look at this (I'm more of a Linux guy, sorry).
A new update with a fix for this would be *VERY* welcome!
Thanks for all the good work.
Thanks for your information. This bug seems not to be related to the opening post. There was another report some days ago, but I could not reproduce it (not enough infos). I cought a cold and don't know if I can have a look at it before next weekend. As KiTTY is outdated, I hope to do some troubleshooting before the update.
-edit-
I did some testing today and I can partly reproduce this. I did not encounter it for now, because I usually just double-click my sessions (same as open). Starting does hide some of my saved sessions, but not all. I did not find out so far, why some are affected and others not.
This applies to the base app as well. I tried with a vanilla KiTTY folder with just the kitty_portable.exe from the developers site. The Sessions folder is created on first start as well as a new kitty.ini. I copied my sessions to the folder and found the exact same behaviour (sessions disappearing after I started the first one). You can report it to cyd on his website: http://kitty.9bis.net/
I'll file a bug report as well, as this still occurs with the latest version.
All relevant files are preserved in the current release 0.67.1.3. I believe it was fixed a while back but this bug was not updated.
Sometimes, the impossible can become possible, if you're awesome!