You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 39 of 159)
DriverPacks.net Forum » Posts by mr_smartepants
TechDud wrote:forgive me, i lack understanding of why a hack would be necessary.
It should not be needed. The .inf already contains a generic [Intel.NTamd64] section which should work with all 64-bit systems.
I think that the Win7 drivers are either included in the OS or downloadable from Windows update.
This is a quick 'hack' test just to see if that section is relevant. I'll bet money that it won't work.
Oh, and WHQL signing will never happen when tinkering with the .inf as I have (unless you have a LOT of time on your hands, which I don't)
ENOUGH of the warez discussion!
Violation of rule#1
1. This is not a warez site! Links to or requests for warez and/or illegal material (OS discs, porn, cracks, serials, etc.) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will not be tolerated. Advertising is also forbidden. If you violate any of the aforementioned you will be banned from this site without further notice.
Consider this the one and only warning for the above list of egregious items.
1a. We do not support warez or pirated installs. Our definition of this is: Did you obtain your license from Microsoft or an authorized OEM vendor? Do you have a legal hologram-ed disc? If the answers to both of those questions is "Yes", please continue. Otherwise, go legit or go home. Warez is a support nightmare for the DriverPacks staff. 99% of the DriverPacks failures are caused by the idiot who modified/released the pirated OS source in the first place because they didn't know what they were doing.
Hiren's boot cd is a KNOWN warez derivative and there will be NO FURTHER DISCUSSION of it on these forums! Clear?
I've never used it. I stick to my batch files. 
revi wrote:Hiren's BootCD
We don't support warez. Strike one!
It's in the SAD2\bin\ folder
The folder structure looks like this:
|--+ SAD2
|--+ bin
|--+ 7-zip32.dll
|--+ dpinst32.7z
|--+ dpinst64.7z (etc.)
|--+ NT6
|--+ x86
|--+ D
|--+ x64
You'll notice that you get a second command window minimized when you see "Please wait for the MicroSoft tool to complete it's job..." which is why we also say "The progress window is minimized to the task bar"
You would see an error if dpinst was missing.
OverFlow wrote:could mod the inf and force install it... but might be better just to have an unknown device
That's what I did.
http://www.mediafire.com/file/dgbmcb9phb2tc76/HECI.7z
Try this from a safe distance.
You'll get an ugly driver signing error but it MIGHT work.
I rewrote the .inf to support Win7 x64 but I don't like how the .inf references the WinXP event log.
For NT6, the correct dpinst.exe is extracted for the architecture of the target system.
Yes, it only updates the drivers for the hardware on the target machine at the time the utility is run. If you change hardware, you'll have an "unknown hardware" listed.
SAD2 could be scripted as part of RunOnce prior to imaging/deployment. Then it would run on first boot after imaging.
Which he stole from my link in post #2
Wim Leers wrote:What we really need to do, is improve our documentation at http://driverpacks.net/docs. For example, there is simply no documentation for Windows Vista/7…
Yes, I am VERY behind in updating our documentation. I'm hoping to have some down-time this winter to update them.
A3 and A5 share PCI\VEN_1191&DEV_0009&SUBSYS_00091191 (Fixed in 11.08.1b1)
M - All 5 hwids are duped accross ms_1 ("mv61xxmm") and ms_2 ("mv61xx") (Normal, this is intended)
M4 - All 3 hwids are duped accross ms_1 (mv64xxmm) and ms_2 (mv64xx) (Normal, this is intended)
M5 - All 29 hwids are duped accross ms_1 ("mvxxmm") and ms_2 ("mv91xx") (Normal, this is intended)
S5 and S4 Share PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 & PCI\VEN_1002&DEV_4379&SUBSYS_43791002 & PCI\VEN_1002&DEV_437A&SUBSYS_437A1002 (Fixed in 11.08.1b1)
List of Inline Dupes
D3 - PCI\VEN_1028&DEV_000A&SUBSYS_011B1028 & PCI\VEN_1028&DEV_000A&SUBSYS_01211028 (Fixed in 11.08.1b1)
L2 - PCI\VEN_8086&DEV_1960&SUBSYS_0466101E & PCI\VEN_8086&DEV_1960&SUBSYS_0467101E & PCI\VEN_8086&DEV_1960&SUBSYS_0490101E (Fixed in 11.08.1b1)
S3 - PCI\VEN_1095&DEV_3531&SUBSYS_30d4103c (Fixed in 11.08.1b1)
S4 - PCI\VEN_1095&DEV_3512&SUBSYS_81E8104D (Fixed in 11.08.1b1)
All the duplicates between the SC# folders are because of the different card BIOS revisions. They've been like that for years.
Seriously though, how did you find those? Jeff's right, you need to be on the testing team!
I have no idea either. 
There's nothing in the dpms .ini that would isolate those three.
RaymondRT wrote:Am I doing something wrong?
Yes. Don't use nlite.
The only way DriverPacks should be integrated into your XP source is with DriverPacks BASE.
If you did use DriverPacks BASE (you hadn't mentioned it), please post your DPs_BASE.log and HWID list.
PaulDG wrote:M - All 5 hwids are duped accross ms_1 ("mv61xxmm") and ms_2 ("mv61xx")
M4 - All 3 hwids are duped accross ms_1 (mv64xxmm) and ms_2 (mv64xx)
M5 - All 29 hwids are duped accross ms_1 ("mvxxmm") and ms_2 ("mv91xx")
Those are all by design. The mv*xxmm driver needs to load before it's corresponding mv##xx driver. That's how magic happens!
I'll look into the others.
Thanks for reporting.
cdusseau wrote:Extracted from Dell CD --> Ryans RVM --> nLite (gfx drivers and a couple tweaks) --> Driverpacks
Well I can see two problems right from the start.
1) You need to start with an untouched XP source. Dell makes significant changes to their install source which makes it "tainted" from our point of view. GIGO (Garbage In, Garbage Out).
2) We do NOT support nlite (neither do they). Please stop using nlite, it makes a mess of your source.
For the purposes of us trying to fix the problem with our DriverPacks, follow our testing advice. Clean XP source. Use only recommended tools (RVMi, DriverPacks BASE). Provide us feedback at each stage so we can nail this down.
HWIDs?
DPs_BASE.log?
Already included in DriverPack Chipset 11.08 on the torrent server. Just getting ready to update the tracker.
This is solved in the upcoming v11.08 release
Implemented for 11.08 release.
- IT\ ITECIR Infrared Receiver (moved to Third Party DriverPack Misc)
To be honest, I've never played with XP-embedded. You should be able to integrate the DriverPacks into your source with DriverPacks BASE. I don't know.
Another option is to install the drivers after your XP install is complete by running our SAD2 utility. But that's an unknown environment to me, so I don't know how it will react.
Posts found [ 951 to 975 of 3,962 ]
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.137 seconds, 9 queries executed ]
