I don't understand what's the issue here.
Either the program can potentially use mouse, or it cannot.
If it cannot use mouse, then the DOS mouse driver could be skipped altogether (i.e. not to load it).
If it can potentially use mouse, then the DOS mouse driver should be loaded. And, if the mouse driver is a problem with specific hardware, then the user can select to not load it during fdubcd boot up.
If, generally speaking, the program is capable of using mouse, and it happens to have some problem in certain specific cases/hardware, then the mouse driver should be still allowed for general use with the program. The user can always avoid loading the mouse driver in specific cases/hardware.
Either the program can potentially use mouse, or it cannot.
If it cannot use mouse, then the DOS mouse driver could be skipped altogether (i.e. not to load it).
If it can potentially use mouse, then the DOS mouse driver should be loaded. And, if the mouse driver is a problem with specific hardware, then the user can select to not load it during fdubcd boot up.
If, generally speaking, the program is capable of using mouse, and it happens to have some problem in certain specific cases/hardware, then the mouse driver should be still allowed for general use with the program. The user can always avoid loading the mouse driver in specific cases/hardware.