-
Update; I don't know what was causing that error, but now before running nLite, I slipstreamed SP3 into XP2 using the /integrate switch, and nLite seems to work fine on that as long as I add the DPs drivers a chunk at a time (C,CPU,G,L,M,S) and not all at once.
-
Thanks, jaclaz. That makes a lot of sense. FYI I am using BartPE (XPpro) to run winnt32.exe from an NTFS volume to install XPpro on my NTFS formatted C-drive, and it appears that winnt32.exe is truncating the 'theme' extension to 'the'. I am testing a workaround at this time.
-
Interesting for me too, tomzi. I am glad you picked up this thread and commented. I am having the same issues. In my case also, long files names (>3 extension) are not getting copied. I am booting to my installation files on the network using a BartPE (XP) bootdisk. Then I am running \network _folder\winn32.exe /unattend:winnt.sif. After the XP setup reboots into the my now local nLited XP Pro installation, I get messages that it can't copy MYTHEME.THE. The actual filename is MyTheme.theme. I am trying to take advantage of nLite's ability to install a custom theme and use it as the default. (Yes, I've installed the uxtheme patch.) FYI, I am building the XP SP3 nLite install on my XP SP3 workstation. Please let me know what you learn and I will do the same. thx!
-
I am running nLite 1.4.6 on XP Pro SP3 and get the error message "Visual C++ Runtime Error! R6025 - pure virtual function call" just as I begin the integration process, adding multiple drivers from a decompressed DriverPacks folder to my XP Pro SP2 installation files. I have had this occur twice. nLite closes after clicking on the error message dialog. See the attachment. nLite_VisualC__RuntimeError01.doc
-
Yes, I know about /integrate. I was hoping nLite would take care of this, but I no longer trust it, and also will need to do it "manually" using /integrate.
-
Its not just me. I found some one else with the exact same problem at http://www.tek-tips.com/viewthread.cfm?qid...6715&page=2 I am using nLite 1.4.6 which is supposed to fix XP SP3 issues. I hate to abandon service pack slipstreaming using nLite. It looks like a great tool to simplify our new hardware builds. But does anyone have a solution to this issue?