VOGONS

Search

Common searches

DOS 21H appends dir and driver name while accessing devices like CON and NUL

Topic actions

First post, by cyberwalker

Posted on 
User metadata
Rank Newbie
Rank
Newbie

I have recompiled the source in VS2005 successfully.
But Borland's TASM.exe and Microsoft's CL.exe failed
to run against my generated DOSBOX. After tracing into
the source code, I found that it stopped in file function stat().
This is caused by DOS INT21H routines that use full
path to access devices like CON and NUL. Maybe DOS INT21H
can verify file name by looking up the device table before file
operations.

I hope this information will be helpful.

Attachments

  • Filename
    dos_files_cpp.diff.txt
    File size
    1.24 KiB
    Downloads
    151 downloads
    File license
    Fair use/fair dealing exception
Last edited by cyberwalker on 2005-08-08, 20:09. Edited 9 times in total.

Reply 1 of 3, by Qbix

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

hmm yes that is a tricky problem
our devices detection doesn't work that well on all file operations.

Thank you for reporting it about that stat. I think that one might be fixable

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 3, by cyberwalker

Posted on 
User metadata
Rank Newbie
Rank
Newbie
Qbix wrote:

hmm yes that is a tricky problem
our devices detection doesn't work that well on all file operations.

Thank you for reporting it about that stat. I think that one might be fixable

Thank you for your attention. I have uploaded patch code for testing.

Go to top of page Go to top of page
Back to DOSBox Development
Close window
Close window