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


________________________________

From: [EMAIL PROTECTED] on behalf of jpb-u2ug
Sent: Fri 11/7/2008 2:52 PM
To: [email protected]
Subject: RE: {Blocked Content} RE: [U2] Need help with GCI system



Are you doing this as the administrator or as a common user?

Jerry Banker

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Little
Sent: Friday, November 07, 2008 7:54 AM
To: [email protected]
Subject: RE: {Blocked Content} RE: [U2] Need help with GCI system

Hi David,

Yeah - I've done make, install, make, install, make install so many times in
the last few days, I think I can do it in my sleep.  :)  Luckily I am not on a
production box.

You mention the registry entry, but that gets updated when you do the
"install", and currently says UvGciLibraries bin\magci.dll;bin\gci.dll.

I've done the environment variable thingie too, and it didn't seem to make a
difference.

So... I don' know.

I'm waiting on a reply from the VAR but I aint holding my breath their gonna
be of any help.

-bob

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hona, David S
Sent: Friday, November 07, 2008 3:14 AM
To: [email protected]
Subject: RE: {Blocked Content} RE: [U2] Need help with GCI system

Hi Bob,

Ah, forgot to ask the obvious, does this file exist:
e:\IBM\UV\bin\magci.dll

As Windows error 126 means missing file or registry entry is invalid.

I see you said you ran "Make a GCI Library from a GCI Definition File"
from the GCI Admin menu.

I don't see you saying you ran "Install a GCI Library" from the GCI
Admin menu.

Quote:

"This option does the following:

- Copies the DLL file from the gcidir directory to the bin directory in
the UV account directory
- Adds the name of the copied file to the GCI library list held in the
Windows Registry

The DLL is now ready for use."

Note it also states you can use the UVGCIDLLS variable to test your DLL,
before committing to updating your UV GCI configuration. Probably a wise
thing to do in a production or live environment! :)

Regards,
David


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Little
Sent: Friday, 7 November 2008 1:41 PM
To: [email protected]
Subject: {Blocked Content} RE: [U2] Need help with GCI system

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.

________________________________

From: [EMAIL PROTECTED] on behalf of Hona, David S
Sent: Thu 11/6/2008 7:53 PM
To: [email protected]
Subject: RE: [U2] Need help with GCI system

Isn't your module called "magci" and not "test"? As your error indicates
it's looking for "TEST" in your GCI library. From the GCI documentation:

Hi Davd,


Thanks for the reply.

The library is indeed called test.lib built from test.c/test.obj.  In it
is
the function "getSum()" I am trying to integrate.  The GCI definition
file
I've created on UV is called MAGCI.  UniVerse creates all the magci.*
items in
the gcidir when I take GCI.ADMIN menu option "5. Make a GCI Library from
a GCI
Definition File".

The way I thought it worked was:
The subroutine visible to UV would be getSum and the external subroutine
name
is the same and the module (.lib) is test because the function is in
test.lib.

What's odd is that the *hello example and it's accompanying BP GCI1
calling
program don't run either.   I'm using straight out of the box IBM
examples and
using the default GCI definition file: GCI.

-bob
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "winmail.dat"
was believed to be infected by a virus and has been replaced by this
warning
message.

If you wish to receive a copy of the *infected* attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Thu Nov  6 18:40:48 2008 the virus scanner said:
   Could not parse Outlook Rich Text attachment

Note to Help Desk: Look on the AngelicHost MailScanner in
/home/virtual/site2/fst/var/spool/mail.quarantine/20081106 (message
mA72ejno008182).
--
Postmaster
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "winmail.dat"
was believed to be infected by a virus and has been replaced by this warning
message.

If you wish to receive a copy of the *infected* attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Fri Nov  7 20:41:49 2008 the virus scanner said:
   Could not parse Outlook Rich Text attachment

Note to Help Desk: Look on the AngelicHost MailScanner in
/home/virtual/site2/fst/var/spool/mail.quarantine/20081107 (message
mA84fi2t005332).
--
Postmaster
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to