You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by compstuff
@Bigfoot
For now... Same feedback from me as the Chipset:
After all your work I'm sorry to hear that... I am trying to get up to date and I am going to put some tests together for a Latitude 5520 and 5530 tomorrow... not sure if I will use this for them
I am also making an image for some Vostro laptops and this may work perfectly... I will test this as is but I will provide some feedback
@Bigfoot
After all your work I'm sorry to hear that... I am trying to get up to date and I am going to put some tests together for a Latitude 5520 and 5530 tomorrow... not sure if I will use this for them
I am also making an image for some Vostro laptops and this may work perfectly... I will test this as is but I will provide some feedback
This is another pack that I want to start looking at and we all know its been a pain so any feedback as to where we should start?
Is this the latest BETA Mass Storage Pack? I am wondering where to start working on updates to the pack. Don't get me wrong I KNOW this pack is over my head but I am obviously capable of checking driver dates, versions etc. and making some easy changes and updates.
This pack has the older 10 series Intel driver so I am wondering how many people have used or tested 12.5 or 12.8 and if anyone has any feedback.
@Techdud
In the same thread it seems two ops seem to feel the answer is setting boot mode to UEFI... but if you don't have UEFI option that may be an issue
Is this the latest BETA Chipset Pack? I am wondering where to start working on updates to the pack. I am also wondering how many people have used or tested this pack and if anyone has any feedback.
http://www.mediafire.com/?b2lzmea9l0pvht3
Cleaned up Pack
Drivers are dism compatible.
TechDud I always enjoy reading your posts :-) and in that spirit I ran across this Astronomy Picture of the Day Archive http://www.star.ucl.ac.uk/~apod/apod/archivepix.html so I thought I would share
I'm trying to catch up with my reading and get up to date so pardon my late response to some previous posts... Like many of us I too have checked SAM's site but I actually haven't used any of his drivers... in fact I find his site so damn confusing that's it's a bit painful. I always wondered what happened and why SAM seems to have "separated" or "isolated" his efforts from here... it seems like such a no brainer that the collaboration would be INVALUABLE to the drivers community. I also see no issue with this site maintaining tighter QC and less releases than them so again I don't see competition I see different goals and methodologies... which BOTH work.
All... I too have simply not had the time to work here on the driver forum even though I think its one of the MOST important. In fact all of my integration's have suffered because I have let my drivers skills diminish at the expense of learning my WIN 7 integration's.
With that said I work almost exclusively with WIN 7x64 and I still have the ability to test driver integration's almost daily on Dell laptops (mostly Latitudes in the 5 & 6 series). I will offer my testing help and be more than happy to reap the benefits :-)
Bigfoot... wanted to say THANKS for your work updating the packs!
What an AWESOME picture... almost textbook Christmas pic...
Merry Christmas & Happy Holidays to Everyone!!!
SamLab that's awesome Thanks very much
I'm always lurking and keeping my eye on you all :-)
Each laptop did something a little different... they each got the wrong drivers but each used a default driver which was definitely from the integration. On my 6420 it kept giving me a dll load failure when I logged in and the Vostro I had to manually install the actual Dell driver.
I have to admit this has been a really bad week at work so between that and my learning curve with these packs I'm sure I made some errors. I haven't even had a chance to follow-up with you Rick but I will once some dust settles at work.
I'm actually having lots of problems with my pack... it didn't work on my latitude 6420 or my test Vostro 3550
Thanks... I need to get more experience on this anyway because I really need to learn how to update these WIN7 packs. I need to cut about 300 dell laptops over to 7 and although I have been using WinToolKit quite successfully it is not a replacement for DriverPacks
@compstuff,
Don't knock yourself out on this one. I'm updating this and the XP HID Third Party DriverPacks now.
Awesome Rick, thanks... I understand both and will try now because I am working on a few other packs as well
compstuff just because the driver did not have the html's could be because it was an older version that did no have them to begin with, you should look in the SourceDiskFiles section for a list of needed files
BTW a quick way to test the driver (also to leave the junk files behind) is to use pnputil to "add" the driver to your current machine
pnputil -a <filename>.infThe driver is added to %WinDir%|System32\DriverStore\FileRepository\, here you can them copy this folder and delete the PNF file and voila, you have a driverpack
I just want to make sure I am corrrect on this:
The following are all from Dell's Dell Tech Center http://en.community.dell.com/techcenter … yment.aspx and they seem to list these as chipset but I am including them in the Card Reader Pack... is that correct?
x64 chipset GVG3T_A00-00 O2 Micro OZ600xxx memory card reader driver A01 3.0.07.37
x64 chipset KC9W0_A01-00 O2 Micro OZ600xxx memory card reader driver A01 3.0.07.23
x64 chipset NFP0X_A04-00 Ricoh R5U24x/R5U23x Memory Card Drivers-Post RTS A04 2.11.01.02
x64 CHIPSET 3316M Realtek RTS5209 CardReader Driver A00-00 6.1.7601.28094
x64 CHIPSET GVG3T O2Micro MS Disk Device n/a 6.1.7600.16385
x64 CHIPSET R247353 TexasI PCIxx21 Integrated FlashMedia Controller n/a 2.0.0.10
x64 CHIPSET R252328 Realtek RTS5159 Card Reader Driver A00 6.1.7600.30103
x64 CHIPSET R263985 R5U24x A04 6.10.02.07
Hi Guys,
It's been a long time since I have participated but I still lurk and admire :-)
I am going to try and update and make some packs and have some questions. In this pack I got the 02/16/2012, 7.1211.101.114 and 09/21/2011, 7.1208.101.125 packs from the Dell Tech Center http://en.community.dell.com/techcenter … yment.aspx
Am I correct that .114 covers all but two ID's that 125 cover?
%Apoint.DeviceDesc% = MouFilter_Inst_Dell_E4_01.ntamd64,ACPI\DLL057D
%Apoint.DeviceDesc% = MouFilter_Inst_Dell_E4_03.ntamd64,ACPI\DLL0584
If that's correct do I just ad them both to the new pack and the hardware that is referenced in both packs will obtain the latest driver?
Man I am rusty at this :-)
EDIT: I updated the Toshiba & Sony drivers and notices that your pack did not contain the html and wmv files only the mpg so I followed your lead and deleted those for the pack. Then when I started to update the HP drivers I noticed you kept all of those files. Can you help me understand? I will upload a beta as soon as I am done and I will be testing this pack on some Dell 5510, 5520, 5530 and 6420 laptops next week. I also have a few Optiplex and Vostro workstations that I can try to make sure they work as well.
WOW you weren't kidding when you said the HP1 inf had lots of hardware ID's :-) Did you make that yourself by combining others? The HP driver that was linked here earlier had different ID's than HP1 and HP2 so does that mean HP3?
I probably screwed this up so this is purely a test pack that I posted for you review and guidance:
DP_Touchpad_Mouse_wnt6-x64_1210b2.7z
http://www.mediafire.com/?dpyg36aloyt3lej
MD5: 12084658318b3130432c1b57e13a5008
Thanks very much!
Thanks very much!!!
Just wanted to say I find your information extremely interesting and thought provoking... thanks
I actually used HashCheck http://code.kliu.org/hashcheck/ and have been using it for years since I learned about it on here :-) It also does SHA-1 checks and I could easily reference those as well because I added the whole bunch in the spreadsheet which was the only way I was able to sort them out... and now I will also use Notepad++ as well :-)
I was really banging my head against the wall with this one so I did lots of tests and even tracked stuff through some spreadsheets to help make sense but I figured an MD5 check against things was the best bet... you are much better at this stuff than me but I will gladly send the spreadsheet to save you some time if you want... its about time I give back to the forum :-)
compstuff wrote:As a further example I looked at the Chipset WIN7/Intel/1 files and the ALL/Intel/1 files... all 116 files in the WIN7 folder are exact MD5 matches for the ALL folder... if thats the case why are they both needed?
Really? To be honest I never checked. If that's the case, then we can just get rid of the Win7 folder and keep the All folder instead. That will shave about 100kb from the pack.
I knew the AMD folders had duplicates, I just didn't have time to weed them all out.
Maybe I should revisit that pack eh?
DriverPacks.net Forum » Posts by compstuff
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.024 seconds, 6 queries executed ]
