Some bugs and some improvments

Tanel Rebane wrote:

How to reproduce bug:
1) Create a few directories in local source path to sync/keepuptodate from.
2) Run WinSCP.bat.
3) Delete the content in local source path.
4) Refresh the local source path in explorer.exe (F5), the directories are still there, they are also still there in the remote path. Trying to delete them locally (again) via explorer.exe results in the following message "Cannot delete file: Cannot read from the source file or disk".
5) Terminate WinSCP, the directories are now gone locally but not remotely.

How to reproduce bug:
1) Run: "C:\Program Files\Synkman\winscp.exe" synkman@192.168.7.10 /keepuptodate
2) Start the keepuptodate.
3) Minimize to tray.
4) Unminimize it. You now have a big grey windows that you can't influence.

Suggestion of improvement 1:
When logging together with keepuptpdate the logfile grows very quickly. Consider having a logging option with less output, maybe the same amount of output as in cmd.exe when running /keepuptodate with /console.

Suggestion of improvement 2:
This one is a bit trickier I suppose, but being able to minimize winscp.com to tray would be just super!

martin wrote:

Tanel Rebane wrote:

How to reproduce bug:
1) Create a few directories in local source path to sync/keepuptodate from.
2) Run WinSCP.bat.
3) Delete the content in local source path.
4) Refresh the local source path in explorer.exe (F5), the directories are still there, they are also still there in the remote path. Trying to delete them locally (again) via explorer.exe results in the following message "Cannot delete file: Cannot read from the source file or disk".
5) Terminate WinSCP, the directories are now gone locally but not remotely.

I'm not able to reproduce this one. So you start with empty c:\WWW. Start "keep up to date". You create few directories, like c:\WWW\a and c:\WWW\b. They get uploaded. Then you remove them?

martin wrote:

Tanel Rebane wrote:

Suggestion of improvement 1:
When logging together with keepuptpdate the logfile grows very quickly. Consider having a logging option with less output, maybe the same amount of output as in cmd.exe when running /keepuptodate with /console.

Which log do you mean? Log on the dialog window or logging to file?

martin wrote:

Tanel Rebane wrote:

Suggestion of improvement 2:
This one is a bit trickier I suppose, but being able to minimize winscp.com to tray would be just super!

I do not think I'm able to minimize winscp.com to tray. But it should be possible to minimize "winscp.exe /console" to tray. Do you need to do this with winscp.com for some reason?

"C:\Program Files\Synkman\winscp.exe" synkman@192.168.7.10 /console /script=script.txt

C:\Program Files\Synkman>"C:\Program Files\Synkman\winscp.exe" synkman@192.168.7.10 /console /script=script.txt

"C:\Program Files\Synkman\cmdow.exe" /run /hid "C:\Program Files\Synkman\winscp.com" synkman@192.168.7.10 /script=script.txt

Tanel Rebane wrote:

There should be an option to log to logfile the same output that is printed in the dialog window. Or something alike, because if you have /keepuptodate running 24/7 the current logfile grows huge.

martin wrote:

This wouldn't be a problem if the cmd.exe-window didn't need input after you've terminated WinSCP.exe.

Example:
Running a bat-file with the following content:

"C:\Program Files\Synkman\winscp.exe" synkman@192.168.7.10 /console /script=script.txt

Starts a cmd.exe-process with the following output in its window:

C:\Program Files\Synkman>"C:\Program Files\Synkman\winscp.exe" synkman@192.168.7.10 /console /script=script.txt

I recorded the bug you could not reproduce on video.

martin wrote:

Tanel Rebane wrote:

There should be an option to log to logfile the same output that is printed in the dialog window. Or something alike, because if you have /keepuptodate running 24/7 the current logfile grows huge.

This is probably what this request is about.

martin wrote:

Tanel Rebane wrote:

This wouldn't be a problem if the cmd.exe-window didn't need input after you've terminated WinSCP.exe.

Example:
Running a bat-file with the following content:

"C:\Program Files\Synkman\winscp.exe" synkman@192.168.7.10 /console /script=script.txt

Starts a cmd.exe-process with the following output in its window:

C:\Program Files\Synkman>"C:\Program Files\Synkman\winscp.exe" synkman@192.168.7.10 /console /script=script.txt

This is not true. At least not generally. Where do you run winscp.exe from, when this happens?

martin wrote:

I recorded the bug you could not reproduce on video.

I've followed the video step by step and still it works for me. The directories, once deleted and gone for good on the first attempt. So there must be something different on your system. I suppose you are using Win XP SP3? What is file system on your C: drive?

It seems to hold true on my system. I made another video that shows this behavior: <invalid link removed>

Windows XP SP3 with C: running NTFS. I shall see if I can create an VMware-image for you. In the meanwhile is there anything else I could do, provide you with debug-info or such?

martin wrote:

It seems to hold true on my system. I made another video that shows this behavior: <invalid hyperlink removed by admin>

OK. This is misunderstanding. The cmd.exe is not run by winscp.exe /console. It is run by Windows to run the .bat file. Which in turn runs winscp.exe, which opens the second window. If you execute winscp.com from the .bat, the .com inherits the .bat console window, hence no new window is opened. But this is reason I do not think i'll be able to minimize the window, because it is not owned by winscp, it is owned by the parent cmd.exe process.
But as your .bat file includes only single command you can replace it by shortcut file, which opens no window.

martin wrote:

Windows XP SP3 with C: running NTFS. I shall see if I can create an VMware-image for you. In the meanwhile is there anything else I could do, provide you with debug-info or such?

I have no idea. I've hoped you have different FS (i do have NTFS as well). I'm going to upgrade to XP SP3 soon in case the problem is caused by it.

Tanel Rebane wrote:

I see. Well, nevertheless it would be great if you could minimize .exe /console and also start it minimized with e.g. .exe /console /minimize.

martin wrote:

Tanel Rebane wrote:

I see. Well, nevertheless it would be great if you could minimize .exe /console and also start it minimized with e.g. .exe /console /minimize.

You can minimize console window by running WinSCP trough shortcut with Run option set to minimize.

Minimization to tray has been added to tracker.

Tanel Rebane wrote:

2) Synkman against Debian 4.0 r3 using sftp-server from XP SP3 produces the same result, being the bug.

In situation 2 another bug occurs. That is that you must provide a password for the user when using "winscp.exe <session> /console /script=<script>" even tho the session is saved with a path to a valid .ppk that works in GUI-mode.

martin wrote:

Tanel Rebane wrote:

2) Synkman against Debian 4.0 r3 using sftp-server from XP SP3 produces the same result, being the bug.

In situation 2 another bug occurs. That is that you must provide a password for the user when using "winscp.exe <session> /console /script=<script>" even tho the session is saved with a path to a valid .ppk that works in GUI-mode.

Can you post a log file?

Anonymous wrote:

martin wrote:

Tanel Rebane wrote:

2) Synkman against Debian 4.0 r3 using sftp-server from XP SP3 produces the same result, being the bug.

In situation 2 another bug occurs. That is that you must provide a password for the user when using "winscp.exe <session> /console /script=<script>" even tho the session is saved with a path to a valid .ppk that works in GUI-mode.

Can you post a log file?

Sorry, this was an error on my side, a copy-paste error. I hope I didn't cause too much trouble.

Tanel Rebane wrote:

The directory-delete bug as described in the first post and also shown in the video IS still there. I hope you can find the source to this bug!

martin wrote:

Tanel Rebane wrote:

The directory-delete bug as described in the first post and also shown in the video IS still there. I hope you can find the source to this bug!

I have already installed SP3. So I'll test this soon again in case it is caused by the SP.

I doubt it has anything to do with SP3 since it occurred on XP SP2, XP SP3, 2003 SP2 and 2008 SP1 for me.

martin wrote:

I doubt it has anything to do with SP3 since it occurred on XP SP2, XP SP3, 2003 SP2 and 2008 SP1 for me.

Sorry, I've missed that information.
Then I have no clue :-(

Tanel Rebane wrote:

Did you try out the Synkman2_v2.rar? In theory you shouldn't have to, but things rarely work in practice as they do in theory.

martin wrote:

Tanel Rebane wrote:

Did you try out the Synkman2_v2.rar? In theory you shouldn't have to, but things rarely work in practice as they do in theory.

I have just tried it with the .lnk and the script from Synkman2_v2.rar. No difference, it works :-(
What about any software you have on your machine that may influence how local files are accessed? Like antivirus.

Tanel Rebane wrote:

Suggestion of improvement 1:
When logging together with keepuptpdate the logfile grows very quickly. Consider having a logging option with less output, maybe the same amount of output as in cmd.exe when running /keepuptodate with /console.

Tanel Rebane wrote:

the first bug reported in the first post (the one you couldn't repeat) is now becoming problematic again. I just tried 4.2.1 beta and it's unfortunately still there. I am about to create one Debian-image and one Windows-image preconfigured so you can confirm this bug, what format would you like it in? VirtualBox or VMWare Workstation/Player?

Anonymous wrote:

And this also would be of great use, in other words: a logging level that is identical to the output of the "winscp.exe /console"-window. And also

martin wrote:

Tanel Rebane wrote:

the first bug reported in the first post (the one you couldn't repeat) is now becoming problematic again. I just tried 4.2.1 beta and it's unfortunately still there. I am about to create one Debian-image and one Windows-image preconfigured so you can confirm this bug, what format would you like it in? VirtualBox or VMWare Workstation/Player?

I doubt I find a time to play with the images. There are so many other issues outstanding, that worry many more people and whose solution is much simpler. I'm sorry.

martin wrote:

Anonymous wrote:

And this also would be of great use, in other words: a logging level that is identical to the output of the "winscp.exe /console"-window. And also

Have you noticed XML logging?

Tanel Rebane wrote:

I understand, but if I provide you with images you have a starting point for when you find time.

So, what format would you like the image in? VirtualBox or VMWare Workstation/Player?

I did notice it. At first I thought it wouldn't be applicable to my situation but having taken a closer look I think it could work well after finding a decent XML-parser. Any recommendations?

martin wrote:

Tanel Rebane wrote:

I understand, but if I provide you with images you have a starting point for when you find time.

That's true. But still I think it i swaste of your time.

martin wrote:

Tanel Rebane wrote:

So, what format would you like the image in? VirtualBox or VMWare Workstation/Player?

Never used these, so I do not care.

martin wrote:

Tanel Rebane wrote:

I did notice it. At first I thought it wouldn't be applicable to my situation but having taken a closer look I think it could work well after finding a decent XML-parser. Any recommendations?

For what language?

Anonymous wrote:

martin wrote:

Tanel Rebane wrote:

So, what format would you like the image in? VirtualBox or VMWare Workstation/Player?

Never used these, so I do not care.

Do you have sufficient hardware to run virtual machines? Eg. 320MB (256MB for XP and 64MB for Debian) of usable RAM.

martin wrote:

Tanel Rebane wrote:

I did notice it. At first I thought it wouldn't be applicable to my situation but having taken a closer look I think it could work well after finding a decent XML-parser. Any recommendations?

For what language?

I was thinking of a native stand-alone Win-app.

martin wrote:

Anonymous wrote:

martin wrote:

Tanel Rebane wrote:

So, what format would you like the image in? VirtualBox or VMWare Workstation/Player?

Never used these, so I do not care.

Do you have sufficient hardware to run virtual machines? Eg. 320MB (256MB for XP and 64MB for Debian) of usable RAM.

Yes I do.

martin wrote:

Anonymous wrote:

martin wrote:

Tanel Rebane wrote:

I did notice it. At first I thought it wouldn't be applicable to my situation but having taken a closer look I think it could work well after finding a decent XML-parser. Any recommendations?

For what language?

I was thinking of a native stand-alone Win-app.

What should such application do?

Tanel wrote:

I saw your mail (received 2009-03-17) and replied (sent 2009-03-19). As I didn't get a reply back I send you a mail again (sent 2009-03-27). Did you ever get my mails? :)

martin wrote:

Tanel wrote:

I saw your mail (received 2009-03-17) and replied (sent 2009-03-19). As I didn't get a reply back I send you a mail again (sent 2009-03-27). Did you ever get my mails? :)

I have replied you on 2008-03-28. I'll do again.

Tanel wrote:

Still haven't gotten anything, how strange. Could you please forward all mails except the very first one to tanel .at. rebane .dot. se. Thanks! :)

martin wrote:

Did you get my emails?

martin wrote:

Tanel Rebane wrote:

I did notice it. At first I thought it wouldn't be applicable to my situation but having taken a closer look I think it could work well after finding a decent XML-parser. Any recommendations?

For what language?

I was thinking of a native stand-alone Win-app.