[Prev][Next][Index][Thread]
Re: E/D 1.99l under Warp mouse conflict summary
On Mon, 10 Apr 1995 12:06:10 -0500 (EST) you wrote:
>> Bengt Kayser
>>
> was recently asked by a few people to post a summary of the things that
>need to be done to get Executor 1.99l to work under OS/2 Warp.
>There have been a few conflicting reports here and there by myself and others
>so it appears that the bug may be system dependent [ ? ]
>
>What I have decided to do is to post all the settings for my
>Executor Session. Many, in fact MOST, of these settings should not be
>necessary, but since I am not able to reproduce the error of the mouse
>not working on but one device driver, I cannot test this.
>
>here are the settings for a Full Screen MDOS session that loads [ for me ]
>executor.bat which contains all my command line switches and the VESA
>TSR if you need it etc...
>------------------------------------------------------------------------------
>AUDIO_ADAPTER_SHARING None
>DOS_BREAK ON
>DOS_FILES 40
>DOS_HIGH ON
>DOS_SHELL C:\os2\mdos\command.com C:\os2\mdos
>DOS_UMB ON
>DPMI_MEMORY_LIMIT 16
>DPMI_NETWORK_SIZE 8
>HW_ROM_TO_RAM ON
>HW_TIMER ON
>INT_DURING_IO ON
>VIDEO_RETRACE_EMULATION OFF
>VIDEO_ROM_EMULATION ON [ your choice ]
>------------------------------------------------------------------------------
>EMS memory must also be set, because that's where executor gets its
>DPMI, but I was being hopeful with DPMI_MEM...8-)
AHEM,
I turned off the EMS page frame and set EMS size to zero and it still
works. Left DPMI to 16 i think...
>For most I have talked to, the solution appears to not need any of these
>settings changes. Rather, one only needs to add \OS2\MDOS\VMOUSE.SYS
>to the OS/2 config.sys file and reboot. This should technically
>be already in your config.sys, along with several other Vdrivers.
>One user did have VMOUSE but also needed \OS2\MDOS\MOUSE.COM in his
>autoexec.bat. This is normally only necessary for disk image boots [ VMB ]
>and not MDOS sessions [ VDM ].
I was that person, but now i don't need it. Don't ask why 'cause i
don't know what changed.
>So... I believe the fix can be summed up by taking these steps:
>
>Step 1: If this is a Microsoft mouse, I urge you to throw it away.
>You paid too much for a mouse that is a piece of trash, albeit a very
>ergonomic piece of trash. You are insulting your system. 8-)
Well i got my nice ergonomic mouse for $15 wholsale. Remember, the
people who make their mice and their programmers are two different
groups. Their mouse is one of the few MS products i'll use.
>Step 2: OK.. now that you've shelled out $10 for a mouse that works better than
>the smooth wonder of a rodent you just pitched, on to step two....
>
>Make sure your OS/2 config.sys file contains the line:
>[ insert your drive letter of course ]
>
>DEVICE=C:\OS2\MDOS\VMOUSE.SYS
>
>and reboot your computer...
>
>Step 3: If that didn't work, determine what kind of DOS sesison you are using.
>
>If you are running this through a VMB [ disk image ] make sure that
>\OS2\MDOS\MOUSE.COM is loaded. You should even be able to use your own
>mouse driver through the VMB.
>
>If you are certian that you are running a VDM [ MDOS session ] try
>running MOUSE.COM before you start Executor.
>[ This conflict may be hardware dependent see below ]
>
>Step 4: Compare your session settings with those above.
>Possible conflicts [ although I am just guessing ]
>are:
> HW_TIMER is not set to ON
> INT_DURING_IO is not ON
> etc...
>
>==============================================================================
>
>** If anyone is an OS/2 Warp user and is trying to run Executor on it, please
>send me your system specs, DOS session settings, whether or not you need
>mouse.com, and if you have had the problem at all. I'd like to compile a
>"final report" on this. Also include your mouse type.
>I am currently hypothesising that the usage of mouse.com is dependent on
>whether your mouse if COM port based, or bus based, or some other adapter
>perhaps.
>
>** I am also curious to find out how well E/D runs in a window for those
>of you who can achieve higher resolutions...
>
> Thanks to everyone,
>
> Charles "Free copy of E/D 2.0?? Do you mean it??" Hunter ;)
>
I no longer need mouse.com (for now). I use a serial mouse and the SIO
drivers. On my CL 5430, windowed VESA screens don't work. The computer
is:
ASUS PVI486SP3 w/ Am486DX4-100 w/ 16MB RAM
The Session settings are:
What you had above but no EMS and no XMS. DPMI is set to 12MB.
Thanks.
PS My copy of Write Now is 4.0.2 and it still has serious problems. No
mouse after typing and lotsa crashes. For example, make a table and
boom...
Baskin
UT Austin
Team OS/2