Thursday, February 20, 2014
I've been a long time Microsoft Virtual PC user. When Win 7 came out, I was very disappointed that Virtual PC 2007 didn't support Win 7 in the guest OS. And when Win 8 came out, I was even more disappointed with Virtual PC because I saw how Win 8 with Hyper-V is so much better than the old VPC 2007 technology.
What prevented me from upgrading at the time was knowing that Technet is going away. I couldn't afford MSDN on a yearly basis, so I wasn't going to need a hyper-V environment anymore. So all my OS stayed as Win 7. In a way, I can't believe I haven't bought a computer for 3 years...
But, working to revamp a couple of my desktops this week, I discovered that Microsoft has made an improvement to Virtual PC. I'm very excited on this change. However, the documentation doesn't say whether a 64-bit guest OS is supported. So I'll find out. But this is awesome. Kudos, Microsoft!
After playing with it for a few days, I got so frustrated that I uninstall the "update" (yes, the windows virtual PC came as an "update" download), and went back to Virtual PC 2007. The wizard just would take an existing virtual PC disc, even though there was a selection to use exsiting (when you select that and go through the wizard, eventually you'll hit an error stating that the virtual PC already exists). So I started from scratch to do a new one. The problem with that is there is no management console for me to change the existing setup. For example, I wanted to add a network adapter, but there is no console for me to change that when the machine is not running. Once it's running, I cannot change hardware settings, so basically I was stuck with the original settings.
I really wouldn't recommend using this until all these problems are resolved.
A few months ago when IE 10 first came out, I made this post.
I'll admit it was a rant, and I appreciate all the comments. People actually care about this topic and spend their precious time to give opinions. After finally having some more free time to review the entire thread, I'd like to declare that the original post was incomplete, and the following is my more coherent opinion.
I've long been a Microsoft fan, love the way they build all kinds of features into their software and just let people's imagination go wild. I can especially say that now since I've owned an iPhone for a while, still owning 2 Android tablets, 4 Windows Desktops/laptop, and played with all the phones in the store to decide to switch from iPhone to a Win 8 phone.
My problem with the IE password eye feature is not that it's there, but that it's on by default. One thing I really think Apple got it right, is that any product out of the box should help prevent people from making mistakes that they unknowingly commit because they are not familiar with the product yet. iPhone, out of the box, is easy to use and the user doesn't have to worry about security or other things they have no interest in learning. This is something I think Microsoft has done from time to time, but not consistently. For example, the new Windows 8.1 comes with Windows Defender automatically on (I hope there is not going to be another lawsuit similar to the old "preinstalled media player" one that will reverse this). My wife is very technology savvy for a Human Physiology scientist, but seeing that for the first time and combined with all the media stories about computer security just turned her off IE. Now she is a Chrome user. I enjoy buying software that has all kinds of features built in, but I just think the default setting should be done assuming every first-time user doesn't know anything about the software. If power users want to tinker with the settings, they are welcome to customize their own copy anyway they want.
I think it's because of that philosophy that I'm the only person who liked Windows Vista, especially the way UAC was done. It protected every user who is new to the system, but the user can turn it off if they choose to. I do wish that the popup dialogue works every time, that would help. :)
Monday, October 7, 2013
I got this error working on a report with subreport. At first I couldn't tell that anything is wrong with the subreport, which ran fine by itself.
Turns out that the subreport pointer was changed, then the RDL did not switch out the references properly. So right-click on solution file and select "Clean".
Then when I run preview again, I got a more detailed message.
Now this is an error I can fix.
When I tried to reproduce the error so that I can document in this post, I found that the Error List tab show this all along, but it shows up as warning. According to the documentation, that's how it's supposed to work.
Thursday, October 3, 2013
I think infrastructure gets the heat a lot of times while not being at fault. I feel for them; I worked support for a while and know how tough the job is. I also feel some injustice, because these are actually really smart people if you talk to them individually. That got me thinking about all the companies I worked for; which one's helpdesk system works, and which one doesn't.
My opinion at this time is that any company with a single system of ticket processing system is doomed to fail. You need different queue for different groups, then you get timely response and professional opinion. However, this is where it gets tricky to get different groups to work together on company-wide issue. Some processes work, and some don't. I certainly don't envy those managers.
I guess I am now "dead man walking". It's just a matter of time before Microsoft kills Zune, much to my chagrin. However, I just had too many problems with iTune podcast syncing that it's not worth my time right now. I wonder how Windows Phone fair with podcast syncing. If it's better, then it'll be time to say bye to my iPhone.