T.R | Title | User | Personal Name | Date | Lines |
---|
3292.1 | | MRPTH1::16.121.160.237::slab | [email protected] | Thu May 22 1997 00:15 | 4 |
|
It would have made much more sense to REPLY to note 2851 than
to WRITE a new note, yes?
|
3292.2 | not necessarily | NNTPD::"[email protected]" | John Plessas | Thu May 22 1997 09:28 | 2 |
| 2851 went off on a completely different tangent not related to SDK.
[Posted by WWW Notes gateway]
|
3292.3 | Let's leave it here. | PEACHS::GHEFF | Do you feel like swimming? | Thu May 22 1997 10:55 | 33 |
| Perhaps a note with a more meaningful title is the place to talk about
this. For the sake of completeness, I'll include the setup
instructions for the SDK on NT 4. Then I'll make some comments in the
next reply.
<<< NOTED::NOTES$7:[NOTES$LIBRARY]EXCURSION.NOTE;3 >>>
-< note 3 has pointer to current kit >-
================================================================================
Note 2851.6 NT V4.0 problems 6 of 15
LJSRV1::BOURQUARD "Deb" 21 lines 28-MAR-1996 16:58
--------------------------------------------------------------------------------
You could work around this by copying files by hand, but I
I believe you'd have to enter some registry info by hand as
well. In the registry you'll need:
Note that spaces (or lack thereof) and capitalization is quite
important.
key:
HKEY_LOCAL_MACHINE\SOFTWARE\DigitalEquipmentCorporation\eXcurion SDK
value:
InstalledPath: D:\dxsdk
I'll mail you a directory listing of d:\dxsdk tree.
(It's a bit long to post here).
What you won't get:
you won't get the rexec service installed.
you won't get a program group with program icons
|
3292.4 | Fair Warning | PEACHS::GHEFF | Do you feel like swimming? | Thu May 22 1997 11:33 | 31 |
| First let me say that I doubt that there's anyone around who knows much
about the SDK anymore. At least from the engineering perspective. I
look at it from the support angle and I'm probably one of the few left
who knows anything about it at all.
The last time I did anything meaningful with the SDK was shortly after
I upgraded my system from NT 3.51 to 4.0 and the SDK came along for the
ride. So I cannot say that I have even tried to install it on NT 4.0.
(The call volume on the SDK has become vanishingly small, so to this
point there hasn't been a compelling reason for me to have it installed
anywhere.)
In addition to the problems with NT itself, there's also the issue of
MSVC versions. SDK was built with MSVC++ 2.x. I have gotten report or
two of problems when using the libraries with MSVC 4.x. (One user
reported serious problems when debugging.) I do not have data on
whether or not 2.x runs on NT 4.0. And I do not have any data on how
well the SDK does with MSVC 5.x. I can say that I ran with MSVC 4.x on
NT 4 and the SDK behaved okay for me. (But I must say that my usage was
limited to number of small x apps. No big projects.)
I post this here as a way of warning would-be SDK users. It may be
more trouble than it's worth and if you really need this functionality
you might be better off looking into something like Hummingbird's XDK.
<http://www.hummingbird.com/products/exceed/exceedxdk.htm> (Though it
is interesting to note that this page makes no direct mention of NT 4
either. ;-) It really pains me to say this because practically all
the customers I dealt with regarding the eXcursion SDK told me that the
it was much easier to use than the XDK. Sigh.
#Gary
|