Lesspace not doing the trick

#1

I'm running PdoxDOS 4.02 on a Netware 5 and 6 network.
Using Lesspace, this has been working flawlessly for many years.

Paradox itself is installed on a Netware 5 server; most of the tables
it uses are on the Netware 5 server, which has 10.2gb free. There are a
few files it writes out to the Netware 6 server (which is actually a
cluster), which has 19.2gb free. We have been writing to the Netware 6
server EVERY DAY for over 2 years.

Starting today, I cannot write to this server using PdoxDOS when it's
running under Win98. However I can write to the server using PdoxDOS
running under Win XP. The test I have tried was to create a table on
the netware 6 server. Running under '98, I get "not enough disk space
to enter subsystem". Runing under XP, I can create the table fine and
add records to it.

I'm starting Pdox with the SAME batch file under both operating
systems. I have replicated the '98 error on two different machines. On
one of the machines, I updated the novell client to the latest one.

Unfortunately, getting rid of Win98 in favor of XP will not be an
option for several weeks, and I have to write to the Netware 6 server
every day.

Any suggestions would be greatly appreciated.

#2

So, did anything unusual happen to your systems/LAN/server just "today"?

There's a section in the Lesspace notes entitled something like "What if
this darn thing don't work". If you send me the outputs, I'll take a look.

I've seen problems created when users also activate other solutions to fix
the space problem (as well as lesspace), and then the data going to lesspace
was already tweaked excessively - and lesspace could not help. Eg, there are
"compatibility" options and products which might conflict with lesspace...

Unless I'm greatly mistaken, your problems are extremely unusual!!

- Mike (lesspace author)

<pipkin0101 (AT) yahoo (DOT) com> wrote

Quote:

I'm running PdoxDOS 4.02 on a Netware 5 and 6 network.
Using Lesspace, this has been working flawlessly for many years.

Paradox itself is installed on a Netware 5 server; most of the tables
it uses are on the Netware 5 server, which has 10.2gb free. There are a
few files it writes out to the Netware 6 server (which is actually a
cluster), which has 19.2gb free. We have been writing to the Netware 6
server EVERY DAY for over 2 years.

Starting today, I cannot write to this server using PdoxDOS when it's
running under Win98. However I can write to the server using PdoxDOS
running under Win XP. The test I have tried was to create a table on
the netware 6 server. Running under '98, I get "not enough disk space
to enter subsystem". Runing under XP, I can create the table fine and
add records to it.

I'm starting Pdox with the SAME batch file under both operating
systems. I have replicated the '98 error on two different machines. On
one of the machines, I updated the novell client to the latest one.

Unfortunately, getting rid of Win98 in favor of XP will not be an
option for several weeks, and I have to write to the Netware 6 server
every day.

Any suggestions would be greatly appreciated.

#3

<pipkin0101 (AT) yahoo (DOT) com> wrote in message

Quote:

Paradox itself is installed on a Netware 5 server;

machines are must faster than in the old days, but network I/O will be
reduced a lot if you put Paadox itself, and the priv, on the local
machines..

Quote:

Running under '98, I get "not enough disk space to enter subsystem".
Runing under XP, I can create the table fine and add records to it.

that is normally an XP error, not a 98 error.. and the cause of the error on
XP is a missing auotexec.nt file in the system32 folder..

Quote:

I'm starting Pdox with the SAME batch file under both operating systems.

can we see the batch file and the pdox command line?
did you just add the XP machines to the mix?

--
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

#4

Steve,

Thank you so much for your reply.

Quote:

machines are must faster than in the old days, but network I/O will be
reduced a lot if you put Paadox itself, and the priv, on the local
machines..

Paradox is fast enough as it is, and installing it on the local
machines will complicate management of the environment. The private
directory is already on the local machines.

Quote:

Running under '98, I get "not enough disk space to enter subsystem".
Runing under XP, I can create the table fine and add records to it.

that is normally an XP error, not a 98 error.. and the cause of the error on
XP is a missing auotexec.nt file in the system32 folder..

I am quite certain that this is happening ONLY under '98. In addition
to not occurring under Windows XP, we also were unable to reproduce it
on a 2003 server machine.

Quote:

can we see the batch file and the pdox command line?
Sure, here it is:

lesspace
f:
CD\apps\pdox40
set rtvmexp=0
paradox -compmode -diag -bios -norealheap -notsr -nettrace -extk
8192 f:\ABTAR2\MAIN
lesspace /u

In the pif file used on the '98 machines, on the memory pages,
everything is set to "Auto", except for Extended memory, which is set
to 8192; also "Uses HMA" is checked.

Quote:

did you just add the XP machines to the mix?
No. We've had them since shortly after the initial release of Windows

XP.

#5

Simple question - are you getting the confirmation message that Lesspace has
installed successfully?

What about the "diagnostics" info from lesspace?

"-emk 0" is also a recommended command-line parameter.

- Mike

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

Quote:

Steve,

Thank you so much for your reply.

machines are must faster than in the old days, but network I/O will be
reduced a lot if you put Paadox itself, and the priv, on the local
machines..

Paradox is fast enough as it is, and installing it on the local
machines will complicate management of the environment. The private
directory is already on the local machines.

Running under '98, I get "not enough disk space to enter subsystem".
Runing under XP, I can create the table fine and add records to it.

that is normally an XP error, not a 98 error.. and the cause of the error
on
XP is a missing auotexec.nt file in the system32 folder..

I am quite certain that this is happening ONLY under '98. In addition
to not occurring under Windows XP, we also were unable to reproduce it
on a 2003 server machine.

can we see the batch file and the pdox command line?
Sure, here it is:
lesspace
f:
CD\apps\pdox40
set rtvmexp=0
paradox -compmode -diag -bios -norealheap -notsr -nettrace -extk
8192 f:\ABTAR2\MAIN
lesspace /u

In the pif file used on the '98 machines, on the memory pages,
everything is set to "Auto", except for Extended memory, which is set
to 8192; also "Uses HMA" is checked.

did you just add the XP machines to the mix?
No. We've had them since shortly after the initial release of Windows
XP.

#6

Mike,

Thank you very much for your reply.

We've been using v1.4s.

I downloaded an evaluation version of 3.6 from your site. I replaced
the call in the batch file to with one to the new version of lesspace
and briefly saw an "out of environment space" before paradox started.
After using LH when calling lesspace, I didn't get the "out of
environment space" message, but I still can't create a table on the
offending drive.

Below is the output for lesspace /d (note that drives N, S and T all
point to the offending server.)
$ I21-1C Drive=$C Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFF6h
MedByte=$F8h
$ I21-1C Drive=$E Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$3E80h
MedByte=$F8h
$ I21-1C Drive=$F Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$G Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$7D00h
MedByte=$F8h
$ I21-1C Drive=$H Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$J Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$K Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$M Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$N Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$O Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$S Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$T Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$X Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$Y Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$ I21-1C Drive=$Z Sec/Clu=$40h Byt/Sec=$0200h Tot-Clu=$FFFFh
MedByte=$F8h
$
$ I21-36 Drive=$C Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFF6h
Fre-Clu=$FFF6h
$ I21-36 Drive=$E Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$3E80h
Fre-Clu=$3646h
$ I21-36 Drive=$F Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$FFFFh
$ I21-36 Drive=$G Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$7D00h
Fre-Clu=$0CDCh
$ I21-36 Drive=$H Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$0000h
$ I21-36 Drive=$J Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$54D2h
$ I21-36 Drive=$K Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$54D2h
$ I21-36 Drive=$M Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$FFFFh
$ I21-36 Drive=$N Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$0000h
$ I21-36 Drive=$O Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$54D2h
$ I21-36 Drive=$S Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$0000h
$ I21-36 Drive=$T Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$0000h
$ I21-36 Drive=$X Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$FFFFh
$ I21-36 Drive=$Y Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$FFFFh
$ I21-36 Drive=$Z Sec/Clu=$0040h Byt/Sec=$0200h Tot-Clu=$FFFFh
Fre-Clu=$FFFFh

BTW, we are not using any other solutions to fix the space problem.

I am looking forward to your reply.

#7

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

Quote:

paradox -compmode -diag -bios -norealheap -notsr -nettrace -extk 8192

please download switches.zip from my web site for explanations of what I'm
about to tell you.. this might not be related, but you *must* get rid of the
notsr switch.. it is unstable and dangerous.. norealheap does nothing, and
it is unknown if it can cause problems.. emk is missing, as Michael said..
and change the 8192 to 15000..

Quote:

In the pif file used on the '98 machines, on the memory pages,
everything is set to "Auto", except for Extended memory, which is set
to 8192; also "Uses HMA" is checked.

you should never change *anything* memory-related in the shortcut.. it can't
help, and it often hurts..

make a new one.. feed it the batch file, change the icon, an move on..

--
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

#8

Any further info on the "not trick" <g>

Check if 3.6 has the same flaws. And, if you're running the Debug options,
please use 3.6 - the "shareware" build supports the "/D" option.

(1.4 was released on 11 Oct, '95, which makes it almost as old as PDoxDOS
!!).

Best regards,
- Mike

#9

Steve and Mike,

Thank you for all your help so far.
I made a new batch file, which reads as follows:
lesspace
f:
cd \apps\pdox40
set rmvexp=0
paradox -compmode -diag -bios -norealheap -nettrace -extk 15000 -emk 0
f:\abtar2\main
lesspace /u

the pif file has no special settings at all, just points to my new
batch file.

I am still having the same problems.

Mike, did you see my post of the 8th where I posted the results of the
/d test with lesspace? It's at
http://groups.google.com/group/comp....01d20860f124c0

There is one more thing I should mention that might be relevant.
My machine is the only one on the network that does not have the
netware client. I am using the netware client, such as it is, that
comes with Windows XP. On my machine, the free space on the offending
drive also appears to be zero. This is not the case with any of the
other machines on the network.

Thanks again for your help.

#10

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

Quote:

paradox -compmode -diag -bios -norealheap -nettrace -extk 15000 -emk 0

please remove the norealheap, too..

Quote:

My machine is the only one on the network that does not have the netware
client. I am using the netware client, such as it is, that comes with
Windows XP.

historically, MS Client bad, NetWare Client good.. but..

Quote:

On my machine, the free space on the offending drive also appears to be
zero. This is not the case with any of the other machines on the network.

of course it's not the case with any other machine (sigh).. no free space
means trouble.. every program in the world will have problems with that..
w/o free space, you can't write to your files, create files, etc.. you're
dead in the water..

--
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