Ponch

Please answer the questions (1 & 2). Also what cd are you starting with (what's on the label)? Attaching the last "session.ini" file would also help. Is the hardware "known good" ? When you say less than 512 meg, is it still more than 64Meg ? In that case, you should stil be able to install. Also depending how much addons you included, you might need a 2gig partition or more as system drive. I guess you have that. AMD64 were produced at the end of 2003 at which point most PCs had 512 of RAM and 40Gig or more of HDD. Celerons are an other story.

You might want to delete it in the Default user as well.

"Pure folie" (it's french) ... I thought so. Thanks.

As most of you know, Seagate makes hybrid disks since a few years, and they seem quite good value. But I haven't found much info about how you actually see the disk. For instance for a 750Gig disk with 8Gig of SSD, I read someone's comment that you are not able to install Windows 7 in the SSD part. He doesn't say why. Seagate says the integration of SSD technology is "transparent" so I guess you don't really see the SSD but the disk (device) uses it internally. Also If I get it right, if you make a dual boot on 2 separate system partitions, you can't "attribute" half the SSD to each so either only one of your OS is gaining from the nature of the disk or you loose a bit of advantage every time you switch from one OS to the other as the internal organisation has to recompute the optimisation ? Or do I get it completely wrong? Has anyone got a little experience/info on those hybrid disks to share ? Thanks.

As far as I remember, there is no "Driver Signing Policy" option in nLite, What you see as result is the settings of the original cd. XP does not have a bcd, Equivalent of "bcdedit" is editing Boot.ini .

Please attach (not paste) your "Last session.ini". I think some users reported that after changing the HAL from "automatic" to something else in the Unattended section.

Not sure if you really mean "repair" or reinstall. AFAIK, you won't be prompted for a key during repair, and only your 6th question is relevant. For a repair, you will need to integrate the CURRENT Service Pack (the one running on the machine), the current Internet Explorer version (more tricky) and the SATA drivers if the disk is not seen when booting from an original cd. Also not sure if integrating other updates has any effect on the repair function. Nor if "Home/Pro" is relevant (in case your CDs are different versions).

You're sure you want to make a cd and reinstall just for that instead of changing this in the registry or create a reg file ? Why would you edit Last Session manually if you intend to run nlite with it anyway and so get the GUI?

Forum Rule 2e.

Integrating SP3 under Win7 will get you problems entering the product key. But befire you retry under XP or a VM, you need to look at your main problem. What do you mean by "after 1st reboot", is it after partition is chosed and XP files are finished being copied to the HDD or did you mean "1st boot" ?

Have you tried integrating the txtsetup.oem file "in text mode"? That file appears on your screenshot. I must admit Allen2's posts and the description ICH10/Marvell are confusing to me as well.

Check for a bios update for your motherboard. I know it sounds odd, but as you state it yourself in the 1st post,

In other thread.

Yes most burning programs can use .ima or .img files instead. I you have an application that really can't do anything than to expand to a physical floppy drive, you can google VFD (virtual floppy drive) to create a virtual floppy drive then make the ima file from there.

Lots of files are replaced by new versions, hence this is not just adding 316 Megabytes. Also the pack includes the installer and verification tools as it is meant to run on any XP system slipstreaming a cd as well as updating any running system). Upgrading your SP2 disc to SP3 level is OK as long as you do this running Windows XP (Vista and 7 create problems with product keys not recognized).

1st, don't ask about illegal downloads, it will only get you banned. We assume you have an original disc. My post about it being possibly not original was just an other possibility to explain similar problems. 2nd, your only problem as i see it is that you integrated a "TEST" user to your XP. Next you retry and nLite does not show that user as it is always assuming you start from an original XP and nLite is NOT scanning for other users and only show standard XP users in addition to what comes in the Last session_u.ini which you did not load (you say). This is why your TEST user is still integrated and you cannot remove it with nLite nor can you see it on nLite's screen. You need to restart with the original disc.

yes.

You are not starting with a fresh set of install files. Or your source is not original. About the bug, as you say you don't load last session, it should not apply.

"Loading last session" loads 2 files; last session.ini and "last session_u.ini". There is known a bug with reloading "last session_u.ini" with added users and trying to remodify them. Try starting from a fresh install and not loading the _u file (rename it before loading last session if needed).

If the computer on which you made the disc is still available, you could find the "Last session.ini" in the "C:\Program files\nLite\Presets" folder. Removed components you can maybe also find in System Properties (Informations button).

The "Last Session.ini" file can be found in the nLite directory (C:\Program Files\NLite\Presets\ ) directory and also in your install files directory if you did not tick the option to remove it. The Last session.ini only reports what has been done the last time modifications were made throug nLite, so it will not tell the whole story if you usenLite twice on the same set of files (which is not advised). Did you set about half the RAM for host and guest ? (512Meg is not much but I know it does work) What does the label on the disc say ?

If you could'n even see the POST screen, it's a hardware problem. I've also had that on a Compaq laptop years ago, the screen would be blank about 1 in every 30 reboots.

Please edit your post to comply with forum rule 12.

This doesn't answer your last question as such but you could create a simple batch fie that does "xcopy /t" from your base folder to the target, so it would do half the work for you (create the directories). Creates directory structure, but does not copy files. Does not include empty directories or subdirectories. /T /E includes empty directories and subdirectories.

You can read those 2 threads as starter.