Analysis of VIDCBandwidthLimit

I honestly fail to see a downside to such a fix, except that purists could say “awww, but we don’t need that *command”. I may be missing something, but a *command in and of itself doesn’t take more than a few bytes does it (ie. it is just an entry in a lookup table followed by the NOOP behaviour)?

Shouldn’t things like this be supplied as a legacy resource to be added/activated as needed?

Perhaps supplied active in the first release after modification. Supplied but not activated in the second release, and a separate download after?

Shouldn’t things like this be supplied as a legacy resource

Bung it in the CallASWI module, with all the other legacy OS support stuff… ;)

Bung it in the CallASWI module

To be really pedantic, it shouldn’t be a module command as such – that isn’t quite equivalent to the command no longer existing.

Instead, (in such a module) you’d claim CLIV and if V is set on exit and it was a command you want to suppress, clear V. ie something like:

  cli  STMFD   R13!, {R0}
       STMFD   R13!, {PC}
       MOV     PC, R14
       MOV     R0, R0
       LDMVCFD R13!, {R12,PC}

       STMFD   R13!, {R0-R3}
       LDR     R0, [R13,#16]

   compare command at R0 with the list of commands to be suppressed, then

       CMPNE   PC, #1<<31
       LDMFD   R13!, {R0-R3,R12,PC}

This way, if the user has a file of the same name it will be run, whereas a module command would always take precedence.

PS. Don’t forget about abbreviations