Ponch

I think you got a bit confused with "integration" concept. It seems you have put your drivers in the CD directory. This is not needed as they are integrated by nLite in the install files (so now you have them twice on your cd). But it should work anyway. The ini shows from where they were integrated, not from where they have to be taken when XP installs.

"U3" sticks get two drive letters, I guess they have two partitions ? I also saw that for "fingerprint secured" sticks. One partition for the security system, one for data.

There's a portable version of Avant Browser (the one thaty says "USB disk version") if you want to try it with IE6 before you make definitive moves.

Search for "removed keyboard layouts".

What are the modifications you made between "everything works great" and "windows will not install" ?

ISO is a complete image of your CD. You don't burn the file to a data cd nor to a bootable cd, adding other boot files. In Nero for instance, you must (find and) use the menu "BURN IMAGE" and point to the ISO files. And you're done !

And what's written on that XP cd ??? For your first issue, is it possible that the 1st time you installed XP, you installed on top of 98se and that's what made the difference and the "good" behaviour of your screen ? If format wasn't erasing data, I think people would have noticed by now.

Zodehala, please read the replies you're given. And that one is given 10 times a day. There's your problem. You integrate a service pack to an incomplete XP version. If it's not there for starting, and it's not added by SP3 either, it won't be there at finish. But adding a SP sort of resets something that makes nLite work as if you were working on a complete OS, so the resulting installer tries to copy the file. Then you get that error.

What do you mean with that ? What did it say ? I'd be surprised any vendor wouldn't have a working driver for XP, unless you card is really too old for your laptop to run XP. Format does erase data "enough" for XP to consider them "gone", so there might also be a hardware problem (video memory?) or maybe a Bios setting that you could change.

That's because it is a component that is not included in XP SP1 for a start (Blaster appeared in the late 2003), so that line is probably ignored when the presets are loaded. Then it's added by your SP3 and reappears for removal. I had the same problem with some exotic languages in SP3.

For your info, I created 4 linux partitions on a drive, rebooted to start XP install, deleted the 1st one, tried to select unalocated space for installing Windows, and got the same message as in your 1st post. Then went to bed as it was late. Just before that I had tried with this setup: -free space -PR-FAT32 ACTIVE -PR-FAT32 -PR-FAT32 and it (XP install process) created an extended partition in the free space. Maybe that's normal if you have it installing in a non active partition ? Maybe you were and maybe XP setup considers exotic partitions as extended and doesn't create a 2nd one ? More later ?

What size is the file ? What is the destination? You could begin to do a "chkdsk /r /f" on both drives.

Wrong option, ...Nero made you a bootable cd with an iso file on it, but it boots Caldera DOS. You need to use the menu "burn image" and select the iso file. the iso contains the boot files and all the files that are transferred onto the cd. Iso is an IMAGE of the cd.

backing geek's comment. Limitation of the file system.

Unfortunately nLite is for personal use only. You agree to that when you install it.

no yes you did, we can see it in you ini file. "CDPromptRemove" When you solve that, note that what happens the first time you use your virtual HDD, there is no partition. In that case, the "press any key to boot from CD" message does never appear as there is no partition to boot from and logical option is to boot from CD. Next, your XP cd install has you creating partitions format them and copy files, and at next reboot you should see the message and be able to not "boot from cd" to resume installation. If not (???), you can still change the virtual machine settings to boot from HDD at that time.

Disabling the message has the machine NOT waiting and just... boot from cd.

You are obviously doing smething wrong. Are you building the ISO in the working directory ?

The key you use might be not quite one you own or that can be used (again ?) for a (that?) computer. It's all a question of license. You know MS XP is not free to be installed on any PC you want, do you ? Either the computer was sold with a license for XP or you own (bought) a disc with a license number (key) that allows you to install XP on ONE computer. You were happily mixing both concepts until now (legally ?) with your one CD but MS brings you back to market reality. More info about what type of computer, what exact cd and what key you are using might bring more precise replies but I guess the discussion could as well be stoped quite abruptly.

I vaguely recall installing Win95 and WinNT from floppies, but I can't remember if the latest used DOS or a preinstall environement. If XP still uses a DOS floppy, see Jaclaz's remark about possibly having remove corresponding support with nLite.

I don't really get the two replies Anyway this is not a question about nLite but about XP unattended so it should be moved. Search for "BartPE" in that forum and you'll already get lots of hints. Formating C: and launching winnt32.exe should not be very difficult.

Everyday you get your strange thing of the day. Today one of my user had his mouse pointer disappearing totally. WinXP-SP2, hardware from 2008, same config on about 90 of them since more than a year (well.... with updates). It would still highlight buttons when hovering or work ok when clicking, and closing all application, going back to desktop made no change. Log off did not solve the problem so I restarted. Anyone got this before or has a nicer workaround ?

A quick search answers both questions: check this.

There's an identical thread in the "software forum".

Until you start the actual nliting process (and the file "last session.ini" gets written), there is no way to save what you've selected or not up to any point. The downside is of course that your set of file gets modified in the process. So there is no point starting nLite in the prospect of doing half the job and coming back to it later. the source is hopefully on a cd, the result is on HDD and in the iso, what exactly are you asking about ? "creating a source" ? Last session.ini is the "road" from A to B. It will only lead you to B if you start from A.