Showing posts with label Microsoft Windows XP. Show all posts
Showing posts with label Microsoft Windows XP. Show all posts

Tuesday, May 05, 2009

Windows XP activation key: activate by phone

Been trying to install a copy of windows xp onto my virtual machine to do some testing. However, upon starting my freshly installed windows xp that resides on the virtual machine, it appears that the windows requires key activation (which is a norm). Then without hesitation, I went and followed the steps in Easy Way to Activate Windows Home Server (Crack and Bypass Activation). Apparently, the registry editing worked. The key icon residing at the right bottom pane has gone after restarting the machine. However, am not sure if it will bypass the genuine windows validation process upon updating the windows. Probably will try it out if there's a chance.

Thursday, November 06, 2008

Remove C Drive network sharing

There are few methods available I suppose, and below are what I found;

1. Delete the sharing for the specific session only. Will re-share once reboot.
Start --> Run --> cmd
then type following command.
net share c$ delete

2. Permanently remove sharing.
Proceed to registry file by typing Start -> Run -> "registry". Look for below registry entry and amend accordingly.
Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
Name: AutoShareServer for servers
Name: AutoShareWks for workstations
Type: REG_DWORD
Value: 0

Should you have any other methods, kindly post it and share~

Tuesday, August 26, 2008

Windows XP Dual boot Windows Vista

If you would like to try out Windows Vista on a Windows XP, you may want to use dual boot to avoid any complication arises and revert back to previous platform. This can be done, guided, through Microsoft MSDN site:

Creating a multi-boot configuration that includes Windows Vista
To create a working multi-boot configuration, install the oldest version of the Windows operating system first. Then, install each newer version in order. Every new Windows version preserves backward compatibility for starting earlier Windows versions.

To create a multi-boot configuration that includes Windows Vista, you must have at least one partition for each earlier Windows version that you install. Follow these general guidelines: • Create at least two partitions. Use one partition for the Windows Vista installation.

Note If the partition for Windows Vista is already formatted, make sure that it is formatted by using the NTFS file system. However, we recommend that you use one of the following methods: • Create the second unformatted partition.
• Do not create the second partition and leave the space as free space. Instead, create the second partition during the Windows Vista installation.

• If the computer does not have an operating system installed, install the oldest Windows version first.

Note Install Windows XP before you install Windows Server 2003.
• Run the Windows Vista Setup program. Install Windows Vista in the free space or in the existing partition. You can run this Setup program in the earlier Windows version, or you can start the computer when the Windows Vista disc is in the CD or DVD drive.
After Windows Vista Setup finishes, you will have a correctly-configured, multi-boot environment that includes Windows Vista and the earlier versions of Windows. The Bootmgr boot menu that appears resembles the following menu:
Microsoft Windows Earlier Windows Operating System

Via Windows Vista no longer starts after you install an earlier version of Windows

Friday, June 13, 2008

Windows XP will not die, so soon

Windows XP is dead... long live Windows XP. You may have heard that as of June 30, you're no longer able to buy the operating system or obtain support for it. But that isn't quite the case. In fact, you'll be able to buy XP on certain mainstream PCs at least until January 31, 2009, and possibly beyond. The cutoff date is even later for some ultra-low-cost notebooks such as those made by Asus: They'll sell with XP until June 2010. As for technical support, that has a lot of life left as well--officially, Microsoft will provide at least some forms of support until 2014.

Given the confusion about XP's future, we decided to lay out your options for buying XP and getting support for it beyond the official sunset date for the OS.

Not Dead Yet

Microsoft's public statement seems to leave no wiggle room. It reads, "Windows XP will no longer be available for purchase from Microsoft for general retail and OEM partners as of June 30, 2008."

But that simple statement hides plenty of loopholes. First, retailers and PC makers can still sell the Windows XP software, and Windows XP PCs, after that date, as long as they purchased the products before June 30. If a retailer stocked up on copies of XP before June 30, it can sell XP for as long as those supplies hold out. The same holds true for PC manufacturers.

An even bigger loophole--something called downgrade rights--will allow people to get Windows XP on new PCs, even after computer makers' stock of Windows XP licenses runs out. An OEM such as Dell can sell you a PC that starts out with Vista Business or Vista Ultimate on it, and then downgrade the operating system to Windows XP Professional before shipping the machine out to you. In the box, you will receive discs for Vista, XP, Vista drivers, and XP drivers. That way, if you decide you'd prefer Vista, you can use the installation disc and drivers to upgrade to that OS.

You can do this only with Vista PCs for which the OEM has decided to offer downgrade rights, however. A Dell spokesperson says that Dell will provide the option for its XPS line of gaming PCs (the XPS M1730 laptop, XPS 630 gaming desktop, and XPS 730 gaming desktop), for its line of Vostro small-business PCs, and for enterprise customers. Dell won't offer the choice indefinitely, though--only through January 31, 2009.

HP also offers a downgrade option on its business desktops, notebooks, and workstations, and will continue to do so until at least July 30, 2009, says a company spokesperson. As with Dell PCs, when someone buys a system, it will have XP Pro installed, and will come with discs for both XP and Vista.

January 31 of next year is also the last date you'll be able to buy XP on a machine from a "system builder"--a company that builds no-brand custom PCs from components and purchases Microsoft software from a distributor rather than directly from Microsoft itself.

If you buy an ultra-low-cost PC--which Microsoft describes as a notebook with "limited hardware capabilities" intended for entry-level buyers or people seeking an inexpensive second system--you're in luck. Such laptops, including the popular Asus Eee PC, can be sold with Windows XP until June 2010. The notebooks must have small screens and low-powered CPUs to qualify.

How to Get Support, Post-Cutoff

Obtaining support for XP after June 30 will be easier than trying to buy XP after that date. For starters, you have access to what Microsoft calls "mainstream support" for XP until April 14, 2009. Mainstream support includes the release of bug fixes and security patches, so you'll still be receiving updates for the operating system. You can pay Microsoft for help, as well, and the company will also honor all warranty claims until then.

After that date, and until April 8, 2014, Microsoft will offer what it calls "extended support" for XP. During that time, Microsoft will continue to issue security patches but won't release public bug fixes. Businesses that signed support contracts with Microsoft will be able to get bug fixes, but no one else will. Paid support will still be available, but warranty claims won't be honored. Microsoft says Windows XP customers will have to take up such claims--even if they relate to software--with the PC manufacturer at that point.

Whether you can obtain support from your PC's manufacturer may depend on the way in which XP was installed on your system. For example, Dell will support XP on your system as long as Dell installed it--perhaps via the downgrade option--or prior to June 30. But if you bought a Windows Vista PC and then installed XP yourself, Dell won't support it.

Where to Find More Details

If you're looking for more information about support for XP, check out Microsoft's Windows Life-Cycle Policy pages and the Microsoft Support Lifecycle Blog.

Tuesday, May 22, 2007

16 bit MS-DOS Subsystem: NTVDM CPU illegal operation Solution

I managed to find the solution. I made a full system search on the following files after enabling the "tools -> Folder Option -> Views -> Show hidden Files and Folders" option and remove them.

c:\windows\system32\CMD.COM
c:\windows\system32\NETSTAT.COM
c:\windows\system32\PING.COM
c:\windows\system32\REGEDIT.COM
c:\windows\system32\TASKKILL.COM
c:\windows\system32\TASKLIST.COM
c:\windows\system32\TRACERT.COM

Once those files have been removed, i try to perform those commands listed and all worked!

I got to know that some extensions is executed first when we perform a command, and one way to know is to run "echo %PATHEXT%". The output that was displayed on my laptop are as below (running on Win XP):

>echo %PATHEXT%
>.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

That might be the reason why I try to perform a "cmd" command in run and was prompted with error, as it triggers the cmd.com program file first before cmd.exe. I wasn't sure why those .com extensions file were there but make sure those files will never exist.

Sunday, May 20, 2007

16 bit MS-DOS Subsystem: NTVDM CPU illegal operation

I have been facing this annoying error for quite some days now. It happened for almost all the commands I try to perform including those general command: cmd, regedit, or even ping. It's really bugging me and I've been searching for the fix but apparently it have been circulated that it was a virus/worm.

With such info on hand, I went and try different type of anti virus software to make sure the virus is eliminated. There was indeed few viruses detected but the problem wasn't solved. The command that I wanted to use still not accessible.

I also did a "sfc /scannow" command to perform a verification of all the windows driver are intact but to no avail. As I just found out another way as quoted below from the source;

MS-DOS or 16-bit Windows-based program Error Message

This installation program will reinstall the missing or corrupt Windows XP system files command.com, autoexec.nt and config.nt. The absence or corruption of one or more of these files causes a "16 Bit Subsystem" error.

XP_Fix.EXE by TRF Systems, Inc.
http://www.visualtour.com/downloads/xp_fix.exe

From Ron:

Running Audit on my computer showed that a program called
WINDUPDATE.EXE (not WINUPDATE.EXE) was deleting my Autoexec.nt file on boot
up. If I replaced the file it would delete it again. Go to \Program
Files\WINDUPDATE folder and delete it!

Go to your registry and delete anything named WINDUPDATE. Put the Autoexec.nt
file back into your \system32 folder and all is well! This was definately the
problem here and I bet most everyone has the same nasty bugger, WINDUPDATE.EXE
on their infected computer.


Hope this would fix the problem now. Will restart my pc and update the status.

Your Ad Here