Portions of screen not showing in medical billing program

[rchusid]

I see you got an old dos program going for someone else in this forum and was hoping you could have as much success with mine. I have successfully launched the program (Medical Manager) but on some of the screens only part of the data which should be on screen shows. In some cases this doesn't matter, but on other screens crucial portions do not show up, making the program unusable.

The program is hosted on a Windows XP computer. I access it on various computers with a combination of Windows XP computers and Windows 7 computers running the program in an XP virtual machine. I'm hoping to replace the Windows XP and Windows 7 computers over time with Windows 10 computers.

I loaded vDos on a Windows 7 computer (which normally will run Medical Manager in an XP virtual machine). I had no problem getting the program to start over the network after using the Use command for the networked location, but as I said portions of some screens do not show up.

The program requires some things be loaded with config.sys and via batch files. From what I have read on the site, it does not appear that these commands are still necessary, but I wonder if there is an isolated command still needed which is causing the problem. In the hopes that it will help trouble shoot this, I'll include the information in config.sys.

Config.sys on the XP computer hosting the application consists of:

files=40

buffers=40

dos=high,umb


Ansit.sys also needs to be loaded in the XP virtual machines. 

[Jos]

www.vdos.info/faqs.html - Miscellaneous - FILES= and other directives, once in config.sys.

ANSI.SYS is built-in, I suppose you use the latest vDos version. Any logic to what and when isn’t displayed, perhaps some screenshots?

Jos

[rchusid]

I just installed vDos yesterday from your website so it must be the latest version.

I don't see any pattern to what shows. I took one screen grab of the opening menu screen where everyone shows, and a second of the screen where payments are entered, on which the vast majority of the screen is blank. Other screens are somewhere in between where some of the text shows and other portions do not. 

[Jos]

Don’t have an explanation for this behavior. The ANSI.SYS implementation only misses some obscure functions like remapping keyboard keys.
What if you select some blank part of the screen with Ctrl+Win+LeftMouseClick, then paste that into for instance Notepad. If the missing text ‘by magic’ appears, the back- and foreground colors in the vDos window are the same. So the text is invisible, though a long shot.

Else see if you can construct and submit some test environment that starts the program, w/o actual data of course, but at least showing one screen with this mishap.

Jos

[rchusid]

Copying and pasting into Notepad resulted in only the data I can see being pasted, with the rest missing.

I tried VdosPlus and there were some minor problems with some screens but most screens are working, so whatever is done different with that program must help with this issue. Unless you have come up with anything else to explain this, it looks like I'm better off working on the far more minor issues in VdosPlus instead.

[Jos]

That’s strange, vDosPlus is essentially vDos with some additions. It’s based on an older version, so the emulated CPU is over 100% slower. That doesn’t explain text not showing, but you can try the undocumented STRICTMEM = ON directive in config.txt.
Then it ends for me, w/o having a look at the program, and my crystal ball still defect, I’m unable to diagnose a problem, unique to your program.

Jos