🚀 go-pugleaf

On Saturday, in article <672669965wnr@ttelmah.demon.co.uk>
     Roger@ttelmah.demon.co.uk "Roger J.Hamlett" wrote:

"Other people have posted the 'normal' answers to this. However I have
"seen one 'other' that might apply. I had a machine that behaves as 
"you describe, and it turned out that somebody had 'fiddled' with 
"ATTRIB. I printed out the ATTRIB settings for the Windows directory, 
"and compared them with the machine, and changed the attributes back 
"on a couple of files. It then all worked. Fun huh :-)

    May the little red-bearded and sharp-pronged demons in hell receive
 all those who post tantalizingly obviously intentionally provocatively
 incomplete answers!  (If the cap fits .....)

    Which files?  Which attributes?

    Is it simply a matter of not setting as r/o any of the files that
 W95 wishes to write to during boot-up?  That would seem reasonable
 on the designers' part.  Any other requirements would not

    I found out long since that S & H were not needed anywhere; just
 M$oft conventions.  I have found a very small number of programs in
 which setting attributes (other than R) on some of their components
 would interfere with their behaviour.  Seemed to be trying to
 protect system administrators against their users.

    Where's my flak-jacket?  Anyway, I'm almost leaving.  For a while.

                                                Chris K.
-- 
Chris Kennington in anti-spam news-posting mode.
  If e-mailing replies, please use name "chris@".