hehe nice Regarding partitions I made the Unattended cd with Autopartition command...booted it on my main rig...you can figure out the rest Good thing that some recovery software undelete function worked but I'll never forget the horror
Well since I don't have it and it's limited in many ways (parallel processes limit?) I don't see it supported that soon or ever. It uses some Vista deployment routines so I'll check that later on when Vista is final.
Carl_50, you don't need to use the integrator, instead lets find out what went wrong. Prepare clean windows cd with sp2 in it, then try again, only that, just to see was it something else in combination.
Did you maybe disabled Printer Spooler service? Did you use Printer Compatibility while removing components? (it's probably something with removed drivers but lets first do this)
When you select Yes for Apply changes then it is created...or in your case should have been. Really weird...maybe your nlite folder or preset folder is read only or something...but then your manual save wouldn't work too, hm.
Remake it then, from scratch, integrate sp2 and be sure to keep ASMS compression disabled...or maybe even try enabled instead. But be sure to report if you find out the pattern as it always works ok for majority.
RJARRRPCGP, you again with your taunts...how many times I have to explain that your issues were yours only and that I can't fix phantoms even though I tried your setup many times, it always worked...no praying involved.
ricktendo64, this is nlite forum, go to driverpacks if you have nothing to say. shumshum, when you select a certain folder to integrate it integrates that folder and it's subfolders. If you put your lets say display drivers on your desktop full of other files it's your fault. Or who keeps a movie in a sound card driver
True, this is a tricky one and nlite updates the i386 folder correctly with that file but that file has to be copied on two places. Will check it, thx for reporting.
You said it yourself...you do more than nlite so how can i know that it is nlite mistake. When you find out what is causing it let us know if it's something I can fix on my part.
Well if you read more careful you'll see that you're missing the Tahoma font. Install it. I'll see about using other font since this 'issue' was reported 2-3 times.
Oh...the old nemesis. Why not boot from it? I tried several times to recreate the issue but it was ok for me...probably I would need that PXE environment and all...I tried by booting from virtual floppy and then running winnt.exe.
How lond did you wait on 'starting windows'? Sometimes it can get up to a minute or two. For me no but I've seen such issues and waiting solved it. Also check your HDD cables, use ata66+ (if that is the name, the one with double the leads).