Warning: Bad Behavior DBQueryError A database error has occurred. Did you forget to run maintenance/update.php after upgrading? See: https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script Query: CREATE TABLE IF NOT EXISTS `bad_behavior` ( `id` INT(11) NOT NULL auto_increment, `ip` TEXT NOT NULL, `date` DATETIME NOT NULL default '0000-00-00 00:00:00', `request_method` TEXT NOT NULL, `request_uri` TEXT NOT NULL, `server_protocol` TEXT NOT NULL, `http_headers` TEXT NOT NULL, `user_agent` TEXT NOT NULL, `request_entity` TEXT NOT NULL, `key` TEXT NOT NULL, INDEX (`ip`(15)), INDEX (`user_agent`(10)), PRIMARY KEY (`id`) ); Function: DatabaseBase::query Error: 1813 Tablespace for table '`wikidb`.`bad_behavior`' exists. Please DISCARD the tablespace before IMPORT. (localhost) in /home/gryzor/cpcwiki_backup/httpdocs/extensions/bad-behavior/bad-behavior-mediawiki.php on line 84
Changes - CPCWiki

Changes

CRTC

26 bytes added, 20:09, 17 November 2024
/* Signal delay */
On all CRTCs, there is a 1µs delay in display between when the CRTC provides a video pointer, and when the Gate Array displays the corresponding 16-bit character.
But on CRTCs 0/1/2, there is no delay for HSYNC. On CRTCs 3/4, the Amstrad engineers fixed the issue by adding a 1µs delay for the HSYNC signal to match the video signal.
So now we have a bigger issue: on CRTCs 3/4, HSYNC occurs 1µs later than on CRTCs 0/1/2. Interrupts being dependent on HSYNC, this is a serious compatibility issue for time-sensitive code. It also explains why the CTM monitor has to be calibrated differently on CRTCs 3/4. Fortunately, the issue is easy to fix, by adjusting the HSYNC width with CRTC register 3.
13,173
edits