Ponch

-What cd do you start with ? -does OOBE run when using your original cd ? -do you do all work in 1 session ?

It was an addon causing that (Enterprise Archive Solution). Upgraded, ok.

It doesn't work like that. It is for you to know what is essential or not. +TinyXP refers to an illegal distribution of a barely usable version of XP that for me doesn't make sense on today's hardware.

Check this thread: http://www.msfn.org/board/nlite-into-multiple-700mb-burning-t141459-pid-905566.html/page__p__905566__hl__multiple__fromsearch__1#entry905566 or if you have a 2Gig USB stick that you can format, you could check the "Install XP from USB" subforum.

Do you click on "Set" before "OK" ?

Google for that error and you'll find a few answers (for old IBM PCs if this is your case). First I found were -wrongly jumpered IDE drives. -using PS2 mouse causing the error. Has anything been changed (hardware) since last time it started alright ? +Giving more info on your system would get you more people to answer.

The "power saving mode" message is probably comming from the screen itself, meaning the PC doesn't send any video signal or that the signal is out of range. You probably do not have an XP problem but a hardware problem, motherboard or configuration. You should not choose "Resume" but F1 to go into BIOS and choose to set it to default (apparently the system has done it already?) and SAVE before exit. Then report how old is the PC and what is the last thing that appears on the screen if it still doesn't start. Good luck.

Depends on what's been done already and on what's in the pipe. So the global answer is always start with an original. or... an original with ONLY service pack applied.

I'd begin with a search for "recovery partition".

Yes it's better to remake an image. If you choose your WinRAR solution, you'll need 14Gig extra disk space on an NTFS volume to extract the image prior to be able to apply it.

That's usually the result of no active partition.

+How is this nLite related ?

Hello, strange thing here. Outlook 2003. We have a .msg file with a .doc form. Users can get it from a web link but the problem is the same if opened from the desktop. The msg contains an attached .doc form. If sent as is, the attachement is sent ok. If modified and reattached (or even removed and reattached) or if replaced by any other attachement (.doc or even .txt), the attachement is not sent. ??? Strange is that it does work on some PC, not on others so it is a matter of settings or of security. Any idea ? If an other attachement is included along with the original, only the original is sent.

1) I'm not sure at all this will fix your problem. 2) Dell has Bios upgrades that run under Windows or even a BartPE/WinPE.

For your first point, you've done it right. Only warning I can give is that if there is no E: drive accessible before install (if you use that disc on an other computer or after repartitioning), XP setup will crash. This is according to your example (I mean probably the complete path up to \documents and settings\ should exist, I can't confirm that, but in your example, "E:\" should be enough). 2nd point, when getting the drivers in nLite, you should delete those that are not specifically for your system, like for Win2000, XP X64 or others. You can do that when they are displayed in the drivers window. But I think it is not that bad if you leave them, it will just bloat your cd, XP will only use those that are needed. I've never used the RunOnce option so I'll leave it to someone else to answser that one.

What makes you think plugging it through USB cable will get you a better connection ? I'd think it would just make the recovery slower and more painful.

What problem are you referring to ? It seems you bought a cable to connect a Nokia phone.

I've seen such problem on a Dell server solved by Bios upgrade.

Unfortunately, nLite is for personal use only and you can't use it to fix your customer's laptop.

Edited. Never mind. (was just going to say that there were only a few months between WinPE2.0 and the last version of XOSL2 in January 2007).

To be clear, it's NO. You should NOT load a last session on a different set of files, you'll end up with a different result and also nLite is not meant to be ran on anything but an original set of files (I know we keep repeating this but some people seem to have a hard time getting it through). As a rule, this is not good. You'll always end up with replies like "it could work but maybe not".

fyi, nLite cannot be used in a Company context, it's in the License agreement.

I have both and they're the same (and both run).

That's the problem. If one is entitled to use a VLK key, one should probably know what VLK means. VLK is used in companies while nLite is for private fun only (it's in its EULA).

Because there is such thing as an original Windows XP SP3 (but nLite won't check if it is an original or not) and also because for SOME operations like adding a driver or some updates in SOME cases you can use a previously nLited source. But... to avoid running into the troubles you have (and that's why you posted here first), you should always start from an original set of files. What you can also do is apply ONLY SP3 (via nLite or with its /integrate switch) to your original set of files and use it as an original SP3 for your next builds.