Search options (Page 55 of 213)

Hmm... Long values (more than 2,048 bytes) must be stored as files with the file names stored in the registry.

Can't find any documentation on this... but it just may be the solution I have been searching for... the 16k limit would fit with the issues reported and explain a lot of the problems we have been having with too many tpdps being added... We suspected we had hit some sort of limit but most documentation led us/me to belive the cap was higher than 16k. Any clues as to how to implement pointing to a file and what the format of the file would be? (A binary format I must assume, but that is not specific enough to generate one, nor specificaly how to indicate it in the registry. ) Typical MS merry go round it documented somwhere but good luck finding it (i thought bing was supposed to be the cure for that ) I've tried every keyword search i can think of... with three different search engines and the built in MS search. I jsut need to figure out what the correct question is LOL

still no log? You are quite dense

you need to learn to read.

My name and address are plastered everywhere, come on over...
If you bring your PC with you I'll fix that too, my rate is $165 per hour

Um no i never have had to ask for help, when i started in 1968 there was no one to ask.
When i worked for the phone company and we rolled out the first installs of DSL in the world not even Cisco had the answers. They said "hey when you figure it out please let us know" And I just had to figure it out myself. I have always been the one that people came to when NOBODY else could find the answers. So no, I have no sympathy for you.

Conversely everything you need is well documented.... In multiple places, all you have to do is look / read.
you obviously just want free help, and are totaly unwilling to do anything to help yourself. Including read.
We don't hold peoples hands at DriverPacks.net

Either provide the info listed in Read BEFORE you post or recieve no help, it is up to you... I'm not going to ban you.
In fact I went out of my way to help you... I even showed you where to find your answers, in spite of you not following the rules or reading the documentation.

Throw another temper tantrum if you like!

An intelligent person would simply provide the missing details and read the linked to info... (Kinda missed the main idea, didn't ya?)

PS you're right courtesy is a two way street and you neither said please or thank you...
nor did you show us any courtesy, IE you did not try to help yourself and prevent the waste of our time.
nor did you say anything nice about us or our FREE project at all
I showed you way more courtesy than you showed us... which was none. (post your log dude!)

only use the nightly mass with the nightly BASE otherwise your source WILL be hosed

I have seen issues with DPInst.exe where it does not behave the same as setup.exe IDK why...
Perhaps a new version of DPInst will be released in the future.

You can still use a script with devcon to remove and reinstall a particular device .

the answer to why it failed is / will be contained in setupapi.log... I haven't had a chance to review the one you submitted yet.

OEMPNPDriversPath has a limit of 4096 in normal windows installation, and half that in SysPrep. If you exceed a path length of 2048 in sysprep then either nothing is installed or only the first 2048, usually nothing .

I suggest you include chipset in  OEMPNPDriversPath, that may cure your issue.

Also I highly recomend you take a long hard look at OLSP (Off Line SysPrep by Galapo).

Let me know if the issue still persists after you add chipset to your base install.

alternately you could try running SAD twice... IE sometimes certain drivers will depend on others, hda depends on hdabus (hdabus=KB888111), hdabus depends on pcibus, no hdabus then no hda this would require two / three passes Test: run SAD reboot run SAD agian... does it work now?

Can you do a test for me please?

I log my chats... and will copy them here if you force me to do so

I did NOT use any expletives,  although Silly was definitely used... and that was well deserved.

I can't believe you actually posted a log from September of last year,
and tried to pass it off as a current problem. (you are being silly again)

If you are unwilling to cooperate by providing the requested info then we can't help you. Simple.
Same thing I told you in chat. I need your logs or I can't help.  We still don't have valid logs .

I also told you your source was no good... This you argued with me.
But let's face it if this is working for thousands of other people, except for you... then we know exactly where the issue exists.

It is either your source or your process... The logs will tell us, if you ever post them.

Your logs don't lie and we know exactly what to look for and where, just like mr_s busted you on not providing a current log.
He also busted you for removing driver files then attempting a reinstall of the deleted driver. When it comes to XP installation we can't be fooled.

If you are unwilling or unable to follow simple directions then we will not be able to help you.
We certainly DO want to help you, but you must be willing to do as we direct you to do. (so far this has not been the case)
IF you are not willing to do as asked that is not our unwillingness to help it is your refusal to cooperate.
That is totally different... It seems like you just want us to say this is our problem, yet you have provided no evidence that it is?

Follow mr_smartepants simple instructions, especially the part about a legitimate hologram-ed XP CD.
Not the copy of XP you said / admitted to me that you downloaded for one dollar of the net
Also nLite's Licence clearly states that it is not to be used for commercial purposes, (For HOME USE ONLY) yet you use it in your PC shop. I have done nothing except try to help you, I even spent an hour in chat with you, and for that you are disrespectful to me?
- It is you who has behaved shamefully!
Go legit or go home! (be warned, I have a complete log of our chat session and your IP address)

Take another shot at me and I will clean up the floor with you . (Show some respect sir!)

that is an archive (self extracting) run it and it will extract itself to a folder on your hdd

BE absolutely certain you only use DriverPack MassStorage 10.x with DriverPacks BASE 10.3 or better, otherwise you will completely HOSE your source
If you have already made this mistake then your source is wasted, hosed, FUBAR. Hint: i always make a backup of my source before i use nLite and before i use DriverPacks BASE, I never work on my original(s), always work on a copy

IE run RVMI on source, (C:\XPSP3-RVM) make copy (C:\XPSP3-nLite)
run nLite on copy of source, (C:\XPSP3-nLite) make copy (C:\XPSP3-BASE)
run DriverPacks BASE on copy of source, (C:\XPSP3-BASE)

never work on original, always on copy ...
That way you don't have to start from scratch if something goes wrong...

Well it is not a bug... it is by design.

If you were to update then the last pack would be selected for slipstream and not the most recent...
IE DriverPack Graphics A 8.12 selected for integrations but DriverPack Graphics A 10.3 was downloaded and available
If you visit the update page then all pack selections are cleared...
the module that finds the most recent versions of the packs in the DriverPacks folder clears the pack selections
If you look at a DPs_BASE.log you will see that the DPs_BASE.ini is loaded after the list of most recent packs is written to the log .
( you could of course reload your DPs_BASE.ini settings file (including your pack selections) from the start page )

that was the whole reason i moved the update page to the front of the list of pages presented to the user. (In all versions post 8.12.x)

In this way the update page appears before the select packs page and "discourages" update checking after the packs are selected. and encourages updating before the packs are selected.

Although it would still be possable to select your packs then go to the update page and "accidentally" clear your selections. Less likely but still possable.

you can test this if you want make all your selections then select the  updatechecker page then return to the settings-DriverPacks page from the GUI tree... You will find all of the selections you made are now gone...

Exactly right! the only thing that could cause that is a missing dummy setup.ex_ and or missing / corrupted presetup.cmd.

Again did you change anything after you installed DriverPacks???
waht is the MD5 checksum on setup.ex_?
does presetup.cmd exist?

@ Sammy need the logs !