tag:blogger.com,1999:blog-6091596357545677014.post2628639067562335307..comments2024-03-12T02:10:00.785-06:00Comments on Addsum Business Software, Inc.: Extend the life of old applications with vDosTony Frateshttp://www.blogger.com/profile/06203800945783503602noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-6091596357545677014.post-89215591547757554602018-11-30T17:01:55.469-07:002018-11-30T17:01:55.469-07:00For newer versions of vDOS there is a registration...For newer versions of vDOS there is a registration process that removes that nag screen. This is explained via the link below. The only way to otherwise remove the nag screen it so use the older version on SourceForge.<br /><br />See:<br />https://www.vdos.info/register.htmlTony Frateshttps://www.blogger.com/profile/06203800945783503602noreply@blogger.comtag:blogger.com,1999:blog-6091596357545677014.post-62967932688670775472018-11-19T11:16:18.616-07:002018-11-19T11:16:18.616-07:00i am running an application build under foxpro dos...i am running an application build under foxpro dos version 1 using vdos in a win 7 64 bit machine, so far ok but the nag window pop at the beginning when the foxpro start, how actually if you can, i can remove that nag window, it ws written in C++ vDos, i opened with Visual studio 2017 community version , i just searched on vdos.cpp and i was trying to remark the code where the nag will pop, but since i don't know c++, probably i am missing something, can you please share, what exactly need to be removed, to avoid the nag to appears please thanks so much in advance.Ernest ERNESTO PAEZhttps://www.blogger.com/profile/12086922921447526757noreply@blogger.comtag:blogger.com,1999:blog-6091596357545677014.post-87958678282183283482016-06-01T15:32:28.347-06:002016-06-01T15:32:28.347-06:00FYI: A new 2016.06.01 vDos version is released. Am...FYI: A new 2016.06.01 vDos version is released. Among others, it’s faster, and a DOS-to-Windows print processor is built-in.<br /><br />Though if one can upgrade the DOS application to Windows, that still remains the preferred route to persuade!<br /><br />JosJos Schaarshttps://www.blogger.com/profile/03920331985231192848noreply@blogger.comtag:blogger.com,1999:blog-6091596357545677014.post-76499759382146127522016-03-13T20:25:47.103-06:002016-03-13T20:25:47.103-06:00Understood and thanks.Understood and thanks.Tony Frateshttps://www.blogger.com/profile/06203800945783503602noreply@blogger.comtag:blogger.com,1999:blog-6091596357545677014.post-31871642168421818582016-03-13T20:25:00.658-06:002016-03-13T20:25:00.658-06:00Thank you for your helpful comments. The user we ...Thank you for your helpful comments. The user we worked with may have been having an Okidata printer problem which accounted for some strange printing issues they were having with formatting and alignment. As to the "run as administrator" option, we found that was necessary on this system or else we could not run the legacy accounting software, but were not trying to indicate that was necessarily a vDOS issue; it may have been due to some restriction on user rights on this particular system and wanted to document a solution should someone else run into the same issue.Tony Frateshttps://www.blogger.com/profile/06203800945783503602noreply@blogger.comtag:blogger.com,1999:blog-6091596357545677014.post-25276297629756893232016-03-13T17:45:48.525-06:002016-03-13T17:45:48.525-06:00I forgot:
…it may be a little more sluggish than ...I forgot:<br /><br />…it may be a little more sluggish than running from a 32-bit PC directly…<br />vDos, simulating the CPU in software, is inherent slower than NTVDM running natively (Windows 32). Accessing files will actually compensate vDos being slower (DOS functions are emulated in Windows 32-bit, instead of DOS 16-bit mode). Certainly if networked files are accessed, that will be the performance bottleneck of a DOS program. So running that program in vDos would benefit (being less slow).<br /><br />JosJos Schaarshttps://www.blogger.com/profile/03920331985231192848noreply@blogger.comtag:blogger.com,1999:blog-6091596357545677014.post-78348576941382535082016-03-13T17:00:29.107-06:002016-03-13T17:00:29.107-06:00Glad, you emphasized people should essentially upg...Glad, you emphasized people should essentially upgrade their software to modern standards. I always state vDos is meant for running legacy DOS programs, that – for whatever reason – still have to be used. I don’t relate at all to people insisting to use some obsolete DOS program, while there are many modern alternatives around.<br /><br />…The April 2015 version (the October 2015 version has a built-in expiration date)…<br />The 2015-10-01 version (not available anymore) has indeed a built-in expiration date, however not intended. To force vDos users, who asked for a pre-release of that version, to use the final release instead, that expiration date was set in the development version. It was just forgotten to be removed from the final release. I’m already plagued with people recompiling vDos, having issues due to the modifications, even without telling they changed the vDos sources. I don’t want to also be surprised with possible issues of some pre-release I once sent.<br /><br />As of version 2015-10-01 vDos has a registration option, but it is still freeware. Only if the PC is joined to a domain, or a networked directory share is used, a nag is displayed when vDos starts. Probably most vDos users who get that nag, simply click it away. The number of vDos users that actually register is small. November 1st 2015, I was not only surprised by vDos refusing to start, I also got 2 registrations that day, 2 on Monday and a last one on Tuesday. More than in the whole month before (and after that)! One reported on Monday that vDos still didn’t start. So I made the link; until then they clicked the nag away, didn’t go to SourceForge or the vDos site and didn’t get the 2015.11.01 fix.<br /><br />…The vDos software uses the C++ dynamic library link file MSVC100.DLL…<br />As of version 2015.10.01 this is no longer needed. Especially with fresh Windows 10 systems, too many got this message, so the MS library is statically linked in.<br /><br />…but would likely require changes to individual programs in order for the output…<br />If the DOS program is set to print to an Epson (compatible) or PCL printer, there is no need to change anything, output should be correctly aligned and formatted.<br /><br />…it will relate to the "run as administrator"…<br />I’m puzzled, vDos does no “funny” things like non-requested network (Internet), or registry access (at all).<br /><br />JosJos Schaarshttps://www.blogger.com/profile/03920331985231192848noreply@blogger.com