New version, http://tict.ticalc.org/beta/tiosmod-0.2.4.zip .
* fixed a very old bug, documented in http://www.technicalc.org/buglist/bugs.pdf , in contrast handling: destruction of the value contained in two processor registers, d3 et d4, which shouldn't be destroyed. This is unlikely to change anything for anybody, since the bug has been worked around in TIGCC, and therefore GCC4TI, for years.
* AMS 2.08 for 92+ and V200 are now supported, after testing.

Nice work so far (as always).

Thanks

The OSContrastUp/Dn routines destroying d3-d4 affects all AMS versions supported by this patcher+patchset, and others in-between (perhaps _all_ known AMS versions, I haven't checked what AMS 1.00 does).
A more direct answer to your question: patching several other bugs is (probably) possible, but most of the bugs in the list (especially those of the CAS) are very hard to patch, because we don't have a complete understanding of what AMS does.

It totally depends on which tool you want to use, and which AMS version you want to patch

bsdiff -h
bsdiff: usage: bsdiff oldfile newfile patchfile
xdelta -h
xdelta: usage: xdelta COMMAND [OPTIONS] [ARG1 ...]
xdelta: COMMAND is one of:
xdelta:   delta     Produce a delta from ARG1 to ARG2 producing ARG3
xdelta:   info      List details about delta ARG1
xdelta:   patch     Apply patch ARG1 using file ARG2 producing ARG3
xdelta: OPTIONS are:
xdelta:   -v, --version      Print version information
xdelta:   -V, --verbose      Print verbose error messages
xdelta:   -h, --help         Print this summary
xdelta:   -n, --noverify     Disable automatic MD5 verification
xdelta:   -p, --pristine     Disable automatic GZIP decompression
xdelta:   -m, --maxmem=SIZE  Set the buffer size limit, e.g. 640K, 16M
xdelta:   -[0-9]             ZLIB compress level: 0=none, 1=fast, 6=default, 9=best
xdelta:   -s=BLOCK_SIZE      Sets block size (power of 2), minimum match length
xdelta:                      In-core memory requirement is (FROM_LEN * 8) / BLOCK_SIZE
xdelta3 -h
Xdelta version 3.0s, Copyright (C) 2007, Joshua MacDonald
Xdelta comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see "COPYING" for details.
usage: xdelta3 [command/options] [input [output]]
special command names:
    config      prints xdelta3 configuration
    decode      decompress the input
    encode      compress the input
    test        run the builtin tests
special commands for VCDIFF inputs:
    printdelta  print information about the entire delta
    printhdr    print information about the first window
    printhdrs   print information about all windows
    recode      encode with new application/secondary settings
standard options:
   -0 .. -9     compression level
   -c           use stdout
   -d           decompress
   -e           compress
   -f           force overwrite
   -h           show help
   -q           be quiet
   -v           be verbose (max 2)
   -V           show version
memory options:
   -B bytes     source window size
   -W bytes     input window size
   -P size      compression duplicates window
   -I size      instruction buffer size (0 = unlimited)
compression options:
   -s source    source file to copy from (if any)
   -S [djw|fgk] enable/disable secondary compression
   -N           disable small string-matching compression
   -D           disable external decompression (encode/decode)
   -R           disable external recompression (decode)
   -n           disable checksum (encode/decode)
   -C           soft config (encode, undocumented)
   -A [apphead] disable/provide application header (encode)
   -J           disable output (check/compute only)
   -T           use alternate code table (test)
the XDELTA environment variable may contain extra args:
   XDELTA="-s source-x.y.tar.gz" \
   tar --use-compress-program=xdelta3 \
       -cf target-x.z.tar.gz.vcdiff target-x.y/

xdelta patch os.89u patch.xdelta patchedos.89uwhere os.89u is the original OS file, patch.xdelta is the delta file, and patchedos.89u is what you want the patched OS to be named.
Edit: This is what I understand by reading the docs posted a couple up. Lionel will have to make sure I'm correct.

err, wait, I am using xdelta3..

Well you have to understand there are things, especially when it comes to such softwares, that are harder to understand for some people than they are for others. An example is when I tried using IRSSI for Windows, I never got to understand the many documentation site/files I could find, simply because the way it was explained was simply too cryptic for me. Eventually, I simply had someone else explaining it to me in a different way and I eventually got the hang of it. I was lucky, though, that someone could explain it in a different way (more visual).

Not everyone is like you. Everyone is different. That said, it might be good, if he did not already, if he did some searching on how to do what he wants to do. However, sometimes, there is a point where some people still won't understand the information they found in help files, so if he DID do his search, it's inevitable he will ask questions.

On Omni we're open towards people who are new to something (including forums) so we won't tolerate negative comments like JFGI or name calling (it can lead to a ban after warnings, although sometimes there's so much posts that such comments might go unnoticed by admins).

That said, qazz it might be good if you posted what you do not understand in the links Lionel provided, if you did check them, so it won't look like you did not search, either. While being rude to someone new to something is not tolerated here, if someone has been around for a while and still won't do efforts to help himself, I understand that some people may be annoyed. I know myself that I got annoyed at one other member here in particular in the past, as he kept asking me the same question every day.

And I hope that the fact I have troubles with such type of softwares implies to you that I am stupid

Yeah I agree with you. At one point we need to make sure the person is really doing an effort. Hopefully he can figure out or tell us what he doesn't get.

And I did not notice any rudeness in your post, so don't worry