The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
My '98 Camry V6 station wagon ('97 build) is still going strong. Travelled round the moon, started on the return journey.
One engine bearing (somewhere in the top end I think) is getting a bit talkative, and the suspension is a bit loosey goosey.
The foam rubber behind the headlining cloth disintegrated, but a staple gun cured the vision issue.
The tailgate wiper doesn't (wiring issue), but hey the original aircon gas is still there.
Toyotas are virtually unkillable. (Top Gear had to try very hard!)
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
I just fixed my car today. Rear break lights were constantly on. In 42 degree celcious heat the break plug (whatever the offical name for it is ! the thing that keeps the break sensor switch pused. ) break away. Replaced it with a screw. Youtube video helped to find the solution. Saved myself a trip to mechanic and few quids and impressed wife with my mechanical skills.
Zen and the art of software maintenance : rm -rf *
Maths is like love : a simple idea but it can get complicated.
Toyotas are ridiculous. The entire car is falling apart around the engine, that seems to be the most durable and enduring piece of the whole mess.
To be fair, for the most part, that can probably be said for most cars nowadays. My Charger (2006, first model year) has had some rust spots done, but engine-wise, there hasn't been a need to touch anything. Not to suggest that anything is "falling apart around the engine" in my case.
I only replaced the (original) battery last month. The car is outdoors 24/7/365 and has been through -35C temperatures. I work from home and hardly have any mileage - and remaining stationary (especially when exposed to the elements) is a lot harder on a car than driving it regularly.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
A human being should be able to change a diaper, plan an invasion, butcher a hog, navigate a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects! - Lazarus Long
Why, oh why can't the Ethernet graph, in the Performance tab in Task Manager, on a Hyper-V host, show the downloads taking place on VMs it hosts?
Right now my router's bandwidth monitor shows some machine is downloading stuff as fast as my bandwidth allows. I currently (finally) happen to know which machine it is - it's one of my VMs; on it, Task Manager shows the bandwidth being maxed out. Great. At least I know.
Only, Task Manager, on the host, doesn't show any activity. The VM is still ultimately using the same physical NIC to talk to the outside world, so why isn't this being reflected on the host bandwidth usage?
If it did, it would have been a lot easier for me to determine what device, on my LAN, is sucking up all the bandwidth. It would've isolated the VMs from the rest of my devices.
Between my phone, my tablets, my laptops, the system on my desk and my VM host, sometimes it's pretty difficult downright impossible to determine who's hogging (for starters - and then there's the "why")...
We've just started a new month. Already I can see that, since midnight (it's currently 11:00am) I've burned through almost 10GB, and I'm actually not actively downloading anything. These are my devices, left to their own devices (so to speak).
thats because VM's communicate to/from the NIC driver, not the host network interface. drivers are not part of the operating system. It's possible for a VM to load a driver for some hardware item [plugged into the host] that the host has no clue about what it is. It's why a say win 7 VM still needs it's own USB 3 drivers to talk to USB 3 ports on the host.
(it makes networking easier for hosts and VM's to talk to each other and the outside world without [lookup/translation] kludgery or some worst case scenario of simulation resulting in TCP packetised TCP packets.) It's made possible if you can recall from computer science the 7 layers of network interface.
(by the way, it's also the reason why VPN's work - they only way some sites can detect VPN's is because they have a list of VPN provider's - not because they can detect the fakery/translations from the data.)
but yes, some other things things complicate that, doesn't work with display, disk, keyboard - partially because those don't have nice i.e. "x layer" interfaces, - the VM has to honor the host's control (consider disk allocation: disk free space tables are cached in host's operating memory, so if a VM wants to grow it's dynamic disk it has to ask the host - otherwise all hell would break loose.)
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
Right click on the list entry in Hyper-V manager and scroll down to the Network Adapter add a unique "VLAN ID" to each virtual machine. Then you can more easily measure bandwidth from your gateway and identify which virtual machine is generating the traffic.