Hi Bob Glad you sorted it out. What can I say, 'Windows happens'...or sometimes doesn't! :)
Are you doing your C programming and UniVerse GCI testing on the same (ie. your own) desktop PC? Are you using Visual Studio on this same PC? Just curious...which version and did you upgrade from an older version? Perhaps that's the culprit? BTW: Check, in your UV account, in APP.PROGS: GCI.MAKEFILE (also GEN.GCI if you're curious how they interface your GCI routine to UV) Regards, David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Little Sent: Saturday, 8 November 2008 3:42 PM To: [email protected] Subject: {Blocked Content} RE: [U2] Need help with GCI system (solved) Warning: This message has had one or more attachments removed Warning: (not named). Warning: Please read the "AngelicHost-Attachment-Warning.txt" attachment(s) for more information. Hi Jerry I finally (about 2-minutes before quittin' time today) got this figured out - or at least a temporary work-around. Actually David Hona said something that got me to approach this problem from a different direction. "A Windows error 126 means missing file or registry entry is invalid" - and he was right on the money really. For web-search posterity's sake - here's how I got things to work. The problem stemmed from the fact that Windows (Not UniVerse) could not load the msvcr90.dll. I'm a little unclear at this point why not - it has to do with a dll manifest not existing in the dll or that Windows is trying to load "new style" dll along side of "old style" dlls. As I say, I'm unsure at this stage just what the crux of the biscuit is, but I'll find out more in the next day or so. Anyway, I had to forego the UV GCI.ADMIN method, and do the build and install manually from the "DOS" command line. First I captured the the compile and link command output and saved them to a text file so that I could study all the various switches. Then, I modified the switches to fit my version of the the Windows SDK. Next I modified the link command switches to do static linking against the msvc90.dll. The resulting dll is or course larger than the dynamically linked one, but when I installed it into the bin directory, everything worked as advertised. The key to the work-around is to statically link everything together. Next step for me is to figure out how to flip the right compiler/linker switches to get dynamic linking to work. Then I need to figure out what to modify in UniVerse that's sending the undesired macros and CLI switches to DOS so that I can change them. This whole GCI thing is sorta useless unless someone else less "competent" then I (I say laughingly) can do the build and install using UV's built-in methodolgy. Thank you everyone for your input. I never would figured it otherwise. -bob ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
