🚀 go-pugleaf

In article: <+Q364KA9wUE3EwDL@chrisprings.demon.co.uk>  Clem Tello 
<Clem@chrisprings.demon.co.uk> writes:
> 
> In article <672669965wnr@ttelmah.demon.co.uk>, Roger J.Hamlett
> <Roger@ttelmah.demon.co.uk> writes
> >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 :-)
> >
> >Best Wishes
> Thanks Roger,
> However, I do not quite follow, and am not sure what I should do. I 
am
> quite a novice, but I am trying hard to learn. There seem to be so 
many
> references to attributes :-
> Drive\Attributes
> lnkfile\Attributes
> Piffile\Attributes
> dllfile\attributes
> Sysfile\attributes
> Vxdfile attributes etc.
> Hidden attributes like R=1; H=2;S=4;HS=6;SHR=7 and so on.
> then there is C:\Windows\Command\Attrib.exe 
> I would be grateful for a more definite explanation, but please 
keep it
> at layman's level.
Sorry to have not been more detailed, but it was a long time ago 
(months). The 'problem', was in the Windows directory (I didn't touch 
anything outside this). If you go into this directory, and type 
'ATTRIB', a complete list of all the files and their individual 
attributes will be displayed. I sent this to the printer (ATTRIB > 
PRN:), and then displayed the same list on the machine with the 
problem. There were I think three files that had attributes 'set' on 
the problem machine, and not on the working one (fortunately both 
were reasonably 'contemporary' installations, and I ignored files 
that were not common to both installations). I didn't persue it any 
further, when this fixed the problem, but I remember being very 
suprised that it had caused this effect. My memory is that it was an 
'exe' file, that had a 'read only' attribute set, that seemed to make 
it all work again when re-set. This is very odd, since there would 
normally be no reason at all to 'write' to an exe...
I suspected that the fault didn't actually come from being unable to 
'write' to the file, but because the attributes did not match what 
Windows expected, it was triggering the odd behaviour.
The files you list, should actually contain a list of the 'expected' 
attributes.

Best Wishes

-- 
--------------------------------------------------------------------
| EMail roger@ttelmah.demon.co.uk  http://www.ttelmah.demon.co.uk/ |
| A beard! A beard! cried Fly Nicholas.'By God, that's a good one!'|
| (Chaucer)                                                        |