Let me start by thanking you for the ongoing development of locate32. I have used it for an extremely long number of years and found it indispensible.
I have switched to Win10 recently and have found a number of issues specific to Win10.
1) When using locate32_3.1.11.8220a_fix.zip when I try to resize the Date Modifed column size Win10 says the program has stopped working and it closes. So I had to install an older version - locate32_x64-3.1.11.7100.zip and this works.
2) In Win10 (all versions of locate32) the file extension is stripped from the Name column in the search results. This has to be specific to Win10 since I tried the exact same version from WinXP on my Win10 PC and file extension is only stipped on Win10 search results. The WinXP PC shows the file extension correctly.
3) Please expand the initial default size of the Date Modified field. It truncates the full date/time and needs to be resized.
Thanks,
Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The development of Locate32 is unfortunately stopped, or at least by me. There is one other person who has done some minor changes but I cannot make promises for him (locate32_3.1.11.8220a_fix.zip is his build).
If 3.1.11.7100 works for you, you could use it (maybe take locate.exe from the 8220a package to fix a issue with it fixed in 8220a).
For the issue with the extension, have you checked settings? If I remember right, there is an option for that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I tried running the latest version 3 1 11 7100 on my windows10 Home, but a windows alert says this app is unable to run on your PC, please contact the maker (translation of the dutch text)
What can I do about this? I wouldn't like to miss Locate32!!!
thanks in advance,
Peter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was not able to reproduce this with Win 10 build 1809 & 1803 64 bit builds. Only on one Notebook with Win 10 1709, i have observed this. But on all colums, not only date column. I have build a debug version to get some more information and took the crash dump to my dev VM. Enclosed the windbg output. Sadly i have no idea how i can trigger this on actual build to investigate this in visual studio, its simply all working with Win10 2018 builds here.
How common it would be to have build 1709? Is there some reason not to update to the newest build? I am not very familiar with these. It might be something strange in Win32 API in Win10 (would not be first time), which is quite nasty to investigate. But would be fixed later
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was looking for another crash (but this one happens also with 7100) at actual build 1809 and looked here in the forum, if somebody was already struggled here and found this one. So i did check this on my company notebook with a 1709 release and i was only able to repoduce this at 1709. (IT departments needs often much more time for updates specially for theses updates for windows releases as a standard home user). Should be more or less an info that its ok at actual build.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm.. ok. but not sure what would the resolution here. At least I do not have resources to start solving this.
You could try to comment that "LRESULT lRes=DefSubclassProc(hwnd,uMsg,wParam,lParam);" line in the code. But that's not very optimal solution as it could have some even worse side effects.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Locate32 support forum" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hello,
Let me start by thanking you for the ongoing development of locate32. I have used it for an extremely long number of years and found it indispensible.
I have switched to Win10 recently and have found a number of issues specific to Win10.
1) When using locate32_3.1.11.8220a_fix.zip when I try to resize the Date Modifed column size Win10 says the program has stopped working and it closes. So I had to install an older version - locate32_x64-3.1.11.7100.zip and this works.
2) In Win10 (all versions of locate32) the file extension is stripped from the Name column in the search results. This has to be specific to Win10 since I tried the exact same version from WinXP on my Win10 PC and file extension is only stipped on Win10 search results. The WinXP PC shows the file extension correctly.
3) Please expand the initial default size of the Date Modified field. It truncates the full date/time and needs to be resized.
Thanks,
Paul
Hi,
The development of Locate32 is unfortunately stopped, or at least by me. There is one other person who has done some minor changes but I cannot make promises for him (locate32_3.1.11.8220a_fix.zip is his build).
If 3.1.11.7100 works for you, you could use it (maybe take locate.exe from the 8220a package to fix a issue with it fixed in 8220a).
For the issue with the extension, have you checked settings? If I remember right, there is an option for that.
View and moderate all "Locate32 support forum" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Thanks for the reply.
Yes, I found the option in the settings area to show the file extension. I must admit I forgot to check there prior to posting.
Thanks,
Paul
View and moderate all "Locate32 support forum" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hello, I tried running the latest version 3 1 11 7100 on my windows10 Home, but a windows alert says
this app is unable to run on your PC, please contact the maker(translation of the dutch text)What can I do about this? I wouldn't like to miss Locate32!!!
thanks in advance,
Peter
I haven't touched Win10, but sounds like a error message you will be given if you run 64bit code in 32bit system.
Try if either of these would work:
http://locate32.cogit.net/download/locate32-3.1.11.7100.zip (32bit)
http://locate32.cogit.net/download/locate32_x64-3.1.11.7100.zip (64bit)
Is there any better similar software? Where else to go, if we have to?
I've been using Locate32 pretty much forever.
Much better:
Everything
A Windows 10 compatible download (binaries):
https://github.com/eladkarako/mods/tree/master/Locate32
also, portable.
Read instructions on the page.
This link is not working for me.
I was not able to reproduce this with Win 10 build 1809 & 1803 64 bit builds. Only on one Notebook with Win 10 1709, i have observed this. But on all colums, not only date column. I have build a debug version to get some more information and took the crash dump to my dev VM. Enclosed the windbg output. Sadly i have no idea how i can trigger this on actual build to investigate this in visual studio, its simply all working with Win10 2018 builds here.
How common it would be to have build 1709? Is there some reason not to update to the newest build? I am not very familiar with these. It might be something strange in Win32 API in Win10 (would not be first time), which is quite nasty to investigate. But would be fixed later
I was looking for another crash (but this one happens also with 7100) at actual build 1809 and looked here in the forum, if somebody was already struggled here and found this one. So i did check this on my company notebook with a 1709 release and i was only able to repoduce this at 1709. (IT departments needs often much more time for updates specially for theses updates for windows releases as a standard home user). Should be more or less an info that its ok at actual build.
Hmm.. ok. but not sure what would the resolution here. At least I do not have resources to start solving this.
You could try to comment that "LRESULT lRes=DefSubclassProc(hwnd,uMsg,wParam,lParam);" line in the code. But that's not very optimal solution as it could have some even worse side effects.