In order to obtain a running EXE's file location, you may use the method: System.AppDomain.CurrentDomain.BaseDirectory to get it. However, this method doesn't work similarly for a running DLL. This is because it would return the file location of the "container" that calls the DLL, but not the DLL itself.
So the proper way to obtain a running DLL's file location is to use the method: System.Reflection.Assembly.GetExecutingAssembly.Location
Many credits to this site.
Sunday, November 27, 2011
Monday, November 14, 2011
Windows XP SP2 installation could not detect your internal harddisk? It's the AHCI/ATA setting in your computer BIOS.
Last night I faced a small glitch when I tried to reinstall a fresh copy of Windows XP Home Edition SP2 on a DELL Inspiron laptop which was pre-installed with Windows Vista - the internal harddisk which had been working fine with Windows Vista suddenly just "vanished" from the radar of the Windows XP installation. In other words, the Windows XP installation told me that there's no internal harddisk whatsoever detected on the computer.
Lucky for me, I read about this AHCI setting previously and I quickly went into the computer BIOS screen (just keep on pressing the F2 or DEL key when you start/restart your computer) and looked for this setting. When I found the place to change the setting (look for something that reads "AHCI" or "ATA") I just switched it from the pre-configured AHCI to ATA mode. After that I just saved the changes made and exited the BIOS screen (then your computer will restart automatically). And then I tried the Windows XP installation once again and finally got it working.
I read it in some Internet forums and some people said it's due to the lack of support for AHCI by the Windows XP Service Pack 2 (SP2).
Lucky for me, I read about this AHCI setting previously and I quickly went into the computer BIOS screen (just keep on pressing the F2 or DEL key when you start/restart your computer) and looked for this setting. When I found the place to change the setting (look for something that reads "AHCI" or "ATA") I just switched it from the pre-configured AHCI to ATA mode. After that I just saved the changes made and exited the BIOS screen (then your computer will restart automatically). And then I tried the Windows XP installation once again and finally got it working.
I read it in some Internet forums and some people said it's due to the lack of support for AHCI by the Windows XP Service Pack 2 (SP2).
Friday, October 7, 2011
Wednesday, February 9, 2011
Couldn't migrate your Workstation/Player VM to VMware Server? Error HTTP 12029? Here's the solution!
When you tried to migrate your existing Workstation/Player VM to VMware Server, the moment when you tried to add it to the Inventory, you were prompted with an error: "The server could not complete a request (HTTP 12029)". Well this happened in my case where my VM Guest OS is running Windows Server 2008 R2 64-bit. The reason why I switched to VMware Server is mainly because it's FREEEEE...
What you should do now is to get a copy of VMware Converter (also FREE) from VMware's website. Previously it was only known to me as a tool to convert a physical machine into a VM image. But in fact it could be used to convert between varied versions of VMware products too! Just grab its installer and install it on your computer and do the conversion. It works!
What you should do now is to get a copy of VMware Converter (also FREE) from VMware's website. Previously it was only known to me as a tool to convert a physical machine into a VM image. But in fact it could be used to convert between varied versions of VMware products too! Just grab its installer and install it on your computer and do the conversion. It works!
Monday, January 10, 2011
One of your VMware Server Guest OS'es could not reach the network (though seemingly it has connection)?
Today I faced a new issue with my VMware Server environment. I had cloned 4 Guest OS'es (I followed the steps on how to clone VMs in VMware Server here: http://panoskrt.wordpress.com/2009/01/20/clone-virtual-machine-on-vmware-server-20/) and had them run simultaneously on a physical server box and interconnected each other (each with a distinctive fixed IP). Due to some technical issue, I needed to replace one of the Guests with a "blank" one and reinstall the apps into it. What I did was just copied the entire VM folder and added it to my inventory (clue: what did I miss out here?).
After I booted up the newly replaced Guest (along with other Guests at the same time), I realized that it could neither ping other Guests, nor it could be pinged by them. After a few cracks (such as disabling all firewall-related settings, changing from fixed IP to DHCP client, etc.), I decided to restart all the Guests in a different sequence. Then it turned out to be another Guest facing the same symptoms this time. With few rounds of tests (and wastage of time), I finally believed there were only 2 Guests which shared the same problem.
It was then I finally recalled back there were some particular steps I must follow in order to clone VMs in VMware Server (unlike VMware Workstation). One of them is the UUID setting. Since I had pinpointed the root cause I started to compare the contents of the .VMX files of the conflicting Guests. It was this line in the .VMX file which must not have the same value as other Guests: uuid.bios = "56 4d ac f5 60 eb ..."
Thank goodness I could resolve it by today! (And get some good sleep tonight hopefully)
After I booted up the newly replaced Guest (along with other Guests at the same time), I realized that it could neither ping other Guests, nor it could be pinged by them. After a few cracks (such as disabling all firewall-related settings, changing from fixed IP to DHCP client, etc.), I decided to restart all the Guests in a different sequence. Then it turned out to be another Guest facing the same symptoms this time. With few rounds of tests (and wastage of time), I finally believed there were only 2 Guests which shared the same problem.
It was then I finally recalled back there were some particular steps I must follow in order to clone VMs in VMware Server (unlike VMware Workstation). One of them is the UUID setting. Since I had pinpointed the root cause I started to compare the contents of the .VMX files of the conflicting Guests. It was this line in the .VMX file which must not have the same value as other Guests: uuid.bios = "56 4d ac f5 60 eb ..."
Thank goodness I could resolve it by today! (And get some good sleep tonight hopefully)
Friday, January 7, 2011
Extremely slow file transfer rate when copy files between host and guest OS (VMware Server)?
Today I managed to resolve a 2-day performance issue with copying files from the host running VMware Server to any guest OS (VM) and vice versa. Luckily I found a solution from VMware Knowledge Base:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006619
It is a known issue with VMware Server host running in Windows Server 2003 or 2008 environment.
Cheers~
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006619
It is a known issue with VMware Server host running in Windows Server 2003 or 2008 environment.
Cheers~
Wednesday, January 5, 2011
New Year's Resolution for 2011
This year I'm gonna upgrade myself, kind of. First is the language. I would like to master 2 specifically: English and Japanese. Secondly is the other language. I would like to learn Java, JavaScript and C#.
The clock is already ticking, and I'm already 30 this year. So no regrets later, fight now!! GO GO GO...
The clock is already ticking, and I'm already 30 this year. So no regrets later, fight now!! GO GO GO...
Subscribe to:
Posts (Atom)