4,901

(18 replies, posted in DriverPack Mass Storage)

Thanks Jaak.

Merry Christmas sir!

(code) tags added to post (/code)

4,902

(18 replies, posted in DriverPack Mass Storage)

Everyone who installs on windows 2000 with the latest mass storage pack will see this problem...

it is because there is a limit to the amount of ram that can be used to load drivers. 2000 allows for the least followed by XP then 2003 and finaly Vista allows for the most. we have yet to reach the limit for XP (yet).

the only work around is to select some of the drivers in the packs to not be loaded for windows 2000.
We will make the neccessary adjustment in the next pack.

good team work guys!!!

thanks, we probably need an INF entry to add it with the finisher.

Could you please post your HWID's

Thanks in advance.

most of the things we do here are driven by requests.

We actually have very few requests for 64bit support. perhaps it will still become popular enough to code.
It seems more likely with SP1 coming out for Vista it will be a high priority soon. LAN for BartPE is my current target.

4,907

(18 replies, posted in DriverPack Mass Storage)

@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.

Merry Christmas Stu,

it is not neccesary to delete anything in QSC unless your low3 on disk space...

the only exception to this is if you modify a pack that you have already slipstreamed. the internal versioning prevents using the wrong qsc folder / version unless you change a pack you have already QSCed.

4,909

(3 replies, posted in Feature Requests)

What is the HWID of the camera?

4,910

(18 replies, posted in DriverPack Mass Storage)

can you tell us what is your HWID?

It is more likely that we need to tag a few more drivers in the inf  for windows 2000. 
It has a very small number of drivers that can be used at the same time before we run out of memory.
we will need to look at the list and create some new exceptions.

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

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-)

can you get to the setupapi.log in the windows folder and post the portions related to the si3112 you could put th ewhole thing here but it will take at least three posts

4,913

(2 replies, posted in DriverPack Graphics)

Merry Christmas !

you da man!

ok, on it...

DPs_BASE_712b.exe posted on nightlies

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

READ BEFORE YOU POST in my sig below

update your post and we will find out what is wrong

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 are always welcome to submit new drivers here!

1 Start your post with a title that begins with [REQ]
2 supply the HWID for your device that is not recognized (there is a HWID tool available in my signature).
3 Most important is a link to the driver that you know is correct for your device.

so if you find them we use the HWID to make sure its not in the pack already (and if it is why it wasn't used.)
and if it not we add them. the team is awsome about adding them quickly. usually they will be in a test pack within days and released with in weeks. we could release packs faster but testers for the packs are a rare breed.

Thanks for the follow up... jeff

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

if you wish to have setup detect your HDD during text mode a third party pack won't help

we will need yoru HWID to add it as tiger said....

however he was wrong about nlite you probbaly do want to add it with nlite but you will have to add it BEFORE you run driverpacks.

driverpacks is always the last step (he is right that if you try to add it after driverpacks it will make a mess)_

NIce work!!!!!!

you may be able to create a third party driverpack ? interesting question.

4,923

(3 replies, posted in Other)

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

i think i will have an alpha for testing by tommorow...

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.