View previous topic :: View next topic |
Author |
Message |
wahorger
Joined: 13 Oct 2014 Posts: 1217 Location: Morrison, CO, USA
|
Posted: Tue Jun 21, 2016 3:16 pm Post subject: Newly compiled and linked SW will not run on Windows 2000 |
|
|
This is occurring after installing under Windows 2000.
Under Windows 10, I downloaded the latest version, rebuilt the SW from scratch, and created my standard SETUP file just like always. However, now, I get an error that the procedure entry point GetModuleHandleExA cannot be found in KERNEL32.DLL.
Under Windows 10 on the development computer, this runs fine. I don't have another computer that is "pristine" on which to try this.
I'm wondering if I'm missing including some DLL(s). In the SETUP process, I include, from the ./redist folder, salflibc.dll and Salford.VisualClearWin.dll.
Thanks,
Bill |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7924 Location: Salford, UK
|
Posted: Tue Jun 21, 2016 5:11 pm Post subject: |
|
|
GetModuleHandleEx is not provided under Windows 2000. If you search the Internet then you may be able to find a work-around. |
|
Back to top |
|
|
wahorger
Joined: 13 Oct 2014 Posts: 1217 Location: Morrison, CO, USA
|
Posted: Tue Jun 21, 2016 6:40 pm Post subject: |
|
|
Thanks, Paul! |
|
Back to top |
|
|
wahorger
Joined: 13 Oct 2014 Posts: 1217 Location: Morrison, CO, USA
|
Posted: Tue Jun 21, 2016 9:34 pm Post subject: |
|
|
Just so we are clear.
Compiling and linking with V8.00 started this problem (just tested that on Windows 2K); compiling and linking with V7.2 did not have this problem.
There must be something different in how V8 and V7 start up to cause this. I have searched my code, and I don't have any calls to GetModuleHandleExA. It must be in the Salford startup (because my code never starts!)
Bill |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7924 Location: Salford, UK
|
Posted: Wed Jun 22, 2016 7:01 am Post subject: |
|
|
Bill
I have checked this out. There is a change in salflibc.dll that can be fixed.
Please let me know if this is critical for you. I should be able to provide a new salflibc.dll after the impending release. |
|
Back to top |
|
|
wahorger
Joined: 13 Oct 2014 Posts: 1217 Location: Morrison, CO, USA
|
Posted: Wed Jun 22, 2016 1:37 pm Post subject: |
|
|
Thanks, Paul. That is a very generous offer.
I have contacted my users to see what platform they are using, specifically Windows 2000. I should know for sure in a few days, at least by Monday evening (27 June).
I have had a couple of them move off of old platforms specifically to use the newer product made possible by FTN95. So I am encouraged that they will all say this is not an issue.
I'll post a reply here on Monday evening (UTC-6) and confirm.
Thank you for your willingness to accommodate! |
|
Back to top |
|
|
wahorger
Joined: 13 Oct 2014 Posts: 1217 Location: Morrison, CO, USA
|
Posted: Tue Jun 28, 2016 1:29 am Post subject: |
|
|
Having heard nothing from the users, I think it's safe to let this sleeping dog lie.
I firmly believe that they should ALL have updated to at least Windows XP by now. This may force their hand and will actually make life easier for me!
Thanks, Paul! |
|
Back to top |
|
|
|