I think you're missing a slash.

Assuming that there is a real directory at C:\WC3 on your windows machine, enter this into dosbox:

mount c c:\wc3

then you can use c: to change to the newly mounted drive.

[Thread moved to DOSBox General]

You should take a look at the 60seconds guide in the guides forum. Especially that you use an extra folder for dos games that you mount. Wing Commander 3 will the make its wc3 folder when you install it (but you'd still mount the dos games folder and not the wc3 folder since otherwise wc3 will think it hasn't been installed)

that didn't work
🙁

can you post a link to the 60 second guide
searched did not find it

Solution Found!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

60second guide
60 seconds guide to getting your game to run in DOSBox

Correct syntax requires " "

ie mount c "c:\wc3"

Cheers

ninjalink0 wrote:

Solution Found!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! […]
Show full quote

Solution Found!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

60second guide
60 seconds guide to getting your game to run in DOSBox

Correct syntax requires " "

ie mount c "c:\wc3"

Could someone more knowledgable please comment on this? I do not use quotes in my mount commands.

Sincerely,

Gene Wirchenko

it's only required if you have spaces in the filenames

the OP probably forgot the backslash that follows the colon.

Qbix wrote:

it's only required if you have spaces in the filenames

the OP probably forgot the backslash that follows the colon.

Replicated. I did not realise that the backslash is compulsory. The error message is misleading then: adjust?

Sincerely,

Gene Wirchenko

It's not misleading. Anything that is not a proper path will get this error message. To make this error more specific you'd need to think ahead in too many ways to make it work.
On Windows c:wc3 is NEVER a proper path, and yes, one could filter those colons without backlashes, but then you'd run into people that try to mount c:/ wc3 (or c:/dosgames wc3 (with wc3 a subfolder of dosgames) etc.)

Btw, if I'm not mistaken, dosbox already is more forgiving and accepts the forward slash instead of the proper Windows path backslash.

Dominus wrote:

It's not misleading. Anything that is not a proper path will get this error message. To make this error more specific you'd need to think ahead in too many ways to make it work.
On Windows c:wc3 is NEVER a proper path, and yes, one could filter those colons without backlashes, but then you'd run into people that try to mount c:/ wc3 (or c:/dosgames wc3 (with wc3 a subfolder of dosgames) etc.)

c:ws3 is a relative path and quite valid.

Btw, if I'm not mistaken, dosbox already is more forgiving and accepts the forward slash instead of the proper Windows path backslash.

Actually, the forward slash will work fine with DOS CLIs. I will not say all of them.

Sincerely,

Gene Wirchenko

How is c:ws3 a relative or valid path? Relative to what?
What does windows command line say to that?

Dominus wrote:

How is c:ws3 a relative or valid path? Relative to what?
What does windows command line say to that?

Relative to the current directory on that drive. For example, given the current directory is c:\games, then c:ws3 is a relative path that resolves to c:\games\ws3.

Sincerely,

Gene Wirchenko

C is not mounted at that point so don't talk shit.

Please, Gene, before saying an error is misleading, read the thread

and since we dealt with the bogus relative thing you came up, let's deal with the valid.

c:ws3 is never a valid path, except maybe for some obscure software. Windows doesn't recognize this as a path, nor does Dosbox.

c:\ws3 is a valid path (if it exists 😀), Dosbox (and some other software) does recognize c:/ws3 as well.

It's a valid expression and it works fine in dosbox.

Dominus wrote:

Please, Gene, before saying an error is misleading, read the thread

and since we dealt with the bogus relative thing you came up, let's deal with the valid.

I said that the error *message* was misleading.

I have read the thread.

As to relative path being bogus, how about you take a look at
http://msdn.microsoft.com/en-us/library/windo … v=vs.85%29.aspx
? There is a section titled "Fully Qualified vs. Relative Paths".

c:ws3 is never a valid path, except maybe for some obscure software. Windows doesn't recognize this as a path, nor does Dosbox.

Windows does recognise it. I have just used it again in a DOS window.

Sincerely,

Gene Wirchenko

And I repeat it works fully fine, and the error message is fully correct if displayed.

Ok, sorry, I take my foot out of my mouth regarding the validity of the path. I was obviously wrong about that part