VOGONS


First post, by lfl_038

User metadata
Rank Newbie
Rank
Newbie

Hi,
I discovered that, when a new file is added by host system (Windows 10) in a mounted drive, this file does not appears in DosBox 0.74-2.
One need to mount a new drive with the same path to see the file.
This could be a small problem if there were un mount command.
Also the number of free bytes is wrong. On my d: drive there are 50.8 GB free and DosBox displays only 249 MB free.

Example :
1) I mount d: drive on d:\temp local path.
2) I copy image222.jpg into d:\temp local path using the Windows explorer.
3) I mount e: drive on same d:\temp local path.

Here is the result :

Z:\>mount
The currently mounted drives are:
Drive Type Label
--------------------------------------------------------------------------------
C local directory C:\Program Files (x86)\DOSBox-0.74-2\ C_DRIVE
D local directory d:\temp\ D_DRIVE
E local directory d:\temp\ E_DRIVE
Z Internal Virtual Drive DOSBOX

Z:\>dir d:\image222.*
Directory of D:\.
File d:\image222.* not found.

Z:\>dir e:\image222.*
Directory of E:\.
IMAGE222 JPG 218,071 23-06-2019 19:49
1 File(s) 218,071 Bytes.
0 Dir(s) 262,111,744 Bytes free.

Thanks in advance.

Reply 1 of 3, by jmarsh

User metadata
Rank Oldbie
Rank
Oldbie

Both of those are expected behaviour.
You're not meant to mess with directories from outside DOSBox while they're mounted, but you can press ctrl-F4 to force a rescan of files.
The free space is limited to workaround some buggy dos programs that can't handle large amounts.

Reply 3 of 3, by lfl_038

User metadata
Rank Newbie
Rank
Newbie

Hi,
Thanks for your quick responses.
Reading another post, I discovered the -t floppy option and discovered also that mounting drive as floppy (using -t floppy) does not need to refresh the directory cache.