[Bug 47355] Making running DosBox reliable

wine-bugs at winehq.org wine-bugs at winehq.org
Wed Jun 12 01:03:55 CDT 2019


https://bugs.winehq.org/show_bug.cgi?id=47355

Lantizia <s.maddox at lantizia.me.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |s.maddox at lantizia.me.uk

--- Comment #1 from Lantizia <s.maddox at lantizia.me.uk> ---
Perhaps I'm missing something.  But are you hoping if Wine encounters a
exe/com/pif/bat/etc.. file - that it'll ask the system each and every time what
should be running it (even if it is within the bottle) so that if mime-info
reports it's a pif or 16-bit com/exe DOS executable - the system will then
start up DOSBox itself (or whatever is associated with it)?

Even if the above made sense, how would DOSBox know what to map drive letters
to so it can access the bottle or related drives (like CD's) properly?

You've linked my bug: https://bugs.winehq.org/show_bug.cgi?id=46125

But I don't see this solves the issue there... as a setup.exe from a CD is
calling another exe that calls a pif that calls a batch file - so DOSBox at a
minimum needs to know where drive C: is and where drive D: is for this to
actually work.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list