pSycho-Y2K wrote:

This topic can be closed

RGR, if you need reopening for w/e reason, PM me smile

If it's the same as with the Intel WLAN drivers, there's usually a smaller package available, stripped of the installer and GUI/CP files, shrinking the whole package down in size noticably!

Generally, this is what you want to include in the DriverPacks wink

Alright, Jaak, that's good to know and was somewhat expected by me (it does not make much sense to simply stop there in an unattended installation).

mr_smartepants wrote:
Bâshrat the Sneaky wrote:

What does "IDK" mean, Helmi?

smile "I Don't Know"

Indeed big_smile

LeveL wrote:

D\S\CR\1 (371 Files / 81 Folders)
D\S\CR\2 (371 Files / 81 Folders)

But the folder sizes are slightly different: folder 1 is 83.1Mb and folder 2 is 83.4Mb.

So all I am asking is what IS the difference between these 2 folders?

http://driverpacks.net/DriverPacks/devices.php?pag=sa

Is it safe to remove folder 2? Will the DpsFnshr still work if I repack the driverpack
without that D\S\CR\2 folder?

Generally, yes.
You may need to adjust the INI and cut out no longer needed lines referring to ..\CR\# though.
IDK whether it will stall when it cannot find a DIR or continue without any hiccup smile
(NB: You can always give it a try to find out tongue)

The INIs are indeed for the Fisnisher so exceptions can be installed.
These are ususally the GUI control panels for various devices.
If none need to be installed (ie Intel uses such a panel but I found the default XP controls to be sufficient for my tasks, also, this will cut down the driver size noticeably!), then no INI needs to be present.

IDK however, whether this intentional or a mistake.

What you can do is DLing the latest driver from the manufactuer's website and compare it to the on the in DP.
If they are of the same version, do a MD5 check of both INF files to verify they are bit-identical and the one included in the DP is no corrupted (you never know...).

If the one found on the website turns out to be newer than the included one, feel free to replace it, repack the archive and upload it so everyone gains from it! smile

You could/should do the same if it turns out the INf may be broken somehow.

Oh, and please test your self-created file so we can be sure it has to work wink

933

(4 replies, posted in Feedback and Support - DriverPacks Base)

In this case, if they are indeed missing, just post a request for each device/driver in the proper sub-forum so they can be implemented.

mr_smartepants wrote:

The problem as I see it, is that once you finalize the driverpack and get the checksum, once you open the pack to add the MD5 to the INI and repack you change the MD5 for the pack itself.  hmm  Kind of a 'catch-22' eh?

Ah, darn!
Totally missed that! tongue

In this case, having them posted on the website along with built-in 7-zip archive check is probabaly the best way to go.
I just don't have the slightest clue how to code that big_smile

rgr.

Your links are totally broken, mate.

I assume the ** was by purpose (so far, we haven't punished any one for posting links, only these darn adbots, so feel free to post proper ones smile), but the smiley messes it up completely.

mr_smartepants wrote:

Bashrat, maybe we should start including MD5 checksums for the packs.  Just a thought.

Yeah, definately, IMO.
There's been a lot of folks who apparently have corrupted DLs (that or corrupted systems wink).
Would it be possible to sort of have the MD5 stored in the INI and the BASE automatically check them?
(I am assuming it may be a bit complicated for newbie users to perform the MD5 check).

Either that or use 7-Zips Test Archive function for (basically, I guess) the same functionallity.

mr_smartepants wrote:

Seriously, why don't you try just disabling your firewall completely for about 5-10 minutes?

Bad idea if you do not have any HW protection (eg router with NAT).
Either you have a PFW that's 100% on or you might just do without it altogether.

That's like using condoms only most of the time, if you get the analogy wink

I would, however, seek for a different PFW if this one behaves such user unfriendly.
What is actually the point in blocking referrers?
It does not add to security in any way known to me...
*puzzled*

Just remember that the server is getting bombarded by a DDoS attack.  Be patient.

This could actually be the real reason.
Best is to sit tzhis one out, then think about measures if the problem persists.

McStarfighter wrote:

If Bashrat give me an OK, I mirror it on Rapidshare ... First I would make a complete package, but atm without the 3rd Party DriverPacks, because imho they aren't compatible with the actual DP versions ...

IMHO?
Either they work or they don't and from what I can tell, they do smile

Anyway, leaving out 3PDPs is fine by me at least.

Bâshrat the Sneaky wrote:

Download managers have been blocked for months now, because they virtually without exception do multiple simultaneous requests, which increases the load on the server.

Well, can't speak for other programs, but the one I use, GetRight, does only initiate additional connections on user input by default.
I don't quite see the difference between DLing one file with, say, five connections or five files with one connection (using just your browser).

Then again, I can live with the situation.
As long as my DL manager still works on those nightlies (fear not, I load these only with one connection per file), it's not too much work switching it off once for the official packs wink

The only "problem" with Rapidshare is that as a non-paying user you can only DL one file at a time and only one every two or so hours.
Unless you could pack all related files (BASE+all DriverPacks) into one big archive it may bt a bit clumsy to get them from there.
Then again, better that way than no mirror at all!

But personally, I would prefer a BT or ED2k link, as that is a one-click DL smile

LeveL wrote:

The reason Bashrats driverpacks won't support your devices
on Server 2003 is because the native support that is in XP
for many onboard sound devices, is simply not there in
Server 2003. I guess the driverpacks BASE relies on whats
in XP.

Just a wild guess here, but could that be related to the HDA hotfix?

Many newer onboard devices are HDa now instead of the older AC'97 standard.
To get them to work (or even the device reckognized so you can install the driver) the hotfix needs to be applied first.
IDK how the situation is with Server2k3, either it requies a different hotfix or it is somehow not compatible with DriverPacks otherwise.

Yes, AFAIK, there's nothing that should stop you from it.
The change regarding the INI is only for the Finisher, when it has to apply exceptings (ie installing the controll panels).
If you only want the drivers just as if you right-clicked on an INF and installed, the 3PDPs should still work as before.

If it does not, please report any errors in the respective threads so the makers (or even yourself!) can fix them smile

943

(3 replies, posted in Feature Requests)

Be sure to slipstream it using the Text Mode option!

944

(3 replies, posted in Feature Requests)

DriverPack MassStorage is what you are looking for! smile

Yeah, I can only second what mr_smartepants has pointed out.
We cannot distribute a full ISO that contains those files to be found on an ordinary XP CD.
While generally the licence only covers the printed genuine sticker seal on the manual along with the serial number (without which you cannot use XP both legally as well as practically), I doubt that distributing the CD even without the S/N would be approved by MS.

Of course, no one will bother if you use the ISO of a real-lifeâ„¢ friend as long as you enter your own serial (for instance, mine is already included i nthe ISO for a true unattended installation) and have your own valid licence.
But putting the stuff on the net means you share it with the whole world basically.

I know I can only speak for myself in this issue, but personally, I found the tuts on MSFN pretty newbie friendly.
Make sure to start with the erasiest level, then, when you managed to come up with a working ISO (be sure to test it on a secondary machine or a VM!), advance to the next tier.
That way you will not only learn how to do it so one day you will be able to even help others smile but also can customize your ISO to your liking.
I'm sure each of us here uses a slightly different ISO which each us deems best for oneself so there isn't the best allround ISO to be found anyway.

What we can do, though, is share the INIs so that you can use the same settings as someone else.
This especially works great for nLite.

Hm, maybe it's indeed missing.

In this case, if verified the archive did in fact extract properly (using 7-Zip it would prompt an error if not), you should report that in the MS forum.

I will move you over there for now.

The reason no one else may have spotted this is either the file only gets loaded in Via systems (which are realtively few now compared to some years ago) or that all our testers are already working with a new version which may already have the error corrected (this would imply no one else of the regular users dared to report it, though...).

bmustillrose wrote:

As always thanks for the work, but what am i doing wrong?

You're extracting the driver files.

The posted link to the tut should make it all clear smile

Usually, such a message means the file cannot be read from the disc, but is present regardless.
That means, either the disc, your HDD or your RAM may be corrupted or there could be some dirt on the reading drive's lense.

We suggest testing a new ISO in a VM before burning and when buring, if you use Nero, definately enable disc verification!

949

(13 replies, posted in DriverPack Sound)

I dunno, back when I was using CDs, I was able to shrink them down to ~700MB and fit all DriverPacks on it, all the recent XP updates with an Update Pack and some other stuff.

You just have to remove more of the original source.
Stuff like .NET, WMP, help files, the update ability etc can be removed.
In the case of .NET, I was integrating a newer version anyway making the included one obsolete.

Also, if you use Nero, you can enable short leadout which will gain you another 12MB on the disc.
You can also try to overburn for some added MBs.

Just don't touch the 3rdPDPs, as that will make it too large.
Esp. the printer packs are huge!

jtdoom wrote:

hi
mass storage textmode will not be slipped in from 3rd party.

Indeed.

Hence, when you are seeking for a quick and dirty method to add missing TM drivers, I would suggest using nLite for the task.
Just be sure you select them as TM and it should work.

An alternative is of course to request these drivers to be added to the official pack -that way we all will profit from them smile