ibliss

just came across this... http://vernalex.com/tools/spdrvscn/index.shtml I know it's meant for sysprep use, but... in the description it says that the registry value for oempnpdriverspath can be VERY frackin large... whereas i read up to now that it's limited to 4000 chars? (which is what you say too) So what is the right thing to believe? Should it work that way? This should solve some problems then... Anyone knows if there is a default registry file located somewhere in the windows setup? Or is it just generated during install from bits and pieces all over the place? If there was a default, maybe this could be modified to include a nice path (i think there are registry editors that don't require windoze to be running, so it might even be automated then...)

i guess you're familiar with this topic wrt the 'add new hardware found' wizard ? (it is frackin' annoying when i have to click in an unattenden=d setup especially when running it on 20+ slow machines)

Ye that's my point to create it. Problem is that after going thru all files from bashrat drivers pack the file with db output is 850kb in size!!! Putting it both at file/memory at same time takes around 662008.467556631ms = 6minutes. Depending if hdd/ram cache kicked in it might be longer. Also it will be hardware dependant. I'm wondering how much time it will take to load it from file to memory (at the time of using the app from earlier preparation) if it will be any faster then doing it all at the time of instalation. Anyway i'll do more testing, will try to remove some unnessecary code + put some additinal code how to handle it. I will probably introduce 2 options. One to use be used as created predb and then loading from at time of instalation or doing it straight at deployment time. One way or another it will take some time Then you have to load it with my program sorry, dont have a windows machine here, will try to test it (==the wmi stuff) tomorrow or otherwise thursday (/me not working on wednesdays, and only have windoze pc available at schools i work for)... Could you specify the format you want your data to be in? I'm extracting data from .inf files right now with some simple linux commands (grep, awk) I could create a php script that does the same, so you can use it on windoze, but i'm really not that good with php and the like

Ye ye, the error seems to be there for a lot of ppl so i'll try to reproduce it why it happens. As for the Wizard comming up i'll check it out aswell. The Inf database is my priority after finishing up with the errors I've some working code for the db creation but it seems that getting thru a lot of .inf files takes a lot of time. It may be worth it thou as the RegistryDevicePath limit won't be the concern here anymore. I'll be trying to optimize the code. Just hold on. just some info: i dont get the "COM error with DOM!" on one of my winxp machines (have tested it only so far with a machine that has been running for a while, so maybe there have been some extra/new components installed... (XML parsing COM stuff probably, maybe something with updated IE components?)

it be worth it especially in the following scenario: * drivers always located on same location (eg z:\drivers) * program always called from same location (so the once created DB is always available) which is (of course) my scenario ibliss PS: why cant windoze just use a top-tree directory as DevicePath and search it recursively for drivers.... *sigh*

i have the same problem: the wizard coming up.. however, when pressing next next next... it doesnt work: file not found dialog, prompting for file location, when pointing to file, weird things happen: 1. file keeps getting not recognized 2. for some reason a "\" is prepended to the path that is returned everytime it said 'file not found'.. so i guess sometihng is set wrong with that path also, i have the "COM error with DOM!" stuff... see attached screenshot hardware_config.xml in attachment location of drivers: unpacked driverpacks at z:\drivers os = win2k The inf dataase project seems very promising, and i think it will be the solution to most of my problems with this program