OldCdfs!! fix, how to resume ?

hi
i got an other RiscPC/600 machine today. All is fine, except the CDROM.

The previous owner has applied the ‘OldCdfs!! fix’ . He hasn’t sold me his CDROM (mode2), and my ATAPI/CDROM is not able to work if the ‘OldCdfs!! fix’ is applied.

How to resume ?

the following is from a pdf i found, locking for a solution

It was only when Kodak PhotoCDs users found their discs unreadable that RiscOS Ltd accepted that CDFS 2.29 did have problems. Although many patches have been issued for RISC OS 4 by RiscOS Ltd the ‘best’ solution is still the ‘OldCdfs!! fix’ by Rex Palmer. This ‘fix’ has been mentioned before in Archive; it will have a place on out web site until such time as a definitive solution is released by RiscOS Ltd. The fix by Rex unplugs the CDFS supplied with the RISC OS 4 chips, V 2.37, and installs an earlier version of the CDFS, V 2.29, which will handle Mode 2 CDs.
-————————————-
OldCDFS!!

This utility is for use with RISC OS 4.xx only. It unplugs the ROM version of CDFS and replaces it with version 2.29 from RISC OS 3.7 – the last version known to work with virtually all CD formats.

The latest versions of my utility have a major alteration: the replacement of the Unplug commands with RMKill.

The reason for this is twofold. The main reason is that Unplug works by using the module number, which indicates its position in the ROM, while RMKill uses the module name. With changing versions of RISC OS, notably with Select, the position of modules in the ROM may well change; so you could end up with the wrong module(s) unplugged! Also the effect of Unplug is lasting, whereas the effect of RMKill only lasts until the computer is switched off or reset. This makes it easier to return to the original state. This is the second reason for the change.

As a consequence of this you now have a choice whether to install OldCDFS!! in your Boot sequence so that it is always called or to use it only when it is found to be neccessary. Full instructions are included in the download.

As this utility is run after the main patches, it will override any that may affect the ROM (or SoftLoaded ROM) version of CDFS.

Earlier versions of this utility were available from Gerald Fitton’s Abacusline website.

This software may be freely distributed.

The fix by Rex unplugs the CDFS supplied with the RISC OS 4 chips, V 2.37, and installs an earlier version of the CDFS, V 2.29, which will handle Mode 2 CDs.

The fix is disabling the CDFS version in the ROM by issuing a *RMKill CDFS, and then loading a replacement which is a different version. The “fix” is here and instructions for add/remove are with it.

If you find the “fix” (probably in the !Boot sequence) and move it to another directory where it will not be seen then you can simply reboot and the fix is no longer in place.

You may then find the drive you have fitted needs a newer driver, but that’s unknown until you move the “fix” out of the way.

Hope that helps.

Note “fix” is in quotes because in this instance it is doing anything but fix things.

thank you, i am still learning RISC OS, i haven’t seen the Readme inside the App

i was afraid the application had re-flashed the ROM, but it has not

the solution seems to be

RMKill cdfs
RMReInit cdfs

RMKill CDFSSoftATAPI
RMReInit CDFSSoftATAPI

the solution seems to be…

That needs to be done after every boot. Did you not read …

move it to another directory

which needs to be done only once?

i removed the OldCdfs, but there still was something wrong: the machine was not able to see the CD.

after removing OldCdfs, the full solution was

RMReInit CDFS
RMReInit CDFSSoftATAPI
RMReInit CDFSdriver
RMReInit CDFSResources
RMReInit CDFSFiler

(a few of them are not in the ReadMe file, btw) everything is now working as expected: New ROMs 4.39 installed, and RiscOS 4.39 installed from the CD

that’s all folks