Search options (Page 124 of 213)

Welcome Crimson_Wake ,

Thank you for your interest. micro xp is not supported by DriverPacks,
supported platforms  are 2K, XP, 2K3 and BartPE XP, 2K3.

Warez are not supported

Have a great day!

PS check out UBCD4Win instead

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

I am so glad to have been able to help you to be successful with the bartpe...

The Bartpe code I wrote myself...
However I could not have done it without CDOB and especially HIGHLANDER from the UBCD4Win team. {hats off}

We do not encourage public testing of our betas. We have a testing team, and that is their contribution to DriverPacks. We refer to our test packs as the 'nightlies'. The nightlies are usually not stable and may even include beta drivers. It has been our experience that many non testing team users will use these in production machines, this is not an acceptable practice. Mostly because all of the info related to the nightlies is in a hidden forum (unless you're on the team). for many reasons Beta/Nightly drivers are for testing purposes only by users who are chosen for thier skills and familiarity with DriverPacks. Occasionaly we will offer a carefully chosen nightly to a particular user who has a specific problem to verify a fix or updated driver. In your case you are helping me to test an alpha feature - i did this because i was impressed that you figured out on your own that you could do this .

I have done some more investigating (i called hilander) and apparently without a modified copy of xpe-pnp (not created yet) only graphics LAN and WLAN are expected to work... all other packs will likely fail... they may not... but we don't expect much if any good results

Thanks for your interest

If you promise not to use test packs in production machines then i will make you a testing team member ... If you like.

ps did you look at the tutorial in my signature (same as help button in pebuilder - plugins page)?

removing any would be considered aggressive

IE not supported and destined for failure...

you can use nLite just don't remove the windows natively included drivers...
DriverPacks depends on them being there to function correctly.

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

OK so you start with a OEM sp1 or sp2 disk and RVM integrate, then nLite (it is important that it is in this order).

you do not remove any drivers with nLite
This is also important, since DriverPacks is designed around the idea that the existing drivers are present.

after you are done with these two programs and are fully done changeing your source then driverpacks

DriverPacks MUST be the very last thing you do... If DriverPacks was the last thing you did you may then remove or update your source with DriverPacks.
selecting no packs removes it when you slipstream and normal selection will upgrade your source.

if you want to cahnge your source just use base to remove the packs (i keep a copy of the folder just before i add them and i then just use copies of that folder)

That looks like a clean log... result of testing this source?

waiting patiently

driverpacks base creates those files (.org) so if they exist then DriverPacks has already been run on the source.
if DriverPacks has already been run then it is not a clean source

that is how i know you are not running base on a clean source... your log is telling me you have used a source that DriverPacks was previously installed on, yet you insist you have not.
So either you are stupid or you are lying.
IF you cheat and just delete the .org files then base is not able to remove the previous base and your I386 folder gets ruined.
if the i386 files are altered after the .org files are created then when base removes itself it Ruins the I386 folder too.

YOUR SOURCE IS RUINED EITHER WAY! you can't make any changes AFTER DriverPacks... PERIOD!

YOU MUST START OVER FROM SCRATCH!

lets put it another way millions of users are haveing no issues.
Since you are one person in a million you must be doing something a million other users are not.

Clearly you have a corrupted source (according to your log)

so start clean and show me the log where you have used a clean source (from an original Microsoft disc)
and we can continue. After you have used a clean source and produced the log that demonstrates this has been done.

IF you do as i have instructed you should not have a problem... if you refuse you have created your own problem and we can't help.

last time i am going to try to help you...

FIND a Retail or OEM Original Equiptment Manufacturers CD (OEM XP DISK) Copy it to your HDD.

THIS is a CLEAN source - USE that.  the prep stage will be skipped in your log when you do this.
and i will know imediately if you have not done this.

For the LAST TIME your I386 folder is Garbage and is Unsaveable START OVER from a MS provided original disk.