trying to get a lighter windows xp image using nlite or otherwise

[weplayqa]

I use vmware primarily for qa testing so that I can have versions of internet explorer 7, internet explorer 6, etc... in different images. The main thing the image needs to do is connect to the network, browse, and print. At times the performance of my images is slow and I would like to speed this up if possible. I read about nlite and created an iso image, but when I tried to install it, I got an 'copy file to disk' error. I tried using both an iso image to install, burning the image to a cd, and then trying the cd. I am working on a macbook pro with leopard installed. Anyone have any tips on either what might be causing the 'copy to disk' or the larger issue of lighter image that would run faster for my purposes?

[WoodyZ]

In all likelihood the error you're getting has nothing to do with Fusion per-se since this is evolving a 3rd party product in which you provided additional 3rd party resources and created an ISO image as well as a physical optical media as an installation source in an attempt to install a user modified version of an OS. So the problem is more likely then not with the process you used to create the user modified installation media or corrupted source files then anything to do with Fusion itself.

Anyway I do not know on what system you created the ISO image that has failed but if the ISO image fails it's understandable that the physical optical media created from the ISO image would also fail so my suggestion is to validate the sources and maybe try using different sources and or processing on a different system to try and narrow down the source of the corruption. Or if you have a physical system you can test the optical media on to see if it also fails then that pretty much validates this has nothing to do with Fusion.

As far as tweaking an OS for optimum performance whether it be as part of the install process or after the fact is also not a Fusion issue per-se and while things of that nature have been mention at times before in this forum you would probably find more resources covering this topic by searching the Internet. Just about anything you find on this topic even if they're talking about physical machines will also be applicable to virtual machines when adjusted for context.

[Jae_Ellers]

nLite is a useful tool for customizing installs & adding drivers, etc. There are forums where you can get troubleshooting help.

There are numerous other solutions. Others have built performance oriented editions of Windows XP Professional SP3. You could use one of these as a model for developing your own nLite build.

It would be helpful to have a screenshot or the exact error message.

[weplayqa]

Thanks for the response (and to WoodyZ). I'll see where some of these paths lead.

[weplayqa]

... though as someone who does qa/support I have to respect the request for a screenshot. The license I have should be fine but the cd I started with was a dell oem that does have some type of $oem folder in it. I will follow your other suggestions (including Ultraiso as I do have access to a pc, it just isn't where I have vmware installed). I may also dig through boxes and look for a full xp install disk and start the process over. Thanks again for the response and suggestions.

[admin]

Are you trying to use Easy Install? Easy Install is only meant for the normal, official CDs or images. Customized install media (such as generated by nLite) have a good chance of not working.

[weplayqa]

I was using easy install. I couldn't find a way to get around it from 'new' in the virtual machine library or the drop downs. Is there another way to create a virtual machine?

[WoodyZ]

I was using easy install. I couldn't find a way to get around it from 'new' in the virtual machine library or the drop downs. Is there another way to create a virtual machine?

When you get to Windows Easy Install while using the New Virtual Machine Assistant just uncheck the Use Easy Install check box.

[WoodyZ]

The license I have should be fine but the cd I started with was a dell oem that does have some type of $oem folder in it.

Dell OEM Windows CD's are typically tied to Dell hardware and may not install however the issue with a branded OEM disc is by EULA it's prohibited to use on any system other then the one it was originally installed on by the manufacture.

[weplayqa]

thanks. Didn't solve the copy error, but that's ok. I'm going to do some more research, look for the non-oem cd for any technical and/or eula concerns, and then give it a fresh start.

[admin]

If you search for (pirate version of Windows, redacted) you'll find one stripped down example.

I don't really think that's a good idea. Aside from the huge legal problem of being a pirate version of Windows, there's also the practical problem of knowing what's in it (e.g. did the creator remove some important driver) or trusting it (e.g. is it clean). At least with an nLite (or similar) image you create yourself, you (theoretically) know what's in it and IMO there's a stronger chain of trust. I believe there are already preconfigured option lists for nLite, so it shouldn't be too hard to create a properly stripped-down version.

The thing about stripped down versions is that if you run into a problem, you need to know whether it's a legitimate bug or a result of removing some component you shouldn't have (and as someone who does QA/Support, weplayqa should appreciate this firsthand). Because of this, it's best to understand what it is you're modifying and what the repercussions are, which you're only going to get by understanding the process (and not by copying someone else's notes). If you're not willing to take the time to do this (which is reasonable, as OSes are complex), it's also probably better that you not customize things.

[weplayqa]

Point taken. I'm not resolved yet, but I've got ideas on how to proceed.

[Jae_Ellers]

That error is typically caused by either bad media or disk and/or controller errors. I have also seen that error installing over the top of an old XP version and having ACL issues.

I have modified my earlier post. It is reasonable to search for the stripped down versions as there is a web page describing how this system was developed.

[drval]

You might also want to consider using XPEmbedded, esp if you're going to be doing this on a collection of systems and not just one.

[weplayqa]

There results of that search did turn up what had been removed which is helpful. I haven't been able to solve my errors yet mainly because I've been bogged down with other things, am hoping to give it a fresh start over the weekend or early next week.