Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Bootable XP disk

Recommended Posts

Yes and no.

Any Virtual Machine (specific, detailed make/version) will be built with some "Virtual Hardware" coded inside it.

As an example, VmWare virtual machines generally default to a "virtual" LSI SCSI subsystem (but there is a specific option to use a - still simulated - "normal" IDE bus (and virtual devices).

Such VMs usually provide (for the supported operating systems) the specific drivers needed.

It seems to me like you have two separate steps before you.

The first one is to *somehow* make your "upgrade disk a "full install disk".

The second is to add to it (if needed) the AHCI/SATA drivers that the "real" machine(s) you want to install it to might need.

Whether objective #1 is "legal" is highly debatable, however what you can do is start from the actual files on your original CD/DVD.

If you start following these threads (seemingly unrelated):




in those the scope was to make an XP install CD with the files from the \I386 directory that most manufacturers (particularly of laptops) used to have on hard disk in case the original CD was lost (or was never provided).

You are in a very similar situation, though you have an actual "upgrade" CD.

If you are OK with a looong an winding thread :w00t:, this one goes into the most small details (at the expense of a lot of words :ph34r:):


To do the test I would personally use Qemu (actually Qemu Manager) because it is a Virtual Machine that by default uses the most "normal" virtual hardware around, and - while it's operation will probably result slower than other alternatives - has a simulated hardware that is well recognized by *any* OS, here:



Share this post

Link to post
Share on other sites

Sadly, the path to making an Upgrade into a Full wouldn't really make any difference unless you have a Full key. An Upgrade key fully well works on a Full cd (AFAICR) but not vice-versa. I "obtained" and Upgrade key at one time and used it with the "borrowed" Full version (from a friend). Both keys worked. However, I did NOT "change" anything (certain file/files) to "create" an Upgrade version. The tacktech links in the first link jaclaz gave (scroll down in that thread) will show you the difference between Upgrade and OEM. OEM's (e.g. Dell/HP Specific) has (-may- have) other "certain files" that are even more different and is irrelevant in this case as they are for using the "internal" (OEM-Specific) Key along with SLP, although the Key on the PC will work with it (it's your personal OEM Key).

A "hint" is here - http://wiki.lunarsoft.net/wiki/Product_IDs

The "ExtraData" part is irrelevant in your case, as it's the same (should be) between them for SP2 Source.

Basically, what I'm saying is, even if you "changed" it into Full, you STILL only have an Upgrade Key which will determine the "type" (Upgrade, not Full/OEM) of Install. Therefore that "change" is totally irrelevant. The "basic" problem still lies with Slipstreaming whatever is necessary and installing in a VM and the TRYING on the real PC.

Side note - ALL files on your XP SP2 CD should be dated 08/04/2004 (Aug 4, 2004) - if not, you have an "altered" one somehow.


Share this post

Link to post
Share on other sites

I think we are getting this thing far more complicated than it needs to be.

I don't see a problem (yet) with the key. Activation should be possible (why go OEM?). I don't see a problem with poping a Win98 cd at install, I guess he has one

I also don't see any reference to the virtualization method that is used, I don't see what why nLite should be used.

(@PinkFreud) I sureley don't see why he should install XP in a VM (which he has trouble doing and asks help for ) in order to install nLite in order to install XP in a VM (which he has trouble doing and asks help for).

And I can't see an answer to any of the three questions in my first post, as it seems that the SP2 install was tried (and failed) on real hardware. As it stands, we are nowhere. :no:

Share this post

Link to post
Share on other sites

??? That's what has been said. I only point out that since the OP has an UPGRADE (Retail, obviously) that simple slipping of the SP3+Fixes should be all that's needed since the Key will -only- work with Upgrade (with valid old OS media). Further, changing a RETAIL Upgrade to FPP will not work with that key.

The problem is that the OP has "somehow" failed in installing on an unnamed VM and assuming it has to do with SATA Drivers, etc. This (slipstreaming) should work in a VM but using AHCI on the REAL Hardware would need the additional step of repeating the nLite and integrating the TextMode drivers.

And yes, the OP apparently is not answering questions, just posing more and/or doing "other" things rather than following simple instructions.

Share this post

Link to post
Share on other sites

First of all, may I say a big thank you for all of your responses. Although I may not have responded directly to certain points I have been reading them all and trying to piece together all the information to have a better understanding of what is going on. Last night I started from basics again. Created a new virtual disc using the MS VM with 1024 Meg of RAM and 3072 Meg of disc space. I then went through the install of the virtual XP using my Win 98 boot disc and the XP SP2 Upgrade disc and it loaded! I don't think I did anything different other than using the SP2 disc rather than my SP3 slipstreamed one - but it worked.

I need to now understand how the virtual XP works to make the most of it. If anyone can point me to a helpful guide, it will be appreciated as I obviously need to load some antivirus and the SP3 plus anything else and at the moment I can't see how to do it. I haven't loaded the integration package and that is something else I need to find out how to do.

Thanks again for all your help.

Share this post

Link to post
Share on other sites

(jeez - banging head on desk...)

Can you PLEASE specify WHICH MS VM? There are SEVERAL variations! Give the LINK to the one you installed and THEN we may help you. PLEASE answer just a FEW basic questions? Reading, then seeing questions, and giving NO answers (what you are doing) is NOT going to allow any of us to help you AT ALL!

Share this post

Link to post
Share on other sites

As requested, here are the details of the MS VM. It is Windows Virtual PC and the file version from vmwindow.exe is 6.1.7601.17514. It is running in Windows 7 Home Premium SP1. The PC is from PC Specialist in the UK and is built using standard ( not tailored) components.

I had to start again with the load as the previous allocation of disk space was insufficient. I have now allocated a max of 20480MB.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.