Search options (Page 197 of 213)

Could you please post your HWID's

Thanks in advance.

@jaak he didn't listen... sorry we can't have a HWID. Will you tag a few more drivers for exclusion in 2000. it seems we have topped out again with all the new drivers. i think you added a dozen or so so you will problaby need to remove close to the same amount to get under the memory limit of 2000. since he wont cough up the HWID just pick some at random.

newbie wants to tell us how to fix it but can't fix it himself and won't answer simple questions.

What is the HWID of the camera?

Yay it works... lol
it is a rare thing to have someone post when its working.

i suppected it worked but needed a true test with a HDA device connected to the machine.
i don't have a test card / machine that requires HDA support. i think the alpha actually worked too.
It just complained about some spelling errors that didn't show up until i made my changes. it was just like the last time for every line i add i have to fix 4 more so our 4 lines turned into 16 (again). the trick as always is knowing WHERE to put the four lines. 8-)

Merry Christmas !

you da man!

I have an alpha posted for testing team members
it is with the nightly's it's named DPs_BASE_0712a.exe

we supply driverpacks base to integrate drivers.

If Nlite could do it we wouldn't bother would we?

If you say i have done it before and it worked i will shoot you.
just becuse you got lucky once doesn't mean it is a good thing to do. Evil knievel flashes to mind.
Nlite adds single drivers very well. so if you have a driver that is not in the pack add it with nlite then add the packs useing DriverPacks BASE.

There are dozens of obsticals to adding thousands of drivers at a time that nLite is not capable of addressing.
and why should it when DriverPacks already performs this function flawlessly.

there are tens of thousands of lines of code, error checks, and prerequisite checks that ensure that the drivers are added correctly that are not duplicated in nlite

remember to always run DriverPacks BASE as the last step in your creation of your image

my suggestion is to use the packs as they were intended (Use DriverPacks BASE to integrate them) before asking why it didn't work. Base integration is the only method that will be supported here.

PS i would like to add we all use nlite and love it. We just don't use it to add more than one or two drivers at a time.

you may have to use devcon to manualy add it .
you can use the driverpacks to call a script using a pack ini.

NIce work!!!!!!

OEMSETUP= yes in winntsif is mutually exclusive to hit f6 if the machine has a floopy you could put a floppy in with a winnt.sif file on it that file on the floppy superceeds the one in the i386 folder on the cd

if they pop out a public release that includes  888111 think it will just work without any furthur action.
if an upgrade for 888111 come out as a patch for SP3 half the work is done Base already recognizes sp3 in its current release.
should be a quick add on to the current 888111 module / code. lets see what they do. in the time being RVM is still earning his keep.