|><I've bought 6.0, have found one code generation bug
|><through pure luck and am petrified that I am going to distribute another
|><code generation bug that I haven't found in a commercial product.
|>
|>You need a test suite for your product. If your livlihood depends on it,
|>or lives do, you must test your product thoroughly, as you are responsible
|>for it, not the tool vendors.
|
|Are you saying that Microsoft is exempt from this rule? I would think a
|company that big would have a "test suite", right? But then again, their
|livelihood isn't at stake, since everyone will buy their products, simply
|because they're Microsoft.
On a product as complex as C 6.0, you must expect that _some_ bugs will slip
though the cracks. You must remember that there are about a dozen megabytes
of executables, libraries, and hypertext files that ship with the C 6.0
development systems. There is a tremendous amount of new material in the
C 6.0 package, from inline assembly to the Programmer's WorkBench.
C 6.0 is the most rigorously tested language product in Microsoft (and probably microcomputer) history. Microsoft Languages has a large, experienced testing
department that ran tens of thousands of hours of automated test suites on the
C 6.0 compiler and related utilities. The high compatibility and relatively
_few_ (for a new compiler) fatal errors is testament to the quality of our
testing department.
-Jonathan
DISCLAIMER: I don't speak for Microsoft Corporation. Sometimes I don't even
speak for myself!
-END-
Doc. #851
-title-
Newsgroups: comp.windows.ms
Subject: Re: Adding fonts in WfW? (LONG)
Date: 13 Sep 90 17:22:01 GMT
Organization: Microsoft Corp., Redmond WA
Lines: 239
-text-
Here is a copy of the docment product support uses to
walk users through this. I would agree with everybody
that this problem is really stupid and confusing. There
isn't anything we can do about it before True Type. The
problem is trying to get 14th century technology (fonts)
to work with many different types of 20th century technology
(screens and printers).
This document is posted on Compuserv in the Microsoft section.
There is actually a bunch of really helpful stuff there.
Please let me know (post or mail) if this doesn't do the
trick for any of you. I do not work for Product Support,
so you would be better off going there first, but I will
Upgrading Symbol Fonts for Windows 3.00 Application Note [W_WinWord]
Upgrading from Windows 2.11
---------------------------
This application note describes the procedures to properly install
Microsoft Word Symbol fonts for those who have been using Word for
Windows version 1.00 under Windows version 2.11 and have upgraded to
Windows 3.00.
If you had the Symbol fonts installed under Windows version 2.11, skip
to the "Upgrading the *.PFM Files" section. Otherwise, use the
procedure described in the "Installing Symbol Fonts" section. All
instructions in this application note assume that you have first
successfully installed Windows 3.00.
Note: If you installed the Symbol fonts under Windows 2.11, you will
have a PCLFONTS subdirectory on the root directory of the drive that
contained Windows 2.11.
References to the LaserJet in this document include both the PCL/HP
LaserJet and the HP LaserJet III printer drivers.
Installing Symbol Fonts
-----------------------
If you have been using Word for Windows under Windows version 2.11 or
Windows 3.00 and did not install the Symbol fonts previously, install
the Symbol fonts using the method below.
Before you perform this procedure, you need to know where your soft
font files are located on your hard disk. If you installed Windows
version 2.11 on Drive C, these files are in the subdirectory
C:\PCLFONTS.
1. Start Windows and open the Control Panel.
2. Choose the Printers icon.
3. Select the PCL/HP LaserJet (or LaserJet III) printer from the
Installed Printers list box.
4. Choose Configure.
5. Choose Setup.
6. Choose Fonts to go to the Printer Font Installer dialog box.
7. Choose Add Fonts.
8. Insert the Word for Windows disk that contains the Symbol fonts
(the 5.25-inch Conversions Disk or the 3.5-inch Setup Disk) in
Drive A.
9. Leave the default drive selection as A:\ and press ENTER.
10. Select the Symbol fonts from the list box on the right.
11. Choose Add. The program will suggest copying the soft fonts to
C:\PCLFONTS. You can use this directory or specify another
location. Press ENTER.
12. After the soft fonts are copied to the list box on the left,
choose Exit.
13. Choose OK three times to close the dialog boxes and return to the
Control Panel.
14. Close the Control Panel.
15. Go to the "Upgrading the *.PFM Files" section.
Upgrading the *.PFM Files
---------------------------
The Symbol fonts installed by the Word Setup program are designed for
Windows version 2.11. To use them with Windows 3.00, you must upgrade
the *.PFM files. Before performing the following procedure, be sure
you know the location of the soft font files. If you installed Windows
version 2.11 on Drive C, these files are in the root directory of
Drive C in the PCLFONTS subdirectory.
1. From within Windows, choose the DOS Prompt icon to go to the DOS
prompt.
2. Insert the Word for Windows disk containing the Symbol fonts
(the 5.25-inch Conversions Disk or the 3.5-inch Setup Disk) in Drive
A.
3. From the DOS prompt, type the following command and press ENTER
copy a:\symbol.w3\*.PFM location
where location is the drive and directory where the soft fonts are
installed -- for example:
copy a:\SYMBOL.W3\*.PFM C:\PCLFONTS
Note: The Word for Windows Conversions Disk and the Setup Disk
contain two directories: SYMBOL contains the Symbol fonts for
Windows version 2.11, which you no longer need.
SYMBOL.W3 contains the Symbol .PFM files for Windows version
3.00, which are the upgrades you now need.
4. Type exit and press ENTER to return to the Program Manager.
Rebuilding the Font Database
----------------------------
If you did not have any soft fonts previously installed for Windows or
Word for Windows, the Symbol fonts are now ready for use. However, if
you installed any soft fonts previously (Symbol or otherwise), you
must now rebuild the printer's font database in order to use the
Symbol fonts. To rebuild the database, do the following:
1. Start Word for Windows.
2. From the File menu, choose New, and then choose the OK button.
3. From the File menu, choose Printer Setup.
4. Select the PCL/HP LaserJet (or LaserJet III) printer from the
Printer list box and choose Setup.
5. If you did not install the Symbol fonts before receiving this
application note, use Method 1 below. If you previously installed
the Symbol fonts under Windows version 2.11, you can use either
Method 1 or Method 2 below.
Method 1
--------
a. Choose Fonts to go to the Printer Font Installer dialog box. Listed
in the box on the left are the soft fonts that are currently
installed for the LaserJet driver, including the newly installed
Symbol fonts.
b. Select any one of the Symbol fonts. You may need to use the scroll
bar to scroll down through the list if you have a number of soft
fonts installed.
c. Choose Edit. Choose OK. Be sure to not change any of the settings
displayed in the Edit dialog box.
d. Choose Exit to leave the Printer Font Installer dialog box.
e. Choose OK twice to close the Printer Setup dialog boxes and return
to Word for Windows.
Note: After choosing OK the second time you may see a dialog box in
the upper-left corner of the screen that says, "Building Font
Database." This box displays a running percentage of completion as
Word for Windows rebuilds the font database.
Your Symbol fonts are now properly installed.
Method 2
--------
a. Select any one of the cartridges in the Cartridges list box.
b. Choose OK twice to close the Printer Setup dialog boxes and return
to Word for Windows.
Note: After choosing OK the second time you may see a dialog box in
the upper-left corner of the screen that says, "Building Font
Database." This box displays a running percentage of completion
as Word for Windows rebuilds the font database. Your Symbol fonts
are now properly installed.
c. Important: From the File menu, choose Printer Setup and deselect the
cartridge you selected in Step a. (This step avoids printing problems
due to selecting a cartridge font that you do not actually have.)
If you still have problems and the Symbol fonts do not display on the
screen and/or do not print, we recommend that you remove the Symbol
soft fonts from your system and start from the beginning with the
"Installing Symbol Fonts" procedure.
To Remove the Symbol Fonts
1. Start Word for Windows.
2. From the File menu, choose New, and then choose the OK button.
3. From the File menu, choose Printer Setup.
4. Select the PCL/HP LaserJet (or LaserJet III) printer from the
Printer list box.
5. Choose Setup.
6. Choose Fonts to go to the Printer Font Installer dialog box. In
the list box on the left are the fonts currently installed for the
LaserJet driver.
7. Select all of the Symbol fonts. (Press the SPACEBAR to select each
of the Symbol fonts or if you are using a mouse, click each font.)
You may need to use the scroll bar to scroll through the list if
you have a number of soft fonts installed.
8. Choose Delete.
9. When the message "Remove corresponding font file(s) from disk?"
appears, choose Yes.
10. Choose Exit.
11. Choose OK twice to leave the Printer Setup dialog boxes and return
to Word for Windows.
12. Perform the steps in the "Installing Symbol Fonts" and "Upgrading
*.PFM Files" procedures.
If you are still having difficulty upgrading the Symbol fonts for use
with Windows 3.00 after following all of the above instructions, please
contact Microsoft Product Support (206) 454-2030 for assistance.
Copyright 1990 Microsoft Corporation. All Rights Reserved.
-END-
Doc. #376
-title-
Newsgroups: comp.windows.ms
Subject: Re: QEMM386/Windows config question
Date: 29 Aug 90 19:27:22 GMT
Organization: University of Hawaii
Lines: 30
-text-
In article <1990Aug29.114402.7527@watserv1.waterloo.edu> tom@mims-iris.waterloo.edu (Tom Haapanen) writes:
>
>In fact, much of the software (soon to be a vast majority) that breaks the
>640K barrier will ONLY run under Windows 3.0 (these are known as "Windows
>applications").
But this is the same old song and dance we have been hearing for
years. The facts are that only a few Windows Applications currently
take advantage of this feature. To become "a vast majority", Windows
3.0 must be clearly superior, and it is not. It does not provide
tools for making the most of EXISTING APPLICATIONS. Countless others
have already learned that you ignore this at your own peril.
Microsoft still seems to be learning the lesson.
>Get a clue, Eric. You're bitching at Microsoft because Windows 3.0 doesn't
>work well with QEMM/386 without understanding *WHY* Microsoft uses DPMI
>instead of VCPI.
I understand Microsoft uses DPMI because it meets its own agenda.
What I'm bitching at is that I have to pay the price for this agenda
that contains many things of absolutely no importance to me.
Microsoft is welcome to go its own way. However, I need to use DOS,
and the extensive powers it already provides. I can't wait for the
still unfulfilled promise of OS/2, and sadly, the currently
unfulfilled promise of Windows 3.0.
Windows is also primarily an operating environment for
Eric Pilger
NASA Infrared Telescope Facility
-END-
Doc. #478
-title-
Newsgroups: comp.windows.ms
Subject: Re: Windows Shareware
Date: 30 Aug 90 11:32:08 GMT
Organization: MIND LINK! - British Columbia, Canada
Lines: 20
-text-
From comments on the net it appears very difficult to get back any money
from registration of shareware. We need a different system. I propose that
Microsoft should directly support individual programmers by making cash awards
for the release of useful, bug-free, public domain Windows programs. Any
programmer would be entitled to submit a program to a jury (which could be from non-Microsoft people) who would look at the functionality of the program and
whether it is a useful addition to the existing set of public domain programs.
The award made would be in proportion to the size and usefulness of the
program.
Where would the money come from? From Microsoft's advertising budget for
Windows. Why would Microsoft do this? What better advertising for an
operating environment than repeated announcements of yet another well written
public domain program.
For $100,000 per year, Microsoft could get a lot of public domain programs released for Windows (increasing Windows sales) and programmers could get cash
award ranging from a $1000 for a minor utility to $20,000 to $50,000 for a
blockbuster application.
_-
Bruce Dunn Vancouver, Canada a752@mindlink.UUCP
-END-
Doc. #761
-title-
Newsgroups: comp.windows.ms
Subject: Re: Mouse on Com3??
Summary: How to install MS-mouse on any non-standard COM port
Date: 11 Sep 90 06:51:17 GMT
Organization: Turing Police, Criminal AI section
Lines: 90
-text-
In-Reply-To: shedevil@portia.Stanford.EDU's message of 8 Sep 90 22:57:02 GMT
In article <1990Sep8.225702.6638@portia.Stanford.EDU> shedevil@portia.Stanford.EDU (Anne Prisk) writes:
I have the ms mouse that came bundled with my windows 3.0. I really
need to run it on Com3, and can't find a way to do it with the docs.
I already posted this once, but it seemed to get lost amongst other
articles... hope this helps !
Patching Windows3 for serial MicroSoft Mouse in other than COM1 or COM2
In article <9121@ur-cc.UUCP> bfag@uhura.cc.rochester.edu (Meneldur) writes:
>As for bug lists, the Microsoft database, also on Compu$erve and (I think)
>GENIE, does pretty well in that regard. I understand that it is the same
>database as is used by the technicians whom you call.
If they publish their bug lists (Om my god, people will know that Microsoft
C 6.0 has bugs in it), why the hell won't they gives these out in any way to
people phoning for technical support. I had figured that it was marketing
droids who figured it was better to put the screws to the people who had bought the thing, rather than admit publicly that bugs existed. Now I found out that
even that excuse isn't valid. What the hell is going on? Why can't MS
distribute buglists for their compilers? WHY DOESN'T TECH SUPPORT EVEN TELL
PEOPLE THAT THESE LISTS EXIST ON COMMERCIAL SERVICES???
Tom West
west@turing.toronto.edu
Can anyone tell me how many bugs cause MSC to generate bad code (rather than
break the compiler)? I've bought 6.0, have found one code generation bug
through pure luck and am petrified that I am going to distribute another
code generation bug that I haven't found in a commercial product.
For people's information:
Bug 1 : If you are optimizing with -Oe (register optimization), do *NOT*
have any register variables in your program. The manual says it
ignores them but it lies. In fact, when using FP, it will generate
bad code that eventually overflows the FP stack after many passes,
possibly well away from the bad code. Removing the keyword 'register'
from the program seems to solve the problem.
Bug 2 : The following function will generate fatal error C1001, compiler
file @(#)emit.c:1.115', line 524 Contact Microsoft Product Support
Services (who will tell you that yes, it's a bug) when compiling
In article <1990Aug27.204452.9786@tc.fluke.COM>, sota@tc.fluke.COM (Bruce White) writes:
> From reading this newsgroup, one could conclude that there are so many
> problems associated with installing and running Windows, that everybody hates > it. Yet the popular press shows Microsoft selling godzillions of copies.
> Since so many people are buying it, some of them must like it.
>
> How about some postings from people who use, and like, Windows. Tell us what > you use it for, why you like it, whether you use it with non-Windows Apps, what
Okay. I admit to liking Windows, even, given to hyperbole (as I am),
of loving Windows. Perhpas not a fashionable stance, but ...
I run Windows quite successfully (i.e., with few crashes, at least
lately, and infrequent unrecoverable application errors) on an
Olivetti M300 --- a 16Mhz 386sx with 4mbs RAM, an 80 mb HDU, superVGA,
5 1/4" and 3 1/2" floppies, Ethernet card, and dedicated QMS PS810
Postscript printer. Flawless configuration, in my opinion (oh, I
could use more RAM, but one can ALWAYS use more RAM, right? And my
hard disk could be bigger, but they can ALWAYS be bigger, can't
they?). Nice tight little footprint, pretty gray box, solid blacks in
the monitor, punchy keyboard, enough speed for my purposes, and
reliable so far.
I had tried Win386 --- hated it. The Dick Tracy colors, the flat
screen, the pathetic MS-DOS executive --- good enough for a prototype,
maybe, but not good enough to use. Ugh. I tried to use Win386 as it
was advertised, bascially the same way I use Windows now, as a multi-
tasking shell, but Win386 couldn't cut it, I gave up, and three months
later, along came my first beta version of Win 3.0. There's no
turning back. The minute I saw Windows 3.0, in BETA release here at
Olivetti, it was love at first sight: the dazzling tasteful colors
(well-suited to the tasteful palette of Olivetti's by-Italians
offices), the clever little 3D buttons, the convincing multi-tasking
affect, all conspired to seduce me into the Windows world.
Why do I find Windows so irresistible? Arguably, the most important
feature is the convicning multi-tasking. I can keep several busy
applications running all day long, which I do, and while I'm pasting a
big clump of text into vi on UNIX, I can be working on a Winword
document and running a Terminal session with another UNIX session,
keeping my place in my todo list and won't be bothered if someone
shows up with a last-minute request for a vendor's phone number.
As you might gather, I use several applications routinely during my day, and
several of the Windows accessories, and a few DOS programs, most
importantly, my FTP Software's PC/TCP software to connect to UNIX for
EMail, news, etc. My Program Manager has an Agenda group, which
contains a Write icon for my ToDo List, a Cardfile icon for my Rolodex
file (66 cards and counting), a DOS icon for my Ethernet connection to
UNIX, a calendar icon for my calendar. My System group contains most
of what used to be in Main, my Tools group most of what used to be in
Accessories, an IS Tools group contains the icons I culled from the
previous two groups, and my Applications group contains all my
applications (Winword, Project, Powerpoint, Excel). Everything is
within easy reach of the mouse, on a pleasant background of forest
green.
I can keep everything I need up and running, switching between
applications as demanded by my rather frenetic life here at Olivetti:
in the middle of creating an EMail message, a colleague will drop by
with a request for a change in a manual, someone elese will chime in
with a request for a vendor phone number, a client will call for help
with an Excel macro. I can keep my EMail alive in the background,
task list over to the Program Manager to launch Winword and the
technical manual file, open my Cardfile Rolodex, and update my todo
list, almost all at the same time! As fast as I can, I fulfill the
requests, and send the requestors off with what they need, to return
to my EMail --- quickly. If I could multi-task as well as Windows
fakes it, I'd be incredible. The only thing limiting my ability to
address all those requests is my own human single-tasking limitations.
And though I hated the idea of Winword (for that matter, I hated the
too-cute MacWord, always favoring the leaner, meaner Word for the PC),
I have learned to like it very much, especially for putting together a
quick table for a report on class schedules, or a summary of system
configurations in a client department. Simple tables, to be sure, and
with Winword, simple to produce. Fast. I also use Write as a
pared-down version of Winword, for fast text entry, final formatting
to be completed in Winword, cutting and pasting between applications,
or using Winword's filters. In fact, a colleague was here today, we
discussed a new lab policy, and I turned to my computer, opened a new
Winword file, and in five minutes, we had publishable text,
attractively formatted. I relied heavily on the ribbon and the ruler,
the pull-down menus, to produce a document which will have immediate
impact on our users. And it was fast!
As short of attention span as I am, Windows lets me run circles around
my desktop, attending to portions of many tasks when so inspired,
finishing all up by the end of a day. It's the way I work.
Especially since everything I do is related: I do Windows training,
user support, technical writing --- all user service kinds of things.
And idea for a lab policy document could have impact on a lab
schedule, which in turn will have impact on users which must be
notified ... you get the picture. Windows lets me accomplish all of
the above without the tedious exiting and launching of applications,
except when I want to shut 'em down to concentrate on a single task
for a while.
Hmm. I wonder if this makes sense. In a way, Windows is bad for a
disciplined mind: you can jump around on whim, instead of being
forced to attend to a single application. Doesn't make for good
linear thinking, you know? And probably that's why I like Windows.
The other advantages of Windows, most importantly memory management,
are pretty transparent for me, and not such a huge issue because I
don't work with large files too often.
Finally, from an aesthetic viewpoint, I am pleased with Microsoft's
achievement. A few dialog boxes and message boxes could probably be
placed a little better and organized more effectively, but on the
whole, I think Windows is a piece of good work.
It's probably not for everyone --- (just the enlightened ;!> ) If you're
willing to invest some time learning a radically different approach to
PC interfaces, you'll probable at least be intrigued by Windows. It
has its flaws, most all well documented in this newsgroup and, to
lesser extent, in the press. But on the whole, I am quite happy with
the accomplishment and look forward to new releases. For the first
time in my life, I'm even thinking about programming: it would be
gratifying indeed to build an application with a face as pretty as
Windows can make it.
Okay, enough. You get the idea. If I gush a little over Windows,
forgive me. It's just that it makes life pretty easy around here
The MIT Software Center is shipping X11R4 on four 1600bpi half-inch
tapes. Call the X Hotline at (617) 258-8330 for prerecorded ordering
information and a good product description.
Integrated Computer Solutions, Inc., ships X11R4 on half-inch,
quarter-inch, and TK50 formats. Call 617-547-0510 for ordering information.
The Free Software Foundation (617-876-3296) sells X11R4 on half-inch
tapes and on QIC-24 cartridges.
Yaser Doleh (doleh@math-cs.kent.EDU; P.O. Box 1301, Kent, OH 44240) is
making X11R4 available on HP format tapes, 16 track, and Sun cartridges. [2/90]
European sites can obtain a free X11R4 distribution from Jamie Watson,
who may be reached at chx400!pan!jw or cernvax!pan!jw. [1/90]
IXI Limited (+44 223 462 131) is selling X11R4 source on quarter-inch
cartridge formats and on 5.25" and 3.5" floppy, with other formats available on request. [IXI, 2/90]
Virtual Technologies (703-430-9247) provides the entire X11R4
compressed source release on a single QIC-24 quarter-inch cartridge and also on 1.2meg or 1.44 meg floppies upon request. [Conor Cahill (cpcahil@virtech.uu.net)
2/90]
[Note that some distributions are media-only and do not include docs.]
Canadian sites can send email to xhacks@csri.toronto.edu to arrange for
the exchange of tapes; the offer is subject to "time availability".
[information from Mark Moraes (moraes@csri.toronto.edu), 2/90]
UK sites can obtain R4 through the UKUUG Software Distribution Service,
from the Department of Computing, Imperial College, London, in several tape
formats. You may also obtain the source via Janet (and therefore PSS) using
Queries should be directed to Lee McLoughlin, 01-589-5111#5037, or to
ukuug-soft@uk.ac.ic.doc. Also offered are copies of comp.sources.x logs.
X11R4 is ftp-able from expo.lcs.mit.edu; these sites are preferable,
though, and are more direct:
Machine Internet FTP
Location Name Address Directory
-------- ------- -------- -------------
(1) West USA gatekeeper.dec.com 16.1.0.2 pub/X11/R4
Central USA mordred.cs.purdue.edu 128.10.2.2 pub/X11/R4
(2) Central USA giza.cis.ohio-state.edu 128.146.8.61 pub/X.V11R4
Southeast USA uunet.uu.net 192.48.96.2 X/R4
(3) Northeast USA crl.dec.com 192.58.206.2 pub/X11/R4
(4) UK Janet src.doc.ic.ac.uk 129.31.81.36 X.V11R4
UK niftp uk.ac.ic.doc.src <XV11R4>
(5) Australia munnari.oz.au 128.250.1.21 X.V11/R4
The giza.cis.ohio-state.edu site, in particular, is known to have much of the
contrib stuff that can be found on expo.
The release is available to DEC Easynet sites as CRL::"/pub/X11/R4".
Sites in Australia may contact this address: ftp.Adelaide.EDU.AU [129.127.40.3] and check the directory pub/X/R4. The machine shadows expo and archives
Various hardware vendors produce developer's toolkits of binaries,
header files, and documentation; check your hardware vendor, particularly if
that vendor is an OSF member. Systems known to be shipping now: HP (sans UIL), Apollo (sans UIL), SCO, ISC, Mips (RISCwindows=X11R3 + full Motif), IBM.
In addition, independent binary vendors produce Motif toolkits. ICS
makes several binary kits, notably for Sun, DEC, Apple; Quest (408-988-8880)
sells kits for Suns, as well; IXI (+44 223 462 131) offers kits for Sun3 (SunOS 3.5 or later, and Sun4 (SunOS 4.0.1 or later). Unipalm XTech (+44 954 211862;
or Aurora Technologies 617-577-1288 in USA) offers a binary kit for Sun 4,
Sun 3, and Sun 386i.
The kits include varied levels of bug-fixing and support for shared
libraries.
An OSF/Motif source license must be obtained from OSF before source can
be obtained from the Open Software Foundation or any value-added vendor. Call
the Direct Channels Desk at OSF at 617-621-7300 for ordering information.
Note: Version 1.1 began shipping in late August, 1990, and is currently
User-contributed software is distributed through the newsgroup
comp.sources.x, moderated by Dan Heller (argv@sun.com); also check that group
for posting information.
The machine expo.lcs.mit.edu has a great deal of user-contributed
software in the contrib/ directory; a good deal of it is present in current or earlier versions on the X11R3 and X11R4 contrib tapes. There is a new directory contrib/R4fixes/ for fixes to R4 contrib software. [Jim Fulton, 2/90]
The material on giza.cis.ohio-state.edu, which tends to duplicate
the expo archives, is also available via anonymous UUCP from osu-cis, at TB+
and V.32 speeds. Write to uucp@cis.ohio-state.edu (same as osu-cis!uucp) for
instructions. [the archive is now maintained by Karl Kleinpaste]
A new west-coast UUCP X11 Archive is administered by Mark Snitily
(mark@zok.uucp) and contains the full X11R4 distribution, the XTEST
distribution, an entire archive of comp.sources.x and other goodies.
The machine zok has a TB+ modem which will connect to 19.2K, 2400,
1200 baud (in that order). The anonymous UUCP account is UXarch with password Xgoodies. The modem's phone number is 408-996-8285.
A sample Systems (or L.sys) entry might be:
zok Any ACU 19200 4089968285 in:--in: UXarch word: Xgoodies
To get a current listing of the files that are available, download
the file "/usrX/ls-lR.Z".
A full subject index of the comp.sources.x files is available in the
file "/usrX/comp.sources.x/INDEX".
The machine has just the one modem, so please do not fetch large
amounts of data at one sitting.
[courtesy Mark Snitily, 2/90]
FTP sites and software available (list as of X11R3; also see above):
The xstuff server is a mail-response program. That means that you mail
it a request, and it mails back the response.
Any of the four possible commands must be the first word on a line. The
xstuff server reads your entire message before it does anything, so you can
have several different commands in a single message (unless you ask for help). The xstuff server treats the "Subject:" header line just like any other line
of the message.
The archives are organized into a series of directories and
subdirectories. Each directory has an index, and each subdirectory has an
index. The top-level index gives you an overview of what is in the
subdirectories, and the index for each subdirectory tells you what is in it.
1) The command "help" or "send help" causes the server to send you a
more detailed version of this help file.
2) if your message contains a line whose first word is "index", then
the server will send you the top-level index of the contents of the archive. If there are other words on that line that match the name of subdirectories, then the indexes for those subdirectories are sent instead of the top-level index.
For example, you can say "send index fixes" (or "index fixes"). A message that requests an index cannot request data.
3) if your message contains a line whose first word is "send", then the
xstuff server will send you the item(s) named on the rest of the line. To name an item, you give its directory and its name. For example
send fixes 1 3 4
You may issue multiple send requests. The xstuff server contains many
safeguards to ensure that it is not monopolized by people asking for large
amounts of data. The mailer is set up so that it will send no more than a fixed
amount of data each day. If the work queue contains more requests than the
day's quota, then the unsent files will not be processed until the next day.
Whenever the mailer is run to send its day's quota, it sends the requests out
shortest-first.
4) Some mailers produce mail headers that are unusable for extracting
return addresses. If you use such a mailer, you won't get any response. If
you happen to know an explicit path, you can include a line like
path foo%bar.bitnet@mitvma.mit.edu
or
path bar!foo!frotz
in the body of your message, and the daemon will use it.
The xstuff server itself can be reached at xstuff@expo.lcs.mit.edu. If
your mailer deals in "!" notation, try sending to
{someplace}!mit-eddie!expo.lcs.mit.edu!xstuff.
[based on information from the MIT X Consortium, 8/89, 4/90.]
Subject: 7)* Where can I find books/articles on X that are good for beginners?
Ken Lee of the DEC Western Software Laboratory (klee@wsl.dec.com)
regularly posts to comp.windows.x and ba.windows.x a list of reference books
and articles on X and X programming. Here is an unordered set of useful
reference books and tutorials, most of which appear on that list [comments are gathered from a variety of places and are unattributable]:
Jones, Oliver, "Introduction to the X Window System," Prentice Hall, 1989. A
fine introduction to programming with Xlib; fairly good background to the X
protocol; nice discussion of Xlib, the X library. ISBN 0-13-499997-5.
Young, Doug. "The X Window System: Applications and Programming with Xt (Motif Version)," Prentice Hall, 1989 (ISBN 0-13-497074-8). The excellent tutorial
"X Window Systems Programming and Applications with Xt," (ISBN 0-13-972167-3)
updated for Motif. [The examples from the Motif version are available on expo
in ~ftp/contrib/young.motif.tar.Z]
Scheifler, Robert, James Gettys, and Ron Newman, "X Window System: C Library
and Protocol Reference," Digital Press, 1988. The bible on X. This is the most complete published description of the X programming interface and X protocol.
It should not be one's first book on X, though. ISBN 1-55558-012-2. DP order
number EY-6737E-DP. The second edition of this book, including R4 information, is available as of 8/90; ISBN 1-55558-050-5, DP order EY-E755E-DP.
Associates, 1989. A professional reference manual for the MIT X11R3 Xt; some
information on X11R4 is included.
Rosenthal, David S.H., "Inter-Client Communication Conventions Manual Version
1.0 (MIT Consortium Standard)." The first real ICCCM, available on the R4 tape; a version is also available from the xstuff mail-archive-server.
(Prentice-Hall ordering is 201-767-5937. O'Reilly ordering is 800-338-NUTS.)
In addition, check the X11R4 core distribution in doc/tutorials for some useful papers and tutorials, particularly the file doc/tutorials/answers.txt. "Late
Night's Top Ten X11 Questions" by Dave Lemke (lemke@ncd.com) and Stuart Marks
(smarks@sun.com) answers other common questions and some of these here in more detail.