76

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

64 bit drivers aren't supported yet.  No clue when it'll be adapted.

Well, torrents can be set to just include all of the DriverPacks, so that downloaders could mark only the packs that they want for download.

Still it seems like too much upkeep.

I don't know, they change pretty frequently...  That means that the .torrent files would be floating around outdated......

hmm

Driver issues are terribly annoying things.  It's like the thorn in the lion's paw...  Not life threatening but oh so irritating.  God Bless DriverPacks.

morland, the DriverPacks can be downloaded from the main site (I have had problems with the packs when I download more than one at a time)
http://www.driverpacks.net/DriverPacks/

The links I provided explain how to use DriverPacks in a way more suited to your needs, but you should read Jaak's tutorial about how to use the DriverPacks normally (you'll want this experience for doing the stuff in the links I provided).

Sounds like you already have the OS installed and want a "drivers only" disk of DriverPacks that can be installed into an existing version of windows.

Check out these links, it should help you use DriverPacks that way:
http://forum.driverpacks.net/viewtopic.php?id=960

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

I have nothing wrong with that link.  I just tested it again.  Try right clicking and "save as" ??

Well, you don't necessarily need an MD5 hash.  If you have 7zip installed and it's integrated to the shell, then right clicking on it you can open the 7-zip command subset and test the archive.


Although if you really want here are the MD5 hashes I got from the packs.

Pack: Hash
DP_LAN_wnt5_x86-32_7062.7z: ab7d58d68b40b72cde3fefceb50d2a06
DP_WLAN_wnt5_x86-32_706.7z: 5240b625c3a06e98970c741a4f411d9b
DP_MassStorage_wnt5_x86-32_7072.7z: 60f9b13cd961e25b74a8336ec205dea8
DP_Sound_A_wnt5_x86-32_7072.7z: 0ebaa4af9e13f5ea5fc145c22328e256
DP_Sound_B_wnt5_x86-32_7071.7z: cb16186e1eaef7fec460c18adfb5c905
DP_Graphics_A_wnt5_x86-32_706.7z: d7d37597cb2bb62e3b8079bb04457b8a
DP_Graphics_B_wnt5_x86-32_705.7z: c94a87f2dfd07b86410528427b294c62
DP_Graphics_C_wnt5_x86-32_704.7z: 37ec1ff6ce889150cce4c9b86a633986
DP_CPU_wnt5_x86-32_7041.7z: 2d402ee9fca45d254406b41f87ada406
DP_Chipset_wnt5_x86-32_706.7z: 37591f8a5f27f306a16463f73aef78a4

EDIT:
I used Turbo WinMD5 0.44 to generate the MD5 hashes - http://www.paehl.de/twinmd5.zip

Oh okay, that makes more sense.  tongue

Does that apply to external hard drives attached through USBs as well, Jaak?

Erm, that didn't really clear anything up.

You unzip it under windows and it works fine, then when you're going through the windows setup it only gets to 99% before having a problem?

Where are you unzipping?  Are you streamlining in and letting it unzip during setup or are you trying to open and unzip within an existing windows installation?

Sometimes when you download you end up with a corrupted file.  It doesn't complete, or it has a problem with the pattern...  You have to re-download when you can't open it up like that.  I've done it tons of times.

I've noticed that the problem occurs most when you download more than 1 pack at a time.

I recommend making a 3rd party pack and slipstreaming it that way.  It should work perfectly normally if you do it that way.  I wouldn't mod any of the standard packs to include what you need. smile

Yay!

Okay, the actual download pages seem to be fixed (something is just messed up with the links).  All that's wrong with them is the lack of defining the HTTP parameters.  Here are the download links

Chipset:
http://www.driverpacks.net/DriverPacks/ … .php?pag=c

CPU:
http://www.driverpacks.net/DriverPacks/ … php?pag=cp

Graphics A:
http://www.driverpacks.net/DriverPacks/ … php?pag=ga

Graphics B:
http://www.driverpacks.net/DriverPacks/ … php?pag=gb

Graphics C:
http://www.driverpacks.net/DriverPacks/ … php?pag=gc

Lan:
http://www.driverpacks.net/DriverPacks/ … .php?pag=l

Mass Storage:
http://www.driverpacks.net/DriverPacks/ … .php?pag=m

Sound A:
http://www.driverpacks.net/DriverPacks/ … php?pag=sa

Sound B:
http://www.driverpacks.net/DriverPacks/ … php?pag=sb

WLAN:
http://www.driverpacks.net/DriverPacks/ … .php?pag=w

Uhhh.... Right.... That's what was said in the first post...

FenyX wrote:

I've tried with IE or Firefox.

I just confirmed that it happened in Opera as well.  Didn't really expect it to be a browser problem anyway...

Something must have gone wrong, because I can't access them either.  I'm using Opera.

It seems more like a problem with not being able to connect to a database, because the template works but none of the pertinant information is filled in.  The download link is left with an unestablished parameter.

Haha, I just got told. big_smile

I see they're only being sold in the business areas now.

Uhh...  Dell don't make Latitude anymore so it must be new to you.

It might be a little more helpful if you listed the specific devices wink

One idea is that they appear as a result of a copy from a hard drive. http://www.ureader.com/message/1359769.aspx

Did you do an upgrade as opposed to a fresh install of windows?


However I have a better idea.  You may have "Hide protected operating system files" unchecked in your folder options.  If that is the case it would indicate to me that you accidentally put in a registry hack/patch that you didn't need.  To check/fix open up any folder/explorer window and Tools > Folder Options > View (tab).  Scroll down a little bit (3 or 4 lines) and make sure "Hide protected operating system files" is checked.


Finally (if that's not the case) - Are you removing the Windows File Protection?  Since the desktop.ini is normally a hidden file (which is perfectly normal to be there when you customize some sort of folder setting) it would seem that WFP got a bad crack or patch.  If you delete the desktop.ini files - then they should come back as fully hidden (according to http://forums.techguy.org/windows-nt-20 … here.html).

I see.  So the prompt goes away, but if you're holding F6 or if you press it at the right time it will still work so you can load RAID drivers.

Then does that mean that DriverPacks doesn't do RAID drivers?  So if we do have RAID devices and we make our own pack for RAID drivers and stick it in the 3rd party for integration you won't need to worry about F6 at all?  Or would there have to be a special text mode for that?

Seriously, abdou - you asked for help and they said use method 2 with text mode.  Even still they've said the methods don't really matter either way.  Text mode is all that matters - just enable that and SATA should work fine.

However, integrating driver by driver with nLite is possible - but not a good idea.  It takes much more work than using DriverPacks.  If you are lazy, you'd just use method 2 with text mode enabled.




I'm curious (@one of you on the team), does Text Mode cause any conflicts at all?  I mean, what is (if any) the downside of Text Mode?

It happened with a fresh install as well.  I did some tests on it to see if it was just me or something, tried reproducing the issue and I used the same source that had already had slipstreaming - that's why the log indicates that the source was already modded.

Doesn't matter anyway, I worked around it.

I know, Bashrat.  However I'm stating that when I select a custom finisher method, the winnt.sif file is completely overwritten (not just having data appended).