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. MFC app failure to boot up in Windows XP

MFC app failure to boot up in Windows XP

Scheduled Pinned Locked Moved C / C++ / MFC
c++helpdiscussion
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.
  • D Offline
    D Offline
    D_code_writer
    wrote on last edited by
    #1

    Hey Guys, I'm looking for a bit of guidance on an intermittant crashing issue I'm having with WindowsXP. I have an MFC based SDI app that loads a dll, but apart from that its pretty bog standard. It was written using Visual C++ 6.0. Anyway very occassionally on some machines running WindowsXP the app won't even boot up. I'm fairly sure the failure is due to the fact that ProcessShellCommand must be returning false. However I could be jumping to conclusions, it may be a dodgy install shield. Would any one have any thoughts or guidance on this issue. Best Regards Danny Nowlan

    B 1 Reply Last reply
    0
    • D D_code_writer

      Hey Guys, I'm looking for a bit of guidance on an intermittant crashing issue I'm having with WindowsXP. I have an MFC based SDI app that loads a dll, but apart from that its pretty bog standard. It was written using Visual C++ 6.0. Anyway very occassionally on some machines running WindowsXP the app won't even boot up. I'm fairly sure the failure is due to the fact that ProcessShellCommand must be returning false. However I could be jumping to conclusions, it may be a dodgy install shield. Would any one have any thoughts or guidance on this issue. Best Regards Danny Nowlan

      B Offline
      B Offline
      Blake Miller
      wrote on last edited by
      #2

      Okay, 'fail to boot up' would imply what? Not even RUN at all? Of course, if you even suspect your program is starting okay, then add more of your own error handling to the application and maybe write to a text log file only when something is wrong. Then your customers could send this file to you when your app will not 'boot up' on their machines. It IS entirely likely you are at least getting into WinMain unless a critical statically linked DLL is missing, in which case Windows would normally tell you that a required DLL is missing. I suspect, as do you, that some part of your framework or app path is failing, but there is no visible external notification. You need to bring that out, either with message boxes or with text file logging. I usually favor the text file logging, as the user does not have to retype or 'interpret' anything. They can usually e-mail you a text file.

      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