Skip to main content

Yahoo store feedback

Whomever the dev was that wrote Yahoo's feedback form needs to be sent back to flipping burgers. Instead of leaving my review with them, I'm doing it here since I know I won't have to do it again. In short RepairsUniverse.com gets a 4/5; Yahoo's Shopping Team gets a 1/5.

I bought a replacement screen for a T-Mobile Dash (AKA: HTC Dash) from RepairsUniverse. It arrived in good condition, I followed the video to replace the broken screen, and the phone works again. The only annoyance was that it took a full calendar week before the thing shipped. They can't be faulted, since the holiday weekend made it only 3 full business days; they were either busy, or took off a day early. Either way, that's just average service instead of "excellent".

However, when I went to fill in the feedback form from Yahoo and submit it, I got a response page with a "Try Again" link; I filled out everything that was indicated to be required. Clicking it resulted in a blank form; yeah, I lost everything I had submitted. I couldn't use the "back" button because everything in the chain was "POST" and browsers seem to think that using the back button is never a client-side only ordeal. So the form doesn't list everything that's actually required, and when it tells you that you missed something, it deletes your work.

And, on the topic of the phone repair, it's worth noting that there were 2 differences between the Dash in the video and the Dash I have.
  1. There's one more screw up by the camera lense after you get the plastic backing off.
  2. There's a metallic strip affixed to the back of the screen. I ripped it when trying to remove it, and I can't figure why it's metallic. The phone works w/o it in it's original condition; I tried to put it back in case it was some sort of ground (unlikely).

Comments

Popular posts from this blog

SqlBulkCopy and the "colid" error

I thought there was a page explaining this somewhere out there on the Internet, but I can't find it anymore. So here's what I re-discovered. When you try to insert the rows from a DataTable and the data in one of the columns of one of the rows is too big to fit into the destination column in the database, you get a SqlException with this error message: "Received an invalid column length from the bcp client for colid N." (Where "N" is a number.) It doesn't tell you which row, and it's a pain to figure out what column to look at. To determine what column it is referring to, you first need to get a listing of all columns in the table, listed in the order as they have been defined in the database. Next, you remove any columns in the list that are not represented in SqlBulkCopy.ColumnMappings (the order of the column mappings is irrelevant). The list that remains is what "colid" is referring to, with the first column corresponding to colid &

Live Migration between domains

For those of you like me who aren't experts at all things Active Directory (AD) and Hyper-V Live Migration (LM) permissions, it can be enough of a pain to LM a Virtual Machine (VM) between domains that you simply decide to take the VMs offline to affect the move. See, I only tolerate AD because it's required for LM'ing VMs; there isn't a choice. (It's also required for Windows Clusters, but that's a different topic.) But I figured it out. My back-story is that we setup a cluster using Windows 2012 r1 as the AD Domain Controller (DC) and Hyper-V Server 2012 r1 for the VM hosts. Then we decided we wanted to use r2 for the AD DC and Hyper-V hosts. Upgrading Hyper-V was easy. But I found that there's some unresolved Microsoft bug with Windows Clustering when upgrading the AD DC from Windows 2012 r1 to Windows 2012 r2--- clustering simply doesn't work correctly anymore . So we gave up and created a from-scratch Windows 2012 r2 AD DC then made a new cluster

Hyper-V and reserving RAM for the host/root/parent partition

After a long process, I finally have a real-world calculation for determining how much RAM to reserve for a Hyper-V host. The question/answer about it is here. But the summary is that Hyper-V loses RAM to the Nonpaged pool (and all of it is "untagged") in addition to the "standard" stuff that Microsoft has documented. Be aware that I write MB/GB here, when I actually mean MiB/GiB. I feel it will be more intuitive to see the notation that Windows (incorrectly) uses. Host Overhead 300 MB for the Hypervisor services 512 MB for the Host OS (This is a recommended amount; you have some wiggle-room with this.) [The amount of physical RAM available to the host OS] multiplied by 0.0425 (result in GB ) for the Nonpaged pool (Which means multiply that by 1024 to convert to "MB") Per-VM Overhead 24 MB for the VM 8 MB for each 1 GB of RAM allocated to the VM. Examples 12 GB RAM, 1 VM @2 GB, 1 VM @4 GB Host: 812 + (0.0425 * 12 * 1024) = 1,334.24 MB