umapathy wrote:
JakeLD wrote:

Changelog:

7.08.1 (August 15 07)

New
- P\1 Added support for Pinnacle PCTV MediaCenter 100i (JakeLD)

I also modified devices.htm to fix tabulations.

DP_TV_wnt5_x86-32_7081.7z
(MD5 Hash: D3FE7FC4A2E0CE059CA427A6C09FAC32)

Decompressed Size: 71.2 MB
Compressed Size: 9.856 MB

I am unable to download the driverpack (Is there any new version released?) . Could you please upload it else where. Thanks in advance.

Please always check the big sticky on top of the forum.
Threads such as this very one are only valid for as long as the respective pack has not been updated.
It's more of an announcement than a link to an always valid file.

One thread per request is sufficient, don't you think?

Obsolete threads deleted...

TigerC10 wrote:

That's not necessarily true, media center editions of windows XP DO need that .net stuff.

I see; never worked with these before, though.
It's also a newer version of the XP .NET by chance, seeing as XPMCE is already newer than XP.

Anyway, I still guess that if you include an (updated) .NET AddOn, you won't need the original (outdated) files anymore.

underdone wrote:

edit: I can't figure out how to attach files to this. But, the dpbase.log doesn't show any error messages in it.

You can't, unfortunately sad

That's all there is to figure out about...

(you can directly post images using the IMG tags, though wink)

The funny thing with Intel is (I've experienced that myself), that they tend to release a LOWER driver version number on a LATER date than the HIGHER version number driver (which is hence OLDER).

Maybe the folks at Intel are actually the blind ones not noticing their own contradiction, who knows...

JakeLD wrote:

that's fine with me, thanks for your help.

Maybe you could add this link to the 1st post ?

http://3rdpartydriverpacks.thesneaky.co … 2/?C=M;O=A

I class the downloads by date so I know which one is most recent, plus if we update the 1st post links couple of days after an update is released people can still access the file by using the ftp link.

Splendid idea, could have been one of my own wink tongue

Done, and updating with the latest packs also done!

gresh wrote:

Requesting update of Logitech SetPoint to v4.00

http://www.logitech.com/pub/techsupport … int400.exe

Now that you mention it, I remember I said in the last Input thread that I would add SP 4.0 to the pack.
Well, the reason I haven't simply was that I couldn't find any INF files whatsoever inside the EXE (and yes, I used all the extraction methods I know...).

This is even more funny because I did update the setpoint in the past, where there was INFs alright...

From what I've seen of the "driver" so far (at a friend's who actually uses Logitech hardware) it does not look much like a driver anyway but more of a GUI with all kind of more or less useful settings...

If we are to add it, it has to work via the Exceptions and for that we need the HWIDs of all the applicable Logitech devices (mice, KBs and gamepads from what I know...).

Just a FYI to you all:

The DH Mobility Modder.NET has been updated to version 0.8.7.0.
You can get it here --> http://driverheaven.net/modtool/

For most users, this will be more convenient than "hacking" the INF files themselves.
Plus, it also supports Vista drivers (for those of you who dare to use it! ;P).

You do not have to "build" that file, all you do is run the BASE and let it do all the work for you smile
You can find links to the tutorial in my sig.

Besides, I do not know what "windows sp3" is, do you mean the Beta SP3 for WIndows XP?
If so, since it's not officially out, I doubt we'll be supporting that already.

Also, who the heck is this "AMIT_TAKIN"???

If you want to get rid of specific DriverPacks (for instance 3rd party DriverPack), just rerun BASE as OverFlow has said and deselect them, then re-slipstream.
This procedure also works for updating a source with the latest DriverPacks.
As slipstreaming the DriverPacks is supposed to be the final step before ISO creation, this shouldn't break anything (I have done it myself several times always with success).

I would not suggest manually removing specific components until you really know what you are doing.
It is also more time-consuming than re-slipstreaming so you gain nothing by it.

If you really need to fit it on CD (I was using that myself until half a year ago or so), there's a couple of steps that can help you:

Firstly, I recommend using nLite to slim down the source.
There's a lot of stuff you never need (really!) and some more you can easily do without.
MSN Explorer, WMP (if you use another player), all the languages and KB layouts, the intro movie, the search dog and whatnot.
If you want to, I can post my ls.INI so you can use that as a template for your own.

Secondly, if you only use the official DriverPacks (or rather not the Printer 3rd party DriverPack), that should not use too much space.

Thirdly, if you use Nero to burn the ISO, there's an option to enable short leadout, that saces about 12 MB of space, definately vital for a CD edition.

Fourthly, if really needed, there's 800 MB CD-Rs and even 900 MB (though the latter might be incompatible with some drives).
Unfortunately, those are not available as RWs from what I know (if you spot these, please tell me! wink) so you will need to do extensive testing in either a VM or use a DVD±RW and a system with a proper drive for testing, then brun the final version on the CD-R.

TigerC10 wrote:

Don't just copy the I386 folder off of the windows disk.  Copy the entire disk.  The cmpnents folder has some .NET stuff integrated to the installer.

The .NET stuff included on the original XP disc is absolutely unnecessary.
It has long ben succeeded by .NET 1.1, 2.0 and 3.0 (of which you will need all three, btw).
Also, it never installs during a regular installation anyway.
If you wanted to use .NET back in that day, you had to manually install it from that dir.

If you want/need .NET (eg for ATi's CCC), you'd best use a .NET AddOn to slipstream it into your source.
Even then, you can delete the original .NET contents as all files needed will be supplied by the AddOn.

Just FYI smile

662

(19 replies, posted in Feature Requests)

Just running the latest test instal to check this out, a little more patience, please smile

SoKoOLz wrote:
waleed_wwn wrote:

lsi_sas.sys Is found twice in    DP_MassStorage_wnt5_x86-32_708.7z

I faced this kind of problems Before . and it is related to your CD/DVD Writer

I didnt burn my ISO on CD, I mapped it with VMWARE, so I don't think my CD/DVD writer is causing a problem.

True.

Have you verified the file is actually there in the ISO?
If so, please run an MD5 check between this file and the original (pre-ISO creation) to check it didn't get corrupted (could be due to defective RAM, HDD).

--> http://forum.driverpacks.net/viewtopic.php?id=1953

JakeLD wrote:

Just refer to the FTP... As a forum moderator you should know this. big_smile

I do know this, but it is a bit bothersome, becase for me it never displays the full file name in the overview so it is a bit hard to check for new files.
Also, nothing beats simply c&p'ing some info wink

I'll just open the main post in one tab and the latest in another and work from there!

Just did that with your Monitor pack, btw, so first post has been updated.

Can I have the right to edit the post instead ?

I doubt that is possible.
You could be made a moderator for this forum, though, just talk to Bâshrat the Sneaky about it.
That's more than fine by me! smile

What we could do otherwise is that you create a new thread with all the info from the first one (use "quote" to obtain the "raw" code of it). As you're the creator then, you should be able to edit your own post.
But that would mean twig123 would lose this functionality, so it's certainly not the best option...

I won't have to bother you plus I update the DP like once a day or so....

Nah, none of you are "bothering" me.
After all, I volunteered for this job, so I won't start complaining.
It's just that I can't make it in here each and every day so some updates may get postponed...



Anyway, as a general idea, because once again someone "complained" about invalid links:
I would suggest that you put the new file into the main folder on the FTP but not remove the older file until the links in the first post got updated.
That way, all the links will remain intact, and you can always link to your new file in a separate post for those that want to use the latest version.
Then, whenever the first post got updated, the updater or the creator can then move the old (now redundant) file to the /old dir.
Comments?

First of, you may find additional info here:
http://forum.driverpacks.net/viewtopic.php?id=101

You could also have posted in there instead of opening a new thread, but that's too late now (I can't move around and merge single posts).

beady wrote:

I'd like to know how to remove only the card reader drivers or others from the xp sp2 cd's (for a standard install) and how to remove them after using driverpacks massstorage

I don't know your card reader but mine directly plugs into the USb port on the mobo and is hence reckognized as a USB mass storage device.
Unless you wanted to remove USB mass storage drivers (which includes external HDDs and USB sticks!), I don't see how this is feasible.

I really can't give you any further advise apart from either unplugging or disabling USB boot ability in the BIOS because for whatever reason, my card reader works just fine during installation and doesn't screw things up *shrugs*

So, never having experienced these problems myself, it's kind of hard trying to imagine a solution for it hmm

AndrejCRO wrote:

I recently downgraded my Vista VAIO to XP Vaio (clever ha?).

Certainly a smart move tongue

Those f***i*g Sigmatel audio chip - instead of common Intel (!).

Just FYI: even mobos manufacturer by Intel are using Sigmatel audio chips, for instance Intel's current desktop flagship Bad Axe 2 (D975XBX2):
http://www.intel.com/products/motherboa … /index.htm

So other drivers more or less functioning (FN key?),

They ususally do.
Personally, I haven't seen a notebook myself where they didn't (not to say it doesn't happen, though).
Even on Linux you have a pretty good chance by now it works right away.

and Audio - the nightmare.

Probably just due to the missing HDA hotfix (KB888111).

This always is a problem with HDA (HighDef. Audio) and not limited to Sigmatel specifically.

JakeLD wrote:

Helmi...you're right. I'll fix this and use the naming schem proposed in the FAQ by Bâshrat the Sneaky.
http://forum.driverpacks.net/viewtopic.php?id=445

Good idea, but actually, it would be even better if you sticked to the naming scheme as proposed in the 3rd party DriverPack FAQ (which you can fined linked in my sig) as we are also using the day as the last figure.
This is better (IMO) because there happen to work a lot more guys on the dp3ps than on the official packs and sometimes the changelog isn't too great (forgotten, didn't know how to do irt right etc) so you can better check for the latest version (i.e. you are currently working on one, then someone updates it, so you need to know which is more recent).

I cleaned my mess. You can now update the 1st post with the correct link for TV and Misc pack. big_smile

So, any new links or such?

Please, I hate having to search for everything by myself wink
(otherwise, it's a quick and dirty copy&paste job to update the first post... smile)

JakeLD wrote:

I'll do it don't worry big_smile

That's great.

Otherwise, I could just slap these in, shouldn't take too long to do it.

Please report back as soon as you're on it so we aren't both working on it...

Jaak wrote:

Hi
a not so subtle hint about reading the tutorial in my signature is in order.

The tute in my sig is quite different then what we first had in the topic, as I added some worthwhile tidbits of information which can help avoid mistakes like this.

So, I guess it's about time I update the link in my sig then, eh? wink

JeremyNNT wrote:

[...] and using the QSC because even though DPBase says not to use it for method two, the tutorial says to use it for all new versions.

BASE is actually saying that?

Are you using the English version or one of the translations?
I don't remember it saying that, but then again I have only been using the (created by me) German translation so I can't really remember...

giloz wrote:

I built my first bootable cd a couple of years ago, updated it once, someone broke in and stole my laptop and all my software,

Oh my, I can really feel for you here! sad

If someone steals your hardware, alright, that's what thievery is about, I guess, selling the stuff on ebay or such.
But stealing someone's SW which probably includes backups and personal data, now that is really a new low.
The insurance company will most likely cover up for the HW loss, but if someone stole my data, if I ever got ahold of them, I'd rip off their balls with my bare hands, I swear to you! >8(
That's on the same level as deliberately damaging someone's car or kidnapping their dog, I guess... (I don't have a dog).

Done and done.

Unfortunately, your naming scheme is still inconsintent and you also gave the wrong link for the Misc pack (it's Monitor actually).

Still thanks for the efford wink
Small steps lead to perfection, too smile

Closed by request.

Cellar Dweller wrote:

Will this be included into a newer driver pack for mass storage that can be used with UBCD4WIN or BartPE???

They are already in the latest DPMS!
As I don't do UBCD4WIn or BartPE (yet, at least, no time to get into that), I'm not sure whether you actually need a special version for these...

I was shocked that they hadn't been included earlier considering how many people do Dell servers

From my experience, Server 2003 already comes with support for the controller, at least when I installed it on my Dell, it worked like a charm out-of-the-box (aka no DriverPacks slipstreamed).
As you wouldn't really want to run XP as a server OS (considering the machine is in server duties, so far, I am using it just to find out how to best build a NAS platform out of it wink), that#s probabaly why it never was an issue.

Plus, we can only add so much drivers ourselves.
If there is no feedback and requests, some may get overlooked simply because there is such a plethora of HW on the market.

JeremyNNT wrote:

3. Slipstreamed ALL Driver Packs using "Method 2"
4. Used the Windows tool to create a .sif file
5. Used RyanVM Integrator to make an ISO (and when I ran into the problem outlined above, I tried creating an image with CDGUI)
6. Burned the image using Nero.

Try flipping #3 and #4 around and see whether that works.

Also, why are you using both RVM as well as nLite?
You can make an ISO with nLite and you can also create the SIF entried with it.
You can even slipstream the RVM packs with it, so you do not need to run it separately (that is, if you do use the update packs).