New version 2023.05.01

[Jos]

I don’t know why dBase complains about not enough memory. If you look at the memory figures, the only significant difference are those of Memory (3) and (8).
The intermediate 2022-03-09 version will provide for 15MB extended/XMS memory, the others for 16MB. 1MB more, and then not enough memory?

If you issue ERASE at the command prompt, you’ll notice ERASE isn’t recognized anymore as an internal command.
vDos command line interpreter is basic, three distinct commands (DEL, DELETE and ERASE) to delete files seemed overkill.
Didn’t imagine anyone using ERASE, so I dropped that. Though I could easily add that back in.

Jos

[Jos]

Appears DELETE is actually only recognized by the Recovery Console command line. So I dropped that instead of ERASE.

Jos

[herman]

Jos,

Thank you for the explanation; I'm not very familiar with that, but I understand the differences
Memory usage also depends on settings made before start in CONFIG.DB as with me (sorted out a long time ago):
INDEXBYTES = 2048 && default 256 Each record in a database file is represented by a node in an index file
MBLOCK = 1 && MEMOFIELDS SET BLOCKSIZE TO 1 for both MBLOCK and IBLOCK
IBLOCK = 63 && Index blocksize default 1
MVBLKSIZE = 100 && default 50 Memory variable block size
MVMAXBLKS = 150 && default 10 Memory variable maximum blocks
RTBLKSIZE = 100 && default 50 RunTime memory variable block size DBF names
RTMAXBLKS = 150 && default 10 RunTime memory variable maximum blocks

Haven't found the time to experiment with it yet, but if i get anything out of it, i'll let you know

For ERASE DELETE (DEL) appears to be the alternative which works well for me.

Herman

[frog]

Today I got error "Memory Low/5300" with this version. When I reproduce with the same method the error not occured for two times, the second try program ran as usual. Still confusing what cause it.

[Jos]

When you have something to reproduce that error, let me know.

Jos

[lynntg123]

I have loaded Vdos on 3 computers and get the same error, "program tried to resize MCB block BF". I narrowed it down to the "set relation" command, which works fine. But when I try to copy to another file that is in that relation, I get that error. Otherwise, everything is running great, even printing correctly with my set fonts.

Could it be that I have something loaded on my machines causing this?

[Jos]

I don't know if you perhaps load some TSR program interfering.

Else you could setup some test program to demonstrate the issue?

Jos

[lynntg123]

use holdings
use active index active
sele holdings
set relation to hissue into active
copy to cashupt for active->adesig = 'TF'


Hopefully you can help me.

[Jos]

I'm no dBase programmer, so would need at least the involved files.
Could be empty, or with one record?

Jos