Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Loadstring Fails on Win98

Loadstring Fails on Win98

Scheduled Pinned Locked Moved C / C++ / MFC
c++helptutorial
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    Lea Johnson
    wrote on last edited by
    #1

    Dear All, I have developed an application with VC++6sp4 on WinNT4sp6 and everything is fine and dandy. The big problem occurs when I compile the same code on a Win98 machine. All calls to Loadstring fail returning an empty string. :mad: I was wondering if anyone else has experienced this behaviour, and if so how to go about fixing it Thanks inadvance Lea

    M 1 Reply Last reply
    0
    • L Lea Johnson

      Dear All, I have developed an application with VC++6sp4 on WinNT4sp6 and everything is fine and dandy. The big problem occurs when I compile the same code on a Win98 machine. All calls to Loadstring fail returning an empty string. :mad: I was wondering if anyone else has experienced this behaviour, and if so how to go about fixing it Thanks inadvance Lea

      M Offline
      M Offline
      Matt W
      wrote on last edited by
      #2

      Lea, can't say I've ever had this problem. I presume you are refering to the WIN32 API version of LoadString? Looking at it in the MSDN my first guess was that maybe you are having buffer problems, NT being UNICODE and Win98 being...well what is it exactly? ;) (sorry that was not very helpfull was it). My advice is to try using the API call GetLastError(), which will return you an error code (that may have been set by the LoadString call). There is an error list in the MSDN some where which will help you decipher what the error code means. Accept that some days you are the pigeon and some days the statue.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups