Hi Will--

Today, I downloaded THES4000.ZIP (THESEUS 4) from the OS/2 Shareware
BBS Web site. When I tried to run it, I got a pop-up error message
reading: "Initialization error: Global DosPerfSysCall fail. Check the t3errorlog.log for return code."

The t3errorlog.log file entry reads as follows:

Theseus4 error log opened at 16:07:41 on 6/9/2001.
comPerfSysCall - DosPerfSysCall error = 1
Call type 000000c0 with parms:
First parm = 00088a68 Second parm = 00000160, Third parm = 00000000.
Theseus4 error log closed at 16:07:54 on 6-9-2001.

I take this as an indication that it couldn't find some DLL that was needed. Interestingly, the "readme" told me to remove the device
driver used with THESEUS 3, and there was no indication of another to
install. Have you tried Theseus4? Any words of wisdom? There wasn't
any discussion of "errors" in the "documentation" :-(.

BTW, Pete has restored his FIDO feed, as of 6/8. However, still no
REXX echo and outgoing date lines still show 00:00 as the time stamp. He
says he is going to fix the date problems RSN :-).

Regards,

--Murray
<Team PL/I>
___
* MR/2 2.30 #120 * One printed manual is worth a thousand INF files

--- Maximus/2 3.01
* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)

Murray Lesser,

09-Jun-01 19:58:00, Murray Lesser wrote to Will Honea
Subject: Theseus 4

Today, I downloaded THES4000.ZIP (THESEUS 4) from the OS/2
Shareware BBS Web site. When I tried to run it, I got a pop-up
error message reading: "Initialization error: Global
DosPerfSysCall fail. Check the t3errorlog.log for return code."

Theseus 4000 will work correctly only with Convienence Packages.

Thanks and Good Luck, Andy Roberts
andy@shentel.net
--- Terminate 5.00/Pro*at
* Origin: OS/2 & Old age are better than the alternatives. (1:109/921.1)

Moin Murray!

09.06.2001, Murray Lesser wrote a message to Will Honea:

Today, I downloaded THES4000.ZIP (THESEUS 4) from the OS/2
Shareware BBS Web site. When I tried to run it, I got a pop-up error message reading: "Initialization error: Global DosPerfSysCall fail.
Check the t3errorlog.log for return code."

...

Do you run OS72 with any convience pack or eCS? Theseus4 requires it, if you use an older version stay at theseus3.

Bye,
Vitus

---
* Origin: "Windows NT Performance", on the next "In Search Of" (2:2474/424.1)

Lee ..

Today, I downloaded THES4000.ZIP (THESEUS 4) from the OS/2
Shareware BBS Web site. When I tried to run it, I got a pop-up
error message reading: "Initialization error: Global
DosPerfSysCall fail. Check the t3errorlog.log for return code."

Theseus 4000 will work correctly only with Convienence Packages.

And WSeB.

Anything that is built on the 4.5 kernel.

I thought Irv commented that 4000 works only on the 4.51 kernel. I thought I understood that FP 15 actually moved it all to the 4.50 kernel,technically, and
that only by going to MCP or ACP could you get the true 4.51 kernel. THES3 whatever sub version 5 sumpthing still works here with the FP 15 setup.

That was one of the things which I was confused about in relation to this whole
FP 15 / MCP deal.

It's behind the whole mess about not being able to upgrade to the new NS 4.61 that will, in theory, fix the open/close bug, together with the new actual kernel for 4.51, which is in the XR-C001 FP for MCP, but not at all for FP 15 boxes...

Thus, technically, FP 15 is, indeed a version of the 4.5 kernel, but, taken together with PMMERGE and lottsa other things, it isn't at all MCP ..

Or do I have it all still confused?


Mike @ 1:117/3001


--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)

Today, I downloaded THES4000.ZIP (THESEUS 4) from the OS/2
Shareware BBS Web site. When I tried to run it, I got a pop-up
error message reading: "Initialization error: Global
DosPerfSysCall fail. Check the t3errorlog.log for return code."

Theseus 4000 will work correctly only with Convienence Packages.

And WSeB.

Anything that is built on the 4.5 kernel.


LRA


-- SPEED 2.01 #2720: "It's a JOKE, son... a JOKE, ah say." - F. Leghorn

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Theseus 4000 will work correctly only with Convienence Packages.

And WSeB.

Anything that is built on the 4.5 kernel.

I thought Irv commented that 4000 works only on the 4.51 kernel. I thought

I
> understood that FP 15 actually moved it all to the 4.50
> kernel,technically, and that only by going to MCP or ACP
> could you get the true 4.51 kernel. THES3 whatever sub
> version 5 sumpthing still works here with the FP 15 setup.

That was one of the things which I was confused about in

> relation to this whole FP 15 / MCP deal.

It's behind the whole mess about not being able to upgrade to the new NS

4.61
> that will, in theory, fix the open/close bug, together with
> the new actual kernel for 4.51, which is in the XR-C001 FP
> for MCP, but not at all for FP 15 boxes...

Thus, technically, FP 15 is, indeed a version of the 4.5

> kernel, but, taken together with PMMERGE and lottsa other
> things, it isn't at all MCP ..

Or do I have it all still confused?

<LOL> !!

I'm not sure if there is actually any single human entity in
existence that groks the current state of the OS/2 kernel in it's
entirety, so don't feel bad about it...you ain't alone.

All I can tell you for sure is that Theseus 4 will NOT run on
anything under FP13, and that it will run under WSeB. Other than
plans to move my desktop to a dual 600 smp MB with WSeB, I'm
staying well away from the whole ACP/MCP/ECS mess until it gets
straightened out. My WSA and WSASMP servers are rock-solid
screamers and I see no reason to change them at this point.


LRA


-- SPEED 2.01 #2720: ** Where were you when your luck changed?

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Yes Lee..

I'm staying well away from the whole ACP/MCP/ECS mess until
it gets straightened out.

I'm trying, I'm trying!

Yet at the same time, you have to buy in to get the silly toolset, even though you do/don't want it, just to keep up with the bug reports!

This whole episode is, I think, running about true to form. It seems like every time a major shift takes place, it takes about a year for the thing to settle out.

The most important thing is that once it does we get solid stability in the OS/2 camp, relatively speaking, as opposed to a yet brand new mess every year that happens when one tries to wash windows.. ;)(;



Mike @ 1:117/3001


--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)

Yes Lee..

I'm staying well away from the whole ACP/MCP/ECS mess until
it gets straightened out.

I'm trying, I'm trying!

To be fair, ECS looks like a winner, and once they get their
current issues in hand, I'll probably be buying. They do seem to
be in it for the long run.

Yet at the same time, you have to buy in to get the silly

> toolset, even though you do/don't want it, just to keep up
> with the bug reports!

Who's making bug reports?

<BLAM>

Any more bug reports? <g>

This whole episode is, I think, running about true to form.

> It seems like every time a major shift takes place, it
> takes about a year for the thing to settle out.

Yup. The bleeding edge is just too...well, just too damned bloody
for me.

The most important thing is that once it does we get solid

> stability in the OS/2 camp, relatively speaking, as opposed
> to a yet brand new mess every year that happens when one
> tries to wash windows.. ;)(;

Fergit that "winders" noise. MonopolySoft's latest "offering" is
unbelievable in the level of hubris...snookering the lemmings
into yet ANOTHER "upgrade" round before they even have the first
fixpak out, AND making it a subscription scam, AND using it to
take over the digital media delivery industry AND the sheep still
bleet approval and nose up to the butt in front of em, cash in
hand, READY TO PAY TO BE SHEARED. Makes you despair for your
species, really it does...


LRA


-- SPEED 2.01 #2720: ... One tequila, two tequila, three tequila, floor....

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)