I haven't been able to run Kitty since the new version (KiTTY Portable 0.73.2.1) was released. I get a message that it may need to be reinstalled. I have uninstalled, removed the local folders, reinstalled, and still get the same message. This is an app I use to get my work stuff done, so any help would be greatly appreciated. Thank you in advance.
You are here
Please Help Support Us
Please help support us by making a donation so we can keep bringing you awesome free software. We accept credit card, wire transfer, PayPal, cryptocurrency, and more.
If you recently donated, thank you!
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
Hello Paul,
I am the packager for KiTTY Portable and it works as expected on my machines here.
Could you please provide some information about your system/os/installation folder etc?
Would you mind running kitty_portable.exe (located in ...\PortableApps\KiTTYPortable\App\KiTTY when installes through the PA.c Menu) directly? It will generate some folders and files apart from "kitty_portable.exe" and "kscp.exe" that can be deleted afterwards. Does the same error occur? What is the exact error message?
Kitty did not work for me today after update.
---------
The fix is to open "PortableApps\KiTTYPortable\Data\Sessions\Default%20Settings" in notepad and remove any ip address from the line HostName.
Before:
HostName\1.1.1.1\
After:
HostName\\
---------
To find this problem and solve it successfully I did steps:
I could not launch default kitty from "PortableApps\KiTTYPortable\App\KiTTY", so I removed sessions folder and re-launched.
Kitty started OK and it created new default settings file. Then I compared fresh default settings with my default settings from
"PortableApps\KiTTYPortable\Data\Sessions" and line by line I experimented to change settings.
Hostname was the line that worked!
Basically, Kitty chokes if any ip address is there.
Thanks for the package!
Thanks for the heads up.
I try to find the reasons for that behavior. In my setup, I don't get an entry in hostname. The default file that is created new by kitty on a new installation just has the empty
HostName\\line. After usage, I still have no entry.The KiTTY base app changed the creation and handling of the
Default%20Settingsfile some time ago and introduced (and fixed) some bugs during that process. Maybe you have a leftover of this.Did you launch
kitty_portable.exedirectly from\KiTTYPortable\App\KiTTYorKiTTYPortable.exefrom\KiTTYPortable(the actual PA.c-Launcher)? The first option would launch the base app, bypass any portablization functionallity from the PA.c-Launcher and create another set of of settings (kitty.ini) and sessions in the same folder. That may not be the reason for this buggy behavior, but you will end up with two configuration sets. Only the set in\KiTTYPortable\Data\is used by theKiTTYPortable.exe, either when launched directly or from the PA.c menu.Hi, thank you for getting back and concern.
Perhaps, I could expand further a little bit.
I am always launching KiTTY from the PortableApps launcher: the file is 'D:\Apps\PortableApps\KiTTYPortable\KiTTYPortable.exe`. Sessions from this executive come from default folder - `D:\Apps\PortableApps\KiTTYPortable\Data\Sessions\`. I have session files there from as early as 2016.
I was surprised that KiTTY did not launch after update from Launcher, so I went to try to launch it manually - via same normal exe, both as regular user and admin. This is afaik the same as Launcher, so no surprise here.
I explored various folders in the installation and found the folder which contains the binray `D:\Apps\PortableApps\KiTTYPortable\App\KiTTY\kitty_portable.exe` (along with kscp.exe and /Sessions/ folder). In this location there were no *.ini files whatsoever. I never touched any ini file, afaik.
I tried to launch without success the exec `D:\Apps\PortableApps\KiTTYPortable\App\KiTTY\kitty_portable.exe`, next I removed /Sessions/ folder from that location to get rid of any possible corruption in the only file that was present in that folder - `Default%20Settings`. Having that deleted, I relaunched the same exe and it worked! It appeared to me that if I could fix the possible problem in my "normal" default session `D:\Apps\PortableApps\KiTTYPortable\Data\Sessions\Default%20Settings` - then the normal launcher would also work. The rest is history
I must acknowledge a big help that I got from my favorite PortableApp - WinMerge. I could easily spot what was different in both settings and copied-restored line by line the lines that were different. I am lucky the problem was solved just by removing IP address. I am already using the KiTTY without issues on my other saved sessions.
Thank you for your work maintaining the app!
You should not have any file or folder in
D:\Apps\PortableApps\KiTTYPortable\App\besidekitty_portable.exeandkscp.exe. If there are is a folder called/Sessions, then you have an indication that sometime you called thekitty_portable.exe(base app ) directly without the PA.c-Launcher (i.e. you did not use theKiTTYPortable.exein the "main" folderKiTTYPortable). That would generate a new/Sessionsfolder beside the base app. That is not used, when launched from the Menu or the PA.c-Launcher.There was a time, when
kitty_portable.exedid not run without a correctDefault%20Settingsin the right place, but that was fixed months ago.Would you please confirm that you use the latest KiTTY version (0.73.2.18p, when you click the About button).
btw. that should not be the reason for KiTTY not starting correctly but is a hint, that something seems messed up in your setup.
Thank you for your time. I wish I could do more to help you investigate the problem. Here is what I have just did -
D:\Apps\PortableApps\KiTTYPortable\App\besidekitty_portable.exeandkscp.exe.KiTTYPortable.exe.That said, I rechecked - If any char is present between slashes in
Hostnameline inDefault%20Setitngsfile -KiTTYdoes not launch. If this line remains asHostName\\then KiTTY launches fine.Thanks for your investigations. This seems to be a base app issue. See here. (btw. did you open that issue on Cyds git?
).
-edit-
KiTTY 0.74.0.2 fixes this issue. I packaged it today. Just wait a while until it is released.