bugs.launchpad.net/sbcl/+bug/1971640

Preview meta tags from the bugs.launchpad.net website.

Linked Hostnames

13

Thumbnail

Search Engine Appearance

Google

https://bugs.launchpad.net/sbcl/+bug/1971640

Bug #1971640 “CancelWaitableTimer could not be located” : Bugs : SBCL

Starting SBCL.EXE on Windows 7-64 w/ESU fails and yields the error: The procedure entry point CancelWaitableTimer could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll This precludes the use of Maxima 5.46.0 (with SBCL 2.2.2?) and the current version 2.2.4. It appears that 2.0.0 is the last official Windows build that works. It is said by some that Windows 7 doesn't support this function, but according to MS it's been present since XP and is certainly present i...



Bing

Bug #1971640 “CancelWaitableTimer could not be located” : Bugs : SBCL

https://bugs.launchpad.net/sbcl/+bug/1971640

Starting SBCL.EXE on Windows 7-64 w/ESU fails and yields the error: The procedure entry point CancelWaitableTimer could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll This precludes the use of Maxima 5.46.0 (with SBCL 2.2.2?) and the current version 2.2.4. It appears that 2.0.0 is the last official Windows build that works. It is said by some that Windows 7 doesn't support this function, but according to MS it's been present since XP and is certainly present i...



DuckDuckGo

https://bugs.launchpad.net/sbcl/+bug/1971640

Bug #1971640 “CancelWaitableTimer could not be located” : Bugs : SBCL

Starting SBCL.EXE on Windows 7-64 w/ESU fails and yields the error: The procedure entry point CancelWaitableTimer could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll This precludes the use of Maxima 5.46.0 (with SBCL 2.2.2?) and the current version 2.2.4. It appears that 2.0.0 is the last official Windows build that works. It is said by some that Windows 7 doesn't support this function, but according to MS it's been present since XP and is certainly present i...

  • General Meta Tags

    6
    • title
      Bug #1971640 “CancelWaitableTimer could not be located” : Bugs : SBCL
    • charset
      UTF-8
    • msapplication-TileColor
      #da532c
    • msapplication-config
      /@@/browserconfig.xml?v=2022
    • theme-color
      #ffffff

  • Open Graph Meta Tags

    6
    • og:description
      Starting SBCL.EXE on Windows 7-64 w/ESU fails and yields the error: The procedure entry point CancelWaitableTimer could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll This precludes the use of Maxima 5.46.0 (with SBCL 2.2.2?) and the current version 2.2.4. It appears that 2.0.0 is the last official Windows build that works. It is said by some that Windows 7 doesn't support this function, but according to MS it's been present since XP and is certainly present i...
    • og:title
      Bug #1971640 “CancelWaitableTimer could not be located” : Bugs : SBCL
    • og:type
      website
    • og:image
      /@@/launchpad-og-image.png
    • og:url
      https://bugs.launchpad.net/bugs/1971640

  • Link Tags

    9
    • alternate
      http://feeds.launchpad.net/bugs/1971640/bug.atom
    • apple-touch-icon
      /@@/apple-touch-icon.png?v=2022
    • canonical
      https://bugs.launchpad.net/bugs/1971640
    • icon
      /@@/favicon-32x32.png?v=2022
    • icon
      /@@/favicon-16x16.png?v=2022

Links

36