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

RE: And the more folks who can make use of this project

LOL we get over a million downloads a month wink that is averaging well over 32,000 DL a day tongue
i don't think having a large audience is an issue... at all wink LOL
too funny... big_smile

Testing team access granted

Welcome to the team, and we are glad to have you!

BartPE is very limited and requires you burn a OS licence for it.
It is a great tool but it is not an OS replacement.
when i added the mass plugin UBCD4Win reported over a thousand downloads in the first week
now it is included. It is in use by hundreds of thousands of users. That is kinda popular.
heck that might be more popular than that new OS that a certain OEM released recently.

You sound like the kind of tester we need more of!


thank you

Jeff

Please avail yourself of the SEARCH feature of our forum.

this is very well documented... as well as a feature request.

http://forum.driverpacks.net/viewtopic.php?id=2723
http://forum.driverpacks.net/viewtopic.php?id=2733

the [Unattended] section of winnt.sif must be Deleted completely to do a repair

PS the answer to this is five posts above this one and stickied in this forum wink

3,079

(2 replies, posted in Software)

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

yeah your missing something...

1 No 3rd party DriverPack are supported for BartPE. None, zip, nada, zero...

2 mass storage drivers can not be added from a third party pack.
   Well they can, but you won't get textmode support only PnP support.
   If your primary drive requires the driver that is in the 3rd party DriverPack it will not appear.
   This is true of BartPE and a normal slipstream.
   Again, an F6 driver wont work from a 3rd party DriverPack...
   BartPE uses the text mode drivers. (the F6 driver)

the best thing for you to do is to [REQ]uest the drivers be added.
We like to add drivers... that is what we do wink big_smile
Requesters are imortant to us and a REQ identifiys you as a person who can test that a certain driver was added correctly!
as Jaak says 'helping us to help you!' wink

your drivers must be in the mass storage pack and they have to be added very carefully.
Mass Storage is one of the most difficult packs. To get it right anyway. any idiot could stuff one in there but to make it not crash the system afterwards is another story wink

In Each of the respective forums (LAN and MASS) create a new thread,
use a title like this [REQ] Promise STAT300 TX4
post your HWIDs and a link to where the team can get to the drivers (the OEM source)
And we will get those added for you


i updated your post per 'Read BEFORE you post' in my signature

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

3,082

(4 replies, posted in DriverPack Mass Storage)

1 you cant add the mass storage pack with nLite.

2 ql40xx is not a DriverPacks file.

3 you are not using the pack in a supported manner so your issue is not supported

4 Read BEFORE you post - in my signature below. be sure to check off each item as you add them to your post.

5 It's Jaak not Jack...

6 Read the DriverPacks BASE tutorial - in my signature below.

7 have a nice day

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

The Bartpe code I wrote myself... big_smile
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 wink.

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 wink then i will make you a testing team member big_smile... If you like.

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

You most certainly can... it is just incredibly difficult wink

removing any would be considered aggressive big_smile

IE not supported and destined for failure... wink

@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

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

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.

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

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 wink

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)

since vmware loads no drivers at all it CAN NOT be driverpacks

I use vmware myself... and i do not have this issue... therefore you are doing something i (and a million other people) are not.
I create and test new packs and OS's daily and test them all in vmware... sooner or later we are going to hit on what it is you do wrong.

do i understand correctly that you tried the source that was produced by the log you just showed me, and that specific source froze?

where did you get, what is, your source?

am i also to understand that your MS disk includes SP3 (it was not added by you)

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

you can update DriverPacks in the OEM folder AFTER base has installed it

you can not simply add the OEM folder to your source that will not work...

perhaps you should try following the tutorial in my signature step by step... wink

waiting patiently big_smile

DPs_BASE.log...

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.

Read the FAQ in that section of the forum

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.

Bâshrat the Sneaky is the original author of the driverpacks and our hero...

He was almost laughed off of the MSFN forum for suggesting that he could get all windows drivers in one place.

Bâshrat the Sneaky's driverpacks was born, and guess who has the last laugh. Bâshrat the Sneaky real name is Wim Leers.
He started DriverPacks when he was like 14. he is 19 now and in college (and now uses a mac).
Wim still owns DriverPacks and stops by from time to time but the torch is now carried by the team.
Bâshrat the Sneaky realized that he could not any longer maintain this by himself and semi open sourced it.
There are a handful of us that have volunteered to keep this project alive.

So to eliminate any confusion - Bâshrat the Sneaky DriverPacks website is DriverPacks.net. wink
anyone who has been around for a while would still call it Bâshrat the Sneaky's driverpacks - i do...

Since Wim went to college about two years ago, you just needed to have been around for a few years to know that. (noob - lol smile)

Jeff