I am running a multiuser Wampum (Clipper indexes) program "that keeps on keeping on" and vDos has been an amazing solution. For some reason scince we moved to the 2019.5 (latest) version we sometimes get a black screen on startup.
When we startup we get the vDos "registered to" splash screen a minute or so after startup and sometimes after we click on the
splash screen we get a black screen in the vDos window and we have to end the task (Cntrl-Alt-Del) which does not do
the indexes any favours and we are having to reindex.
I did wonder if this was a memory/graphics issue and whether changes to the Config.txt may alleviate it.
I tried making a coupleof changes to the XMEM statement but I obviously had the syntax wrong...
although the application manual says 2-4 MB of extended memory is useful
A black screen doesn’t ring a bell. If it only occurs after the nag is displayed: The virtual PC is put on halt until you click the nag away, could be it’s some timing issue with Clipper or one of its libraries.
You already have a Network license. The nag popping up with “Registered to …” would mean vDos is running with another server name, or the license file is damaged. You shouldn’t get the nag, could you send me a copy of license.txt and a screenshot of the nag.
The XMEM directive is removed from config.txt, XMS and EMS memory are fixed at 10MB. I doubt the black screen is related to the amount of memory.