Comp.Sys.Acorn.FAQ part 3 of 4

Comp.Sys.Acorn.FAQ part 3 of 4

Post by Paul Viga » Tue, 02 Dec 2003 09:00:11


rchive-name: acorn/faq/part3
Frequency: monthly

WELCOME TO THE COMP.SYS.ACORN FAQ MONTHLY UPDATE.

This update is automatically generated by my machine, so please email me at
XXXX@XXXXX.COM if any parts are missing or corrupted.
--------------------------------- part 3 of 4 ------------------------------

----------------------------------------------------------------------------

Section 5: Software Issues

----------------------------------------------------------------------------

Q5.1) Why does DOSFS corrupt my files occasionally?

Under RISC OS 3 DOS, and indeed with any other ImageFS filing system, discs are treated as one large file and ADFS applies write-behind buffering to nearly everything it does. (See the question on ADFSBuffers for more details about this.) This means while working on a DOS disc the entire disc is treated as one large open file.

However as long as a file is held open the cache is not flushed out fully till the machine is explicitly told to do so. This means when working with non-ADFS format discs always dismount them before removing them from the drive. With ADFS format discs this is not so critical, as files aren't held open during most operations on them, but it is good to get into the habit of dismounting floppy discs.

----------------------------------------------------------------------------

Q5.2) Where can I obtain the latest version of module X?

All patch modules, official RISC OS extensions and the like can be sourced from the RISC OS ftp sites. Ideally your dealer will also have copies of them too and you should be able to obtain them from them. (If they don't you may like to pass on the ones from the ftp site, if you request them, so that they are up to-date.) Failing that you should probably contact RISCOS Ltd who now manage all aspects of RISC OS development.

I am also in the process of compiling a complete list of up-to-date module version numbers, together with links to where you can download them from.

This database is online at http://www.vigay.com/riscos/system/

----------------------------------------------------------------------------

Q5.3) What are the current File-type allocation ranges?

Acorn originally reallocated the File-type ranges for applications. The new ranges are :-

Non-user area
&E00-&FFF Acorn/RISCOS Ltd
&B00-&DFF Commercial software
&A00-&AFF Acornsoft, and other commercial software
&400-&9FF Commercial Software

User area
&100-&3FF Non-commercial distributed software (ie PD)
&000-&0FF User's personal usage (ie non-distributed)

75% of the user area is for PD/Shareware, with allocations co-ordinated by Pineapple. If your software is going to be distributed, you should have an allocated filetype to avoid clashes.

RISCOS Ltd cannot publish its master list of filetypes because, at any given time, it will contain allocations made for products which have not yet been announced. Therefore, they would be in breach of confidence by doing so - and the editing overhead for producing a sanitised list is too great.

However, all is not lost. Denis Howe maintains an unofficial list of filetype allocations. This can be found at http://wombat.doc.ic.ac.uk/acorn/doc/filetypes and includes details about whether the allocation is an official one, a de facto one and what the file contains. If you would like an official 'Acorn' filetype issued to you, you should contact Pineapple Softwa
 
 
 

Comp.Sys.Acorn.FAQ part 3 of 4

Post by Paul Viga » Fri, 02 Jan 2004 09:00:04

rchive-name: acorn/faq/part3
Frequency: monthly

WELCOME TO THE COMP.SYS.ACORN FAQ MONTHLY UPDATE.

This update is automatically generated by my machine, so please email me at
XXXX@XXXXX.COM if any parts are missing or corrupted.
--------------------------------- part 3 of 4 ------------------------------

----------------------------------------------------------------------------

Section 5: Software Issues

----------------------------------------------------------------------------

Q5.1) Why does DOSFS corrupt my files occasionally?

Under RISC OS 3 DOS, and indeed with any other ImageFS filing system, discs are treated as one large file and ADFS applies write-behind buffering to nearly everything it does. (See the question on ADFSBuffers for more details about this.) This means while working on a DOS disc the entire disc is treated as one large open file.

However as long as a file is held open the cache is not flushed out fully till the machine is explicitly told to do so. This means when working with non-ADFS format discs always dismount them before removing them from the drive. With ADFS format discs this is not so critical, as files aren't held open during most operations on them, but it is good to get into the habit of dismounting floppy discs.

----------------------------------------------------------------------------

Q5.2) Where can I obtain the latest version of module X?

All patch modules, official RISC OS extensions and the like can be sourced from the RISC OS ftp sites. Ideally your dealer will also have copies of them too and you should be able to obtain them from them. (If they don't you may like to pass on the ones from the ftp site, if you request them, so that they are up to-date.) Failing that you should probably contact RISCOS Ltd who now manage all aspects of RISC OS development.

I am also in the process of compiling a complete list of up-to-date module version numbers, together with links to where you can download them from.

This database is online at http://www.vigay.com/riscos/system/

----------------------------------------------------------------------------

Q5.3) What are the current File-type allocation ranges?

Acorn originally reallocated the File-type ranges for applications. The new ranges are :-

Non-user area
&E00-&FFF Acorn/RISCOS Ltd
&B00-&DFF Commercial software
&A00-&AFF Acornsoft, and other commercial software
&400-&9FF Commercial Software

User area
&100-&3FF Non-commercial distributed software (ie PD)
&000-&0FF User's personal usage (ie non-distributed)

75% of the user area is for PD/Shareware, with allocations co-ordinated by Pineapple. If your software is going to be distributed, you should have an allocated filetype to avoid clashes.

RISCOS Ltd cannot publish its master list of filetypes because, at any given time, it will contain allocations made for products which have not yet been announced. Therefore, they would be in breach of confidence by doing so - and the editing overhead for producing a sanitised list is too great.

However, all is not lost. Denis Howe maintains an unofficial list of filetype allocations. This can be found at http://wombat.doc.ic.ac.uk/acorn/doc/filetypes and includes details about whether the allocation is an official one, a de facto one and what the file contains. If you would like an official 'Acorn' filetype issued to you, you should contact Pineapple Softwa