Re: Any experience with "The Last One"?

From: Richard Heathfield (dontmail_at_address.co.uk.invalid)
Date: 11/30/03


Date: Sun, 30 Nov 2003 15:05:43 +0000 (UTC)

Mark McIntyre wrote:

> On Sun, 30 Nov 2003 08:36:45 +0000 (UTC), in comp.programming ,
> Richard Heathfield <dontmail@address.co.uk.invalid> wrote:
>
>>Seriously, if it (and we're talking mainly
>>about Word here) doesn't work for me, either I'm using it wrong (which I
>>doubt, since I hardly ask it to do anything out of the ordinary), or it's
>>out to get me (which is a tempting conspiracy theory but an unconvincing
>>one), or it's broken.
>
> If "broken" includes "badly installed",

No, I don't think so, since we're generally talking vanilla installs here,
although I won't deny that some companies try some fancy stuff. Or is it an
error to do a vanilla install?

> "installed on unstable version
> of windows",

Oh, definitely. I don't, in fact, know any other version of Windows. Is
there a counter-example, a stable version of Windows? If so, please share
the secret.

> and "broken by subsequent user hackery",

Such as what? Typing? That's usually when it goes (although sometimes it
gives up the ghost when I try to do something complicated, like create a
table - something which vim can handle trivially, without crashing).

> then I think
> you've covered it. If "broken" means "broken by the developers in the
> first place" then I think you're incorrect.

I know you think that.

>>That you don't have problems with it yourself is
>>great for you, but unhelpful to me unless you can pinpoint exactly what it
>>is that you {do|avoid doing|chant} to get it to work.
>
> 1) use a Proper Version of Windows, not one you bought in Hamleys

Client issue. How do you define "proper"? Which is the magic version of
Windows that actually works?

> 2) don't run as Admin

I don't, on versions of Windows where the distinction is meaningful.

> 3) keep the system fully patched.

Client issue. Generally not a problem.

> 4) do use a machine with the right spec

Client issue. Generally not a problem.

>>In the meantime, in my opinion at least, it is broken software.
>
> User Error.

Fine. What was I doing wrong? Typing? Was that my problem? I must admit it
tended to crash far less frequently when it wasn't running.

-- 
Richard Heathfield : binary@eton.powernet.co.uk
"Usenet is a strange place." - Dennis M Ritchie, 29 July 1999.
C FAQ: http://www.eskimo.com/~scs/C-faq/top.html
K&R answers, C books, etc: http://users.powernet.co.uk/eton


Relevant Pages

  • Re: Windows XP User Experience/Design Mistakes
    ... The main thing that bothers me with Windows is how it constantly ... steals the focus away from me while I'm typing in another window. ... It's odd how Windows needs an unsupported unofficial utility to ... is the only 'proper' way to do things...oh, ...
    (comp.sys.mac.advocacy)
  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Fax service on W2003Sbs - client dont send fax
    ... follow the steps to Update the Windows Small Business Server ClientApps ... Please paste the full content of the file to the Newsgroup. ... Microsoft CSS Online Newsgroup Support ... >the same day I do a system restore to monday;-) and client can send fax. ...
    (microsoft.public.windows.server.sbs)
  • RE: Windows 9X clients?
    ... Windows Server 2003 domain. ... Please install Directory Services Client on these Windows 98 systems. ...
    (microsoft.public.windows.server.migration)
  • Re: Changes in 2005.
    ... The client base I currently have makes transitioning to new technologies ... out over the UK which is Windows 2000 with SP4. ... > VS.NET 2003 does not compile to unmanaged code. ... > the JIT compiler handles the compilation to unmanaged code from IL. ...
    (microsoft.public.dotnet.languages.csharp)