Lesspace not doing the trick

#31

owens.maggie wrote:

Quote:

With the Paradox RUN, it works *sometimes*. It is not consistent
and they were unable to determine why or fix it.

Between Netware 3.x and Netware 4.x, the memory requirement of CAPTURE.EXE
quadrupled. Shell-to-Dos execution of CAPTURE were more likely to fail
because of memory management issues. We ran into this as we began to
implement 4.x servers in bindery emulation mode. NPRINT is probably the
best solution.

--
Larry DiGiovanni
Digico, Inc.
IT Consulting and Staffing Solutions
www.digicoinc.com
Check out www.thedbcommunity.com for Paradox resources.

#32

Maggie,

(I'm kinda enjoying this, but I reckon I shouldn't <g>).

Quote:

Apologies - Lesspace cannot pretend that there's more space available
that
there REALLY is.
Right, but there REALLY is like 21gb free.

And lesspace does not appear to understand this... Or do I
misunderstand?

*YOU* know there's 21GB free. Because you used some Windows function to tell
you.

Lesspace is running is a simple DOS environment. It's restricted to the
STANDARD commands that that DOS box honours. Those functions are telling
Lesspace that there's NO space free.

Quote:

Lesspace cannot fix the problem, if the OS is saying there's NONE
available.
We're... er... bunched <g>.
The OS reports 21gb free. If I start up paradox, shell out to dos and
ask how much space is free, I get the same number.

All depends on what internal functions are being used to report what's
free - eg, DIR might use one function, CHKDSK might use another one, etc.
The Novell client may be hooking in here also, and fiddling with the data
that Lesspace sees. There are numerous such functions.

Quote:

If I run command, load lesspace and ask how much space is free, the
number is still the same.

Again, all depends on what internal functions are being used to report
what's free. If the functions are going through Lesspace, it'll kick in and
do it's thing. If not, it'll never see what's going on.

Your "/D" traces indicate that the normal functions (1C, 36, etc) that are
trapped by lesspace, are seeing nothing free. Lesspace is having no effect.
Something is lying to lesspace. Maybe a "compatibility" fiddle in the
Netware configs; maybe something passed over from the server...

If we could extablish what functions are being used in the CMD shell to show
you 21GB, and if they are "normal" functions, then I guess we could
intercept these with lesspace, and see if we could pass back some acceptable
values to Paradox. BUT, telling lies like this might not be easy. You might
check on the "File" monitoring utilities at www.SysInternals.com, and check
if they'll give you some info on what's going on under the cover when you
get the 21GB results. (I have some Trace utils also, that I could send you,
but...).

But, this level of "lying" has not been required previously in Lesspace, so
we might still be barking up the wrong tree.

Apologies to others if this is too long-winded...

- Mike

#33

Quote:

As an added bonus, instead of my own PC reporting 0 space free on that
drive, it now cannot see the drive at all.

Hello!!

Hello!!

Hell...

#34

<owens.maggie (AT) gmail (DOT) com> wrote in message

Quote:

With the Paradox RUN, it works *sometimes*. It is not consistent and they
were unable to determine why or fix it.

not related to "permissions" either?

Quote:

There is really nothing else in the app that uses RUN

excellent..

Quote:

As an added bonus, instead of my own PC reporting 0 space free on that
drive, it now cannot see the drive at all.

I guess that would now be "less than zero" ? (g)

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Lesspace not doing the trick

comp.databases.paradox comp.databases.paradox

Re: Lesspace not doing the trick - 02-14-2006 , 03:21 PM

Re: Lesspace not doing the trick - 02-14-2006 , 03:24 PM

Re: Lesspace not doing the trick - 02-14-2006 , 03:48 PM

Re: Lesspace not doing the trick - 02-14-2006 , 04:37 PM