I remember CDD as a 4DOS command, which would have been available in the Norton Utilities as NDOS. JP Software’s other shells also implement CDD, so 4OS2 and 4NT users would probably recognise it too.
There are several external implementations of CDD too, both as batch files and binary executables. One was developed by Gary Mays in 1996, and provided as part ...
The smiley program was posted to the comp.sources.misc Usenet newsgroup multiple times. Here is the description from the Volume 20, Issue 73 posting:
Submitted-by: DaviD W. Sanderson
Posting-number: Volume 20, Issue 73
Supersedes: smiley: Volume 18, Issue 82
smiley(1) is a "smiley server" I wrote for my own ...
The story is told in this 1988 usenet post by Paul Homchick:
Some time went by and it was a CP/M world, and diskettes were bigger.
In 1981 Richard Greenlaw released SQ and USQ, based on Huffman
encoding and written in BDS C. This was the first popular compression
technique. Greenlaw gave away the binaries and source code.
By 1983 it ...
People do use KiCad for this job! The S100 Computers group have created many, many boards using KiCad (included in the list here) and provide the KiCad files used to create each of them. Including the relevant libraries. These will be in 2013 format, but you can convert them to a later format if neccesary.
For 8086 components, S100 Computers - 8086 CPU ...
I don't remember if it contains those specific backgrounds, but one pack that otherwise matches your description is included among the freeware bundled with the Demo releases of Executor from before it got open-sourced.
I believe it's called "Desktop Textures Vol. 1", which would suggest that what you're looking for is Desktop Textures (III, 2.1) ...
If you want to get it running on a modern Posix system, here's what you can do.
Get the source from this archive. (This is a more recent version than the one cited in the other answer.) Follow the instructions to obtain the files bsearch.c, Makefile, etc.
In smiley.c, there is a function explain, which looks like this:
If one doesn't need particularly high data rates, it's possible to implement data-to-audio and audio-to-data routines in a very small amount of code. To store a "1", generate 250us of high followed by 250us (e.g.) of low; to store a "0", store 500us of high followed by 500us of low. Note that some tape-drives' electronics, which are designed for analog ...
Actually, in that case, no fancy algorithm changes were used - the tape recorder was literally "overclocked" - frequency of interrupts handling communication with the tape recorder changed.
I found a program that allowed to override speed on the standard C: handler. It allows operation at up to 1400 baud, but as the author writes, the ability to use higher ...
With Atari, some or combination of the following practices were used:
Increasing block size from default 128 bytes to more bytes. Fewer blocks
resulted in fewer overhead bytes (calibration sequence, record header, checksum) and fewer IRGs (gaps between blocks)
Reducing duration of the IRGs (standard duration was 0,25 s)
Increased baud rate. The FSK ...