Search options (Page 13 of 213)

We are always looking for help . Welcome to DriverPacks!

I have added you to the Testing Team and you will find some forums that were hidden are now visible.
TechDud is mostly adding drivers ATM.

Have you tried the test packs?

Jeff

Thanks TD!

You can use any driver you like in textmode since it will be updated properly when PnP re-installs all the drivers in PE Mode

Yeah and they don't much credit us for our (major) part in "their solution" either.
And they have never even donated a dollar.
Our DriverPacks work without their software but their software doesn't work without our packs .

ROFL  B E A U tiful post TD!

Jaak will be rolling on the floor when he reads it.

Try using SAD to install your 3rd party DriverPack and the issue may / might disappear. (if you are not already)

It really depends what you choose to do with nLite. Some features work great others do not. I am not going to list them. Most are related to how nLite adds registry entries.  if you have used nLite with WSUSB then you know nLite is still broke . Again I use nLite myself for certain tasks, it's "OK" RVMI is "GREAT". if you use RVMI then you don't have any problems. I can use nLite successfully because I don't need it, I know where the issues are why they are and how to address them if needed. Many of our users are at this same level, or higher. Ricktendo for example,  CDOB, etc... some of the sharpest minds in the industry pop in and out of here all the time. We are  blessed. Soooo my advise is use nLite but only if you don't need it LOL.

Honestly TD I think he is trying to modify someone else's work, the last time I saw this kind of a post it was our good friend FvcknutFour.

here is the KEY line from his post

That SCREAMs dirty source. the first thing BASE does is restore the original files if it finds a previous DriverPacks BASE install. Soooo, he said he started clean but that is a lie because he said his nLite changes were missing. They are missing because BASE restored the files from when it was run previously. Therefore hi ssource was not clean and he lied.

Being lied to pisses me off. thus my attitude in the response.

I got this guy TD... don't need any help. I was just waiting to see if he would lie to me again, then I was going to ban him.

But thanks for always being so kind and helpful, but there are other lines that are way more telling than the one you picked out .

I was going to give him the benefit of the doubt and not call him a liar in open forum, since it may have just been sloppy work. Sloppy work is only annoying, which is why I tempered my answer to only address laziness / sloppiness and not give a response appropriate to an outright liar. The last time I was here the poster (FuknutFour) was also a pie-rat. When people tell me what they had happen I know EXACTLY what they did. Sometimes I need more info to determine their character and intent.
In this case a wanted to know if they were using a pirated source from the internet. The answer I gave fixes the issue guaranteed. The response I had hoped not to get was "I didn't use a clean source, I got if from the net.",  that response is the ban response .

The fact we got no response tells me he was not lying, just sloppy. LOL
People never post when everything is working fine

Jeff

RTFM

IF you read the directions you will not have this issue.

the tutorials are everywhere. on our home page linked in our signatures and in the FAQ section of the site.

http://driverpacks.net/docs/beginners-guide-windows-xp
0) Pay particular attention to the CAUTION printed in BOLD

We plaster this info everywhere.

nLite will quite often corrupt your source...
although i do use it myself for certain things, like making the ISO for example.
RVM integrator is a much better way to go.

1) YOU CAN NOT... I repeat CAN NOT modify your source after you add the driverpacks.
MOST ESPECIALLY with nLite, If you run nLite after DriverPacks you absolutely WILL (guaranteed) end up with GARBAGE.

2) DriverPacks must be the LAST step in your process ----> the LAST step <----  This is made clear in EVERY tutorial we have printed.  read the directions and you will not have issues. We are NOT the support forum for nLite, thank god.

3) Follow our simple directions. modify source first, then add DriverPacks. 
4) Once DriverPacks is added to your source, you CAN NOT make further changes to your source.
5) Read that again...
6) OK, now read it again... Got it now?

It's really easy if you follow our simple directions. (RTFM)
please note all the numbered items say the same thing as the caution in the tutorial.
Most of the non numbered items tell you the read the directions.

you failed to also read "read before you post" linked in my signature and agreed by you that you have read when you signed up. You didn't follow the instructions you were provided multiple times and now you wonder why you have issues???

Start over with a CLEAN source, your current source is corrupted and CAN NOT be salvaged.

Follow the directions and then please come back and tell me what happened  .

Please note: if you think i have been harsh DriverPacks is not, and has never been, a noob friendly site like MSFN.org. Failure to follow directions or RTFM is a noob mistake.  And yes I know you have been a member for five years, it's still a noob mistake .

Welcome back to DriverPacks!

Yeah we're down a few PackTeam members. Most notably MrSmartepants.
I am looking at having some time for BASE, and releasing some of the Betas soon.

I am hoping to get things current again, want to help?

i add the mass and chipset to my source... that seems to do it

For the moment you need to get the nightlies.

There will be new releases soon

A decade already?

quick easy...

skip them for 2k