[Prev][Next][Index][Thread]
Re: E/D 1.99l under Warp mouse conflict summary
On Mon, 10 Apr 1995 23:46:42 -0500 (EST) you wrote:
>>
>> On Mon, 10 Apr 1995 12:06:10 -0500 (EST) you wrote:
>>
>> >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...
>>
>
>but can executor actually use this memory? [ ie the -stack -applzone etc
>switches ] I think you will find that you cannot allocate extra memory to
>these areas without some EMS or XMS.
I use the switches -nosplash -applzone 4096 -size 800x600 and it works
just fine.
>> >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....
>> >
>> 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:
>
> Did you just install SIO ? [ could that be why you don't need
> mouse.com? ]
Nope, had SIO since day one (Mid March for this machine)
>
>>
>> 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...
>>
>
>I haven't looked into this at all, but could it be because of lack of
>memory?
>
I doubt it since the applzone is at 4096.
Later
Baskin
UT Austin
Team OS/2