Strip the insulation well back, slide over heatshrink, form an eyelet in the end of the conductor, then bring the heatshrink up to the edge of the eyelet and shrink.
I suspect most IECs won't have enough space inside to do this though.
I usually buy a lead with the plug moulded on one end and bare ends at the other - then wire the other end. Except where the other end was a riveted-together PDU...
I know, I hate all this stuff that MS is secretly installing on my PC with XP, but Windows generally works and you can interface easily to MS products and development tools. After years of discussions about monopoly and possible split, MS is back in business as if nothing had happened...
I had a look around Ubuntu and their development tools (C++), they are still under development, so to speak. This means that the situation is somewhat fluent with frequent bug fixes coming out. MS tools are not perfect either; the best environment ever was Borland, but their tools have now become so expensive that they're out of reach for the common man developer, sad really.
Changing a northbridge heatsink. Should be simple but requires the motherboard out of the box, which pretty much means disconnecting anything.
Changing anything on a Ducati 900SS, including the oil as it means removing the fairing that has a stupid fastening system of nuts inside rubber grommets (or if more than 2 months old, blobs of rust with bits of perished rubber flaking off them).
With the right tooling, and decent plugs, it's not such a huge problem, however with the prices of RedStore.com's ready-made patch leads, I have to wonder why I buy RJ45 plugs at all.. The trick is to get the wires straight, and the right length. Clue: The sheath is flexible and can be stretched/compressed along the length of the cable a little.
Worst computing job... One of: Maintaining old FORTRAN-IV code. The part of PC building when you extract all those spot-welded sections from cheap cases, and shred your fingers in the process on all the sharp edges. Hint: If you want sharp, buy cheap. Cwarling awound in de undergwoth (or any other places where the cleaner has never been) fixing broken network cabling. Reinstalling windows for the Nth time after it got itself hosed again.
This pales into insignificance compared to my teenage years spent at Safeway in East Sheen, where it is amazing just how much yuk and bad smells can be generated when an entire palletload of long life milk (or other dairy products) leaks in the warehouse and goes off.
Not a problem currently, but I remember five solid years where they didn't have any drivers that worked reliably on an SMP NT4/w2000 machine. Crashy.
Particularly if Windows doesn't support your ethernet. I always have an Intel EtherExpress card in if the mobo one isn't supported.
See below...
I've moved 75% over to Mac, which has reduced my incidence rate of all those by 75%. You should see the OSX Migration Assistant in action, it Just Works, I was deeply impressed when I moved from a G4PPC to a Core2 box. Even the calendar sync with my phone over bluetooth worked first time.
Cheers - Jaimie (doing Usenet on a homebuilt XP PC still)
It always takes the three times as long to do everything on OS X. Installing a printer, installing a scanner, setting up networking etc etc all are far much easier on XP, in fact i get so fed up, and end up going back to xp.
As a user of both... I'm amazed. Possibly you're so well trained in XP's way of doing it that you tripped over the OS X way? I've done that for some things too, and still hate the OSX Finder and the Search thing compared to Explorer.
But networking is my usual smug "Having trouble? Look how easy it is on the Mac, I'm already done" while other folks are struggling to join a wifi point or get on a wired network.
Really? I don't know what you're doing with it, then.
I've done all of those within the last two weeks and had no problems with OS X at all. It just works; and I don't even need to bring any Unix experience into play.
Well, yes, I can understand that. But I also have never had any significant network issues with windows either. It's always 'just worked' for me.
A lot of networking issues are due to crapware that people load ( possibly unwittingly ) onto their systems. Sadly, respectable software often comes into the crapware category, but the users don't realise this. symantec.
If you consider the long view...
Not so long ago, the setup, configuration and maintenance of a TCP/IP network and managing NTFS and share permissions was strictly in the professional SysAdmin scope.
In a few short years, this has been pushed down into the mainstream, and Joe Blow has to deal with this.
A lot of the complexity has been understandably concealed ( for better or worse ), but at the end of the day, it's actually quite complex stuff you are dealing with. If the smoke and mirrors which conceal the complexity from the end user can't handle a particular scenarion, it goes pear-shaped. I don't think there's any substitute for understanding what's going on behind the scenes. I think that to a large extent is why some of us can make Unix and Windows systems work with no problem.
Had a short-term job as a milkman in the East End of London nearly 30 years ago. Rushing to finish my round one day in order to catch the train back oop North for my grandmother's funeral (seriously), I took a corner too fast in the electric milk float and the whole damn lot slid off the back and smashed, in the centre courtyard of a grotty block of council flats. These were of course the days when milk came in bottles. Cleaning that up was fun.
I have data in files, email messages, etc. etc. all over the machine. Spotlight is very fast at finding them and produces sensibly ordered lists. XP is horrendously slow, even on a faster machine.
That's true. Microsoft never has been effective with anything to do with networking.
HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.