axelseaa

I am looking for a scripted way to set file type associations. Commonly our media files get changes due to software upgrades and such - and it would be nice to just run a script to fix things. I have found informatino about the assoc and ftype commands, but when trying to change a wmv file to play back in VLC instead of windows media player it does not work correctly. Does anyone have any ideas? Thanks!

I have added the sysprepmassstorage drivers: PCI\VEN_10DE&DEV_008E=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_00D5=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_00EE=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_00E3=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_0036=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_003E=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_0054=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_0055=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_0266=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_0267=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_036F=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_037E=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_037F=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_03F6=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_03F7=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf PCI\VEN_10DE&DEV_03E7=c:\sysprep\drivers\xps-710\nvraid\nvraid.inf However, It still bluescreen's with the 7b stop code. Any other suggestions as to what the issue is?

I am trying to image a XPS 710 with the same image we use on all of our other dell's gx260, gx270, gx280, latitudes, etc However, I come up with a BSOD 7b error. I think this is related to not having the proper mass storage drivers since I can't even boot off a regular winxp cd (using the dell supplied OEM cd works). Does anyone have any suggestions on how I can get my current image to work on the XPS?

Tried that, still similiar behavior. I also tried the program posted above to detect the drivers. When i used that, the drivers were not installed at all, and nothing worked.

I did before, but the sysprep documentation says that the UpdateInstalledDrivers line and the -pnp switch should not be used together. This also appeared to be the issue before as well though

That definetly looks like a handy program, i'll give that a shot and see what happens. The way the image is setup, it is in a VM Virtual machine, and the HAL is set to Standard PC. Could the UpdateUPHal line of the sysprep be causing the drivers to not work at mini-setup?

Greetings! I am attempting to build a windows image on a VMware Virtual Machine. I have been using the sysprep file below, and have been running "sysprep -mini -reseal". Here is the problem. When the mini setup runs, it does not have the network drivers installed so it is not able to join the domain. The weird thing however, is that after the first login, windows detects and installs all the drivers successfully without asking for locations of drivers, which leads me to believe its not an issues with mini setup finding the drivers. Does the OemPNPDriversPath directory structure have to be anything specific? Is there any reason for this behavior? Any info is appreciated, thanks! -- Aaron Sysprep.inf: