20 May
2012
20 May
'12
7:47 a.m.
I used the only address I'm aware of, but the mail and attachment bounced:
----- The following addresses had permanent fatal errors -----
<contrib at bitsavers.org>
553 5.3.0 <contrib at bitsavers.org>... You are blacklisted by the
receiving mailserver.
Is there a secret handshake required?
Steve
--
20 May
20 May
9:07 a.m.
On 5/20/12 7:47 AM, Steven Hirsch wrote:
I used the only address I'm aware of, but the mail
and attachment bounced:
----- The following addresses had permanent fatal errors -----
<contrib at bitsavers.org>
553 5.3.0 <contrib at bitsavers.org>... You are blacklisted by the receiving
mailserver.
Is there a secret handshake required?
Steve
aek at bitsavers.org is the only working address on bitsavers, afaik
11:56 a.m.
I used the only address I'm aware of, but the mail and attachment bounced:
----- The following addresses had permanent fatal errors -----
<contrib at bitsavers.org>
553 5.3.0 <contrib at bitsavers.org>... You are blacklisted by the
receiving mailserver.
Is there a secret handshake required?
FWIW, I've sent several sets of ROM images (and commented diassemblies)
to Al and never received any response. I have therefore given up trying
to contribute.
-tony
21 May
21 May
1:41 a.m.
On Sun, 20 May 2012, Tony Duell wrote:
I once had an FTP account but it has become invalid a long time ago. It
just doesn't make sense to send hundreds of MB via email. I'd really like
to contribute what I have scanned in the meantime (and will scan in the
future), but I need a solution != email. It would be really nice to have a
separate FTP account for uploads (i.e. one chroot environment for each
contributor); then some "magic" (may be a person) puts the stuff in the
right directories. But right now I just put everything on our local FTP
server.
Christian
Is there a
secret handshake required?
FWIW, I've sent several sets of ROM images (and commented diassemblies)
to Al and never received any response. I have therefore given up trying
to contribute. 
1:34 p.m.
In article <alpine.DEB.2.02.1205211035530.19688 at linuxserv.home>,
Christian Corti <cc at informatik.uni-stuttgart.de> writes:
But right now I just put everything on our local FTP
server.
....and then you can email the FTP url to Al and he can transfer to
bitsavers if he wishes.
That's how I do it and it works just fine.
--
"The Direct3D Graphics Pipeline" free book
<http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
22 May
22 May
1:06 a.m.
On Mon, 21 May 2012, Richard wrote:
....and then you can email the FTP url to Al and he
can transfer to
bitsavers if he wishes.
That's how I do it and it works just fine.
Now that you mention this... I've done that in the past, too. But I would
need to send a (rather long) file list because I've sorted everything into
subdirectories.
Christian
3:23 a.m.
On 22/05/12 09:06, Christian Corti wrote:
On Mon, 21 May 2012, Richard wrote:
Well... if there's anything classiccmp-related which doesn't fall under
the remit of Bitsavers (or which Al doesn't want), feel free to let me
know. I might be able to provide hosting for some of this stuff... What
have you got?
There's also Gene Buckle's Retroarchive, which might be worth a look.
--
Phil.
classiccmp at philpem.me.uk
http://www.philpem.me.uk/
....and then you can email the FTP url to Al and
he can transfer to
bitsavers if he wishes.
That's how I do it and it works just fine.
Now that you mention this... I've done that in the past, too. But I
would need to send a (rather long) file list because I've sorted
everything into subdirectories.
10:46 a.m.
In article <4FBB690A.4000402 at philpem.me.uk>,
Philip Pemberton <classiccmp at philpem.me.uk> writes:
There's also Gene Buckle's Retroarchive, which
might be worth a look.
I can also host documents on manx. I am already hosting a mirror of
stuff from vt100.net that's more complete than what's currently on
vt100.net. I haven't updated the URLs in the manx database yet, but
that's on the list of things to do.
--
"The Direct3D Graphics Pipeline" free book
<http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
7:39 a.m.
On 5/22/12 1:06 AM, Christian Corti wrote:
On Mon, 21 May 2012, Richard wrote:
That really does work best for me. I normally either acknowledge when the files are
transferred, or
if they're small they just appear in the bitsavers hierarchy.
Jay runs the host that bitsavers is on, and there is only a single account on there with
no shell access.
I don't have any other machines that you can ftp into.
I'm in the middle of detailed specification of CHM's digital repository, and
haven't had many cycles
for anything other than a couple of outside projects that I need to get done in the next
month or two
so don't expect to hear much from me in a while. There is one project of general
interest that I may
talk about soon, which is a set of tools for transcoding raw media images into tarballs
with an
embedded extensible metadata file that looks like this (from a Tektronix fbr formatted
backup diskette)
TarXc_1.0
| Created: "2012-05-21 23:45:15 UTC"
| Format: "Tektronix fbr"
| Label: | Mode: 000777 | UID: 75 | GID: 15 | Sz: 989184 | Sbk: 3F |
Cks: 43 | Cre: "1984-04-10 00:22:06" | Mod: "1984-04-10 00:22:06" |
Nam: "REDOLAIR_SRCH_OK__APR9__16.00PM"
| File: 1 | Offs: 0 | Mode: 100644 | UID: 75 | GID: 15 | Sz: 3835 | Sbk: 3F |
Cks: 6E | Acc: "1984-04-09 23:33:55" | Mod: "1984-04-09 15:25:05" |
MD5: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
Path: "NEW_STUFF/jmc/attmess.asm"
| File: 2 | Offs: 0 | Mode: 100664 | UID: 75 | GID: 15 | Sz: 21639 | Sbk: 47 |
Cks: 4C | Acc: "1984-04-09 23:34:06" | Mod: "1984-04-03 23:18:11" |
MD5: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
Path: "NEW_STUFF/jmc/cmstar.asm"
| File: 3 | Offs: 0 | Mode: 100644 | UID: 75 | GID: 15 | Sz: 200 | Sbk: 72 |
Cks: 76 | Acc: "1984-04-06 23:29:05" | Mod: "1984-04-03 23:25:13" |
MD5: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
Path: "NEW_STUFF/jmc/cont.pan.ch"
| File: 4 | Offs: 0 | Mode: 100644 | UID: 75 | GID: 15 | Sz: 11817 | Sbk: 73 |
Cks: 79 | Acc: "1984-04-09 23:34:12" | Mod: "1984-04-09 12:47:15" |
MD5: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
Path: "NEW_STUFF/jmc/disp.drvs.asm"
It's not fully cooked yet (MD5 and file payload offsets are still missing)
It is interesting because tar is a really simple format to write, but is missing per file
checksums and
a fast way to randomly access an individual file. A metadata file with a magic file name
(__TarXc_TOC.txt)
as the first file in the tarball seems to solve this problem along with carrying
information that doesn't
translate from the original file format into the Unix world. Yes, I know it's not XML.
This was intentional
because I wanted it to look like a report, be fairly compact, and practical to parse.
"|" and ":" are the
keyword delimiters, certain keywords trigger nesting "Label:" and
"File:" and others (like "Mode:") are
context sensitive with things like a default radix associated with them. strings are
"" delimited and follow
Unix string conventions. Since file names may need to be munged into ones that Unix can
handle, the original
file name is maintained in the metadata file.
Another small tool that I needed to write for someone working on a Convergent floppy file
extractor converts
....and then you can email the FTP url to Al and
he can transfer to
bitsavers if he wishes.
That's how I do it and it works just fine.
Now that you mention this... I've done that in the past, too. But I would need to
send a (rather long) file list because I've sorted everything into subdirectories.
Christian
from IMD to RAW. It has one useful feature that it
writes a flaw and interleave map to stderr
http://bitsavers.org/bits/Convergent/ngen/imd2raw/
Keeping track of bad sectors is necessary when trying to note if an extracted file is
known to be bad because
of media flaws or if you have a flaw in the file system metadata.
12:01 p.m.
On Tue, 22 May 2012 07:39:24 -0700
Al Kossow <aek at bitsavers.org> wrote:
Yes, I know it's not XML.
!XML = feature.
XML is most often overcomplicated, misunderstood and
missused. What I prefere in such situations is JSON. Quite simple but
perfectly suitable for deserialization of hierarchic, structured data.
--
\end{Jochen}
\ref{http://www.unixag-kl.fh-kl.de/~jkunz/}
10:45 a.m.
In article <alpine.DEB.2.02.1205221002300.30569 at linuxserv.home>,
Christian Corti <cc at informatik.uni-stuttgart.de> writes:
On Mon, 21 May 2012, Richard wrote:
I sort into subdirectories too, but I match the directory layout of
bitsavers.
Still, I include an "ls -lR" listing in the email so Al can see what's
there.
--
"The Direct3D Graphics Pipeline" free book
<http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
....and then you can email the FTP url to Al and
he can transfer to
bitsavers if he wishes.
That's how I do it and it works just fine.
Now that you mention this... I've done that in the past, too. But I would
need to send a (rather long) file list because I've sorted everything into
subdirectories.
11:02 a.m.
On 5/22/12 10:45 AM, Richard wrote:
In article<alpine.DEB.2.02.1205221002300.30569 at
linuxserv.home>,
Christian Corti<cc at informatik.uni-stuttgart.de> writes:
Decreasing the thinking I have to do to process a submission is helpful. The easier it
is for me to process as I see them, the more likely it is that I'll remember to do
something with them. I have a bunch of balls in the air right now, and frankly if I
can't deal with something in a few minutes, it gets deferred. I've got a couple of
big things
like a whole disk full of errata that Jay Jeager sent that hasn't even had the
envelope
opened yet. This is also why there is no contact information on bitsavers right now,
I'm
not actively seeking any more work to do.
Email attachments of a couple of megabytes work to me if your outgoing mailer can deal
with it. A tarball with a description of how to drop them into the heirarchy is the most
useful.
It probably is best if someone else wants to pick up the areas that I've not been
concentrating
on, particularly in the consumer computer space, which never has really been the focus of
what's
on bitsavers.
On Mon, 21 May 2012, Richard wrote:
I sort into subdirectories too, but I match the directory layout of
bitsavers.
Still, I include an "ls -lR" listing in the email so Al can see what's
there. ....and then you can email the FTP url to Al and
he can transfer to
bitsavers if he wishes.
That's how I do it and it works just fine.
Now that you mention this... I've done that in the past, too. But I would
need to send a (rather long) file list because I've sorted everything into
subdirectories.
11:15 a.m.
In article <4FBBD4D2.5010607 at bitsavers.org>,
Al Kossow <aek at bitsavers.org> writes:
I have a bunch of balls in the air right now, and
frankly if I
can't deal with something in a few minutes, it gets deferred.
This is why I try to offload Al with as much scanning as possible;
currently I've got a bunch of manuals I'm scanning that were
originally headed out to CHM, but I figure they'll show up sooner on
bitsavers if I can scan them to Al's specifications.
--
"The Direct3D Graphics Pipeline" free book
<http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
6:58 p.m.
On Tue, May 22, 2012 at 1:02 PM, Al Kossow <aek at bitsavers.org> wrote:
Micros and consumer/office grade stuff has been the majority of what
we've managed to post at chiclassiccomp.org, mainly because that's
what I've run into personally. I've been away from the scanning game
for too long now but hope to get into a groove again this summer. We
can also host submissions if anyone has anything that doesn't fit
elsewhere.
--
jht
It probably is
best if someone else wants to pick up the areas that I've not
been
concentrating
on, particularly in the consumer computer space, which never has really been
the focus of what's on bitsavers. 
23 May
23 May
2:46 p.m.
New subject: Juki 6100 Daisywheel printer operation manual PDF available
Greetings folks
I've just scanned a Juki 6100 Daisywheel printer operation manual - it
is available from here:
http://www.wickensonline.co.uk/printers/Juki_6100_Operation_Manual_Sep83.pdf
I've informed Al so hopefully it will appear on bitsavers at some point.
Regards,
Mark.
4548
days inactive
4551
days old
14 comments
9 participants
participants (9)
-
aek＠bitsavers.org -
ard＠p850ug1.demon.co.uk -
cc＠informatik.uni-stuttgart.de -
classiccmp＠philpem.me.uk -
jkunz＠unixag-kl.fh-kl.de -
legalize＠xmission.com -
mark＠wickensonline.co.uk -
silent700＠gmail.com -
snhirsch＠gmail.com