I might have give you info that's not relevant to your current task. Please let me know. One last thing We'd have to crack open the exe to know for sure, but it's probably just the way path recognition is coded internally.
Something about those paths or their encoding is failing to parse correctly with the logic coded in. Different paths and encoding were used back in the day, it shouldn't be that surprising to see gremlins.
I don't want to even begin speculating the effort it took to bring the old NT 4. To continue this discussion, please ask a new question. I will happy to give you more details if you require. Thanks, Rajesh. Wednesday, January 20, AM. Your code has a manifest that specifies the version s of the runtime that it requires. If you install a lower version of the runtime your program won't work. Phil Wilson. Wednesday, January 20, PM. I think this might help. Thursday, January 28, PM. If you install the VCRedist-x86 for VS it should work, assuming of course that those 3rd party Dlls etc have their own dependencies installed.
All systems are different with different sets of Dlls installed, so it shouldn't be a surprise if it works on some systems and not others. Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations. If you're not already familiar with forums, watch our Welcome Guide to get started.
Join over , other people just like you! Forums New posts Search forums. What's new New posts Unanswered threads Latest activity. Members Current visitors. Log in Sign up. Search titles only.
Search Advanced search…. New posts. Search forums. The manifest contains metadata that describes assembly dependencies of the executable. Every dependent assembly has a unique identity. This time, when I run the jsl -debug command I get this message: "The system cannot execute the specified program". Are you using the 32 or 64 bit version of jsl? Thanks in advance nevermind, it's fixed now. Sign up for Free! Read these next
0コメント