First post, by VannevarKush
I've been working on getting Windows 3.11 working in DOSXbox. This is a version for the original Xbox that is based on DOSBox 0.72. My goal is to create a slimmed down and optimized build of Windows 3.11 vanilla that can be used to run Windows 3.1 software (at least, as well as the 733Mhz Pentium III in the original Xbox can handle.)
What I'm finding is that Windows 3.1 has been working well in DOSBox, and DOSXbox. The only problem that I am having is when I go to open a file from an open file dialog. If I open Notepad, and I go to open a text file on drive C, I get a dialog with the message "Cannot select Drive C", and I can't open the file. Running "notepad [path to file]" from within Windows opens the file without issue.
Now, I know DOSBox is not expressly intended to run Windows and I am using a port of an old version of DOSBox. This issue also doesn't show up in DOSBox 0.62 for Windows, so I know that I am out in the weeds here. What's more, this issue doesn't show up when I am running Windows 3.x from inside a hard drive image. Everything works as expected on DOSXbox in that situation, the only problem is the speed of the Xbox CPU. 😀 So even if I can't solve this, I have a workable solution. But, it is still much more easy and convenient to set up content as a mounted directory, rather than as a mounted image.
One more note, I set up a build of Windows 1 and Windows 2. Both of these had the same issue when running as a mounted directory, rather than as a hard drive image. For these versions, they seemed to try to open the file as a directory, and then the open file dialog would display an empty directory, named as the full name and extension of the file.
So, I am wondering if anyone has any ideas on what I could investigate here? Recompiling DOSXbox may be possible to fix the issue if I can begin to narrow down where the issue is happening. It might have something to do with an idiosyncrasy of the FATX filesystem and how it is being mounted in DOSXbox, or it may just be a bug in DOSXbox.
I've tried the following:
- I'm testing by trying to open a file on the drive with Notepad
- This issue does not apply to the Z: drive, to mounted ISOs, or to floppy images mounted on A:. Windows does not seem to see directories mounted on A although DOS does; not a big issue
- The issue does apply to a directory mounted as D
- Removing DOS files from PATH has no effect
- Turning off virtual memory in Windows has no effect
- Disabling all audio devices in DOSXBox config has no effect
- mount c "..." -freesize 1024 has no effect
- Changing every disk related option I could find documented for system.ini did not help
Would there perhaps be a tool to allow me to monitor what is happening here in the winAPI at a low level, from within Windows? I'm open to any suggestions here!