ArtinSoft's Blogs

Software Migration Experts
Welcome to ArtinSoft's Blogs Sign in | Join | Help
in Search

Christian Saborío's Blog

The blog deals mostly with problems and their respective solutions that I find on day to day basis at my current workplace. Most of the issues so far deal specifically with Virtualization (mostly Microsoft related), 64-bit migration, and Windows 2003 issues. Many of the problems I have faced in various projects have been solved by reading someone else's blog. This is an effort to pay back and hopefully someone will be able to solve some of their problems by reading something within these pages.

April 2006 - Posts

  • Intel's Early Access Program

    Did you know that you can get Intel's suite of tools such as VTune, the C/C++ compilers, and threading tools for free? These tools, when purchased are worth every cent. So how can you get them? Go to the Intel Early Access program webpage at the Intel site and read on.
  • How to use the Intel Compiler with Visual Studio 2003

    So we have mentioned that using the Intel compiler to generate 32 or 64-bit binaries is possible with Visual Studio, but we have not mentioned how to do it...until now.

    I have found a web page on the Intel site that shows you step by step instructions on how to use it. The link can be found here.

    Of course this brings the immediate question on whether this will work with Visual Studio 2005. Furthermore, if it does work, will it be a supported scenario? Stick around and I may have the answer to these and other questions on my next blog entry.

  • Weighing POGO Profiles

    Even though we have talked quite a bit about POGO on our 64-bit sessions, we seldom have mentioned how you can actually weigh down the profiles that you use. In order to find this information, check this link at the MSDN site that explains everything.
    If you want to 'take it up a notch' when it comes to POGO and find exactly what is happening with your scenarios, check this blog post from Kang Su Gatlin.
    If there is anything you would like to know about POGO, just let me know and I'll more than happy to research it for you!
  • Longhorn Conference Afterthoughts

    The Longhorn Server conference finishes today but we had to part yesterday since we had to be in Costa Rica today :( This means that we missed some of the sessions on the last day. The one we regret the most was the second part of Virtualization which has some cool stuff for the future. I will not dive into specifics because I am sure Jose will probably blog about this so keep visiting often to read about how virtualziation on Longhorn will change the ways things are done. I also had the chance to attend the HPC session. This deals specifically with Windows Server Cluster Edition 2003 which is slated to be released in Summer 06. What does this have to do with 64-bit, you might ask? Well, this version of Windows Server only runs on x64 hardware. It is really cool to see everything pointing towards 64-bit. Applications have been starving for more memory for a long time, and now that we have the tools and OS to get things up and running, we just have to stand back and watch the transition happens. One session we most definitely enjoyed was Monad, which is a shell that will ship with Longhorn Server. This environment makes it so easy to carry out many tasks that in Unix would require several visits to the man pages again and again. What makes Monad so special is that its a shell in which you type commands that actually make sense from a human perspective - no AWK, GREP. For instance, a Monad command 'get-services', does what you expect, gets the list of services. Once you get this listing, there is a plethora of things you can do by piping to other Monad commands. One that blew me (and the audience as well) was a command to output the result as a series of bar graphs in IE - pretty neat stuff!
  • Virtualization in Longhorn: 64-bit Only

    I am writing this blog as I sit and am listening to the Virtualization session at the Longhorn Software Review. This one has been particularly interesting. The presenter has talked about what Longhorn develpers have done to make sure that the OS takes advantage of the Virtualization technology that is now offered with most mayor chip vendors. If you want to take advantage of Virtualization with Longhorn, you will *NEED* a 64-bit box (x64) as this technology will not be supported in Longhorn 32-bit. Running Virtual machines does require a lot of memory and 64-bit is the way to go when you are going to be hosting lots of guest OS. There are many, many things that have happened under the hood to make sure Virtual Machines will run almost at full speed when running under Virtualization. This will definitely make things very interesting in the future for datacenter administrators and test servers. Can't wait to get my hands on one of those development versions
  • Compile to 64-bit with previous IDEs

    Some have asked in the past about building for 64-bit using previous IDEs such as Visual Studio 2003 and Visual C++ 6.0. Even though this is not a supported scenario, it is possible. Please follow this link in order to get instructions on how to accomplish this. I cannot stress this enough: if you need to build 64-bit binaries, please use Visual Studio 2005. By doing so, you know that you are dealing with a supported scenario, are most likely to find answers to your problems online, and will make sure you are using the most stable versions of several programming libraries such as ATL, MFC, etc.
  • True Image 64-bit: Finally!

    It has been mentioned in the past that we use Acronis True Image in order to manage our x64 imaging needs. The procedure on how this was done, involved a mix of boot disks and the 32-bit version of True Image. A couple of weeks ago, TrueImage announced the 64-bit version of both its workstation and server software. I just imaged an x64 server on the fly and it worked like a charm. Keep in mind that TrueImage allows you to create images without the need to reboot, which is a real time saver. Now if only we could get an Itanium version...
  • Do we really need another compiler?

    In our sessions, we have taught you to how to use the PSDK compiler and the compiler included with Visual Studio 2005. The Intel sessions have also taught you how to use the Intel compiler and many have asked me lately why would someone use the Intel compiler given that there is a Microsoft C/C++ compiler? First off, do not think of the Intel and Microsoft compilers are mutually exclusive when it comes to writing code for the EM64T or the Itanium. The libraries and even debugging tools that are generated by both compilers can be used interchangeably without any problems. That being said, you may now start to think that these two compilers compliment each other instead of compete with each other - this is the mayor key giveaway that we want to teach during our sessions. If you are ever working with matrix multiplication or code that has to do with products between arrays, you might want to give the Intel compiler a try. It can easily vectorize your loops and you will be taking advantage of the 16 SSE3 registers that are now available in the EM64T. Furthermore, if you need to write inline assembly in code that will compile for 64-bit, the Intel compiler will allow you to do this as well. Hopefully this will clear some doubts...remember, you can use both compilers to your advantage and make them work together so that your code will run a lot faster than it did before.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems