Search options (Page 176 of 213)

well this thread is kind of old...

the double d folder error Skinlayers refered to was fixed in RC2
So advise that pertains to that issue no longer applies IF your useing the new base RC2 and much of the work he does is to get around that error. I fixed that in January and nobody seemed to notice...

apparently, from what i read, make pnf is not desirable to a process that is done by sysprep so we should  skip that step. that is how i read it...

ps make pnf just caches an index of the drivers for fast searching it is not mission critical but it can cause problems.

this is going to seem strange but does it work if you disable the driverpacks plugin in pebuilder...

bartpe is windows on a read only disk - if youuse windows 2003 as your source for your PE build then you will be able to access all of your servers partitions and edit files . one of our members has been working on off line sysprep for bartpe.

the easiest way to get started with bartpe is to use UBCD4win
UBCD4win is based on bartpe however it includes hundreds of useful plugins without haveing to go and get them all and install them.
(it even includes minesweeper) you can then add galepos tool to your ubcd4win cd and reset your driver on the server with his offlinesysprep tool and you should be off to the races...

description of UBCD4win to help get your head on straight

Ultimate Boot CD for Windows link to contents page download link is there on left side

it may be that two of the included tools may help too...
Fix HDC  n/a Fix the Hard Drive Controller when replacing your motherboard on an XP system, possible replacement for Fix IDE?
Fix IDE  n/a Fix the IDE Controller when replacing your motherboard on an XP syst

that was FAST! wow. if i start a volunteer fire department your my first call...  

thanks

i agree, if dell is putting it out there... it's solid.

that is always a tough one...

i suggest not modifying the new one (thus not breaking its signing)
and not modifying the old one either if they are both signed then the newer version should win out when appropriate.

If they do conflict (they shouldn't in theory) fix by removing the HWID's from the old one that exist in the new one.
this will break signing (probably) on the old one which is probably ok it will likely be seen as the best match even unsigned.

the only way to be sure is if remy007 or someone else with the device can test and report back

as jaak always says - help us to help you!

please tell us what your post is in reference to.
If it is a request then we need your HWID's and a link to the driver.
also the title should start with [REQ]
please read the read before you post in my signature.
which version of base and which version of the lan pack were you useing.
what is the HWID of the controler that did not install (link to HWID tool is in my signature below)
also look as some other REQ posts to see how they are formated...
(rapid share does not count it must be an OEM site)

since you are useing M1 you should be useing the RC version of base on the home page linked in the news artical

it's working now...

and...

i belive that thread is self explanitory. where did you get lost in the discussion...

i assume you are refering to the Motorola drivers and Agere drivers

they are conflicts... and editing the HWIDs breaks signing and could cause the driver to not install when it should.

the requested drivers cannot coexist in a single pack. they will need to be in thier own pack
and then the two packs cannot be used together. support is not feasable. if you need the missing drivers you will have to create your own pack.