Hi Arkady,

Which would recomend we use to work on the widest array of systems...
CuteMouse 1.9.1 or 2.0a4? We don't need any fancy support (we don't need
scroll wheels, etc), we just need it to be robust... meaning, not to crash.

Would you suggest one over the other?

Thanks Arkady!

Andrew


Arkady V.Belousov wrote:
> Hi!
> 
> 24-Авг-2006 02:51 [EMAIL PROTECTED] (Andrew Greenberg) wrote to
> freedos-user@lists.sourceforge.net:
> 
> AG> We're using cutemouse 2.0 alpha4 under FreeDOS 1.1.35W (Build 2035W),
> AG> HIMEM64 3.11,
> 
>      This (3.11) may be reason. Update to latest edition:
> 
> ftp://ftp.devoresoftware.com/downloads/emm386/emmx225.zip
> 
> and try again.
> 
> AG> and FreeCOM 0.84-pre. We're using it on a large range of
> AG> systems, and we're getting lots of lock ups (on maybe 10% of the
> AG> systems). We don't mind if cutemouse fails and there's no mouse, but we
> AG> do mind if it locks up up the system (which is what it's doing).
> AG> Any ideas on what we might try to stop it from locking up?
> AG> For example:
> AG> 1. All of our systems are fairly modern, so there's no COM mouses (that
> AG> we know of).
> 
>      There was changed (fixed) EMM386 so, that it now correctly preserves
> interrupt flag when calling INT15 - whereas CuteMouse 2.0 depends precisely
> on INT15 BIOS services. Before this change in EMM386, CuteMouse was locked
> (at least) in QEMU. This is why I recommend you firstly try latest EMM386
> edition.
> 
> AG> So should we use /P?
> 
>      No, PS/2 searched first.
> 
> AG> 2. We don't understand /Y - if this is important, can someone explain it
> AG> to us?
> 
>      Do you read ctmouse.txt "(This is because the Mouse Systems protocol
> defines no detection sequence). Option /Y in the command line disables Mouse
> Systems protocol support and prevents driver installation if no mouse with
> Microsoft or Logitech protocol is found."? What precisely not understand by
> you there?
> 
>      Let me rephrase: mice with Mouse Systems protocols can't be detected,
> so driver always installs itself on first available COM port (with support
> of Mouse System protocol) if there are no PS/2 or serial mice with other
> protocols. To prevent driver installation when there are no mice at all, use
> /y option.
> 
> AG> 3. Could this be a memory issue, and /W would help?
> 
>      I doubt.
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user

-- 

---------------------------------------------------------------------------
       Andrew Greenberg - [EMAIL PROTECTED] - 503.788.1343
---------------------------------------------------------------------------


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to