VOGONS


First post, by cyberwalker

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.

Last edited by cyberwalker on 2005-08-08, 20:09. Edited 9 times in total.

Reply 1 of 3, by Qbix

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

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.

Reply 3 of 3, by cyberwalker

User metadata
Rank Newbie
Rank
Newbie

Patch code refined. Only one file and few lines need changing.