Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Guest

well this is somewhat interesting

in the documentation we can read:

Transferring the Configuration

To transfer your configuration to another computer/location, export the configuration to an INI file and then import the file on the another computer/location.
Registry Key

well - that means that we only have to take the file and port it over...
is this true
Guest

we have several occurences of the path in the ini file


we can change it (that is the path )= in the ini-file of - perhaps somewhere at the winSCP-Client itself




PuttyPath=
LogFileName=
ActionsLogFileName=
[Configuration\History\PuttyPath] 0=
[Configuration\Interface\Explorer] ToolbarsLayout=
UserName=vhost
PublicKeyFile=
LocalDirectory=
RemoteDirectory=/
Guest

this is certainly a problem to me.


where can i enter /( edit) the data of the path!?
openSuseman

Fehler:

kann protokolldatei "C:\Users\my_old_computer\path_to_file" nicht öffnen.
System Error Code: 2
Das System kann die angeegebenen Daten nicht finden.


translated -

could not find the protocoll-file...
openSuseman

moved from one machine to another - importing correctly

hello dear experts i moved from one machine to another

and now the protocoll says - cant find the (credential) files on -- path (the old_machine/c/etc/etx

note - even if i have entered a new protocoll file - (with the upload of new credentials ) i get this annoying message...

why this happens.


how to fix that correctly