MrJinje

I wrote this a week or three ago, the packages tabpage is basically an install_wim_tweak gui. It does wildcards, unhides single packages, pre-populated drop-down list, etc. All credits to Lite8 / Aviv00 for the original idea back in 2008 that everyone has since stolen.

if you were in powershell, you could call the garbage collector to release those handles after unload the hive. [System.GC]::Collect()http://jrich523.wordpress.com/2012/03/06/powershell-loading-and-unloading-registry-hives/

throw a reg save on the mounted hive before making changes.

If the user is logged out when it runs, you'll need to additionally mount the ntuser.dat file because the SID path is only available while a user is actually logged on.

Not sure, maybe someone with that type of hardware can report back. EDIT: Can verify it works in a VM with a non-loaded A: drive floppy disk. I see an A: in explorer, when I click on it, it says please insert a disk or some such. When I run the script no errors.

Here is my take on the alphabet loop from powershell. 65..90 | Foreach {$tag = "Sources\Install.wim";$drive = [char]$_+':'; $test = $drive + '\' + $tag; If (Test-Path $test){write-warning $drive}}

Maybe if you hold your breath I will release FreeLite™

Easy method write the value to a registry key or temp file, then program your second script where to look.

Does the EULA have a binding arbitration clause ?

Here is an Official™ kludge for readers who cannot wait. Rename attachment to .ps1 and it will do the rest. Side effect, the %TEMP% setting no longer reverts to %APPDATA% upon open. NTLite_Starter_Tool.ps1.txt

1) No they are not duplicated. 2) Yes of course. Here is a powershell snip that prints out net use commands for proof of concept. $MAPS = Get-Item HKCU:\Network\*ForEach ($MAP in $MAPS) { $KEY = ($MAP).name $UNC = (Get-ItemProperty -Path "registry::$KEY" -Name "RemotePath").RemotePath $LETTER = Split-Path -Path $KEY -Leaf Write-Host "Net Use "$LETTER": "`"$UNC`" Write-Host "Net Use "$LETTER": /DELETE /YES"}

The top key is a letter and the value "RemotePath" is the path. Those two values are all you need. Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Network][HKEY_CURRENT_USER\Network\Z]"RemotePath"="\\\\vmware-host\\Shared Folders"So from a programming stand point, just loop through HKCU\Network, look for top level keys (which are single letters), and read it's RemotePath value. Use the net mapping API as it will perform faster than "Net Use". ad infinitum OnLoad event. A second loop removes them during the OnClose event. That setting Andre mentions requires a reboot before it takes effect, re-mapping of pre-existing drives on the fly does not. The effect is instantaneous. Very easy to do. No need to make permanent settings on every machine. Net Use Z: \\vmware-host\Shared FoldersEDIT: I read the article you linked, it seems they back up my story, but for different reasons.

Test box is a Windows 8.1 x86 inside vmware. Opened NTLite after installation, attempted to browse. Did not see the mapped Z: drive which is mapping to shared folder on host machine. I manually mapped the drive via net use command in elevated cmd.exe window and NTLite could see the drive.

On every machine I plug this into ? Last I checked, it's $249 for the USB corporate version. Imagine some of my clients won't like me introducing another 24/7 security risk to their domains. Why not a loop routine during the onopen and onclose events. Temporary mapping, only for the duration of NTLite, un-map them afterwords, leaving no trace.