Has anyone got a config - ie modeline to run a DEC VR319 (-DA) or VR297
in X they can grab and post for me?
Thanks
Alex
--
My computer's heavier than yours.
> -----Original Message-----
> From: Richard Erlacher [mailto:edick@idcomm.com]
> > Maybe they're willing to type a couple lines for the sake of
> > the added reliability, maybe it's easier for them to type
> Now just a minute there, Chris ... You don't make any fewer
> typos than I do
Nope, and I handle it fine.
> and if I had to type a line of gibberish such as what you
> showed us all a week
> or so ago and then figure out what was mistyped I'd go blind.
You do realize that any sane person would never write code that
looks like that, unless he were using TECO? ;)
At any rate, that was Perl. There is a windows port too, and
it's certainly not a requirement.
> Every keystroke
> is a mistake waiting to happen. How do more keystrokes make
> it more reliable?
I think you may have misread me there. It's not the keystrokes
that make it reliable, it's the underlying system that accepts
them. Remember, I don't trust windows. (Possibly more than
you distrust Unix...)
I'd rather use a command line system and know (or at least
believe ;) that it will do what I ask without having anything
explode, and without making me wait until it finishes thrashing
itself into oblivion.
Admittedly, windows is better recently on those two counts, but
I can not trust it to stay that way, and it's not good enough
yet, anyway.
Unfortunately, I'm forced to use windows in my work, (I assume
and hope that you're no longer forced to use Unix in yours) so
I imagine that I have a fairly good idea of the current windows
platform. It still strikes me as severely lacking in several
departments (some subjective, and some not), including
reliability.
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
Having just (re)installed Win95 twice in 3 weeks on reformatted hard drives
(trying to install Adaptec CD burning software trashed Windows so badly that
I had to reformat the drive to clean up the mess), I can say that an
installation is not one keystroke. You have to agree to the EULA, enter the
serial number, select the install directory, select the type of install, and
must reboot at least once in the process.
Also, by the way, Win95B is OSR2, IIRC.
-----Original Message-----
From: Richard Erlacher [mailto:edick@idcomm.com]
Sent: Tuesday, May 07, 2002 12:21 AM
To: classiccmp(a)classiccmp.org
Subject: Re: APPLEVISION Monitor
I agree it's a pain to babysit the Windows installation if you have to. An
installation on a bare drive is just one keystroke and a 40-minute wait,
during which you can go out to lunch. It's simply going to assume the
defaults when you do that but at least you get to eat lunch.
What's really awful is when you upgrade, say, from 95B to 95OSR2, having
<snip>
>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 better than I did
>with the Apple "finder," whatever that is...
Find file has been included with the Mac OS since I think System 6, maybe
7 (either way, for some 10+ years).
Command-F from the finder... or go to the File menu and choose "Find"
(where, it should logically be... you want to find a "file" go to the
"file" menu, and choose "find").
But we know you haven't used a Mac since right after the Lisa came out,
so you probably messed with System 4 or 5 as the latest, which IIRC you
actually had to run the Find desk accessory manually to search for a file.
Granted, the IE warped versions of Windows have that nice "Search" button
in the folder views, which is a little easier. Is there a find button in
the windows of OS-X? (Dave? Anyone? Sorry, not a huge X user yet, I can't
quote all the features off the top of my head yet)
-chris
<http://www.mythtech.net>
> From: Chris <mythtech(a)mac.com>
> I can't... I just can't any more. I have been trying to be nice to
> Richard despite all the clear flame bait he has been throwing out here.
>
> I'm sorry... I just can't do it any more.
Perhaps a VRE (Victims of Richard Erlacher) support group
(alt.support.vre?) is needed to assist those of us who have suffered
repeated neurological meltdowns as a result of exposure to the content of
his posts ;>)
Glen
0/0
From: Glen Goodwin <acme_ent(a)bellsouth.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 :>(
Borland TurboPascal V5.5 and TurboCV2.01 They are 8086 sized and still
produce good code that seems to run fine under W98se and NT4.
Allison
From: Glen Goodwin <acme_ent(a)bellsouth.net>
>> 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.
I used it with one PC based system with excellent results. However, up
front
I assumed it may be twitchy so I used the best ST225 (minimum surface
defects) I had , shortest cables usable, and didn't format it until it was
warmed up to operating temp and the controller was a WD1005 (memory
test here). I'd never do it with an ST251 as they were flaky in my book
even for MFM. I found the best candidate for this was Quantum D540s
a 30mb MFM drive.
Allison
From: Carlos Murillo <carlos_murillo(a)epm.net.co>
>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.
When I dont want to see the underlying machine Pascal is very nice
and has proven very portable. When I need to get at the underlying
machine and don't wish to use assembler then C wins usually at the
expense of some portability.
>(portable) code, and Matlab and FORTRAN rule in that realm. Yes, FORTRAN.
:-)
Fortran is old but well proven.
Allison
> >> 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.
My only problem with Pascal argument passing was the lack of
support for missing arcguments (or short lists as some call them).
Modula-2 corrected that omission.
> 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.
Been working on a utility in F77 myself, just recently...
-dq
> [1] RedHat, and I believe SuSE, offer true walkaway install scripts.
> From a RH box, you can use a GUI point&click interface to set up a boot
> floppy that will install exactly what you want, How you want it. Insert
> floppy, turn on power, go away for ~25 minutes, come back, remove
> floppy, reboot. Gorgeous.
Slackware 7.0, once you finish answering the up-front
questions, runs by itself, although you can also choose
a "hand-holding" mode...
-dq