-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DosBox-X 0.84.1 is not recognized as a valid operating system by Microsoft QuickBasic 7.1 (alias PDS 7.1) #3626
Comments
Behavior under very early versions of dosbox-x is identical to dosbox-svn. I ran a git bisect. Starting from this, a warning appears about the not recognized DOS version as MS-DOS or PC-DOS. |
Withdrawing this commit, i.e. returning to the previous state, QuickBasic 7.1 starts without this unnecessary warning. |
@joncampbell123 Could you explain 9fbbb52 in a bit more detail? |
The intent was to allocate in sequence instead of hardcoding segment offsets. Does QuickBasic require that at segment_base+0x80? |
See https://www.os2museum.com/wp/how-to-void-your-valuable-warranty/ for an explenation of what is happening... This was a MS trick to get people to buy MS DOS rather than DR DOS. Apparently NTVDM has the same issue. |
Fixed. Those specific DOS kernel structures are allocated properly and line up to satisfy any Microsoft software that checks the DOS kernel in this manner. |
Describe the bug
Each time you start, the following error message appears:
WARNING: THIS MICROSOFT PRODUCT HAS BEEN TESTED AND CERTIFIED FOR USE ONLY WITH THE MS-DOS AND PC-DOS OPERATING SYSTEMS. YOUR USE OF THIS PRODUC WITH ANOTHER OPERATING SYSTEM MAY VOID VALUABLE WARRANTY PROTECTION PROVIDED BY MICROSOFT ON THIS PRODUCT.
Under DosBox 0.74-3, no error message is displayed.
If you execute the command ver under DosBox or DosBox-X, a string is displayed in both cases, which differs from the original operating system MS-DOS. Nevertheless, it works under DosBox, but not under DosBox-X. So, the program seems to resort to some other function to determine the validity of the operating system. This function, unknown to me, seems to be implemented under DosBox, but not under DosBox-X.
It could be the folling function from the logfile: ERROR INT10:Function EF00 not supported
Steps to reproduce the behaviour
Expected behavior
The program runs without an error message.
What operating system(s) this bug have occurred on?
Windows 10 21H2
What version(s) of DOSBox-X have this bug?
0.84.1 (VSBuild) and before
Used configuration
Output log
Additional information
No response
Have you checked that no similar bug report(s) exist?
Code of Conduct & Contributing Guidelines
The text was updated successfully, but these errors were encountered: