home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.acorn.tech
- Path: sparky!uunet!gumby!yale!cs.yale.edu!news-mail-gateway!daemon
- From: /G=Owen/S=Smith/O=SJ-Research/ADMD=INTERSPAN/C=GB/@mhs-relay.ac.uk
- Subject: DragASprite CMOS byte
- Message-ID: <ARM200-921109213120-5A05688E*@MHS>
- Sender: /G=Owen/S=Smith/O=SJ-Research/ADMD=INTERSPAN/C=GB/@mhs-relay.ac.uk
- Organization: Yale CS Mail/News Gateway
- Date: Mon, 9 Nov 1992 21:31:20 GMT
- Lines: 21
-
- jwil1@cs.aukuni.ac.nz (TMOTA) wrote:
-
- (about using *fx 162,28,3 to set the DragASprite CMOS bit)
-
- >Well, academically, it's not a good way to do it, but seing as how the
- >default value is 2 and you want to set bit 1 (thus needing a final value of
- >3) this seems perfectly adequate.
-
- ...
-
- >I mean, is there *anyone* out there whose byte has a value other than 2 or
- >3?
-
- You asked for it :-) - I have a value of 0 in that byte. The bottom bit is
- the *Configure Truncate bit, which I always have set to Off. This gives the
- RISC OS 2 behaviour of giving an error if I try to save a file with a name
- above the length limits. With truncate set to On, the filing system doing
- the file creation just truncates the filename to whatever the limit on that
- filing system is.
-
- Owen. (owen.smith%gb.interspan.sj-research@mhs-relay.ac.uk)
-