Access violation when calling synchronization tool in separate process
Moderators: Hacker, petermad, Stefan2, white
Access violation when calling synchronization tool in separate process
Hi,
up to version 9.20, the synchronization tool could be started in a separate process. Since version 9.21 you get an intercepted access violation. I start it with a button in the button bar.
Command: C:\TotalCmd\TOTALCMD64.EXE
Parameters: /S=S "%X%P" "%X%T"
The following window appears immediately:
https://xqxaja.bn.files.1drv.com/y4m_KMnh1NauwDNSLyNM25dAopk7wwcWEuUgNJFmHXBFTU_7zQooe5QkmMvEDPhIqXeDMM97RkYTRZ2Dw0vijWkW1ortVM-pzsH2I-pKT5RJIrJZo1rxavId8Q ... lation.png
The cm_FileSync command works.
Best regards
up to version 9.20, the synchronization tool could be started in a separate process. Since version 9.21 you get an intercepted access violation. I start it with a button in the button bar.
Command: C:\TotalCmd\TOTALCMD64.EXE
Parameters: /S=S "%X%P" "%X%T"
The following window appears immediately:
https://xqxaja.bn.files.1drv.com/y4m_KMnh1NauwDNSLyNM25dAopk7wwcWEuUgNJFmHXBFTU_7zQooe5QkmMvEDPhIqXeDMM97RkYTRZ2Dw0vijWkW1ortVM-pzsH2I-pKT5RJIrJZo1rxavId8Q ... lation.png
The cm_FileSync command works.
Best regards
Re: Access violation when calling synchronization tool in separate process
No confirmed here.
I do this many times and it still works in the actual TC (x86 and x64) without any problems.
May be you have some special dirs the parameters are pointing to ?
I do this many times and it still works in the actual TC (x86 and x64) without any problems.
May be you have some special dirs the parameters are pointing to ?
Windows 11 Home, Version 24H2 (OS Build 26100.4061)
TC 11.55 RC2 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.4 x64
TC 11.55 RC2 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.4 x64
Re: Access violation when calling synchronization tool in separate process
I just noticed that I only have this problem under Windows 8.1 Home 64bit, not under Windows 10 Pro 64bit.
It doesn't matter which directories I compare.
It doesn't matter which directories I compare.
Re: Access violation when calling synchronization tool in separate process
A good reason to update to Windows 10Lolly-Bob wrote: 2018-08-29, 19:45 UTC I just noticed that I only have this problem under Windows 8.1 Home 64bit, not under Windows 10 Pro 64bit.
It doesn't matter which directories I compare.

Its still for free and much better as 8.1
May be Christian has some idea.
Windows 11 Home, Version 24H2 (OS Build 26100.4061)
TC 11.55 RC2 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.4 x64
TC 11.55 RC2 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.4 x64
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Re: Access violation when calling synchronization tool in separate process
Thanks for your report. It's caused by the "prevent scrollbar crash" function, which should prevent another crash from happening on Windows 8.1.
You can disable this:
wincmd.ini, under [Configuration], please add:
PreventScrollbarCrash=0
However, Lister will crash again after calling it a few times when you set this.
Solution: Make a copy of your wincmd.ini, e.g. named synctool.ini, put PreventScrollbarCrash=0 only in that copy, and then start the standalone sync tool like this:
totalcmd64.exe /S=S /i=c:\totalcmd\synctool.ini "%X%P" "%X%T"
You can disable this:
wincmd.ini, under [Configuration], please add:
PreventScrollbarCrash=0
However, Lister will crash again after calling it a few times when you set this.
Solution: Make a copy of your wincmd.ini, e.g. named synctool.ini, put PreventScrollbarCrash=0 only in that copy, and then start the standalone sync tool like this:
totalcmd64.exe /S=S /i=c:\totalcmd\synctool.ini "%X%P" "%X%T"
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Re: Access violation when calling synchronization tool in separate process
Thank you very much. It works.
Re: Access violation when calling synchronization tool in separate process
2Lolly-Bob
You don't have to repeat %X - /S=S %X "%P" "%T" will do the same
Command: C:\TotalCmd\TOTALCMD64.EXE
Parameters: /S=S "%X%P" "%X%T"
You don't have to repeat %X - /S=S %X "%P" "%T" will do the same
and it is cancelled again with:Help wrote:%X Interprets the following parameters after this parameter as left/right instead of source/target:
HElp wrote:%x Interprets the following parameters after this parameter again as source/target
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Re: Access violation when calling synchronization tool in separate process
Thank you, petermad, good to know.
Re: Access violation when calling synchronization tool in separate process
This issue could not be a reason to update.
Access violation occurs in Windows Server 2016, TC 9.21a.
If Ok button was pressed, the same dialog appears again, and next Ok causes crash.
Re: Access violation when calling synchronization tool in separate process
You didn't mention Windows Server 2016 until this newest post
You said "I just noticed that I only have this problem under Windows 8.1 Home 64bit"
And this is definitely a reason to update to Windows 10 as long as it is free.
Windows 11 Home, Version 24H2 (OS Build 26100.4061)
TC 11.55 RC2 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.4 x64
TC 11.55 RC2 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.4 x64
Re: Access violation when calling synchronization tool in separate process
You mix something up, Horst.Epp. I'm Lolly-Bob, the initiator of this thread, but browny talked about Windows Server 2016.Horst.Epp wrote: 2018-09-04, 09:59 UTC You didn't mention Windows Server 2016 until this newest post
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Re: Access violation when calling synchronization tool in separate process
This should be fixed in Total Commander 9.22 rc1 even with PreventScrollbarCrash=1 now. Please test!
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Re: Access violation when calling synchronization tool in separate process
The 9.22 rc1 x64 Version works on Windows 8.1 Home 64-bit. I can start the synchronization tool with or without PreventScrollbarCrash is set. But I don't know the lister scrollbar problem. I didn't had this problem.
Thank you.
Thank you.