> > hi simon
> >
> > many tks for rushing to my assistance without the aid of caffeine. >
> no probos - its what we do in this group ;-)
>
> > everything you said i kind of knew but i just ran your word for word
> > instructions on one of the machine pairings and one can now see the other.
>
> woohoo - perhaps I should give up caffeine
>
> > what i find so damn infuriating is how complicated it all seems. your
> > instructions are simple and clear but i always end up getting lost in the
> > plethora of 'sharing / network' menus that seem to live all over the
> > machines. i guess it doesnt help that im using four different versions of
> > W*****s!
>
> What I do on one of my networks at home is to have one machine as "server"-
> and dump all the files to that. That way, you don't have to fart about too
> much with shares all over the shop.
>
> > still your tcp/ip route worked, i can breathe a sigh of relief. im going
> to
> > pick up a copy of networking for dummys as recommended by another member > of
> > the gp.
>
> The dummies books are pretty good
>
> > grrrr. . . windows. did you ever hear the (true) story of the $1bn > aircaft
> > carrier that ran on a windows platform. they had to tow it home when the
> > system crashed apparently!!
>
> > again tks
> >
> > Ted :0]
>
> quid pro quo time - what are you like at tuning rover 3.9's?
>
> Si
>
>
hi si
alas im crap at mechanics and crap at computers and probably crap at a host of other stuff but im willing to (slowly slowly) learn.
i just hope hereabouts are patient!
and again: thank you
ted