It now works! (i.e. with core=dynamic) Thanks wd and minimax! It works with either cycles=max or cycles=auto. Since the readme file recommends cycles=max, I'll leave it there. Attached is a .ppt file with slide 2 showing the new results (slide 1 is the old/bad results, and pay no attention to slide …

I won't be back to my office PC until Friday, at which time I will try the suggested core=dynamic setting in my config file. I'll post the results after I try it.

Yes, the display on the screen in the full-screen DOS mode has more info (plots and labels beyond 10 km) than the display on the screen inside the DOSBox window in the windowed mode. I will attach a file of the DOSBOX screenshot in a couple of seconds.

Thanks for your quick reply. Sorry for not being more clear. It IS the same image as what I am seeing. The problem is that the old DOS application produces an incomplete image when operating within DOSBox, but produces the complete and correct image when not using DOSBox. I know this might sound …

I am running DOSBox version 0.72, in Windows version 5.1 service pack 2, in Windows XP Professional version 2002 service pack 2. I have a Pentium(R) 4 CPU processor at 3.4 GHz with 992 MB of RAM. I am trying to run an old (1993) full-screen DOS application called CARPET in DOSBox. The application …

I just read the posting guidelines again, and had previously read the readme file. I got to my post after registering and then entering the DOSbox forum. How can one start a NEW thread within the DOSbox forum? My problem IS an old game (actually not a game per se, but an app that loads and runs like …

I have DOSbox working OK, but it is causing the DOS application to create graphics that are incomplete (e.g. the radar range stops at 10 km instead of going out to the required 60 km -- running the app without DOSbox goes out to 60 km, but the alt-print screen doesn't work). Any ideas? I tried …