As some of you have already noticed, the new COM automation features in KiXtart 2001 require (D)COM 1.2 or higher. What this means is that the current implementation of KiXtart 2001 runs *only* on the following Windows versions:

Windows 95 *NOTE* requires separate install of DCOM 1.2 or higher.
Windows 98
Windows Millenium
Windows NT 4.0 Service Pack 4 or higher
Windows 2000
Windows XP

In other words, Windows NT 3.1, Windows NT 3.51, Windows NT 4.0 Service Pack 1 through 3 and Windows 95 without DCOM are no longer supported.

I could invest time in trying to remove the dependency on DCOM 1.2, but it will require quite some effort.

My question to you is: would this be worth my time (and if so, should I delay the release of 2001, or postpone this work until after the release of 2001)?

Many thanks in advance for your thoughts on this!

--Ruud

in other words, I'll not migrate to 4.00 if it does not run on win9x's and I still have them. (still doing win9x-never-again! killing project.)

anyways, it's not huge loss, but some workers do not like it, you know.

from my point of view : Go ahead !!!

(what the H*** is Windows 95 , NT 3.51 , NT 4 < SP4 ? )

Cheers
Jochen

_________________________

It is 800+ of our client base. I'm with Lonkero, does it run as long as you don't call any COM calls? If not then I will stick with v3.63 apparently for some time. These machines are not scheduled for replacement due to budget for the next year.

so there are Companies out there that have 95 running (I didn't considered that !)

Hmmm ... what are the risks and expenses to install a newer Version of DCOM to them ?

Jochen

_________________________

KiXtart 2001 will not even start on NT4 SP3. It complains about a missing ordinal (159) in OLEAUT32.DLL. I'm doing some further testing (for my own benefit) to get a work-around - I have a feeling (and this is what I'm testing) that IE5 fixes the problem. What I do know for sure is if you install the latest VB6 runtimes (FREE from MS) - OLEAUT32.DLL gets upgraded to OLE 1.2 (and beyond) and all is well.

-Shawn

My vote (suggestion) right now is to release as is - and address the issue in a future release - most folks are well beyond SP3 by now -

[ 20 July 2001: Message edited by: Shawn ]

-Shawn

Thanks... That sounds great. We pushed out IE 5 earlier this year. All but a few clients have IE 5 to 5.5

Here is a sampling of our clients in one location:

code:

---

Windows ME	15
Windows 95	6
Windows 95a	42
Windows 95b	419
Windows 95c	5
Windows 98	362
Windows 98a SE	217
Windows NT 4.0 SP1	1
Windows NT 4.0 SP3	108
Windows NT 4.0 SP4	59
Windows NT 4.0 SP5	107
Windows NT 4.0 SP6	601
Windows 2000 Pro	78
Windows 2000 Pro SP1	232
Windows 2000 Pro SP2	35
Windows XP	6
  

---

Plus Unix, Linux, and Macs

OH MY GOD - I think the question should be "what don't you have ?" - Is anyone really using the single NT SP1 box there ?

How do you manage that lot ? I hope they pay you loads of money because you're GOOD !

Would you be willing to test RC1 on those Win95 variants and NT<4 boxes of yours ? We'd all like to know and I'm sure Ruud would be very interested as well (?)

-Shawn

[ 21 July 2001: Message edited by: Shawn ]

Because the current public release KiXtart 2001 - 4.00 rc 1 (build 45)
doesn't have any major problem: we suggest to publish it first a final
version.

For people who are really need to install DCOM it can't be hard to do
that. On the board there are an enormous amount of dicussions about
upgrading kixtart files on clients to, but we are glad that we can
use our iexpress packages to do that on a clear and simple way.

The most interesting thing of kixtart was (and can be): you don't
really need additional software for running a script. No additional
software means for us: you are not changing the current configuration
of a workstation of server.
Greetings.

btw:
we think that the KiXtart population have a lot of interest for what
the other to-do things for a new release will be.
please can you tell us about it.

Take a break... Your supposed to be on vacation.

I think KiXtart has become a WORK-A-HOLIC disease for you

But I'm glad you are on this board and do have such dedication and drive to help others.

Indeed we try to start our vacation last week, but it wasn't possible
to leave. What is some days when you are gone for about two months.

During this weekend it is also not the right moment in Europe to travel.
Extreme amount of holidaymakers are on the road and you see more cars
around you then you wanted and your distance in one day is very low.
In Europe we had during the summar always "black saturday" and "black
sunday" moments, which means: a lot of traffic, accidents and don't
get the feeling you are on holidays.

We know that during the coming months you and other members must
miss on the board and we are glad that some significant "problems"
has been fixed at the end (some of them: new links to the topics
on the board, the minor problem with the operators * and
/ which influence kixstrip tool).

At the moment we look for the latest response to our
input of topics related to our tools.
Greetings.

I would like to test, but since the files in KiXtart 2001 have the same name, I have no way to separate them out from the release version. I can't run beta sotware in our environment with out envoking the wrath of Management. I could probably rename the KIX32.EXE file for NT/2000 boxes, but my guess is that if I rename the *.DLL files for the Win9x they won't work right.

Although Ruud hasn't officially stated his intentions - reading between the lines (here and there) I'm betting the house that he's going to hold back and delay the release of KiXtart 2001 (and fix the OLE dependency) ... Ruud ?

-Shawn