This one’s another issue that was eating my brain for the past 2 days. Little bit if story first.
I have a Windows 10 Pro virtual machine on my MacBook Pro. Things went well until I tried installing SQL Server 2014 Express, which required .Net Framework 3.5. .Net 3.5 is built-in and we need to enable it from “Turn Windows Features On or Off”.
That’s where the bummer was. I could not turn .Net 3.5 on at all. Following was the error message that I was getting:
This is my first post from Perth, WA. It’s been an excellent journey and so far so good. More about my Perth life later.
This is something that I never experienced before. When you download any file from PartnerSource or CustomerSource, Microsoft would let you do that only through it’s File Transfer Manager program. If you have that installed already, any download initiation would first invoke this program and then let you set the path/folder to take in that download and etc.
However, when I tried to do that from my new Windows 10 machine, the FTM did not open. I tried to figure that out, but later remembered this same issue happening on my Windows 8.1 machine.
Everything works other than pictures; that’s what I had found. Upon drilling down further, what I realised is that it sounds obvious that it doesn’t work on Mac based browsers. Reason: Native Pictures.
Definition of Native Picture says following:
Consider, for instance, the following snapshot of GP login window on a web client rendered on Mac Safari:
It’s not shown. Initially I thought it was something to do with Silverlight rendering. But not exactly. It’s because, this picture is a Native Picture. And by definition, it’s specific to Windows OS. Look at this picture definition below:
Apparently, by nature, it’s NOT supposed to show up on any OS other than Windows.
It’s not just this picture. Lookup Button icons, Note icons are all Native Picture types. And due to that, they are not going to render on any other OS. And if I am not mistaken, this will remain as it is at least till next major version of GP.
Those who implement GP web client MUST be aware of this.
I had been struggling with this for sometime. I wanted to create a USB installer for Mavericks and was not able to get thru’ a step where I had to show hidden files and folders.
In Windows OS, it’s a simple step which is available graphically to either show or hide hidden files and folders. But in Mac OS X, for some reason, this has to be achieved by typing a command on Terminal. Following is the command that is required to enable showing hidden files and folders:
defaults write com.apple.finder AppleShowAllFiles TRUE
So, those who struggle to get it done, above is your key to unlock this.
I got a new MacBook Pro couple of days back and needless to say, I am more than excited to use it.
I have been a Mac OS user for the past 1 year, as I had already replaced my personal computing machine from an old warrior named Lenovo N300 to an amazing MacBook Air. Been driven by that experience, I had always been yearning for my work computer to get changed to a MacBook too.
This topic is more about how Mac OS utilises the System Memory (RAM) to it’s fullest advantage and how it keeps any MacBook machine highly efficient. When we look at the Activity Monitor (equivalent to Task Manager on Windows OS), you would find something like below:
I was so intrigued by the term Wired Memory as all other terms made some sense to my H/W & OS expertise. Checked with my friend (who else but Google), and he as usual returned several results. One post stood out from all other.
It’s a very old post (posted precisely in the year 2007), but an amazing post about the topic which I was interested in. In case some people like me, who has shifted to Mac OS (or going to shift), I thought this post would be for them and would be useful to know about your Mac.
Alright… Another off-topic one, but is worth sharing. This post again shows how much Customers are aware about technology and go that extra mile to get educated on systems/software that they use.
The Old New Thing has got a post which explains a flaw in Windows Vista (yeah I can hear you yelling at me as soon as you heard that word) and Windows Server 2008, but got fixed in Windows 7 (are you OK now?) and Windows Server 2008 R2.
Just in case, people are wondering why this thing never work on Windows Vista (ok ok, that’s the last time I would utter that word) and Windows Server 2008, you have one more reason to dump *you know what*.