|
Post by bobneedssomehelp on Apr 3, 2020 21:13:44 GMT 1
Hello,
I have been doing some testing with vDos and ATB-WU v2. Everything was going good until I tried to load the current in-use database.
proc NETUSEEXCL line 147, out of memory The full blown "database" (really just a folder with subfolders and files) is ~300MB, whereas the test database is ~1MB. I don't understand how it can be a memory issue. Is vDos limiting the available memory somehow? I tried to change XMEM (command I saw in vDosPlus) but it didn't seem to work in either program.
I'm at a little bit of a loss and hoping that you can shed some light on this. Thanks Jos.
Bob
|
|
|
Post by Jos on Apr 3, 2020 21:43:13 GMT 1
EMS and XMS memory are now (version 2020.03.01) fixed at 16 MB. The XMEM directive was dropped because too many kept (to no result) playing with the options. That static 16 MB should just do and takes off some of the burden of memory addressing (speed).
I also ‘don't understand how it can be a memory issue’. vDos provides for more memory than DOS or NTVDM. Would be a parachute of some function in your DOS program, not related to a memory issue?
I would need some basic vDos setup to reproduce the error, the less provided, the better.
“NETUSEEXCL” seems questionable to start with. It’s supposed to do a Window CMD NET USE command?
Jos
|
|