i am using slist v2.03 with openinsight v3.7 on a win2000 system on a nt server platform.

when i go into slist, at the "sentence" prompt if i try to execute a listing, i get the following exception error:

ntvdm.exe

access violation 0xc0000005

exception address 0x00610069

what i have done in the past to resolve this, was in openinsight i went into:

database manager

database

environment settings

removed the "sort path"

whether this actually did anything i do not know, if theory, i don't that it should have, but we no longer got the exception error.

this system was recently upgraded to win2000 from nt v4.0 and now it is causing the same problem as before. removing the sort path this time has no effect.

any ideas?

stacy mecklenberg

forerunner systems, inc.

email: stacy@forerunnersystems.com

voice: 415.332.4032

fax: 415.332.9170

The NTVDM crashing seems like a memory problem. We're just getting ready to do wide ranging Windows 2000 installations at the office (though we might wait for the first patch) so we'll do heavy testing then. We have access to a few machines now so we'll see what we can find.

Since it's memory crashing, I'd like us to be on the same versions, so if you could upgrade, that would help. I know, the first resort of the clueless is upgrade.

You also might want to run OI in a seperate session in case there is a memory leak problem.

The Sprezzatura Group

World leaders in all things RevSoft

memory leakage would be nothing new to an rti product. i did upgrade to slist v2.09. i downloaded it today and installed and it still acts the same way.

i will say that the problem DOES NOT happen in sysprog, yet it does happen in any other application that is selected.

i did go into s/list, help/about. the prompt for listing system stats is helpful, i have printed the stats in sysprog, then i went into our development application and printed the stats as well.

since its ONLY 32 pages long (EACH!), it will take me a little time to do some comparision analysis.

also when booting oi, sysprog and application are booted with the same executable, so that elimates different boot techniques. i did check the environment settings between the two applications and they were the same.

know of anything else i can try?

stacy

forerunner systems, inc

415.332.4032 - voice

415.332.9170 - fax

stacy@forerunnersystems.com - email (mondays only)

sxmy@pge.com - email (any other time)

View this thread on the forum...