CSpect:known bugs - Revision history

Ped7g: DMA WR3 enable bit bug reported by Holub, tested with dmaDebug.sna test and by checking VHDL

2025-09-23T14:41:57Z

DMA WR3 enable bit bug reported by Holub, tested with dmaDebug.sna test and by checking VHDL

← Older revision		Revision as of 15:41, 23 September 2025
Line 18:		Line 18:
	** More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border. (may be related to soft-reset)		** More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border. (may be related to soft-reset)
	** DMA: reading-registers are a bit off (for example status bit5+0 not reset correctly after LOAD, probably few more (but core 3.1.5 also reads bit0 wrongly, so always test own code with all target platforms))		** DMA: reading-registers are a bit off (for example status bit5+0 not reset correctly after LOAD, probably few more (but core 3.1.5 also reads bit0 wrongly, so always test own code with all target platforms))
			** DMA: setting WR3 enable bit does NOT start transfer (ie. CSpect is emulating the East Germany clone chip, HW Next and Zilog DMA chips will start the transfer after such write like WR3 = 0xC0)
	** NextRegs $09, $34, $41, $8E read incorrectly (reads after certain writes produce wrong value) (but also the test is checking 3.1.5 behaviour, needs update to 3.1.10)		** NextRegs $09, $34, $41, $8E read incorrectly (reads after certain writes produce wrong value) (but also the test is checking 3.1.5 behaviour, needs update to 3.1.10)
	** debugger: the step-over F8 does run interrupt handler every 16-20ms (as part of debug-live-screen-view drawing), so it's almost after every F8 press		** debugger: the step-over F8 does run interrupt handler every 16-20ms (as part of debug-live-screen-view drawing), so it's almost after every F8 press

Ped7g: V2.19.1.0 refresh (2)

2023-01-25T20:53:37Z

V2.19.1.0 refresh (2)

← Older revision		Revision as of 21:53, 25 January 2023
Line 10:		Line 10:
	** DMA: Zilog mode is not implemented (port 0x0B) (but zxnDMA does listen to both ports, so SW using 0x0B will get one byte shorter transfers)		** DMA: Zilog mode is not implemented (port 0x0B) (but zxnDMA does listen to both ports, so SW using 0x0B will get one byte shorter transfers)
	* subtle differences		* subtle differences
			** sprites: in border vs tiles in modes 3,4 and 5 are not drawn same weird way as HW
	** sprites: the wrap-around the 512x512 coordinate space is only partially implemented in extreme cases (relative sprite so far from anchor that x8 scale wraps it back onto screen)		** sprites: the wrap-around the 512x512 coordinate space is only partially implemented in extreme cases (relative sprite so far from anchor that x8 scale wraps it back onto screen)
	** NextReg $02 implementation of soft-reset does something, but not the same thing like HW		** NextReg $02 implementation of soft-reset does something, but not the same thing like HW
Line 40:		Line 41:
	* direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5, all common ones should work)		* direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5, all common ones should work)
	* sprites: something something about default clipping... just set clip windows explicitly in your SW.		* sprites: something something about default clipping... just set clip windows explicitly in your SW.
	* sprites: clipping in non-over-border configuration is maybe wrong (~~further~~ fixed in 2.19.1.0~~, needs more testing~~)		* sprites: clipping in non-over-border configuration is maybe wrong (probably fixed, needs more testing with 2.19.1.0 or later)
	* fixed by V2.19.0.3 <del>stencil mode is not implemented</del>, needs more testing		* fixed by V2.19.0.3 <del>stencil mode is not implemented</del>, needs more testing

Ped7g: V2.19.1.0 refresh

2023-01-25T20:46:16Z

V2.19.1.0 refresh

Ped7g: L2 clipping crash documented

2023-01-23T13:25:06Z

L2 clipping crash documented

← Older revision		Revision as of 14:25, 23 January 2023
Line 6:		Line 6:
	** modifications to NextRegs done by CPU propagate to rendering usually only once per scanline, usually retroactively for whole current scanline		** modifications to NextRegs done by CPU propagate to rendering usually only once per scanline, usually retroactively for whole current scanline
	* major differences / missing features		* major differences / missing features
			** L2 mode 320x256 and 640x256 could crash when clip.X2 > clip.X1 (should be fixed in next version)
	** blending modes: improved greatly in V2.19.0.3, blending only L2 priority colours wrongly.		** blending modes: improved greatly in V2.19.0.3, blending only L2 priority colours wrongly.
	** NextZXOS streaming API doesn't work (the initialization of stream fails - rst 8 service 0x86 ; DISK_STRMSTART)		** NextZXOS streaming API doesn't work (the initialization of stream fails - rst 8 service 0x86 ; DISK_STRMSTART)

Ped7g at 17:44, 20 January 2023

2023-01-20T17:44:07Z

← Older revision		Revision as of 18:44, 20 January 2023
Line 12:		Line 12:
	** sprites: the wrap-around the 512x512 coordinate space is only partially implemented in extreme cases (relative sprite so far from anchor that x8 scale wraps it back onto screen)		** sprites: the wrap-around the 512x512 coordinate space is only partially implemented in extreme cases (relative sprite so far from anchor that x8 scale wraps it back onto screen)
	** NextReg $02 implementation of soft-reset does something, but not the same thing like HW		** NextReg $02 implementation of soft-reset does something, but not the same thing like HW
	** NextBASIC SPECTRUM command may load SNA file with wrong ROM paged in (~~may be~~ related to ~~soft-reset~~)		** NextBASIC SPECTRUM command may load SNA file with wrong ROM paged in (very likely related to SW NMI trigger emulation <code>nextreg 2,8</code> ROM2 $0aab)
	** NextZXOS browser is unable to load SNA/SNX/Z80 files in latest distribution (does work with older 3.1.5 core NextZXOS) (may be related to ~~soft-reset~~)		** NextZXOS browser is unable to load SNA/SNX/Z80 files in latest distribution (does work with older 3.1.5 core NextZXOS) (may be related to SW NMI)
	** More >> ZX80 and ZX81 modes reset and hangs on a black screen while launching the Paul Farrow emulators. (may be related to soft-reset)		** More >> ZX80 and ZX81 modes reset and hangs on a black screen while launching the Paul Farrow emulators. (may be related to soft-reset)
	** More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border. (may be related to soft-reset)		** More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border. (may be related to soft-reset)

Ped7g: V2.19.0.3 refresh

2023-01-19T22:28:59Z

V2.19.0.3 refresh

← Older revision		Revision as of 23:28, 19 January 2023
Line 1:		Line 1:
	CSpect V2.16.6.0		CSpect V2.19.0.3
	* intentional for performance reasons:		* intentional for performance reasons:
	** sprites: the collision bit is not implemented		** sprites: the collision bit is not implemented
	** sprites rendering is not one-scanline-buffer delayed and all changes in sprites affect current scanline		** sprites rendering is not one-scanline-buffer delayed and all changes in sprites affect current scanline
	** ~~(moved a bit in 2.16.0)~~ modifications to NextRegs done in copper propagate to rendering usually only once per scanline, the state for rendering is sampled after right border area (ahead of copper wait h=39), affecting previous line instead of next (palette changes, X/Y offsets, etc)		** modifications to NextRegs done in copper propagate to rendering usually only once per scanline, the state for rendering is sampled after right border area (ahead of copper wait h=39), affecting previous line instead of next (palette changes, X/Y offsets, etc)
	** modifications to NextRegs done by CPU propagate to rendering usually only once per scanline, usually retroactively for whole current scanline		** modifications to NextRegs done by CPU propagate to rendering usually only once per scanline, usually retroactively for whole current scanline
	* major differences / missing features		* major differences / missing features
	** blending modes: ~~wrong, but the test is not comprehensive (HW core 3~~.1.~~5 now blends Layer2+ULA in different way ([https://github~~.~~com/MrKWatkins/ZXSpectrumNextTests/issues/8 details]))~~		** blending modes: improved greatly in V2.19.0.3, blending only L2 priority colours wrongly.
	** vertical ULA clipping is not working in Timex modes
	** ULA scroll and half-width scroll is not implemented in Timex modes
	** NextZXOS streaming API doesn't work (the initialization of stream fails - rst 8 service 0x86 ; DISK_STRMSTART)		** NextZXOS streaming API doesn't work (the initialization of stream fails - rst 8 service 0x86 ; DISK_STRMSTART)
	** DMA: Zilog mode is not implemented (port 0x0B)		** DMA: Zilog mode is not implemented (port 0x0B) (but zxnDMA does listen to both ports, so SW using 0x0B will get one byte shorter transfers)
	* subtle differences		* subtle differences
	** ~~there's still~~ something not ~~completely right about Enhanced ULA colours, maybe just default values are~~ wrong~~, or even something~~ is ~~emulated wrongly?~~ (~~test TFalBUla~~.~~sna~~)		** sprites: the wrap-around the 512x512 coordinate space is only partially implemented in extreme cases (relative sprite so far from anchor that x8 scale wraps it back onto screen)
			** NextReg $02 implementation of soft-reset does something, but not the same thing like HW
			** NextBASIC SPECTRUM command may load SNA file with wrong ROM paged in (may be related to soft-reset)
			** NextZXOS browser is unable to load SNA/SNX/Z80 files in latest distribution (does work with older 3.1.5 core NextZXOS) (may be related to soft-reset)
			** More >> ZX80 and ZX81 modes reset and hangs on a black screen while launching the Paul Farrow emulators. (may be related to soft-reset)
			** More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border. (may be related to soft-reset)
	** DMA: reading-registers are a bit off (for example status bit5+0 not reset correctly after LOAD, probably few more (but core 3.1.5 also reads bit0 wrongly, so always test own code with all target platforms))		** DMA: reading-registers are a bit off (for example status bit5+0 not reset correctly after LOAD, probably few more (but core 3.1.5 also reads bit0 wrongly, so always test own code with all target platforms))
	** NextReg $02 implementation of soft-reset does something, but not the same thing like HW
	** NextBASIC SPECTRUM command may load SNA file with wrong ROM paged in (may be related to soft-reset implementation?)
	** sprites: the wrap-around the 512x512 coordinate space is only partially implemented in extreme cases (relative sprite so far from anchor that x8 scale wraps it back onto screen)
	** default value: $6E and $6F are supposed to be fixed since V2.12.30, but the SNA test still reads zeroes
	** some NextRegs read as zero until they are written into first (quick-boot mode with SNA file without full NextZXOS image) (for example regs <del>$03,</del> $12, $13, $14, $42, $4A, $4B, $4C)
	** NextRegs $09, $34, $41, $8E read incorrectly (reads after certain writes produce wrong value) (but also the test is checking 3.1.5 behaviour, needs update to 3.1.10)		** NextRegs $09, $34, $41, $8E read incorrectly (reads after certain writes produce wrong value) (but also the test is checking 3.1.5 behaviour, needs update to 3.1.10)
	** debugger: the step-over F8 does run interrupt handler every 16-20ms (as part of debug-live-screen-view drawing), so it's almost after every F8 press~~, and may force interrupts-enabling, use only F7 step-into when debugging parts of code which expect interrupts disabled~~		** debugger: the step-over F8 does run interrupt handler every 16-20ms (as part of debug-live-screen-view drawing), so it's almost after every F8 press
	** divMMC automap-enabled traps certain addresses even when RAM is mapped to MMU0/MMU1
	** Z80: <code>di : halt</code> doesn't put CPU in infinite loop waiting for NMI, but proceeds further		** Z80: <code>di : halt</code> doesn't put CPU in infinite loop waiting for NMI, but proceeds further
	** Z80: block of prefixes/instructions 0xDD/0xFD/EI does not inhibit masked interrupts		** Z80: block of prefixes/instructions 0xDD/0xFD/EI does not inhibit masked interrupts
	** Z80: when masked interrupt handler is entered, the interrupts remain enabled (IFF1=1, IFF2=1)
	** F3 reset does not autodetect NextZXOS 2.06 vs 2.07 when running with card-image, so 2.06 image ends with purple stripes.
	** More >> ZX80 and ZX81 modes reset and hangs on a black screen while launching the Paul Farrow emulators.
	** More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border.
	* recently fixed:		* recently fixed:
	** <del>~~tilemode 80x32~~: ~~horizontal scrolling has wrong scale~~ (~~probably expecting only 320x256 offsets~~, ~~confused by 640x256~~)</del>		** <del>CTC timing is affected by the Z80N clock speed. It should be using a constant 28Mhz reference clock.</del>
	** <del>~~NextReg $02 hard~~-~~reset~~</del>		** <del>vertical ULA clipping is not working in Timex modes</del>
	** ~~verified fixed in V2~~.17.0.0 <del>~~CTC timing~~ is ~~affected by the Z80N clock speed. It should be using a constant 28Mhz reference clock.~~</del>		** <del>ULA scroll and half-width scroll is not implemented in Timex modes</del>
			** <del>Z80: when masked interrupt handler is entered, the interrupts remain enabled (IFF1=1, IFF2=1)</del>
			** <del>divMMC automap-enabled traps certain addresses even when RAM is mapped to MMU0/MMU1</del>
			** <del>something not completely right about Enhanced ULA colours (test TFalBUla.sna)</del>
			** <del>F3 reset does not autodetect NextZXOS 2.06 vs 2.07 when running with card-image, so 2.06 image ends with purple stripes.</del>
			** <del>some NextRegs read as zero until they are written into first (quick-boot mode with SNA file without full NextZXOS image)</del>
			** <del>Layer2 640x256x4bpp clipping is broken</del> (V2.19.0.3 does fix this correctly, was still broken before)

	not verified in V2.16.6.0 (but known bugs of older versions, may be still present):		not verified in V2.19.0.3 (but known bugs of older versions, may be still present):
	* CTC time constant of 0 causes incorrect code execution.		* CTC time constant of 0 causes incorrect code execution.
	* stencil mode is not implemented
	* the initial file-import sequence of CP/M BIOS fails. (get cpm-a.p3d file from somebody with a working clean CP/M installation and copy that into c:/NextZXOS, or use other emulator to create the file)		* the initial file-import sequence of CP/M BIOS fails. (get cpm-a.p3d file from somebody with a working clean CP/M installation and copy that into c:/NextZXOS, or use other emulator to create the file)
	* default ULA palette after power on (quick boot without NextZXOS) is slightly different		* default ULA palette after power on (quick boot without NextZXOS) is slightly different
Line 41:		Line 39:
	* direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5, all common ones should work)		* direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5, all common ones should work)
	* sprites: something something about default clipping... just set clip windows explicitly in your SW.		* sprites: something something about default clipping... just set clip windows explicitly in your SW.
	* sprites: clipping in non-over-border configuration is maybe wrong		* sprites: clipping in non-over-border configuration is maybe wrong (probably fixed in 2.19.0.3, needs more testing)
	* fixed ~~(but needs thorough test)~~ <del>~~Layer2 640x256x4bpp clipping~~ is ~~broken (and rendering partially too? should be fixed in next release)~~</del>		* fixed by V2.19.0.3 <del>stencil mode is not implemented</del>, needs more testing

	Platform Specific (may be already fixed):		Platform Specific (may be already fixed):
	* Mac: Mouse does not work / behaves erratically		* Mac: Mouse does not work / behaves erratically
	* Mac: after launch keyboard being irresponsive - try "alt+tab" to other app and back		* Mac: after launch keyboard being irresponsive - try "alt+tab" to other app and back
	* ~~works in 2.16.5.0 <del>~~Linux: ~~the copper disassembly window added in 2.15.01~~ (ctrl+alt+c) does not ~~draw its content and remains as empty frame~~ (~~after debugging the~~ plugin~~: the winform doesn't receive paint messages from the emulator, same winform code running as stand-alone app without emulator~~ does draw ~~in linux)</del>~~		* Linux: (some/all?) plugin windows like nextregisters (ctrl+alt+r) does not refresh while in debugger
			* Linux: (some/all?) plugin windows like nextregisters (ctrl+alt+r) does draw hover-hint tooltip only for one frame, then it becomes invisible

	Not a bug:		Not a bug:
	* CSpect works with "-sound" (does switch sounds OFF), but shows only black screen without it:		* CSpect works with "-sound" (does switch sounds OFF), but shows only black screen without it:
	** you forgot to install OpenAL, check the ReadMe.txt of the emulator.		** you forgot to install OpenAL, check the ReadMe.txt of the emulator.

SevenFFF at 19:35, 18 January 2023

2023-01-18T19:35:31Z

← Older revision		Revision as of 20:35, 18 January 2023
Line 26:		Line 26:
	** Z80: when masked interrupt handler is entered, the interrupts remain enabled (IFF1=1, IFF2=1)		** Z80: when masked interrupt handler is entered, the interrupts remain enabled (IFF1=1, IFF2=1)
	** F3 reset does not autodetect NextZXOS 2.06 vs 2.07 when running with card-image, so 2.06 image ends with purple stripes.		** F3 reset does not autodetect NextZXOS 2.06 vs 2.07 when running with card-image, so 2.06 image ends with purple stripes.
			** More >> ZX80 and ZX81 modes reset and hangs on a black screen while launching the Paul Farrow emulators.
			** More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border.
	* recently fixed:		* recently fixed:
	** <del>tilemode 80x32: horizontal scrolling has wrong scale (probably expecting only 320x256 offsets, confused by 640x256)</del>		** <del>tilemode 80x32: horizontal scrolling has wrong scale (probably expecting only 320x256 offsets, confused by 640x256)</del>
Line 40:		Line 42:
	* sprites: something something about default clipping... just set clip windows explicitly in your SW.		* sprites: something something about default clipping... just set clip windows explicitly in your SW.
	* sprites: clipping in non-over-border configuration is maybe wrong		* sprites: clipping in non-over-border configuration is maybe wrong
	* More >> ZX80 and ZX81 modes reset and hangs on a black screen while launching the Paul Farrow emulators.
	* More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border.
	* fixed (but needs thorough test) <del>Layer2 640x256x4bpp clipping is broken (and rendering partially too? should be fixed in next release)</del>		* fixed (but needs thorough test) <del>Layer2 640x256x4bpp clipping is broken (and rendering partially too? should be fixed in next release)</del>

SevenFFF at 19:33, 18 January 2023

2023-01-18T19:33:29Z

← Older revision		Revision as of 20:33, 18 January 2023
Line 40:		Line 40:
	* sprites: something something about default clipping... just set clip windows explicitly in your SW.		* sprites: something something about default clipping... just set clip windows explicitly in your SW.
	* sprites: clipping in non-over-border configuration is maybe wrong		* sprites: clipping in non-over-border configuration is maybe wrong
			* More >> ZX80 and ZX81 modes reset and hangs on a black screen while launching the Paul Farrow emulators.
			* More >> 128K BASIC launches but gets no keypresses on 2.19.0.2. On V2.16.6.0 it hangs on a black screen and border.
	* fixed (but needs thorough test) <del>Layer2 640x256x4bpp clipping is broken (and rendering partially too? should be fixed in next release)</del>		* fixed (but needs thorough test) <del>Layer2 640x256x4bpp clipping is broken (and rendering partially too? should be fixed in next release)</del>

Taylorza at 16:45, 22 December 2022

2022-12-22T16:45:27Z

← Older revision		Revision as of 17:45, 22 December 2022
Line 29:		Line 29:
	** <del>tilemode 80x32: horizontal scrolling has wrong scale (probably expecting only 320x256 offsets, confused by 640x256)</del>		** <del>tilemode 80x32: horizontal scrolling has wrong scale (probably expecting only 320x256 offsets, confused by 640x256)</del>
	** <del>NextReg $02 hard-reset</del>		** <del>NextReg $02 hard-reset</del>
			** verified fixed in V2.17.0.0 <del>CTC timing is affected by the Z80N clock speed. It should be using a constant 28Mhz reference clock.</del>

	not verified in V2.16.6.0 (but known bugs of older versions, may be still present):		not verified in V2.16.6.0 (but known bugs of older versions, may be still present):
	* verified fixed in V2.17.0.0 <del>CTC timing is affected by the Z80N clock speed. It should be using a constant 28Mhz reference clock.</del>
	* CTC time constant of 0 causes incorrect code execution.		* CTC time constant of 0 causes incorrect code execution.
	* stencil mode is not implemented		* stencil mode is not implemented

Taylorza at 16:44, 22 December 2022

2022-12-22T16:44:15Z

← Older revision		Revision as of 17:44, 22 December 2022
Line 31:		Line 31:

	not verified in V2.16.6.0 (but known bugs of older versions, may be still present):		not verified in V2.16.6.0 (but known bugs of older versions, may be still present):
	* CTC timing is affected by the Z80N clock speed. It should be using a constant 28Mhz reference clock.		* verified fixed in V2.17.0.0 <del>CTC timing is affected by the Z80N clock speed. It should be using a constant 28Mhz reference clock.</del>
	* CTC time constant of 0 causes incorrect code execution.		* CTC time constant of 0 causes incorrect code execution.
	* stencil mode is not implemented		* stencil mode is not implemented

← Older revision		Revision as of 21:46, 25 January 2023
Line 1:		Line 1:
	CSpect V2.19.0.3		CSpect V2.19.1.0
	* intentional for performance reasons:		* intentional for performance reasons:
	** sprites: the collision bit is not implemented		** sprites: the collision bit is not implemented
Line 6:		Line 6:
	** modifications to NextRegs done by CPU propagate to rendering usually only once per scanline, usually retroactively for whole current scanline		** modifications to NextRegs done by CPU propagate to rendering usually only once per scanline, usually retroactively for whole current scanline
	* major differences / missing features		* major differences / missing features
	** L2 mode 320x256 and 640x256 could crash when clip.X2 > clip.X1 (should be fixed in next version)
	** blending modes: improved greatly in V2.19.0.3, blending only L2 priority colours wrongly.		** blending modes: improved greatly in V2.19.0.3, blending only L2 priority colours wrongly.
	** NextZXOS streaming API doesn't work (the initialization of stream fails - rst 8 service 0x86 ; DISK_STRMSTART)		** NextZXOS streaming API doesn't work (the initialization of stream fails - rst 8 service 0x86 ; DISK_STRMSTART)
Line 23:		Line 22:
	** Z80: block of prefixes/instructions 0xDD/0xFD/EI does not inhibit masked interrupts		** Z80: block of prefixes/instructions 0xDD/0xFD/EI does not inhibit masked interrupts
	* recently fixed:		* recently fixed:
			** <del>L2 mode 320x256 and 640x256 could crash when clip.X2 > clip.X1</del>
	** <del>CTC timing is affected by the Z80N clock speed. It should be using a constant 28Mhz reference clock.</del>		** <del>CTC timing is affected by the Z80N clock speed. It should be using a constant 28Mhz reference clock.</del>
	** <del>vertical ULA clipping is not working in Timex modes</del>		** <del>vertical ULA clipping is not working in Timex modes</del>
Line 33:		Line 33:
	** <del>Layer2 640x256x4bpp clipping is broken</del> (V2.19.0.3 does fix this correctly, was still broken before)		** <del>Layer2 640x256x4bpp clipping is broken</del> (V2.19.0.3 does fix this correctly, was still broken before)

	not verified in V2.19.0.3 (but known bugs of older versions, may be still present):		not verified in V2.19.1.0 (but known bugs of older versions, may be still present):
	* CTC time constant of 0 causes incorrect code execution.		* CTC time constant of 0 causes incorrect code execution.
	* the initial file-import sequence of CP/M BIOS fails. (get cpm-a.p3d file from somebody with a working clean CP/M installation and copy that into c:/NextZXOS, or use other emulator to create the file)		* the initial file-import sequence of CP/M BIOS fails. (get cpm-a.p3d file from somebody with a working clean CP/M installation and copy that into c:/NextZXOS, or use other emulator to create the file)
Line 40:		Line 40:
	* direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5, all common ones should work)		* direct loading of NEX files does not support all combinations of loading-screen type and palette on/off (but V2.12.9 does load more files than V2.12.5, all common ones should work)
	* sprites: something something about default clipping... just set clip windows explicitly in your SW.		* sprites: something something about default clipping... just set clip windows explicitly in your SW.
	* sprites: clipping in non-over-border configuration is maybe wrong (~~probably~~ fixed in 2.19.0.3, needs more testing)		* sprites: clipping in non-over-border configuration is maybe wrong (further fixed in 2.19.1.0, needs more testing)
	* fixed by V2.19.0.3 <del>stencil mode is not implemented</del>, needs more testing		* fixed by V2.19.0.3 <del>stencil mode is not implemented</del>, needs more testing