D folder always on my C drive

[Guest xman]

When I've used nlite to create an unattended setup, a folder named D and other files relating to driverpacks always appears on my root folder C after installation. Is there a way to stop them using nlite?

[johnhc]

xman, I do not use driver packs and do not know why they are leaving folders/files about. I would suggest you contact the forum/site where you found the pack and ask them. NLite will not delete this folder directly as far as I know. You could use the RunOnce feature of the Unattended section to run DOS commands to delete the folders/files. This will be done after T-13. I suspect there is no more use of the folder at this time but, of course, can't be sure. NLite has an Option to delete its driver folder (NLDRV in Windows folder). Enjoy, John.

[Sp0iLedBrAt]

Driverpacks are always unpacked in the root of the system hard disk, so that appropriate drivers can be found and installed. I can't remember at the moment if it was at T-18, T-13 or even T-12 with cmdlines.txt. I suggest you use search and find appropriate commands to delete files and/or folders through Command Prompt, and then add the batch file with the commands to the GuiRunOnce in the Unattended section of nLite, which will be executed at first logon.

Cheers

[Guest]

When using DriverPacks_BASE, do not enable "Keep the Drivers (KtD)". The folder will be deleted automatically.

[Guest xman]

Driverpacks are always unpacked in the root of the system hard disk, so that appropriate drivers can be found and installed. I can't remember at the moment if it was at T-18, T-13 or even T-12 with cmdlines.txt. I suggest you use search and find appropriate commands to delete files and/or folders through Command Prompt, and then add the batch file with the commands to the GuiRunOnce in the Unattended section of nLite, which will be executed at first logon.

Cheers

I would have thought the necessary drivers were already installed.

When using DriverPacks_BASE, do not enable "Keep the Drivers (KtD)". The folder will be deleted automatically.

I don't enable the "Keep the Drivers (KTD)". I can't understand it.

Edited December 6, 2009 by xman

[Guest]

Make certain that DriverPacks_BASE is used last, after using nLite but before creating the ISO or burning a disc. nLite makes changes to certain files after using the DriverPacks that may cause your symptoms.

Which do you select in DriverPacks_BASE for the Finisher to run, GuiRunOnce or RunOnceEx?

Edited December 6, 2009 by 5eraph

[Guest xman]

I use the GuiRunOnce.

[Guest]

Please, bear with me. It has been several years since using the DriverPacks myself. Follow these directions and report your findings:

1. Was nLite used after DriverPacks_BASE?
   
2. Open WinNT.sif in I386.
   1. 
      
   2. Find the [GuiRunOnce] section and see if a line with "DPFinisher" or a similar file name is listed.
      
   3. In the [unattended] section, verify that OemPreinstall="Yes" is present.
      
      
   4. Navigate to the $OEM$ folder at the root of your source:
      1. Verify that the file listed in [GuiRunOnce] at step 2-a. is present. It may be in $$, $1, or a subfolder within either.
         

Edited December 6, 2009 by 5eraph

[Guest xman]

Make certain that DriverPacks_BASE is used last, after using nLite but before creating the ISO or burning a disc. nLite makes changes to certain files after using the DriverPacks that may cause your symptoms.

Which do you select in DriverPacks_BASE for the Finisher to run, GuiRunOnce or RunOnceEx?

If I integrate the Driverpacks after nlite, can I still use nlite to create the bootable unattended .ISO?

I use the GuiRunOnce.

[Guest]

Yes, nLite can be used to create the ISO after the DriverPacks, but make no other changes after the DriverPacks.

Please be specific: What were your findings for steps 2 and 3?

[Guest xman]

Yes nlite was used after the DriverPacks_BASE.

There is no section called [GUIRunOnce] in my winnt.sif

No there is no file listed in $OEM$

Edited December 6, 2009 by xman

[Guest]

nLite replaced the WinNT.sif file created by DriverPacks_BASE with one of its own creation. But the Finisher should be somewhere within $OEM$ regardless. It may be necessary to start from the beginning using an unchanged source.

[Guest xman]

nLite replaced the WinNT.sif file created by DriverPacks_BASE with one of its own creation. But the Finisher should be somewhere within $OEM$ regardless. It may be necessary to start from the beginning using an unchanged source.

The only items I have in my $OEM$ folder is $$ in which are Themes under Resources and Wallpaper under Web.

[Guest]

It sounds like nLite removed the $OEM$ folder created by DriverPacks_BASE before adding its own.

The above suggestion still applies: Start from the beginning with an unchanged source. Use nLite, then DriverPacks_BASE, then create ISO.

[Guest xman]

I'm a little confused. Don't you mean the OEM folder created by DriverPacks_BASE and not the $OEM$ which I added myself?

Edited December 6, 2009 by xman