stebie

Oh ok. Sorry, my bad! - stebie

He made a note that it only started occurring when he added the OemPnPDriversPath option. I'm using FileSystem=* in my winnt.sif file and have no problems. However, I'm not using the OemPnPDriversPath option in mine. I think the issue could be with both. Maybe it's expecting to use a file system that allows for semi-colons in path names (which doesn't exist), therefore reports an error at the first line out of FileSystem and OemPnPDriversPath? Just an idea. The semi-colon is used as a separator for paths, so quoting the whole line is going to make it think the path is inclusive of those semi-colons. Still working with FileSystem, try using FileSystem=LeaveAlonehowever, personally I don't think the issue is with FileSystem. - stebie

Doing a search on Google reveals the following: http://hanzzon.tk/WindowsUpdate.txt All 3 KB (BETA) hotfixes are listed in the text file. KB838904 KB838907 KB838909 As said initially, it appears they're not officially released, so it's up to you what you do with these links. If they fail, try searching Google for KB838904 / KB838907 / KB838909. However, what interests me is the path includes a folder v3-19990518 - hopefully this is to indicate the version of Windows Update and not the age of the files... - stebie

Try OemPnPDriversPath="Drivers\000_chipset";"Drivers\001_network";"Drivers\002_raid\hpt3xx";"Drivers\003_graphics";"Drivers\004_sound";"Drivers\005_modem"if you must. How I see it, the quotes are used to specify one path when spacing is present. So, if you must use quotes, use them around each specific path only and not all paths combined. Also, as suggested earlier, you can do without quotes as none as the paths you've stated include spaces. - stebie