You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by mr_smartepants
DriverPacks BASE automatically selects only the newest versions of each of the DriverPacks. No real need to isolate the old from the new.
Failure "Vmware 7". verify what a "real PC" and commented
Burn your .iso to a DVD and boot the actual computer (NOT vmware) from the DVD and see if the jraid problem is still there.
Welcome to DriverPacks.
That's an excellent first post. You posted nearly all the info we need.
That's an odd problem too. Is your RAID controller an Intel-branded chip or Promise-branded?
It wouldn't be a problem with DriverPacks BASE, but with the .ini in dpms.
I'm super busy this week but I'll try and get something sorted out maybe this weekend.
Functionally speaking, there isn't any need for this pack anymore since we included the contents in DriverPack Chipset.
But I would continue to pursue this as a matter of principle! "WTF" indeed!!!
VMs don't pass the hardware through properly. Please try to boot your .iso on real hardware and see if the problem returns.
We haven't changed the jraid drivers in over a year. There's no reason why 12.09 is any different from 12.06 in regards to jraid.
Please double-check the file hash also.
I have JMicron RAID on my old board and didn't have any problems.
Yes, please post your HWID list.
We never use drivers downloaded from station drivers (or other 3rd party sites) because their sources can not be verified.
We try to use only drivers downloaded from their vendor source to maintain a "chain of custody" to ensure DriverPacks integrity.
The drivers in the "All" folder are supported by "all" the OS. The other folders are OS-specific. So when integrating into a Vista OS, you should use both "All" and "Vista".
Though if you come across any errors, let me know in case we need to shuffle some drivers around.
Why not do all that in a "for" loop?
@ECHO off & setlocal EnableDelayedExpansion
::blah blah blah...
SET "PEIMG=%~dp0WindowsAIK\Tools\PETools\peimg.exe"
SET "DRIVERS=%~dp0BootDrivers"
FOR /F %%I IN ('dir /b /s "%DRIVERS%\*.inf"') DO (
ECHO Integrating %%I
%PEIMG% /inf=%%I %~dp0Mount
)
::blah blah blah...I can't remember. It's been so long since I've done a Vista image.
To make it easy for myself, I think I just put all the mass storage drivers in a folder named "$WinPEDriver$" at the root of the .iso.
Uploaded to mediafire and updated first post with link.
Hope it works for you.
Welcome to DriverPacks!
Thank you for the "Thank you".
Methode 2 still copy all the driver on local drive is this normal ?
Yes, of course.
can't find flxhcic.sys
[FRESCO] ;DOESNT WORK ms_1_sysFile="flxhcic.sys" ms_2_sysFile="flxhcih.sys"any ideas?
The header in brackets [] is the folder name.
So in order to find the two .sys files the file path would need to be:
dpms -
D\M\FRESCO\flxhcic.sys
D\M\FRESCO\flxhcih.sys
Obviously "FRESCO" is a long name and should be shortened to something like "FR" or "UF" (USB-Fresco).
Well, they exceed the 8.3 DOS filename restriction for textmode to work...
Welcome to DriverPacks.
Can you post your full HWID list using the tool in my signature?
Here's the link from the FAQ on how to make your own dpms: http://forum.driverpacks.net/viewtopic.php?id=2461
Can you tell us exactly WHY the current drivers in D\M\N8\ don't work?
The driver we use is from 15.56 and the reference nvidia driver for 630a is 15.45.
I compared the two RAID drivers and couldn't find any differences.
If you want to be sure, you can do this test.
1) Open the dpms .7z file using the current version of 7-Zip ONLY (not winrar or other archiver).
2) Copy all the files from the extracted 15.45 folders (\IDE\WinXP\sataraid\) & (\IDE\WinXP\sata_ide\) to the dpms D\M\N8 folder.
3) In 7-zip, copy nvgts.sys to nvgts7r.sys and nvrd32.sys to nvrd327r.sys so you have 4 .sys files.
4) Close 7-zip to repackage.
5) Integrate into source with DriverPacks BASE and retest.
I'll look into the "spaces" issue.
To convert a method2 to method1 NT6 utility, simply extract all the x86 .7z files to the StandAloneDriverpackUtility_SAD2\NT6\x86\D\ folder. Same for x64.
The folder size will be HUGE though. You've been warned. 
That one is older than the release version.
Don't use it.
Marking as "solved".
We don't have a tutorial for Win7.
My scripts here are pretty self explanatory and probably the closest you'll get to simplicity.
Well, the driver in DP_MassStorage_wnt6-x64_1208\x64\All\M\ITE\2\ is slightly newer and matches your HWID.
I'm not sure why it doesn't work other than to echo TechDud's comments about driver signing. Win7 x64 is super-critical about signed drivers and will ignore ones that are not signed or improperly signed.
Using the /ForceUnsigned command would be required for this old driver since it's certificate is probably expired and it was designed for XP/Vista anyway.
Let us know if you find a driver that works under normal conditions and I'll add it to the packs.
I'm looking at the current Third Party DriverPack Misc 1201 and there is no D\3\X\H3 folder!
What version are you using? (Because it's not ours)
It DOES work from a USB key because that's how I use it.
Please post a screen shot of the folder structure where you have the .7z DriverPacks located.
Also post the contents of the log file found at %SystemDrive%\DP_Install_Tool.log
They are contained in the Intel chipset drivers.
We have them in dpms \D\M\I5\cougide.inf
OK, I'll see what I can do.
How about uploading it to github or similar free code hosting?
It would be a shame to lose you as a developer. This utility is awesome and I can't imagine being able to build these DriverPacks without it.
DriverPacks.net Forum » Posts by mr_smartepants
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.093 seconds, 5 queries executed ]