CPC-Mousepack 2.0 - Revision history

Phi2x: /* Pictures */

2024-06-05T23:27:13Z

Pictures

← Older revision		Revision as of 23:27, 5 June 2024
Line 45:		Line 45:
	Image:Mauspack 2 2.jpg\|		Image:Mauspack 2 2.jpg\|
	File:NoPicture.gif\|Inside of Interface		File:NoPicture.gif\|Inside of Interface
			</gallery>

			<gallery caption="CPC Mousepack">
			Mousepack-box.jpg\|The box
			Mousepack-contents.jpg\|Box open
	</gallery>		</gallery>

Prodatron at 11:12, 25 January 2023

2023-01-25T11:12:29Z

← Older revision		Revision as of 11:12, 25 January 2023
Line 3:		Line 3:
	A mouse for the Amstrad CPC. The CPC mousepack was distributed by the German company [[Reisware]].		A mouse for the Amstrad CPC. The CPC mousepack was distributed by the German company [[Reisware]].
	The mouse itself is an MSX mouse, which was sold by different companies like Sony and Philips for the MSX computers:		The mouse itself is an MSX mouse, which was sold by different companies like Sony and Philips for the MSX computers:

	https://www.msx.org/wiki/Sony_MOS-1		https://www.msx.org/wiki/Sony_MOS-1


	== Technical ==		== Technical ==
Line 19:		Line 21:

	As it is an MSX mouse you can find information how to read the mouse movements on an MSX here:		As it is an MSX mouse you can find information how to read the mouse movements on an MSX here:

	https://www.msx.org/wiki/Mouse/Trackball#Direct_usage_of_mouse		https://www.msx.org/wiki/Mouse/Trackball#Direct_usage_of_mouse

	Now it's maybe possible to understanding the following (old text of this article) in a better way:...		Now it's maybe possible to understanding the following (old text of this article) in a better way:...


	The exact mechanism that defines when the hardware does output the next 4bit fragment is unknown. The software does manipulate row 9 & row 6 signals, which does somehow request and/or acknowledge the fragments. Looking at the [[Media:CPC Mousepack 2.0 disassembly.txt\|disassembled software]], the hardware seems to work like so (not confirmed):		The exact mechanism that defines when the hardware does output the next 4bit fragment is unknown. The software does manipulate row 9 & row 6 signals, which does somehow request and/or acknowledge the fragments. Looking at the [[Media:CPC Mousepack 2.0 disassembly.txt\|disassembled software]], the hardware seems to work like so (not confirmed):
	switch from row0 to row9 --> invoke reading X counter (after 200 clks: MSB, after another 200 clks: LSB)		switch from row0 to row9 --> invoke reading X counter (after 200 clks: MSB, after another 200 clks: LSB)

Prodatron: in fact this is an MSX mouse

2023-01-25T11:11:37Z

in fact this is an MSX mouse

← Older revision		Revision as of 11:11, 25 January 2023
Line 1:		Line 1:
	[[Image:CPC mousepack 5.jpg\|thumb\|The mouse that came with the CPC mousepack]]		[[Image:CPC mousepack 5.jpg\|thumb\|The mouse that came with the CPC mousepack]]

	A mouse for the Amstrad CPC. The CPC mousepack was ~~manufactured~~ by the German company [[Reisware]].		A mouse for the Amstrad CPC. The CPC mousepack was distributed by the German company [[Reisware]].
			The mouse itself is an MSX mouse, which was sold by different companies like Sony and Philips for the MSX computers:
			https://www.msx.org/wiki/Sony_MOS-1

	== Technical ==		== Technical ==
Line 16:		Line 18:
	Bit0-7 Keyboard keys (dummy read from row 6 is done... to request/acknowledge something...?)		Bit0-7 Keyboard keys (dummy read from row 6 is done... to request/acknowledge something...?)

			As it is an MSX mouse you can find information how to read the mouse movements on an MSX here:
			https://www.msx.org/wiki/Mouse/Trackball#Direct_usage_of_mouse
			Now it's maybe possible to understanding the following (old text of this article) in a better way:...
	The exact mechanism that defines when the hardware does output the next 4bit fragment is unknown. The software does manipulate row 9 & row 6 signals, which does somehow request and/or acknowledge the fragments. Looking at the [[Media:CPC Mousepack 2.0 disassembly.txt\|disassembled software]], the hardware seems to work like so (not confirmed):		The exact mechanism that defines when the hardware does output the next 4bit fragment is unknown. The software does manipulate row 9 & row 6 signals, which does somehow request and/or acknowledge the fragments. Looking at the [[Media:CPC Mousepack 2.0 disassembly.txt\|disassembled software]], the hardware seems to work like so (not confirmed):
	switch from row0 to row9 --> invoke reading X counter (after 200 clks: MSB, after another 200 clks: LSB)		switch from row0 to row9 --> invoke reading X counter (after 200 clks: MSB, after another 200 clks: LSB)

MacDeath at 17:10, 19 December 2010

2010-12-19T17:10:39Z

← Older revision		Revision as of 17:10, 19 December 2010
Line 55:		Line 55:
	* [[Media:CPC MousePack 2.0.zip]] - driver disk with sample tools		* [[Media:CPC MousePack 2.0.zip]] - driver disk with sample tools

	[[Category:Input ~~device~~]][[Category:Peripherals]]		[[Category:Input Device]][[Category:Peripherals]]

MacDeath at 17:05, 19 December 2010

2010-12-19T17:05:15Z

← Older revision		Revision as of 17:05, 19 December 2010
Line 55:		Line 55:
	* [[Media:CPC MousePack 2.0.zip]] - driver disk with sample tools		* [[Media:CPC MousePack 2.0.zip]] - driver disk with sample tools

	[[Category:~~Hardware~~]] [[Category:Peripherals]]		[[Category:Input device]][[Category:Peripherals]]

Nocash: /* Technical */

2010-08-06T14:00:56Z

Technical

← Older revision		Revision as of 14:00, 6 August 2010
Line 16:		Line 16:
	Bit0-7 Keyboard keys (dummy read from row 6 is done... to request/acknowledge something...?)		Bit0-7 Keyboard keys (dummy read from row 6 is done... to request/acknowledge something...?)

	The exact mechanism that defines when the hardware does output the next 4bit fragment is unknown. The software does manipulate row 9 & row 6 signals, which does somehow request and/or acknowledge the fragments. Looking at the disassembled software, the hardware seems to work like so (not confirmed):		The exact mechanism that defines when the hardware does output the next 4bit fragment is unknown. The software does manipulate row 9 & row 6 signals, which does somehow request and/or acknowledge the fragments. Looking at the [[Media:CPC Mousepack 2.0 disassembly.txt\|disassembled software]], the hardware seems to work like so (not confirmed):
	switch from row0 to row9 --> invoke reading X counter (after 200 clks: MSB, after another 200 clks: LSB)		switch from row0 to row9 --> invoke reading X counter (after 200 clks: MSB, after another 200 clks: LSB)
	switch from row9 to row6 --> terminate X read		switch from row9 to row6 --> terminate X read

Nocash at 13:58, 6 August 2010

2010-08-06T13:58:16Z

← Older revision		Revision as of 13:58, 6 August 2010
Line 1:		Line 1:
	[[Image:CPC mousepack 5.jpg\|thumb\|The mouse that came with the CPC mousepack]]		[[Image:CPC mousepack 5.jpg\|thumb\|The mouse that came with the CPC mousepack]]

	A mouse for the Amstrad CPC. The CPC mousepack was manufactured by the German company [[Reisware~~]] and a similiar product to the more known one from the British company [[Advanced Memory Systems]] the [[AMX Mouse~~]].		A mouse for the Amstrad CPC. The CPC mousepack was manufactured by the German company [[Reisware]].

	~~Mousepack came with software. But nothing else is known about this product. Please supply!~~		== Technical ==

	== ~~Technical =~~=		The mouse/interface includes two buttons (0=pressed), and two signed 8bit motion counters (distance since last access: positive=up/left, negative=right/down). The buttons can be read via the normal BIOS keyboard scanning routines, the motion counters requires custom ASM code that reads & combines four 4bit fragments into two 8bit values (to be done once per frame).

	Unknown ~~how~~ to ~~access the mouse by software~~.		Joystick 1 Read (keyboard row 9):
			Bit0-3 Motion Counter (4bit fragment) (requires four reads to get the two signed 8bit values)
			Bit4 Left Mouse Button (aka Joystick Fire 2) (0=Pressed)
			Bit5 Right Mouse Button (aka Joystick Fire 1) (0=Pressed)
			Bit6 Unknown/Unused (aka Joystick Fire 3) (old CPC only, not CPC+)
			Bit7 Keyboard DEL key
			Joystick 2 Read (keyboard row 6):
			Bit0-7 Keyboard keys (dummy read from row 6 is done... to request/acknowledge something...?)

	The ~~Centaur screenshot~~ (~~see below~~) ~~claims that using~~ the ~~program with~~ "any other ~~mouse will cause malfunction~~" ~~- if that's true~~, then ~~it's apparently not [[AMX Mouse]] compatible~~.		The exact mechanism that defines when the hardware does output the next 4bit fragment is unknown. The software does manipulate row 9 & row 6 signals, which does somehow request and/or acknowledge the fragments. Looking at the disassembled software, the hardware seems to work like so (not confirmed):
			switch from row0 to row9 --> invoke reading X counter (after 200 clks: MSB, after another 200 clks: LSB)
			switch from row9 to row6 --> terminate X read
			switch from row6 to row9 --> invoke reading Y counter (after 66 clks: MSB, after another 280 clks: LSB)
			switch from row9 to row6 --> terminate Y read
			switch from row6 to row0 --> terminate all
			Whereas, one of the "terminate" actions does apparently reset the motion counter(s) to zero. Instead of "row0" one could use any other non-joystick row (ie. anything else than row6,row9). The "invoke" actions do request the MSB, which is then automatically followed (without another request) by the LSB after some hundred clock cycles.

	== Pictures ==		== Pictures ==

Nocash: /* Download */

2010-08-06T13:20:05Z

Download

← Older revision		Revision as of 13:20, 6 August 2010
Line 40:		Line 40:
	== Download ==		== Download ==

			* [[Media:CPC MousePack 2.0.zip]] - driver disk with sample tools

	[[Category:Hardware]] [[Category:Peripherals]]		[[Category:Hardware]] [[Category:Peripherals]]

Nocash: /* Pictures */

2010-01-12T13:57:50Z

Pictures

← Older revision		Revision as of 13:57, 12 January 2010
Line 20:		Line 20:
	Image:Mauspack 2 1.jpg\|		Image:Mauspack 2 1.jpg\|
	Image:Mauspack 2 2.jpg\|		Image:Mauspack 2 2.jpg\|
			File:NoPicture.gif\|Inside of Interface
	</gallery>		</gallery>

Nocash at 20:57, 8 January 2010

2010-01-08T20:57:16Z

← Older revision		Revision as of 20:57, 8 January 2010
Line 4:		Line 4:

	Mousepack came with software. But nothing else is known about this product. Please supply!		Mousepack came with software. But nothing else is known about this product. Please supply!

			== Technical ==

			Unknown how to access the mouse by software.

			The Centaur screenshot (see below) claims that using the program with "any other mouse will cause malfunction" - if that's true, then it's apparently not [[AMX Mouse]] compatible.

	== Pictures ==		== Pictures ==