I forget, which topic did you write it in? Or, you can repeat it here ;DIn my project's topic on this page (http://ourl.ca/64420).
EDIT: I remember now, it isnt allowed on some tests..
Well, what about using the pre-made binary diffs ? ;)
Users just interested in testing patchsets should use the binary diffs with the program whose name is indicated by the binary diff's extension.
Yeah but I think he wants to know what is a binary diff.Well, free online information sources such as http://en.wikipedia.org/wiki/Diff give much more information than one needs to know for the specific purpose of patching TI-68k OS :)
(read: he is used to just double-clicking an executable and fill forms)If someone made graphical frontends to the binary patching (the reverse operation of diffing) programs that can work with the binary diffs I provided, he can do that :)
Yeah but I think he wants to know what is a binary diff. He is not tech-savy on that stuff (read: he is used to just double-clicking an executable and fill forms)
Nice work so far (as always).Thanks ;)
bsdiff -h
bsdiff: usage: bsdiff oldfile newfile patchfilexdelta -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_SIZExdelta3 -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.* 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.Wow, I didn't know that domain name was still active. I am amazed it has been around for this long because generally those smaller sites get shut down after a few years.
and have you either looked at the documentation (I found the appropriate usage example for xdelta3 in one click) [snip]Clearly, you haven't... so let's outline the steps for you:
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.Indeed. Because it really starts to look like (well, to me, at least) that he has put hardly any effort into searching or trying to adapt things, if at all.
I've gotten pretty busy lately and have been having some trouble keeping up with a lot of things, even with processing pending files which normally isn't a problem (plus there's been a sudden increase in submitted files lately), but I expect to be able to make more headway eventually within a few days. You guys just have to be patient with me and give me a chance to test, research, write about, and format these things for posting—it can be quite time-consuming. I'll make a best effort to try to have the rest of my pending feature queue flushed out in time for POTY voting.Aaah ok I wasn't sure, I thought those OS patchers were missed or something x.x, which can happen though. And yeah I noticed the suddent increase in file submissions lately. I hope you have more free time soon. X.x