mode the games choppy or unstable.
-- Původní e-mail --
Od: ZB
Komu: Discussion and general questions about FreeDOS.
Datum: 22. 1. 2022 15:54:05
Předmět: Re: [Freedos-user] Cutemouse /O
"It was serial mouse used in Microsoft mode ("mouse /3"). Connected to Mul
It was serial mouse used in Microsoft mode ("mouse /3"). Connected to Multi
I/O adapter inserted into slot of my trusty Soyo-SiS mobo. It's Fellowes
"Combo" mouse, which has PS/2 connector and PS/2 <-> RS-232 adapter
(currently in use).
As I wrote: I did a comparison, and no problem when using
Hi ZB,
Please, note: CuteMouse v2.1 beta4 probably is flawed. One day
I was tried it with "Civilization", but when using this mouse
driver the game always has been hung after relatively short
>> period of time (like 30-40 moves) and then I wasn't able to
do any more input (it was beeping at
Please, note: CuteMouse v2.1 beta4 probably is flawed. One day I was tried
it with "Civilization", but when using this mouse driver the game always has
been hung after relatively short period of time (like 30-40 moves) and then
I wasn't able to do any more input (it was beeping at me like in case
> a) in germany we have a saying "Kein Backup, kein Mitleid" which
> translates roughly to "no backup, no pity"
> b) one of the advantages of open source software is that you have
> automatically backups on a bazillion of computers.
It happened a long time ago, and I actually did have backups
Ok the editor eding modificstion of cutemouse
Enviado desde mi Samsung Mobile de Claro
Get Outlook para Android<https://aka.ms/AAb9ysg>
From: Ladislav Lacina
Sent: Friday, January 21, 2022 5:30:11 PM
To: freedos-user@lists.sourceforge.net
Subject: Re: [F
The text editor Blocek has experimental support for mouse wheel when using
with CuteMouse /O___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
> Also,
> through a series of unfortunate hard-drive problems and corruptions,
> I managed to lose the source code for MOUSKEYS. So, in order to
> "upgrade" MOUSKEYS to support wheels, I would need to start by
> recreating it from scratch again (basically, I would need to
> reverse-engineer my
> CuteMouse doesn't have any of these "elevating" resources. But
> whatever the mouse sends is passed over to the application. In DOS
> it is up to Appication to uses it.
Not quite. CTMOUSE does support a mouse wheel, but it has a "special" way of
accessing it in the Mouse Driver API (INT 33h).
The /O switch makes cutmouse detect scroll wheel.
Den 2022-01-21 kl. 16:59, skrev Mercury Thirteen via Freedos-user:
Most mice operate in a "staged" manner; that is, upon power-up even
the most sophisticated mouse emulates a basic two button affair, until
software jumps through a series of
CuteMouse doesn't have any of these "elevating" resources. But whatever
the mouse sends is passed over to the application. In DOS it is up to
Appication to uses it
Alain
Em 21/01/2022 12:59, Mercury Thirteen via Freedos-user escreveu:
Most mice operate in a "staged" manner; that is, upon
Most mice operate in a "staged" manner; that is, upon power-up even the most
sophisticated mouse emulates a basic two button affair, until software jumps
through a series of hoops to elevate its capabilities by sending a series of
magic sequences of commands. The problem is that most
I believe the problem with the scroll wheel is that it doesn't generate
an interrupt, so if the mouse driver doesn't specifically look for the
scrool wheel, there's no way for the computer or operating system to
know that it is being used. I had a similar problem under windows
several years
There is a feature in DOSBox-X that "emulates" a scroll wheel. Scrolling
the wheel does the same thing as moving the keyboard arrows up and down.
Also, there is a program called TSR - MOUSKEYS, written by Bret Johnson.
MOUSKEYS emulates any mouse movement (up, down, left, right). In some
On Fri, Feb 12, 2021 at 04:38:52PM -0800, Ralf Quint wrote:
> That is rather hazy, as in your initial post, you only mentioned you tried
> "keyboard only", which is not the same as using another mouse (driver)...
Just tried gmouse driver, and this one gave no problem. Yesterday I tried
CuteMouse
On 2/12/2021 3:42 PM, ZB wrote:
On Fri, Feb 12, 2021 at 03:35:13PM -0800, Ralf Quint wrote:
And have you tried both another mouse and another mouse driver to determine
that the problem is indeed with Cutemouse?
The problem indeed seems to be in the Cutemouse, since without Cutemouse
I see no
On Fri, Feb 12, 2021 at 03:35:13PM -0800, Ralf Quint wrote:
> And have you tried both another mouse and another mouse driver to determine
> that the problem is indeed with Cutemouse?
The problem indeed seems to be in the Cutemouse, since without Cutemouse
I see no problem anymore. Only if
And have you tried both another mouse and another mouse driver to
determine that the problem is indeed with Cutemouse?
On 2/12/2021 3:22 PM, ZB wrote:
On Fri, Feb 12, 2021 at 11:54:33PM +0100, Eric Auer wrote:
Which hardware are you using
My trusted Soyo-SiS mobo with Fellowes "Combo"
On Fri, Feb 12, 2021 at 11:54:33PM +0100, Eric Auer wrote:
> Which hardware are you using
My trusted Soyo-SiS mobo with Fellowes "Combo" mouse.
> and which command line options have you tried?
At the moment just "mouse /3" (Microsoft mode).
> Have you compared to other
> cutemouse versions,
Hi!
Which hardware are you using and which command line
options have you tried? Have you compared to other
cutemouse versions, in particular in the 1.9 range?
Regards, Eric
> I've got a feeling there's something in a need for fix; I tried today to
> play Civilization, but using this mouse
On Wednesday 02 July 2008, Eric Auer wrote:
Hi everybody,
Hi Eric :-)
Known issues:
Hey, I noticed some months ago that there is a weird behaviour in ctmouse...
I have a KVM switch, and if I change my video mode, the keyb/mouse are freezing
for about 1-2 seconds. It doesn't happen if I
On Thursday 03 July 2008, Mateusz Viste wrote:
Hey, I noticed some months ago that there is a weird behaviour in ctmouse...
Oooops, wasn't meant to go to the group! Sorry!
Mateusz Viste
--
You'll find my public OpenPGP key at http://mateusz.viste.free.fr/pub_key
signature.asc
Description:
Eric Auer wrote:
almost a year after cutemouse 2.1 beta 3 I can
present ctmouse 2.1 beta 4 :-). This is a version
with debugging output in the PS2 config stuff.
Is this the debugging output or is it garbage?
***
CuteMouse v2.1 beta4 [FreeDOS]
5/3 0/33/3 0/34/3 0/07/@ 0/@7/0 0/04/0
2008/06/03 17:48 +0200, Japheth
Also bad is the direction
in which the fields are defined (from high to low), making it very difficult
to convert C headers to ASM include files.
Flatly against the Intel conventions, which in all respects number all
integers from low to high.
Hi Robert!
present ctmouse 2.1 beta 4 :-). This is a version
with debugging output in the PS2 config stuff.
Is this the debugging output or is it garbage?
CuteMouse v2.1 beta4 [FreeDOS]
5/3 0/33/3 0/34/3 0/07/@ 0/@7/0 0/04/0 0/0Installed at PS/2
port
7/3 0/30/1 0/12/5 0/5
This is
Eric Auer wrote:
CuteMouse v2.1 beta4 [FreeDOS]
5/3 0/33/3 0/34/3 0/07/@ 0/@7/0 0/04/0 0/0Installed at PS/2
port
7/3 0/30/1 0/12/5 0/5
This is debugging output about the mouse and/or wheel detection.
But why is it turned on by default? Because it's a beta driver for
testing purposes
Maybe it is context sensitive in TASM, 0 in .data and nop in .code?
I believe NASM has a whole range of ways to align things, including
pad with user-specified value and pick a multi byte noop machine
code instruction where appropriate but you would have to check the
docs which is selected
It's fixed in v1.8.
Odd, my report already was about 1.80 ...
Ok, then you forgot to tell us that you have access to a time machine. Because
the versions stored on my site are v1.7 and v1.8pre.
Then an error message would have been better than a 0 value...
Sure. Looking back, many things
2008/06/03 08:42 +0200, Japheth
Indeed. I couldn't imagine anyone using bitfields seriously, because there are
some stupid design flaws.
I did, using only the offsets.
-
Check out the new SourceForge.net Marketplace.
Hi!
Eric Auer wrote:
almost a year after cutemouse 2.1 beta 3 I can
present ctmouse 2.1 beta 4 :-). This is a version
with debugging output in the PS2 config stuff.
Compared to beta 3, it adds support for touchpads
in Dell Inspiron 1501 (where int 15.c204 PS2 ident
fails) and changes the
Hi,
thanks for posting your results!
- TASM evendata pads with 0, JWASM even pads with 0fch
I do not know how to change this, I just used db 0.
this is indeed hard-coded in the source and will be used only if a 16-bit CODE
segment has to be padded by 1 byte. The reason why not just 0x00
Hi!
28-Авг-2006 18:05 [EMAIL PROTECTED] (Andrew Greenberg) wrote to
freedos-user@lists.sourceforge.net:
AG Which would recomend we use to work on the widest array of systems...
AG CuteMouse 1.9.1 or 2.0a4? We don't need any fancy support (we don't need
AG scroll wheels, etc), we just need it to
On Wed, 30 Aug 2006 04:20:04 +0400, you wrote:
Hi,
If you need wide array of systems and not need wheels support -
1.9.1 is your choice. 1.9.1 works with PS/2 mice on higher levels (through
BIOS, not directly with hardware) and, thus, should be more portable and
reliable.
Agree! 1.9.1
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
Probably 1.9.1 for stability. Although 2.0a4 works quite well for all
of my computers.
On 8/28/06, Andrew Greenberg [EMAIL PROTECTED] wrote:
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
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:
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
37 matches
Mail list logo
