|
Recorded voice - usually female: "Please stay on the line. Your call is important to us."
|
|
|
|
|
That's pretty bad, but the AS system was a "tell me what you want so I can redirect you" system.
And then it decides I want something totally different and "is that correct?"
Finally went to the (mobile supplier) phone shop and was shown the cheat code: every time it asks what you want you say "to talk to a human being". After the third try it connects you to ... a human being. He was pretty useless as well, but with the help of the guy in the shop we got it done.
All I wanted was a new nano-sim for Herself's new phone ...
Don't even think about their website: my login id for that is "IHateThisCr@p" for a reason. 
Why is it that phone companies are so utterly useless at communication?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Why is it that phone companies are so utterly useless at communication?
They're the inspiration for the Sirius Cybernetics Corporation? 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
OriginalGriff wrote: every time it asks what you want you say "to talk to a human being". After the third try it connects you to ... a human being. He was pretty useless as well
Bell Canada[*] has a "chat with a representative" function that, I'm convinced, is just a chatbot. Within 5 minutes of "chatting" with him/her/it, I bluntly said "you're either a bot, or a dumbest human being I've ever had the displeasure of talking with".
I forget exactly what response I got to that, but it did not help in removing my doubt it was indeed a bot.
[*] I wasn't calling on my own behalf...but for someone who needed to get their password reset. And in order to do that...I couldn't find any means on their web site that did not require you to first login. Y'know, with your password. Even their password reset procedure made no sense, and following all links offered brought me back to their login page.
|
|
|
|
|
Similar to when my wife used "Stup1dStuff!" for an account password with a previous mobile phone company.
|
|
|
|
|
Now that I'm fully remote I remain calm, but if I ever have to go back to wearing suits at the office, you will definitely see a tie rant...followed by me whining and trying to avoid returning with a deter rant... if they don't give in I start complaining about anything and everything my vag(ue) rant.
|
|
|
|
|
j snooze wrote: if I ever have to go back to wearing suits at the office, you will definitely see a tie rant
I turned down an nice offer once because I would have had to wear a tie to work.
That and the boss was a triple-plated double-bonded dyed-in-the-wool asshat.
The two phenomena might have been related.
Software Zen: delete this;
|
|
|
|
|
I once worked for a British company that got taken over by EDS. (Yes, that EDS). At the time I had a beard, and was (grudgingly) allowed to keep it due to "grandfather rights". However when I was recruiting staff, I had to reject people with beards if, at interview, they declined to shave if offered the job. It was pretty shortly after that that I quit. (Oh, and the debacle at the Christmas lunch when it turned out the caterers had used real brandy in the brandy butter and the managers came round and removed our desserts from in front of us... zero alcohol at work policy. Fair enough, but taken to stupid levels.)
|
|
|
|
|
Please don't hold back and tell us how you are really feeling... 😁
|
|
|
|
|
Hyper-V makes it trivial to create a new VM and point to an existing .VHD/.VHDX file to boot from it. This makes it rather easy to take a hard drive full of VMs, and move them to another machine and run those VMs from there. Even if all you have is VHD/VHDX files and not the associated config files. You may be asked to re-activate (in the case of Windows) in some instances, but it beats recreating a VM entirely from scratch.
It gets tedious however if you have a lot of VHDs and have to manually recreate VMs one-by-one and point each instance to a different file. Hyper-V has lots of PowerShell cmdlets - has anyone ever tried to create a script that would (a) enumerate .VHD files starting from a given root folder and (b) create a new VM for each VHD it finds?
I'm not looking for a full solution. Just some pointers as to what cmdlets might be useful to get the process going.
|
|
|
|
|
Not quite the same, but I did create a library of Hyper-V commands that I used for a project, allowed me to create a new VM, VHDs and virtual floppies, mount and unmount drives, and start/stop a VM. I haven't looked at in years though. I could brush off the cobwebs and bundle it up. Is this of interest?
|
|
|
|
|
Sounds interesting, but overkill for the simple task I'm trying to do. And unless I'm misreading your response, PowerShell already has all the commands to do this nowadays.
In the end, it turns out New-VM has all the params it needs to do a pretty decent job, so I banged together a smallish script after posting my previous question - by far the most complex part was deciding what to name the VMs being created based on the name of the subfolder a VHD/VHDX was found in.
[Edit]
My script recreated 159 VMs from 159 VHD/VHDX files it found in a bunch of folders on an external drive in well under 5 minutes. The script took less than 2 hours to write. If I ever re-use it a second time, its value will go up even more.
Worth it.
modified 12-Jul-22 13:25pm.
|
|
|
|
|
Understood. I needed a non-PowerShell solution, so tapped into the WMI actions to do this.
I might still rework this as a library, post to Github. Originally I created this to create a DOS VM on the fly, so that users could continue to use a wine store POS application. It also included a way to allow the old DOS style printing to work with a Windows printer. Some interesting challenges all around.
|
|
|
|
|
Andreas Mertens wrote: Some interesting challenges all around
I'll bet! 
|
|
|
|
|
When you said... Quote: however if you have a lot of VHDs
I thought 30-ish... but 159?!?!
Humour me... WTH does one do with 159 VMs?
|
|
|
|
|
These are the Linux VMs I tinker with.
How many Linux distributions do you know of? Variants of those distributions? Number of versions for each variant?
It doesn't take long before it adds up.
I'm not gonna claim I run many of them at the same time. And I only start deleting older versions when I start to run out of space. And unless you start collecting pictures/videos/music libraries (which belong on a NAS anyway), OS drives don't grow all that much. You can pack a lot of them on a 2TB SSD.
|
|
|
|
|
dandy72 wrote: These are the Linux VMs I tinker with.
It's a wonder you're not 'cidal'* - after tinkering with 159 Linux VMs. 
I play with 2 or 3, pick one. Use it for a couple years then rinse and repeat.
* either 'homo' or 'sui'
|
|
|
|
|
I typically don't spend all that much time with them individually - install them from newly-downloaded ISOs, make sure they can access the internet, download the latest updates, then leave them alone. If there's some distro I then decide I want to further tinker with, it's there and ready to go.
|
|
|
|
|
fgs1963 wrote: Humour me
No, you had it right first time 
Paul Sanders.
Not that the story need be long, but it will take a long while to make it short - Henry David Thoreau
Some of my best work is in the undo buffer.
|
|
|
|
|
This is a good example where you should post this as a question in a forum and then provide your answer.
Google will help you find it later.
|
|
|
|
|
Well, I have my script now, and it's in a location where I won't have to search for long to find it.
I considered posting it as a tip, but ultimately there's more code in the script trying to decide what folder name to use to name the VM (~40 lines) than actually creating it (one line)
|
|
|
|
|
|
I'm somewhat familiar with DSC. All I was trying to do here is "enumerate all existing VHD files, create a bog-standard VM mapping to each one of them". As I understand it, DSC serves a different purpose (defining templates, creating resources configured as dictated by said templates).
|
|
|
|
|
DSC does not take a photo of the current setup and builds it again on the target system?
|
|
|
|
|
Well, nothing really needs to be "rebuilt" in this case. I just have a bunch of fully functional VMs sitting on a disk. Their config files aren't that important; what matters is their disks (VHD files). It's really not all that different than taking an existing hard drive and putting it into another machine so it can boot from it.
What I needed to do in my case is create new VMs, but at the step where you can either create a new VHD or use an existing file - point it to an existing file on disk. I really don't think DSC could have contributed much here. I could very well be wrong, but that's not my understanding of what DSC tries to do.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
