The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,908 other followers

Archive for the ‘Windows XP’ Category

Some notes on (temporarily) using CIFS/SMBv1 with Windows 10

Posted by jpluimers on 2022/06/13

Warning: only do this in a well confined network because of the SMBv1 has serious security implications!

Temporarily allowing SMBv1 makes it easier to transfer files from/to ancient Windows XP (virtual) machines.

Sometimes you need those to support hardware for which more modern drivers or support do not exist.

Read the rest of this entry »

Posted in Power User, Windows, Windows 10, Windows XP | Leave a Comment »

Windows: shutdown or reboot while preserving most of the running apps has been possible since…

Posted by jpluimers on 2022/05/26

Vista!

Shutting down or rebooting Windows allowing existing applications to reopen

Windows Vista introduced the /g switch in shutdown.exe and was unchanged in Windows 7:

    /g         Shutdown and restart the computer. After the system is
               rebooted, restart any registered applications.

I never noticed it until Windows 10 which began actively use it when applying system updates: then suddenly many of the previously running applications would reopen during startup.

Read the rest of this entry »

Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Vista, Windows XP | Leave a Comment »

Converting an existing XP machine to a VMware ESXi  Virtual Machine and having boot issues?

Posted by jpluimers on 2022/05/02

A while ago I wrote about Stop 0x0000007B after converting an existing XP machine to a Virtual Machine (ESXi, Hyper-V, or other).

After this, the machine still had boot issues (a grey or black screen after boot, unless booted via Grub from a rescue CD).

The solution in retrospect was simple, but I only figured out after the fact what the solution had done.

Of course this gave me a facepalm moment, as back in the days, this was exactly the warning I gave everyone when installing Windows XP on ESXi anyway: use a SCSI buslogic based virtual disk, not an IDE or SATA virtual disk.

The reason is that Windows XP does not like the IDE/SATA disk that VMware provides. Windows Vista and up are less of a problem.

This is indeed what my practical solution did:

  • VMware Converter 4.x creates a VM with an IDE/SATA disk (as it cannot talk to the more recent ESXi versions at all because of API changes)
  • VMware Converter 6.x creates a VM with a buslogic SCSI base disk (and it can create it directly on your ESXi rig, though it will use a directory in the root of your data store, even if you prefer it somewhere deeper in the directory tree)

References:

–jeroen

Posted in ESXi6, ESXi6.5, ESXi6.7, Hardware, Power User, SAS/SATA, SCSI, Virtualization, VMware, VMware Converter, VMware ESXi, Windows, Windows XP | Leave a Comment »

10 things you can do when Windows XP won’t boot – TechRepublic

Posted by jpluimers on 2022/03/30

For my link archive:

If your computer powers up okay, but the Windows XP operating system won’t boot properly, you have some troubleshooting ahead of you. Here’s a look at the likely culprits and what you can do to fix the problem.

[Wayback] 10 things you can do when Windows XP won’t boot – TechRepublic

Via: [Wayback/Archive.is] Product IDs – Lunarsoft Wiki

–jeroen

Posted in Power User, Windows, Windows XP | Leave a Comment »

windows xp – How to know which license version has an XP installed system – Super User

Posted by jpluimers on 2022/03/29

When virtualising your final physical Windows XP machines (just in case you need to hook up old hardware that is unsupported from newer Windows versions), you need to figure out the kind of license of each physical Windows XP machine in order to stand a chance to keep it licensed.

This answer by [Wayback] Moab [Wayback] windows xp – How to know which license version has an XP installed system – Super User helped me a lot.

I tried to make it a bit easier to read:

  1. First obtain the “Product ID” from the Windows XP machine. It is derived from the original Windows XP installation product key and displays a few values:

    xxxxx-yyy-zzzzzzz-zzzzz

    • xxxxx: the MCP (Microsoft Product Code) describing which product version, or in case of Windows XP: what language, edition (like “Home” and “Pro”) and often some more information)
    • yyy: the Channel ID (especially important to set apart OEM from other channels; OEM is not allowed to be virtualised, so would need a complete new Windows XP key to be activated as Virtual Machine; Channel IDs being neither OEM nor VLK (volume license key) can often be re-activated, sometimes over the phone to explain the situation; I’ve not tried virtualising a VLK based Windows XP yet.
    • zzzzzzz-zzzzz: semi-random values

    [Wayback/Archive.is] Product IDs – Lunarsoft Wiki has quite detailed lists of not just the MCP and Channel ID values for Windows XP and Windows Server 2003, but also the disk volume labels and setup.ini label values.

    Often this is easier to do from the physical machine before virtualising it, but even afterwards you can get it by running Windows in Safe Mode, then use either of these to get the Product ID:

    1. Run the Windows Contol Panel applet sysdm.cpl which shows the “Product ID” us under the “Registerd to” information.
    2. From the console, run reg query "hklm\software\microsoft\windows nt\currentversion" /v ProductID
    3. From another machine or boot CD (like Hiren’s Boot CD or Windows Ultimate Boot CD), mount the hard disk, mount the registry hive, then show the above registry key value
    4. Download and run NirSoft [Wayback] ProduKey (which usually will give you both the Product ID and Product Key)
  2. From the product key, determine if you can re-activate Windows, either by phone, or by this link:

    [Archive.is] Self Service for Mobile

    I got the link from [Wayback] activate windows xp – Microsoft Community via [Wayback] windows xp – How do I activate WindowsXP now that support has ended? – Super User.

    Phone (in most countries) and on-line activation should still work; it worked in 2016 (see [Wayback] license – Will I still be able to activate Windows XP after support ends? – Super User) 2019 (see [Wayback] windows xp – How do I activate WindowsXP now that support has ended? – Super User) and 2020 (see [Wayback] XP activation – Windows XP Home and Professional).

  3. When OEM, try to obtain a legal Windows XP license key that matches the MCP, then change the key using steps in for instance:

    Note that it is no use searching Google for Windows XP License keys: Microsoft did and invalidated them back in the Windows XP SP1, SP2 and SP3 days: Wayback: Error message when you install Windows XP Service Pack 1 (SP1) or Service Pack 2 (SP2): “The product key used to install Windows is invalid

     

The 2001 Windows XP Professional License is archived in the Wayback machine as Microsoft Windows XP Professional END-USER LICENSE AGREEMENT: Windows%20XP_Professional_English_9e8a2f82-c320-4301-869f-839a853868a1.pdf (via [Wayback] Convert your existing Windows XP system into a virtual machine – TechRepublic).

Note this does not cover OEM or Volume Licenses.

–jeroen

Posted in ESXi6, ESXi6.5, ESXi6.7, Power User, Virtualization, VMware, VMware ESXi, Windows, Windows XP | Leave a Comment »

 
%d bloggers like this: