![]() ![]() At a very minimum there should probably be a command line parameter to override this behavior (say -r for relative?) However, I think it is generally better for intuitiveness and convenience if it is relative by default and would require a parameter instead to override that (say -h for host?) There are a lot of disadvantages to requiring a full absolute path including the simple possibility of it being run on a different computer (ex from a USB drive) where drive letters may be different. I'm sure this has come up before and perhaps it is intentional behavior. What version(s) of DOSBox-X have this bug?Īll recent builds, including the most current (0.84.1) Used configuration ![]() I am running 10, but I believe it's the same for all of them. Probably all OSes, but certainly all versions of Windows. Imgmount should accept a relative path within the mounted filesystem What operating system(s) this bug have occurred on? Type imgmount where is a file that does exist within that directory.Use a mounted filesystem such as drive Z: or any other (say, for example, "C: then cd \game").I'm not clear on if this is 100% intentional behavior or not, but it Steps to reproduce the behaviour ![]() This has been a thing that has confused me several times about DOSBox-X specifically (I am pretty sure I remember the original DOSBox not doing this.) When in a mounted system - say a mounted C: folder or the automatic drivez mount - if you use imgmount without specifying an absolute path, it produces an error that can be quite confusing saying the file is not found. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |