use the new version of Dosbox and use the dynamic core, it is much faster now.

And I'm glad the guide helped you! 😀
(if there is any step in the guide you would have liked to be more precise or you had to guess what to do, please tell me, fine tuning is hard 😀)

One of the 16 bit Win programs that I use actually calls a DOS subroutine that does not work correctly with DosBox .70 (Seems to be a keyboard handling thing). I am glad that you kept the DosBox .65 specific instructions.

As for the quide,
one step that I did not understand was how to extract the drivers from my win311 folder to put into the drivers folder.
Also, at first I did not know where the dynamic core setting was so you could include (core=normal) at the end of the next line (like the EMS comment)
- do not use dynamic core
- disable EMS (EMS=false)

Great work on the guide, it made thing painless for me.

One of the 16 bit Win programs that I use actually calls a DOS subroutine that does not work correctly with DosBox .70 (Seems to be a keyboard handling thing). I am glad that you kept the DosBox .65 specific instructions.

maybe the devs are interested which program that is, so please tell us its name and what it does.

one step that I did not understand was how to extract the drivers from my win311 folder to put into the drivers folder.

hmm, that is kind of hard since I don't want to go into details on how to extract an archive and move the files where you want them to be. Use Winzip or Winrar or some other (un)archiving program for that.

Also, at first I did not know where the dynamic core setting was so you could include (core=normal) at the end of the next line (like the EMS comment)
- do not use dynamic core
- disable EMS (EMS=false)

ok, will change that right away. Thanks

Great work on the guide, it made thing painless for me.

Thanks, I'm happy to be of help and to make contributions to one of my favourite projects 😀

I read you on the driver extraction details.

The Dos app (and called dos subroutines) that does not work in DosBox .70 and does work in .65 is a vertical market app witten in Clipperthat calls graphing functions from a linked graphics library. The problem arises in the graphing routines. Any keyboard entry causes repeating screen refreshes.

As the Dos app is not "game" related, I tend to gather from many other posts on this forum that it may not be considered to be important.

I am very appreciative that gaming has been the major driving force in DosBox dev but also feel that DosBox has done a great service to the user community as there are a large number of vertical market apps for Dos and Win 16 bit that are valuable to many. This will be additionally true if Microsoft does drop 16 bit support in Vista 64. Vista 32 seems to do 16 bit just fine and many Dos apps.

As the Dos app is not "game" related, I tend to gather from many other posts on this forum that it may not be considered to be important.

You might be right there 😀
(but one never knows sometimes the devs are in a good mood 😀)

Microsoft never dropped support for 16bit in 64bit versions of Windows....they just never included it. (Except for some 16bit installshield installers).

Sometimes the devs will include non-game releated fixes into DosBox but there's nothing stopping you or other people from making patches and integrating them into DosBox CVS and then using them. If that's too hard then the devs (or somebody else) will accept money to create the patch.

Thanks,

Do we know for a fact the Vista 64 will not run 16 bit apps? Have you tried this on a Vista 64 box? Or do you know anyone that has?

Yes, the only way to run 16bit programs in XP/2003/Vista 64bit is by using virtualization/emulation programs.

So any 16bit program wether it's DOS/Windows will not run natively on Windows 64bit.

For what it is worth, just an update on the issue of the Dos app and subroutines running correctly in Vista 32. on 0.65 and not on 0.70

If called from a windows 16 bit app, the dos program or dos subroutine does work correctly using 0.65

If called from a windows 16 bit app, the dos program or dos subroutine do not work correctly 0.70. The dos program, if started stand alone (not called from a win 16 program), does work correctly.

hmm interresting. with the same core ? (and same windows instalation)

It's worth checking out. All that stuff is very subtle and may indicate a small drift from the correct solution from our part.

Yes with the same core and Win 3.11 installation. Happens on both my Vista 32 laptop as well as a 98se box. Also when returning to Win311 from the called Dos app the Win 311 video goes haywire. Can see enough to exit Windows 3.11. Calling Dos from Win 3.11 certainly does not have high priority but it is an interesting problem.

I will put together a small zip file to try and demonstrate this behavior. Should I post it here or start a topic in the Applications section?

Tried different cores? Different cycles?

I have switched between Core Normal and Auto, EMS True and False. I'll mess with cycles a bit.

On the video going haywire mentioned above (not the Dos yes on 0.65 - no on 0.70 issue). My win 3.11 setup is set at standard VGA. If I pull down File, click Run and enter: z:\command Win 3.11 shells out to Dosbox as would be expected but on exit back to Win 3.11 my video goes south. I believe this happens in both 0.65 and 0.70 and on my vista32 laptop as well as a 98 se box.

but on exit back to Win 3.11 my video goes south

That's known but doesn't hurt that much.