Differences

This shows you the differences between two versions of the page.

--- troubleshooting [2025/05/25 15:21] – admin
+++ troubleshooting [2025/07/31 17:56] (current) – admin
@@ Line 1: / Line 1: @@
 ======Trouble Shooting======
-**NOTE:** If you encounter a persistent problem when using //Git Winch// please email us at admin@gitwinch.com
+**NOTE:** If you encounter a persistent problem when using //Git Winch// please email us at **admin@gitwinch.com**
+**Starting trouble**\\
+If the application simply does not start or displays a dialog and then quits, usually it would be because the application was not able to load some critical files that are always needed. For example; if the translation file for the language you had set the value for //trTranslate=// in the ini file was not available, it will not be able to proceed. That is because it just does not understand what messages to show you!
+The solution is usually simple: Just get the original downloadable zip file from our website and use that as per the [[/installation?do=export_xhtml|instructions given here.]]
 **Git functionality**\\
-We have simplified Git to such an extent that we have only given a small subset of all the stuff that //Git// can do. If you encounter some unusual situations in //Git//, you can always right-click on the folder for the pop-up menu, and drop down to the CMD window of that folder, and execute //Git// commands manually there. In many cases you can also use the excellent //TortoiseGIT// software also to do advanced //Git// work.
+We have simplified Git to such an extent that we have only given a small subset of all the stuff that //Git// can do. If you encounter some unusual situations in //Git//, you can always right-click on the folder for the pop-up menu, and drop down to the CMD window of that folder, and execute //Git// commands manually there. In many cases you can also use the excellent //TortoiseGIT// software also to do advanced //Git// work. Read more about TortoiseGit [[advancednotes?do=export_html|here]]
 **Handling known_hosts file**\\
 Whenever you connect to a new Git host using an SSH key, your computer would want to know if the connection to the server is to be allowed. So when you clone a new repository, first //Git Winch// preforms a check to see if the connection is to a "known host". Internally //Git Winch// runs a special batch file "setknownhosts.bat" and that fetches the correct data from the server and if found okay, it would append a file at //known_hosts// which is inside the .ssh sub-folder inside your Windows <userprofile> folder. This uses a special utility called ssh-keyscan and unfortunately, Windows does not update this to the current requirements. So install the latest SSH utilities from https://github.com/PowerShell/Win32-OpenSSH/releases Choose an appropriate .msi installer from the list there and run it.
+Read more [[knownhosts?do=export_xhtml|about known_hosts here]]
@@ Line 14: / Line 21: @@
+**Known Issues**\\
+//Git Winch// works closely with the underlying Windows Operating system. Once you start //Git Winch// and then you start making changes to the work folder and/or sub-folders underneath the work folder, Git Winch will throw some errors and you may get some technical messages. Usually //Git Winch// will not work properly after that. So if you do want to make any changes to those folders, do all that when //Git Winch// is NOT running.
 -----
 [[/concepts?do=export_xhtml | Learn the concepts]] | [[/configuration?do=export_xhtml|Configuration]] | [[/advantages?do=export_xhtml | Advantages]] | [[/tsManage2?do=export_xhtml|Management]]  | [[ /advanced?do=export_xhtml | Advanced uses]] | [[ /topics?do=export_xhtml | Table of Contents]]

Git Winch Guide

Differences

Page Tools