That's an interesting idea. Not sure that it's super-useful though unless you could somehow make it smart enough to automatically mount floppy and cdrom drives correctly too (a non-trivial task considering the different modes and such that are possible).
I'd imagine the same reason why I didn't auto for delete and friends; errant or malicious batch file/exes. I've added exclusion of drive c and yet to be written is having automount only work from keyboard input. Once something is mounted though, auto or manual, are once again exposed to such a risk. For that, another safety precaution could be to add a confirmation for delete/overwrite/modify when coming from batch or exe.
In shell_misc.cpp, remove all the lines related to the handling of execution from a different drive.
It will fix the bug. However, typing "d:\game\game.exe" without mounting D as a drive will not work (even though you have d:\game\game.exe in your real hard/floppy drive).
Last edited by ykhwong on 2006-06-04, 13:59. Edited 1 time in total.
Stockholm, Sweden, Europe, Earth Interests: Old games & young women
Uh uh - this sounds convenient, but also dangerous to me. Like the way Windows likes to autoplay my CD's/DVD's, hide file extensions, etc.
I would like to see more control of what gets auto-mounted and when.
I want something that allows me to declare auto-mounting of drive C for unsafe, but D and E and all local read-only media for safe. Give me something like
1# automount - Allow DOSBox to automatically mount drives: true, false, paths 2# autopaths - List of paths that are safe to automount when automount=paths. 3automount=paths 4autopaths=D:\ E:\ /mnt/cdrom
Also imo it's dangerous because it removes the responsibility of the user.
And with the availability of frontends there's not much need for it anyways.
Stockholm, Sweden, Europe, Earth Interests: Old games & young women
Maybe a more intelligent mount command is what is needed? Something that will try to detect the type of media being mounted and automagically use the correct mount type (-t), label, ioctl, cd-number, aspi, ...
It seems to me that we spend a lot of time asking newbies about how they mounted their virtual drives, and suggest adding this and that option.
> It seems to me that we spend a lot of time asking newbies about how
> they mounted their virtual drives, and suggest adding this and that option.
But frontends seem to be the more straightforward solution to this,
maybe their use should be forced even more at least for first time
users and newbies.
The follwing idea was actually made to ask users to automount drives before as you see the screenshot.
I also agree that using frontend is the best choice to easily mount drives.
However, lots of newbies in my page have difficulties with mount drives in dosbox as Minimax mentioned. (Some of them do not try to use even frontends though I posted a thread about the introduction of recent frontends)
The current automount patch is basically planned to work only in win32 by ih8registrations, so it will not work on other platforms.
Attachments
Last edited by ykhwong on 2006-11-11, 07:31. Edited 1 time in total.
Stockholm, Sweden, Europe, Earth Interests: Old games & young women
ykhwong - I think the newbie that blindly tries to switch to C: and D: will be very confused when confronted with that question.
S/he will have no idea what all that mounting is about. They will start looking for a horse to mount and ride off into the sunset...
Better rephrase it and ask the newbie something like this:
1Z:\>c: 2Do really you want to give DOSBox access to everything on your real C: drive? Yes or no? 3 4Z:\>d: 5Do really you want to give DOSBox access to everything on your real D: drive? Yes or no? 6 7Z:\>g: 8Do you want to give DOSBox access to your real CD/DVD-ROM drive? Yes or no? 9 10Z:\>i: 11Do you want to give DOSBox access to your real CD/DVD-ROM drive? Yes or no?
Last edited by MiniMax on 2006-11-11, 15:15. Edited 1 time in total.