You are not logged in. Please login or register.
that is your problem DriverPacks depends on the fact that ALL existing windows drivers are still included
problem solved... don't remove the native windows drivers. it says this in the tutorial too 
yes i did what you do, intgrate driverpack at least.
but I think i will put my pack over the last source to see what it does. after all dpbase only creates an oem folder and changes a few lines in winnt sif no?
in fact my only doubt is about my pack. because i integrate my own pack with rvm and it contains raid drivers but I'm sure there is no errors.
Read my last
removing drivers with nLite is causeing your problem...
we supplement the existing drivers we don't fully replace them...
some of those drivers have not ever been updated and never will be.
and wont ever be included in DriverPacks
but overflow Ive always removed drivers with nlite without problems. mm there si one thing that has changed before i didnt use rvm and it breaks "driver.cab" it could be that.
just because doing it wrong has never cause you a problem before just makes you lucky...
It is still wrong and not supported. and apparently causes a freeze at t-34...
problem solved.
no I made mistakes. driver.cab is still present but not sp3.cab it did the same before and i didnt use it for that but my pack is not compatible any more with nlite.
I will integrate my pack without using nlite at all. I'll tell you what happen. I'm afraid its that.
you can use nLite just don't remove the windows natively included drivers...
DriverPacks depends on them being there to function correctly.
in fact nlite i noticed nlite keeps sp3.cab and driver.cab but if you want to integrate drivers in a pack there is no support for certain line in dosnet. I leave you good night.
@all
Please note how an issue that could have been solved in two posts has drug out to nearly 60 posts.
this is why it is important to tell us what you did in your first post!
('Read BEFORE you post' is designed to help you do this every time)
Had he said i use rvm to update a ms xp sp2 source then i run nlite and automate and remove the windows drivers then install DriverPacks.
then i would have solved this issue in my first response.
always include DriverPacks version your DPs_BASE.log and a description of what you did.
TIA
i agree. ill tell you if its really that.
now look at that http://www.image-upload.ch/upload/November2008/imp.jpg
with that source and driverpack its works. (on several computer), but in my new source i think ive been a little agressive with drivers.
removing any would be considered aggressive 
IE not supported and destined for failure...
Well in fact I havent solved my problem but its due to an incompatibility with my updatepack. I dont understand because Ive tested under vmware with my previous source that worked (contains old graphic packs) and if I integrate my updatepack (only contains hotfixes, no raid drivers) it freezes. So I will remove hotfixes to see which one causes problems (some of them are not officially distributed under wu).
I dont want to contradict you but it seems drivers being removed are not a problem (I mean only drivers not hardware support under nlite that can cause crashes if removed)
Last edited by scarface (2008-11-25 07:16:41)
well since you can't test every possable combo of hardware yourself (like we have) you are not able to make that determination. Since we have gotten the feedback of thousands of users and hundreds of thousands of machines over the last 4 years you will just have to belive what we tell you. if you remove drivers with nLite sooner or later it will blow your install up... So you got lucky on a machine or two... that does not put you in a position to disagree. now if you had a few thousand machines at your disposal and you had tried them all... but you haven't have you... i don't tolerate disrespectfulness.
DON'T Remove drivers with nLite... if you do we will not support you and you're on your own.
(like a little freakin kid... don't touch the stove its hot... Oh did you burn yourself, I freakin told you the stove was hot...)
problem resolved...I removed hotfixes from my update pack and it seems one of these 2 kb is not compatible KB956841 or KB950162 with driverpacks. there is a new version of ntoskernel so its removed from my pack. these hotfixes being not official.. I ll tell you more later. Its quite strange this problem only appears with driverpack installed. I dont really see the link between them
Last edited by scarface (2008-11-26 11:45:44)
ok then integration of KB950162 was the problem. I removed ntoskernel v5.1.2600.5586 and now its works (I also integrate KB956841 and there are newer versions of ntkrnlpa,ntkrpamp,ntkrnmp. no problem removing drivers with nlite for me.
That's it... The limit of my patience has been reached.
Don't remove native drivers. it does cause problems...
this is clearly an id-10-t error. One that just can't be fixed.
Note to team: do not ever support this bonehead again.
He does not listen nor follow even the simplest of directions
KB950162 Is a hotfix...
this hotfix is intended to correct only the problem that is described in the article.
Apply this hotfix only to systems that are experiencing this specific problem.
PLEASE READ THE ABOVE LINES AGAIN
It must be supplied BY MS to you directly.
if this is not the case then you have again reinforced the 'You can't follow directions' assessment
Furthermore lets reference http://support.microsoft.com/kb/950162
When application repeats the driver load and unload operation many times on a computer that is running Windows XP or Windows Vista, the computer may become unresponsive.
If you use the Memory Pool Monitor (Poolmon.exe) utility to monitor the IoSe and Pp memory tags, the memory that these two tags consume increases as every successful driver load and unload operation occurs.
Restart requirement
You have to restart the computer after you apply this hotfix.
This Hotfix affects how drivers are loaded. DriverPacks loads drivers (DUH).
I don't see any way to apply this hotfix and then REBOOT before the DriverPacks are installed.
IT may be that this Hotfix will more often than not kill a windows setup when it starts installing drivers.
That is this hotfix's core function to alter driver installation (guess you didn't read the info provided)
this is definately an ID-10-T Error...
therefore you have a choice one or the other - not both
(I suggest you install the hotfix and not use DriverPacks... please.)
Slipstreaming this HotFix is CLEARLY YOUR MISTAKE.
I will bet that you don't even need KB950162...
I have cash for this bet - if there are any takers 
AGAIN YOU CAN'T FOLLOW DIRECTIONS
(i was jsut going to close this but... in response to Email I just received... here we are)
you just can't fix stupid...
Hint
after your machine is loaded
and you have VERIFIED the issue exists
REPEAT and you have VERIFIED the issue DOES exist on a specific machine
then IF MS has provided you (personaly) this HotFix
THEN and ONLY THEN feel free to install this hot fix on that specific machine.
(Don't forget that instruction i mentioned... REBOOT required)
- It is designed to affect how drivers load
- It affects Driver installs adversely according to your reports.
DO NOT slipstream this hotfix! ... Simple
you should not install any hotfix unless it is absolutely necessary!
and you need to install the OS to the machine first in order to establish this need.
Clearly not the way you're approaching this...
- Updates are a different story - have at! -
LOL, "Meat Virus" strikes again!
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.055 seconds, 11 queries executed ]
