My personal preference is a dark border, and leave the char/background colour the standard. The border change is enough of a visual que to say that something different is installed in this machine. If the whole scheme is up for change, char=border is perhaps the way to go. That way programs using reverse characters, but don't set colours (eg stuff ported from PETs or written to operate on all CBM BASIC machines still look Ok. Regarding PETSCII versus ISO, I propose we follow the C65 example. PETSCII default, by setting a bit in the VIC you get another font charset (this could be ISO). That is a 4k CHAR ROM, rather than 2k. In fact, I have a 100fonts, so one possibility is the font mapping register be several bits which address a larger ROM 8k or 32k. If the charROM was an external 27xxx 28pin socket it could be customised for international requirements also. Jeri, Does your expansion have a "new VIC" feature as does the VIC-III in a C65. The feature means it always powers up on VIC compatible mode, but once a key is written to it, the additional registers become available? I figure they did this for software /mapping compatibility. - Nick PLEASE TAKE NOTE: The contents of this email (including any attachments) may be privileged and confidential. Any unauthorised use of the contents is expressly prohibited. If you have received this email in error, please advise us immediately (you can contact us by telephone on +61 8 9441 2311 by reverse charge) and then permanently delete this email together with any attachments. We appreciate your co-operation. Whilst Orbital endeavours to take reasonable care to ensure that this email and any attachments are free from viruses or other defects, Orbital does not represent or warrant that such is explicitly the case (C) 2000: Orbital Engine Company (Australia) PTY LTD and its affiliates - This message was sent through the cbm-hackers mailing list. To unsubscribe: echo unsubscribe | mail email@example.com.
Archive generated by hypermail 2.1.1.