1

(1 replies, posted in Other)

I've been away for a while. Tonight I looked around, however can't find driver packs overview, recent driverpacks (latest = 12.12), nightlies, ...

I'm lost. Please show me the way.

OverFlow wrote:

'Changed (for shorter paths)'

Woo hoo!

Is that why MD5 isn't correct?

More recent pack here: http://forum.driverpacks.net/viewtopic.php?id=3985

Thanks Jaak, I guess I overlooked SAD. I'd say: remove KTD-option in BASE and replace it with SAD-creator.

Helmi wrote:

look up INFs for matching HWIDs (don't we have such a tool already, BTW?)

I think this is what WsnoW's Drivers Pack Unpacker & Installer does (http://forum.driverpacks.net/viewtopic.php?id=2403).


Helmi wrote:

Problem's just, I wouldn't know how to code that idea into a binary tongue

You're not the only one with this problem wink

Thanks Overflow, you've put it very diplomatic wink I have programming nor scripting knowledge, so if you address it medium high difficulty just forget about it. I'd just noticed copying the driver packs took some time and thought: less copying => less time and I got inspired by (or carried away with) jaws1975's [Add-on] Select desired DriverPacks during M2 install or after install.

IMHO there's no/little advantage in modifying the pack(s) after extraction; it wouldn't save space or time. Helmi mentioned the use of a database. Perhaps this could replace the listing of 'Supported Devices' from DriverPacks.net > Driver Packs. Adding or deleting drivers (or folders) from there seems easy to me. Selecting for sure is, however a tool would be needed to create the ini file, based on the selected drivers (or folders). I've no idea how difficult that would be.

Nevertheless, I'm happy the way DP is working now. Keep up the good work roll

Thank you for your comment. I should have been more specific and will try to do that here.

I endorse your policy. I maintain 8 different systems and DP as it is now certainly is a better option than adding specific drivers for each system. BASE offers a selection possibility (location below D\). Drivers for as much HW as possible still are provided, yet it's a back step creating a Universal Installation Disc lol

I'd just like to make one additional back step (location below D\x). I don't request nor want a list of thousands of drivers. The listing of 'Supported Devices' from DriverPacks.net > Driver Packs would be great. I.E.: from Graphics B I just need I4, I7 and \Sa. I don't have/use 3dfx, Matrox, S3, Via, .. and it would be nice to skip those drivers to save space and time.

If my request is difficult or takes to much effort; no hard feelings if it will not be approved. Maybe it's a challenge to someone. This has happened before (I.E. software section, jaws1975 and WsnoW).

Dpbase offers the possibility to select or unselect the driver packs I want to integrate. That's great as it saves space and time smile

I'd like this possibility for the drivers in the driver packs as well. That way I can skip drivers for hardware I definitely don't have. I know I can trim a driver packs, yet have to do that every time a new version is available; chances of mistakes are high.

With the settings remembered by dpbase.ini updating a trimmed driver pack would be so easy cool

This seems a nice project, however it's not clear for me how to use it. Should I run dpbase.exe as usual and then add the tools and replace presetup.cmd or shouldn't I use dpbase.exe at all?

When I tried to set write cache of my RAID array I couldn't find the Intel Matrix Storage Manager/Console. Is it possible to add this to the driverpack PLEASE.

THANKS!

Thank you for your advice Overflow. I assumed Windows would benefit from the speed also after it was loaded and I didn't know about the impossibility of simultanious access. Yet I think there is a misunderstanding about my configuraton. With strip size (term used by Intel Matrix Storage Manager option ROM) I meant the stripe block size. I get to think what you call stripe I call volume. Please let me explain what I had in mind and if you still think it's a bad idea let me know wink

1. Two Samsung 320GB HHD's joined in 1 RAID-0 array. This 1 array is divided into 2 volumes:
a. Volume 1 has a capacity of 46,2GB and a stripe block size of 64k. It just contains Windows (including swap file, excluded the folders "Program Files" and "Documents and Settings"). Everest speed random read is 145.5 MB/s and access time is 9.00 ms. My considerations choosing this: 1. Fast Windows startup; 2. Fast swap file; 3. Fast Windows running. Because of what you wrote I understand 3 is not a big advantage.
b. Volume 2 has a capacity of 550GB and a stripe block size of 128k. It just contains the folder "Program Files". Everest speed random read is 125.5 MB/s and access time is 17.37 ms (same physical disks; big difference in performance hmm) . My considerations choosing this: 1. Fast loading of apps; 2. doesn't reduce the speed of Windows/swap file; 3. enough place for more than one virtual CD/DVD, thus saving a lot of time loading games/levels/...; 4. doesn't contain valuable data, just stuff I can reinstall.

2. 1x Hitachi 320GB HDD (=different physical media) just for data and the folder "Documents and Settings". Everest speed random read is only 63.5 MB/s and access time is 13.52 ms (compared to RAID rather slow sad  Considerations: 1. safer for my data (roughly half the chance of disk failure compared to RAID-0 (besides that: most valuable data will be backupped to portable HDD); 2. easier to reinstall Windows or change the array/volumes since I can leave the data (it is on a different physical disk); 3. The least need for speed (files aren't large).

Please also tell me if the Intel Matrix Storage Manager/Console should be installed by the driverpack, cause I still can't find it???

OverFlow wrote:

Is it possable for you to kill the MBR on the non raid drive to force the first RAID partition to boot?

I've formatted the non-raid drive. Does that kill the MBR or do I need to do more?
After formatting and booting with both RAID and non-raid I'm getting a "Windows not found" message. Disconnecting the non-raid drive makes Windows start from RAID. Seems like the same pattern; attaching any HDD in addition to RAID array makes the system refuse to boot from RAID mad

OverFlow wrote:

I think i would put the OS on the non raid HDD,
thus improveing perfomance on the stripe and separateing OS/DATA to seperate physical media 
(with SCSI... i could be 'forced' into doing the os and data on the same array IE at gunpoint wink )
sounds like they are trying to lead the horse to water LOL wink

I don't understand your thoughts. I've put the OS on RAID in order to improve performance. Average read speed on the non-raid HDD was 60 MB/s and acces time 15 ms. On the 64k stripe volume it's 130 and 9,5; on the 128k stripe volume 110 and 17! I've tried also an array with one volume. Both 64k and 128k stripe size performied worse.
Seperating OS and data is exactly what I'm trying to achieve by using the raid HDD (=seperate physical media) for my data. Could you please explain??

I'm also still wondering about the Intel Matrix Storage Manager/Console. Please tell me where I can find it or isn't it installed with the driverpack???

Q9450 runs at 3.4GHz with only 1.175V. Memory (OCZ2P10004GK) is bottleneck running faster without Prime95 or MemTest errors. Memory now @ 1020MHz with Performance Enhance (Turbo).

BIOS is F7. I saved 8 profiles to CMOS, so I don't like to clear cmos (I on't know how to save the profiles to HDD and restore them after clearing or updating BIOS. I'll follow your suggestion asking Gigabyte for help.

RAID is on ICH9R, so I guess Hardware based. DiskTune and PCMark05 show best results for the Windows volume with 64k stripe size (faster than 128k; twice as fast as non-raid HDD).

In post #36 I wrote: "I've installed a new WinXPsp3 on my Gigabyte GA-P35-DQ6 using DPBase 8.06 and the latest driverpacks from nightlies (DP_Chipset_wnt5_x86-32_806A_PUBLIC.7z; DP_MassStorage_wnt5_x86-32_806E.7z; ...). The installation was flawless so THANKS for the great DriverPacks"

I then installed it on a non-raid HDD. Now I've added two HDD's in RAID-0 array with two volumes: 45,2 GB Windows (64k stripe) and 550 GB Programs (128k stripe). I've installed WinXPsp3 with DP_MassStorage_wnt5_x86-32_806F.7z on the raid array. If booting with raid AND non-raid HDD connected, my system always boots from the non-raid HDD, although BIOS boot order is 1. Intel Windows; 2. Intel Programs; 3. non-raid HDD.

Connecting the non-raid HDD to the Gigabyte SATA port doesn't solve the problem. Connecting an IDE-HDD neither.

If I disconnect the non-raid HDD it perfectly boots from raid volume 1. Connecting the non-raid HDD after starting Windows makes the contents of the non-raid HDD available.

I tried to look into the Intel Matrix Storage Manager/Console, however I can't find it. Isn't it installed with the driverpack???

Is the boot problem a known issue or better: how can I solve it, so I can run my OS from RAID and keep the data on the non-raid HDD??

PLEASE AND THANKS tongue

I've installed a new WinXPsp3 on my Gigabyte GA-P35-DQ6 using DPBase 8.06 and the latest driverpacks from nightlies (DP_Chipset_wnt5_x86-32_806A_PUBLIC.7z; DP_MassStorage_wnt5_x86-32_806E.7z; ...). The installation was flawless so THANKS for the great DriverPacks smile

I found the Intel Storage driver 8.2.3.1001, however, when booting I get this information:

Serial ATA AHCI BIOS, Version iSrc 1.07 08042006
Copyright (c) 2003-2006 Intel Corporation         10
**This version supports only Hard Disk and CDROM drives **
Please wait. This will take few seconds.

AHCI BIOS installed
Intel (R) Matrix Storage Manager option ROM v 7.5.0.1017 ICH9R wRAID5
Copyright (c) 2003-07 Intel Corporation

As a noob it looks to me like the ROM is old. Could you PLEASE tell me how to update this roll

OverFlow wrote:

And post your hwids with your feedback if you want to see us do a little dance of happyness wink

Since I really want to see the little dance:

===========
PCI devices
===========


PCI\VEN_104C&DEV_8024&SUBSYS_10001458&REV_00\4&1ADD88A5&0&30F0: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_10DE&DEV_0611&SUBSYS_11701462&REV_A2\4&1A9C9F1A&0&0008: NVIDIA GeForce 8800 GT
PCI\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_01\4&CF4E44&0&00E5: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_92\3&13C0B0C5&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2822&SUBSYS_B0001458&REV_02\3&13C0B0C5&0&FA: Intel(R) ICH8R/ICH9R/ICH10R SATA RAID Controller
PCI\VEN_8086&DEV_2916&SUBSYS_00000000&REV_02\3&13C0B0C5&0&F8: Intel(R) ICH9R LPC Interface Controller - 2916
PCI\VEN_8086&DEV_2930&SUBSYS_50011458&REV_02\3&13C0B0C5&0&FB: Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_2934&SUBSYS_50041458&REV_02\3&13C0B0C5&0&E8: Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_2935&SUBSYS_50041458&REV_02\3&13C0B0C5&0&E9: Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2936&SUBSYS_50041458&REV_02\3&13C0B0C5&0&EA: Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2937&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D0: Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2938&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D1: Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2939&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D2: Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_293A&SUBSYS_50061458&REV_02\3&13C0B0C5&0&EF: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_293C&SUBSYS_50061458&REV_02\3&13C0B0C5&0&D7: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_293E&SUBSYS_A0221458&REV_02\3&13C0B0C5&0&D8: Microsoft UAA-busstuurprogramma voor High Definition Audio
PCI\VEN_8086&DEV_2940&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E0: Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_8086&DEV_2948&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E4: Intel(R) ICH9 Family PCI Express Root Port 5 - 2948
PCI\VEN_8086&DEV_294A&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E5: Intel(R) ICH9 Family PCI Express Root Port 6 - 294A
PCI\VEN_8086&DEV_29C0&SUBSYS_00000000&REV_02\3&13C0B0C5&0&00: Intel(R) G33/G31/P35/P31 Express Chipset Processor to I/O Controller - 29C0
PCI\VEN_8086&DEV_29C1&SUBSYS_00000000&REV_02\3&13C0B0C5&0&08: Intel(R) G33/G31/P35/P31 Express Chipset PCI Express Root Port - 29C1
21 matching device(s) found.


===========
USB devices
===========

USB\ROOT_HUB\4&26397AB7&0                                   : USB-hoofdhub
USB\ROOT_HUB\4&2D364FD6&0                                   : USB-hoofdhub
USB\ROOT_HUB\4&30B58B36&0                                   : USB-hoofdhub
USB\ROOT_HUB\4&70ACE42&0                                    : USB-hoofdhub
USB\ROOT_HUB\4&99F0121&0                                    : USB-hoofdhub
USB\ROOT_HUB\4&BD04752&0                                    : USB-hoofdhub
USB\ROOT_HUB20\4&269B1DF4&0                                 : USB-hoofdhub
USB\ROOT_HUB20\4&88AB043&0                                  : USB-hoofdhub
8 matching device(s) found.

@Fragbert,

Sorry for my ignorance and your subtile way of making that clear tongue

Just a humble explanation of how my insane 'opinion' disturbed my mind:

Following your link I read: "Installs the Intel® Matrix Storage Technology (RAID) driver version 8.2.3.1001 for Intel® Desktop Boards." and "valid for the products listed below".

From Intel Download Center > Chipsets > Chipset Software > Intel® Matrix Storage Manager > Windows* XP Professional I'm getting to the place I provided a link to; ver.# 8.2.0.1001.

I'm still trying to figure out how I could have overlooked the consideration of Intel messing up their site hmm

Fragbert wrote:

Updated! v8.2.3.1001

IMHO this driver is for Intel boards only. For other board it still is 8.2.0.1001: http://downloadcenter.intel.com/filter_ … ;submit=Go!

I'm reluctant integrating an Intel board driver on my non-Intel (p.e. Gigabyte) board, even if it's newer.

Will the update driverpack contain both versions or just the newest for Intel boards?

OK, I will integrate streaming video as well ;-)

Thanks for all the good work. I appreciate the time you spend and don't want to look impatient. Yet I'm eager to apply the new Intel Matrix Storage.

In DriverPacks Overview the MassStorage Pack is still 8.05. Is it safe to use 8.06C or should I wait until a final version appears in Overview?

I uploaded DP_PrintersHP_wnt5_x86-32_71126.7z (at least I hope I did). It was the first time I used a FTP program and uploaded a file. If something went wrong -or I did wrong- let me know; I'll try to correct it tongue

DP_PrintersHP_wnt5_x86-32_71126.7z available (35.810 kB); download from 31-12-2007.

If you can tell me where and how I can upload it.

OverFlow wrote:

...in danger of not being appreciated for the work that it is...

Certainly not on my behalf.....reffering to the danger wink

I DO very much appreciate the work big_smile big_smile big_smile

From first post;
DriverPack Misc: 7.12.16
View the thread - Here
(MD5 Hash: D8E99C169EB67C9C4C0788F35352A9FE)

Link to the thread doesn't work and Hash isn't correct. Is it still safe to download?

DriverPack Monitor: 7.11.1 also has wrong Hash in first post. Hash in thread is correct.

24

(5 replies, posted in Dutch)

It's no problem at all not to speak Dutch, as long as you can read and write it smile

Ik ga het gewoon proberen met RC2.

25

(5 replies, posted in Dutch)

Bij voorbaat excuses als ik dit onderwerp op de verkeerde plaats post; ik kwam bij een zoekopdracht naar nightlies zoveel hits tegen dat ik door de bomen het bos niet meer zie.

Na het downloaden van de driverpacks via de Overview, wilde ik checken of er nog een nieuwere Base dan 801RC2 was. Op de site kon ik echter allen 7.05.2 vinden. Via google kwam ik vervolgens uit bij http://dev.driverpacks.thesneaky.com/dr … nightlies/

Daar vond ik veel recentere versies van de driverpacks dan bij Overview. Chipset is bijvoorbeeld 8021 <> 7101.

Het is me niet duidelijk of de overview achterloopt en ik dus beter de nieuwere versies van nightlies kan gebruiken of dat het toch beter is om de oudere versies via overview te gebruiken.