The Nvidia driver is still being worked. I'll post an update when it gets addressed.

Thanks!

Warren

I have a feeling the install of dotnet may have to do with some of these fixes. If there are any requirements though I think they should be noted in the cab instructions and I don't remember seeing anything listed.

Here is the script I use
echo * 6x20 Step 1 STMicroAccelerometer *
echo %date%,%time%,errorlevel: %errorlevel%,6x20_STMicroAccelerometer: Begin >> c:\RISlog\ScriptPack.log
START /WAIT c:\Drivers\misc\R294986\setup.exe /s
echo %date%,%time%,errorlevel: %errorlevel%,6x20_STMicroAccelerometer: End >> c:\RISlog\ScriptPack.log
echo * 6x20 Step 2 ControlVault *
echo %date%,%time%,errorlevel: %errorlevel%,6x20_ControlVault_dotnet: Begin >> c:\RISlog\ScriptPack.log
start /wait c:\install2\dotnet\dotNetFx20SP1_x86.exe /q /norestart
echo %date%,%time%,errorlevel: %errorlevel%,6x20_ControlVault_dotnet: End >> c:\RISlog\ScriptPack.log
echo %date%,%time%,errorlevel: %errorlevel%,6x20_ControlVault_Driver: Begin >> c:\RISlog\ScriptPack.log
cd "c:\Drivers\misc\R293396-ControlVaultSecurityDrivers\"
START /WAIT msiexec /i CVHCI.msi /qn
echo %date%,%time%,errorlevel: %errorlevel%,6x20_ControlDriver: End >> c:\RISlog\ScriptPack.log
echo * 6x20 Step 3 Nvidia 4200m *
echo %date%,%time%,errorlevel: %errorlevel%,6x20_NvidiaDisplayDriver: Begin >> c:\RISlog\ScriptPack.log
START /WAIT c:\Drivers\Video\nvidia\r297610\setup.exe /s /noreboot
echo %date%,%time%,errorlevel: %errorlevel%,6x20_NvidiaDisplayDriver: End >> c:\RISlog\ScriptPack.log
echo * 6x20 Step 4 O2Micro *
echo %date%,%time%,errorlevel: %errorlevel%,6x20_O2Micro: Begin >> c:\RISlog\ScriptPack.log
START /WAIT c:\Drivers\chipset\R300787\setup.exe -SMS -s -f1c:\Drivers\chipset\R300787\SilentInstall.iss -f2c:\RISlog\O2Micro.log
echo %date%,%time%,errorlevel: %errorlevel%,6x20_O2Micro: End >> c:\RISlog\ScriptPack.log
IF ERRORLEVEL 1 GOTO fail

Ok I have resolved all of this by doing this: Deleting all NV*.* files from the cab and then just deploying the new nvidia drivers via a command line script. The cab nv files were causing the above error when I would try to run the install of the new drivers since the ones in the cab don't work. At the same point I also for the e6420 deploy via a script the o2 drivers, free fall sensor and the controlvault drivers. The bad Mass Storage drivers are no longer a problem after this process.

"I have a feeling the install of dotnet may have to do with some of these fixes. If there are any requirements though I think they should be noted in the cab instructions and I don't remember seeing anything listed."

That's an excellent question. I'll check with the Dev team on an pre-requisites like .NET versions.