TC 8.0b3, creating directory bug
Moderators: Hacker, petermad, Stefan2, white
TC 8.0b3, creating directory bug
I was trying to create new directory with F7, and this window appeared:
---------------------------
Total Commander 8.0ß3
---------------------------
Access violation.
Access violation
Windows 7 SP1 6.1 (Build 7601)
Please report this error to the Author, with a description
of what you were doing when this error occurred!
Stack trace (x64):43B222
43B380 436D85 436C26 434F41 7ACF69 7C415D 7C1745 434EDE
4395CF 520F88 51FACC 51FD92 6914E1 69C516 68A1B2 7B1737
Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Yes No
---------------------------
---------------------------
Total Commander 8.0ß3
---------------------------
Access violation.
Access violation
Windows 7 SP1 6.1 (Build 7601)
Please report this error to the Author, with a description
of what you were doing when this error occurred!
Stack trace (x64):43B222
43B380 436D85 436C26 434F41 7ACF69 7C415D 7C1745 434EDE
4395CF 520F88 51FACC 51FD92 6914E1 69C516 68A1B2 7B1737
Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Yes No
---------------------------
Well, version of windows is written in bug report, also the version of beta TC, and if I wanted to create directory on CD drive, I wouldn't be able to post bug report in appropriate forum, now, would I?Sir_SiLvA wrote:According to my glassball you have win 7 64bit and are using TC8 64Bit and tried to create a new folder on a cd drive wich cant work ofc

Everything is standard - drive is NTFS formatted, NOT EXT4 or something more exotic, like FFS/DC. I do have all rights to write on it, and all the subfolders. I ruled out user error, and I've got this error twice in few hours. If the error is pressing F7 to create directory, then I am guilty as charged...
- ghisler(Author)
- Site Admin
- Posts: 50479
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
This is a strange bug, it happens in Windows function GetMonitorInfo, which TC uses to avoid that a dialog is shown outside of the current monitor.
Do you get this every time, or only after certain other operations?
2Valentino
Yes, it's the same problem, it's called for all dialogs which are centered over the main or parent form...
Do you get this every time, or only after certain other operations?
2Valentino
Yes, it's the same problem, it's called for all dialogs which are centered over the main or parent form...
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
GetMonitorInfo receives two arguments: HMONITOR and LPMONITORINFO.
In my case I was using remote desktop, so probably monitor handle that you supply to the function becomes invalid in scope of remote desktop session?
Another potential reason is wrong pointer to MONITORINFO(EX), or uninitialized cbSize.
In my case I was using remote desktop, so probably monitor handle that you supply to the function becomes invalid in scope of remote desktop session?
Another potential reason is wrong pointer to MONITORINFO(EX), or uninitialized cbSize.
- ghisler(Author)
- Site Admin
- Posts: 50479
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
It seems that Lazarus sometimes returns null for Screen.ActiveCustomForm.Monitor or Application.MainForm.Monitor, no idea why. I will catch it.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50479
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
- ghisler(Author)
- Site Admin
- Posts: 50479
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact: