Hi you MSX lovers,
This is a message specially for those people, interested in
specifications, technical details & such.
I noticed, that quite often there are questions, or you find info on
webpages, that contains all sorts of nonsens, but you don't want to
take the trouble to point them out what's missing, or done wrong.
Instead, it would be easier, and better to point them to a place
where they can find the correct info on some subject.
For MSX, a lot of essential information can be determined in several
ways:
-checking out MSX specifications (MSX Technical Data Book, MSX2
Technical Handbook, DOS2 references, that sort of stuff).
-checking out datasheets of MSX-specific parts
-looking into circuit diagrams, or checking out the hardware of a
real MSX, to see how these parts are connected (and what parts are
used)
-checking out MSX SYSTEM software (rather than application -)
-dropping a question in a newsgroup, or on this mailing-list
Well, many of this info is available somehow, but there's one
important piece missing on the web: the MSX Technical Databook,
describing all specifications for MSX-1. I've noticed that a guy
called Nestor Soriano put online the MSX2 Technical Handbook (good
work, Nestor!), but as far as I know, the MSX-1 spec's are still not
on the web anywhere (correct me if I'm wrong here!). Not that it
really bothers me, but I would love to see this standard-work being
available for download.
I have a copy of this book myself, and several of you will have it as
well, but not in electronic form. I would not mind doing some work to
get this online, but I'm not willing to type this entire book in
myself. I think several of you might feel the same. So I had this
idea: why not create an online version of this book, as a joint
project, where everyone who wants to participate, can add his/her own
contribution. There would be someone maintaining some webpages, doing
nothing much more than making available the latest versions of what's
available at that time. There would be someone writing a particular
chapter, not having to worry about how big the rest of the book is.
And there would be people who would just read pieces of it, and
report errors or other things they might find. For all of this, there
would be no hurry, no deadlines to be met, and if someone wants to do
only 1 specific part: okay.
The general result would be an ongoing project, where in a relative
short time, a lot of info might become available, and checked
properly by several people, and in a form in which most people would
prefer it. For most people involved, taking part could mean no more
than just devoting a few nights in a row to the subject, or spending
some more time, spread over a longer period.
I think the time is right for this particular project, and for most
people, many or all means that might be needed, became available in
the meanwhile (such as the internet).
So, I'll light the fuse here:
What would be needed:
Some webspace, several MB's will probably be needed, preferably under
some easy to remember address. Maybe someone at the MSX Resource
Center or MSXNET can create some new 'directory'? I would think of
something like "www.msx.org/msx1tech" or "www.msxnet.org/msx-tech" or
something like that. This webspace should ofcourse be pretty normal
available, and be able to handle the traffic that it would generate.
That won't be so much anyway, you could mirror some of the most
important files on several other places, just a general 'entry point'
would be needed.
Then one or two people maintaining the webpages involved here, or
watching after mirror-sites etc. would be needed. These people
wouldn't HAVE to do anything more than receiving the latest updates,
and putting these online, in some logical manner. Any editing of the
materials could be done by others (ofcourse, the 'webmasters' would
be welcome to take part themselves). Hint: I will offer myself as A
volunteer helping with this part of the work.
The rest is a matter of discussion (which might be done right here on
this mailing-list), and adding the latest contributions.
I'll start with that as well:
The form in which such a document should be available:
Personally, because of the ease of text-searching, and using any
text-editor to make changes, I would prefer ordinary text. BUT:
because of the convenience of hyperlinks, I would even more prefer
simple HTML. To be distrubuted, and downloaded, this would best be
ZIPped (rather than using LZH, ARJ or similar, ZIP is simply a de
facto standard, and a very good archive format).
Other formats you might consider: .PDF (I hate it, far bigger files
to download, not text-searchable (at least I wouldn't know how), a
separate reader required, not available on many systems).
Windows Help-format (.HLP): could be nice, but only useable on
Windows-systems, text-searching also not possible).
One small issue: in order to be used on as many systems as possible,
for filenames only the famous 8.3 type DOS-compatible filenames
should be used. In that way, all links would remain valid, even if
transferred to systems not supporting long filenames. This limitation
would only apply to filenames, for named hyperlinks (that is, links
to specific parts WITHIN documents) you can ofcourse use longer
names.
I have used the MSX Technical Data Book myself many times, and only
found one or 2 very minor mistakes in it. For the rest, it seems a
very 'solid' piece of documentation. Because many things are in there
somehow, even though they don't appear to be so on a first look, and
because even the exact form sometimes reveales some usefull detail, I
would prefer a document that sticks to the original as close as
possible. Any additions could be added in a separate chapter, or
another document.
Exceptions might be:
-Correction of ordinary spelling mistakes
-Adding notes where needed
Because it's often usefull to have all the information on a
particular subject in one place, I would prefer any notes to be added
at the place, where they comment on. BUT: to have a clear view of
what the original says, it should be pointed out clearly, what was in
the original, and what notes where added (for instance by marking
notes in some special, consistent manner).
In order to let this be useable on a many systems as possible, I
think a HTML markup as simple as possible should be used (no colors,
define you own), no special markup, at least not for the bigger part
of the text. Most of the data in for instance 'preformatted' text, or
simple tables (again, without special extra's), and as little
pictures as possible. Only where needed, or more clear, and in
common, simple formats (GIF, JPEG).
What would be needed on webpages for this:
-Latest versions of 'the' documents
-A 'status' of the parts of the project (who's doing what, what's
left to be done, what has been checked & what not, maybe an 'address
book' of participants)
-Overview of latest changes, so that anyone updating his/her own info
need only check what changed since the last time he/she looked into
it.
Why would you take part in it:
-Because you're interested in it
-Because you want to contribute to the 'cause'
-To earn 'eternal glory' by having your name 'engraved' (like carved
in a stone somewhere) as being one of the several unique people who
made it all possible (and yes, you WOULD get a good book as a
reward!)
Who will help? Drop your answers on this mailing-list! To me
personally also okay, but inform others as well, if interesting to
these others....
Greetings,
Alwin Henseler ([EMAIL PROTECTED])
http://huizen.dds.nl/~alwinh/msx (MSX Tech Doc page)
http://www.twente.nl/~cce (computerclub Enschede)
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
