Upgrading through Windows NT; Windows XP Pro

No more NetBEUI

While without fail Windows XP may have been the most popular version of Windows ever, it did remove the OS/2 subsystem, something I had grown used to having around.

But without fail the MS-DOS and DPMI environments were still in place.

Windows XP of course also entered the home market with the aptly named Windows XP Home edition, which was limited to a single processor and couldn’t join any domains.  For the sake of my upgrade path, the ‘workstation’ versions became PRO with Windows 2000 & XP, so that is what I’ve upgraded to is XP Pro, without the slipstreamed SP1/2/3.

Faster, more reliable!

 

Unfortuanatly right now this is the end of the road, XP doesn’t upgrade correctly from Windows 2000 and it leaves me with a black screen at best, or a BSOD related to Bug Check 0x19: BAD_POOL_HEADER … Error code was 20 so … there you go.

5 thoughts on “Upgrading through Windows NT; Windows XP Pro

  1. I’m running into the same problem with VirtualBox. Seems that multiple upgrades takes its toll on something related to video drivers or likely the registry. If I install the VBox additions in 2000 (after fixing the same stupid permissions problems), I can see the final XP setup screen asking about setting automatic updates. After that it tries to log in and just…. hangs. No lockups or BSODs though.

    I’m going to give it a shot on real hardware, but something tells me I’m going to run into the same issue.

    • I think it’s the upgrade from 3.1 to 3.5 that breaks the whole thing. I’m somewhat sure that ignoring 3.1 will give far better results. I think 3.1 sets security on some part of the registry that later versions need.

      • Sure enough, NT 3.1 was the problem. Started with NT 3.51 and now up to Windows 7. After 2000, upgrades wipe out custom themes and wallpaper for the most part.

        • It kind of figures, NT 3.5 was really first ‘feature complete’ version of NT, 3.1 was really more of a get it the out the door already kind of release with that wonky Spider TCP/IP.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.