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

FlashGordon

No change in size, 12:01, 13 May 2019
Now that the hardware is configured, it's time to learn how to use it. Before we detail the use of the ROM manager, here are some informations about ROMs and the best way to use them.
The CPC firmware allows up to 252 expansion ROMs to be added to the system. This feature was present exen even in the CPC 464. It allowed the very clean integration of AMSDOS to manage floppy disks in a natural way from BASIC and assembler programs, without any change to their code.
The expansion ROMs are accessed the same way as the BASIC ROM. They are mapped in the C000-FFFF range and can be read by the z80. Writing in this area will always affect the RAM, either the central memory, or expansion RAM if present and enabled. In the default configuration, this area is used as video memory, and there is no need to read from it.
4
edits