Tuesday, June 4, 2013

Windows XP Activation Loop (Can't log-on to Windows desktop)

Windows XP Activation Loop (Can't log-on to Windows desktop) Zebulah Saip on Friday, February 03, 2012 9 comments You've just turned back on your computer and suddenly you can't get into the desktop. It gets stuck in the Windows log-on screen. And what's pretty surprising about it, the activation screen comes up and would ask you to activate again your Windows XP. What you would normally do is to activate the product hoping you could log-on back to the desktop. Unfortunately in most cases, the activation will not work. And in some other cases, when you activate the product, it would tell you that it is already activated but does the same anoying thing after a restart. Here's the fix that I've tested in quite a few Windows XP system. This works on either Windows XP Home or Professional. Just follow the steps in order: Start your computer in safe mode (use plain safe mode). Login using an administrator user account. If you could login to the hidden Administrator account, then use that. Go to Windows Start menu and open RUN. Or you can press on your keyboard the Windows key and letter R. 
Type CMD in the run textbox and click on OK. 
This will open the command prompt window. 
Type these commands and press enter. 
Then click OK on each prompts : 

  1.  regsvr32 regwizc.dll 
  2.  regsvr32 licdll.dll 
  3.  Type this last command (type exactly as what you see here): rundll32.exe syssetup,SetupOobeBnk 

Wait for a couple of minutes because the last command will not show anything on the screen. However, it will reset the licensing components in the background. You may now restart your computer and you can log-on back to your normal Windows desktop screen.

Ref :///http://troubleshooting-101.blogspot.sg/2012/02/windows-xp-activation-loop-cant-log-on.html#.Ua3zL9iP2x4

Wednesday, May 29, 2013

HTML and CSS Testing

ကိုယ့်စိတ်ကြိုက် လုပ်ထားတာလေး အမှတ်တရ တင်ထားတာ ကျတော် HTML, CSS, Java Script တွေ အကြောင်း တော်တော် ကို သိချင်နေတာ စိတ်ထဲကလဲ စိတ်ဝင်စားလာတယ် ဒါကြောင့် အတတ်နိုင်ဆုံးလုပ်ထားတယ် တကယ်မှ ကကြီးရေးက ဝလုံးတန်းကနေ စတတ်နေတယ် တစ်နေ့တော့ ကိုယ့်ဟာကို သတ်မှတ်ထားတဲ့ လယ်ပယ်တော့ ရောက်လာမှာပါ ... 


Friday, January 18, 2013

Windows 8 ၏ Hyper-V role

ဒီနေ့ Windows 8 Enterprise Deployment Program သွားတက်ရတယ် ပြန်လာတော့ စမ်းမယ်လို့ လုပ် ပြီးတော့ ကိုစက်မှာ Hyper-V role ကိုတင်တယ် မရဘူး၊ Feature တစ်ခုက လုံး၀ ရွေးလို့ မရဘူး ဖြစ်နေတယ်၊ တလောလေးကဘဲ Server 2012 ကိုတင်လိုက် သေးတယ် အဆင်ပြေတယ်လေ၊ ဒါနဲ့ google မှာ မွှေလိုက်တာ အောက်ပါ အတိုင်း ထွက်လာတယ် ....
http://www.howtogeek.com/73318/how-to-check-if-your-cpu-supports-second-level-address-translation-slat/

သူပြောတဲ့ အတိုင်းစမ်းကြည့်တော့ ဟုတ်တယ် ကိုယ့် CPU က SLAT feature မပါဘူးဖြစ်နေတယ်၊ နောက်စမ်းမယ်ဆိုရင် သတိထားဖို့ အတွက် မှတ်သားထားလိုက်ပါတယ်။

Windows 8 will bring a lot of new features to the Windows computing environment, one of which will be Hyper-V. In order to run Hyper-V your processor must support Second Level Address Translation (SLAT). Read on to find out if your processor supports SLAT. What Is SLAT?

Second Level Address Translation is a technology introduced in both Intel and AMD flavors of processors. Both companies call their version of the technology different names, Intel’s version is called EPT(Extended Page Tables) and AMD calls theirs RVI (Rapid Virtualization Indexing). Intel introduced Extended Page Tables in its processors that were built on the Nehalem architecture, while AMD only introduced RVI in their third generation of Opteron processors codenamed Barcelona. Hyper-V uses this to perform more VM memory management functions and reduce the overhead of translating guest physical addresses to real physical addresses. By doing this, Hypervisor CPU time is significantly reduced, and more memory is saved for each VM. How It Works

The processor has a Translation Lookaside Buffer (TLB) that supports virtual to physical memory address translation. A TLB is a cache on the processor that contains recently used mappings from the page table. When a virtual to physical address translation is required, the TLB checks it’s cache to determine whether or not it contains the mapping information. If the TLB contains a match, the physical memory address is provided and the data is access. If the TLB doesn’t contain a record, a page error occurs, and the Windows checks the page table for the mapping information. If Windows finds a mapping, it is written to the TLB, the address translation takes place, and then the data is accessed. Because of this buffer, the hypervisors overhead is substantially decreased. So What?

With all the hype surrounding Windows 8, it has been made known that Windows 8 will come with Hyper-V as a vitalization platform. While that might not appeal to everyone at first glance, it has been thought that this will be the only form of backwards compatibility, somewhat like XP Mode. SLAT will be required for Hyper-V in Windows 8. How Do I Know If I Have SLAT? Credit To How to Geek Web Site