> Why Apple Computer changed the spelling, I don't know.
IIRC, in "The Mac Bathroom Reader" they said they changed it simply to be
slighty different than the fruit. But who knows if that is correct.
-chris
<http://www.mythtech.net>
> First off, a Mac mouse has one button. That is a conscience design choice
>made by Apple. No confusing the user with this ``left button/right button''
>choice---there's just ``the button'' on the mouse. Simply saying ``use the
>left mouse button'' may cause confusion because not everyone is right
>handed. On a right-handed mouse (or a mouse to the right side of the user)
>the left-button is used as the primary button, which is also under the index
>finger of the user. The right-button will be under the middle finger (or
>ring finger for three-button mice).
Some people say this is a hogwash arguement. I personally would like to
see Apple issue a two button mouse, but as long as 3rd parties are doing
it, I'm probably not going to argue.
But I CAN tell you, probably the most recurring statement I give over the
phone for windows tech support is "unless I specify right-click, it is
always left-click"... and this is to people that use the Windows PC every
day... and they still are unsure which button to click at a given point
in time. And despite that friendly reminder, they mess it up time and
time again ("I clicked, but no menu popped up" or the opposite "I
clicked, but all that happened was this menu appeared").
I will freely admit, when it comes to that issue, it is MUCH nicer on the
Mac. I just say "click" and they have no issues. If I want them to use
the context menu I can then specify "hold the control key", but then, on
the Mac, it is rare that I tell them to access a context menu, as there
are few times it is of any additional help except to a more advanced
user. Unlike in windows, where the context menu is almost a neccessity
for doing some actions... try it, create a new folder on the windows
desktop... without using contextual menus... now, try to explain that
process to someone that is having a hard time grasping left and right
clicks, and tell my if it is easier than just explaining "put the arrow
on the desktop someplace that has no icons, right click on the desktop,
choose NEW from the menu that pops up, choose Folder from the submenu
that pops out" (we will discount the repeat the process that occurs when
the person that can't handle a mouse clicks off the menu or clicks on the
wrong thing).
Or for the Mac varient... "hold the command key down, it looks like a
cloverleaf, has an apple symbol on it, its next to the spacebar.... press
the letter N".... There's no step 3... there's no step 3!
-chris
<http://www.mythtech.net>
> From: Ben Franchuk <bfranchuk(a)jetnet.ab.ca>
> I think small and clean ( bootstrap able too is handy) languages are few
> and far between. C was that at one time, but not any more. While I don't
> expect complers to run in 64kb I think 64 Meg is far too much bloat.
So, use an older C compiler. I still use Turbo C++ 1.0. The C++
implementation sucks, but for "real" C code under MS-DOS, it still kicks
ass, and runs in 640 Kb. I wish I had something as good for CP/M-86 :>(
Glen
0/0
> From: Allison <ajp166(a)bellatlantic.net>
> No, a St251 would not interface to EDSI. It will interface to both MFM
and
> RLL though RLL may/may_not be reliable with that drive. I have used
ST225s
> with RLL controllers to get ~30mb from them (st225 is 20mb MFM).
What's your success rate with this? I tried it a couple of times years ago
and encountered some very subtle but nasty data corruption.
Glen
0/0
At 10:51 AM 5/6/02 -0500, you wrote:
>> -----Original Message-----
>> From: Allison [mailto:ajp166@bellatlantic.net]
>> I disagree. The UCSD version was an excellent teaching tool but
>> slower than sludge due to the P-code thing. Later implementations
>> namely JRT and Borland were very useful tools.
>I'm also of that opinion. I like Pascal, and Modula, and Oberon...
>Chris
I went from HP3000 BASIC to UCSD Pascal. I liked it. In retrospect,
the things that suck about Pascal are the argument passing mechanism
and strings. C is better essentially because it lets you manage
memory directly, without predefined string sizes. And it lets you
handle the guts.
But I am not a C programmer in general (except when programming
microcontrollers in RT applications); I write mostly scientific numerical
(portable) code, and Matlab and FORTRAN rule in that realm. Yes, FORTRAN. :-)
My stuff runs under Solaris, AIX, Linux, HPUX, and Win32, using gcc/g77,
HP f77, Sun fortran, xlf.
carlos.
--------------------------------------------------------------
Carlos E. Murillo-Sanchez carlos_murillo(a)nospammers.ieee.org
> From: Pat Finnegan <pat(a)purdueriots.com>
> - Altos 580-B02, dual 5-1/4" drives, software
> - Altos 8000-15A, dual 8" floppies
> - "User manual" for the Altos Series 5, Xerox'd
> - Televideo TV-925 w/user manual and maintenance manual
> - 3xOsborne-1's, at least two need some repair.
> - Commodore VIC20 with "all the fixin's"
Nice job!
> I've managed to get an Osborne 1 to power up, it looks to have a stuck
bit
> on the video memory (bad DRAM perhaps). I don't have software. Does
> anyone have software for this?
I have tons of the stuff. Let me know what you want.
Glen
0/0
Hello. I have joined the list into the see if any of you subscribers have
a copy of Norton Utilities 1.0. This is the original NU issued in 1982 on
one double-sided 5.25 floppy. I don't know whether this came out after DOS
1.0 and before DOS 1.25 or came out after DOS 1.25. I do know that
DOS 2.0 came out in March 1983 and NU 1.X was superceded shortly
thereafter by NU 2.0. I am only looking for an NU diskette or copy that
was before NU 2.0. If you have an old diskette and know what is on it but
don't know the version, I will be able to tell you whether you have 1.X or
something later.
I am doing this research for a client who will buy at market price or better.
Please email me or call me at 202-778-0002 and tell me what you have.
Thank you
Ceceile
Ceceile Kay Richter
mailto:crichter@ResearchSource.com
Should have asked this 20 years ago when everyone
remembered (well, those of you who'd been weaned by
that point, anyway...).
200, 556, 800, 1600bpi: bpi, bits per inch. I understand this one.
3200 cpi: is this characters-per-inch?
6250 fcpi: what, "framed" characters per inch?
One certainly can't figure this out merely by looking
at the capacities of the various modes...
Mostly just a curiosity, nothing really hinges on this...
-dq
> -----Original Message-----
> From: Richard Erlacher [mailto:edick@idcomm.com]
> It's not difficult to do, since everything ends up in
> "MyDocuments" as a
> default. Now, with very little effort at all, you CAN,
I don't remember that working too well under windows 95 --
possibly it's been fixed since then. I haven't paid much
attention to that part.
> indeed, lose a file.
> However, if you use the Find command (assuming you know the
> name of the file,
> or at least an extension), there's some help there. That's
But if you've never seen a computer, how are you supposed to
know what an extension is? Or how do you tell where to "find"
the find command? :)
> better than I did
> with the Apple "finder," whatever that is...
Yep, "finder" is a pretty stupid name, and so is "chooser," but
no more stupid than "explorer" (any of the three ;) "Excel" --
what does it do again? "Access..." Yep, that's great too. "Power
Point..." It must be a software implementation of a hunting dog.
To be clear, "finder" does actually provide the "find" command
to find a file. Chooser actually does provide a list of "stuff"
and let you "choose" something off of the list (for all that it's
worth :) The names aren't sufficient at all, though.
> Excel. It worked
> fine, though, at least within the limits of himem.sys and
> smartdrv.sys, both
> of which were flawed in that incarnation.
Well, you've just hit on my main complaint with windows again...
but we've covered that.
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
I have the datasheet. It is a 64kx16 static ram module. Can be
configured as 64kx16, 128kx8 or 256kx4. Offered 25 to 65ns access time.
If you need more email me, the datasheet is 8 pages. Mine is 1990.
David Gesswein
http://www.pdp8.net/ -- Run an old computer with blinkenlights.
