251

(55 replies, posted in Vista / 7 DriverPack Mass Storage)

Please post the HWIDs of the PC with the problems.

252

(16 replies, posted in DriverPack Graphics)

Alright! Problem solved! big_smile
For the modem, make a request in the Third Party DriverPacks section.  Post your HWIDs and link to the driver and someone will update it.

253

(1 replies, posted in 3rd Party DriverPacks)

Please read our tutorial.
http://forum.driverpacks.net/viewtopic.php?id=1449

254

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

Please read our tutorial.
http://forum.driverpacks.net/viewtopic.php?id=1449

Cool!  Thank you.
Symantec is coughing up a hairball and their 'Insight' scanner is flagging the x64 version as "unknown".
Simple enough to click "ignore" but thought you should know.

256

(16 replies, posted in DriverPack Graphics)

Yes.  You have too many DriverPacks.
You are experiencing this bug
Remove all of the Third Party DriverPacks (except the graphics sub-packs) and install them with SAD2 once Windows is fully installed.

257

(16 replies, posted in DriverPack Graphics)

And your DPs_BASE.log please?

258

(12 replies, posted in Windows 7 tools)

Damnation wrote:

So where do I place SAD2 in XP ISO?

Damnation wrote:

%WinXP-Disc%\$oem$\$1\D\SAD2

259

(12 replies, posted in Windows 7 tools)

No, for XP you need to use DriverPacks BASE or the "RunOnceEx" method.
http://unattended.msfn.org/unattended.x … 7369cedba/

@echo off

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /V TITLE /D "Installing stuff" /f

REG ADD %KEY%\005 /VE /D "SAD2" /f
REG ADD %KEY%\005 /V 1 /D "%systemdrive%\D\SAD2\DP_Install_Tool.cmd /s" /f

EXIT

260

(16 replies, posted in DriverPack Graphics)

Be specific with which HWIDs are missing.  And which driver fixes each one.

big_smile

262

(12 replies, posted in Windows 7 tools)

SAD2 is compatible with all Windows OS.
My other scripts are for Win7 only.

263

(16 replies, posted in DriverPack Graphics)

I fixed your post layout and added code tags.
I'm not sure what you're asking for.  Was something not installed?  Or are you looking to add the Maxdata branding to the drivers?

Welcome to DriverPacks!
It's probable that you have a UEFI instead of a common BIOS.  UEFI machines format the boot drive as GPT and XP can't boot to GPT.
You should consider having Win7 installed as the host OS and use XP in a virtual environment (VirtualPC, VirtualBox, VMware, etc.)
http://www.microsoft.com/resources/docu … x?mfr=true

GPT disks are supported only by Windows XP 64-Bit Edition. You cannot move GPT disks to computers running the 32-bit versions of Windows XP. From Disk Management on computers running a 32-bit version of Windows XP, GPT disks appear as basic MBR disks with a single partition covering the whole disk, but the data on the partition cannot be accessed.

http://technet.microsoft.com/en-us/libr … Structures

Partition Structures

The partition types must match the firmware of the computer. You can install Windows® 7 and Windows Server® 2008 R2 on hard disks that are based on any of the following types of firmware:

Basic Input/Output System (BIOS). Uses the Master Boot Record (MBR) partition structure.

Extensible Firmware Interface (EFI) Class 1. Uses the GUID Partition Table (GPT) partition structure.

Unified Extensible Firmware Interface (UEFI) Class 2: Uses the GPT partition structure. Also includes a compatibility support module (CSM) that enables you to use BIOS functions, including the MBR partition structure. This module may be enabled or disabled in the firmware.

Unified Extensible Firmware Interface (UEFI) Class 3: Uses the GPT partition structure.

265

(12 replies, posted in Windows 7 tools)

No.  SAD2 will install drivers into a running system.
To inject drivers into boot.wim (or install.wim) you will need my other scripts.
Or use a tool like Win7Toolkit.

266

(12 replies, posted in Windows 7 tools)

Yes to all except your last question.
You create a new setupcomplete.cmd file with the above as it's contents.

267

(12 replies, posted in Windows 7 tools)

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

mr_smartepants wrote:

To get this working in Win7 during an unattended install do the following "setupcomplete.cmd" method.
Create the following folder structure to your Win7 disc:
%Win7-Disc%\sources\$oem$\$1\D\SAD2 (entire SAD2 folder with all DriverPacks goes here)
%Win7-Disc%\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd
Add the following code to the setupcomplete.cmd file.

@echo off
START %systemdrive%\D\SAD2\DP_Install_Tool.cmd
vvs wrote:

This file (LSI_gen2.sys) exists in WinXP SP3 distributive.

I don't know where you got your XP source, but lsi_gen2.sys does NOT exist in a MSDN virgin XP-SP3 source.

vvs wrote:

This bug will be fixed?

Did you follow my prior instructions?  That will fix your problem (not a bug with dpms).
You have a corrupted source and you need to start again.

I'll take it from here and make any corrections (if needed).
Thanks for your help!

270

(45 replies, posted in 3rd Party DriverPacks)

Third Party DriverPack HID 12.09 finally made it onto the torrent tracker!
@techdud, I didn't incorporate your additions in this version.  Sorry.

271

(53 replies, posted in 3rd Party Vista / 7 DriverPacks)

@compstuff,
Don't knock yourself out on this one.  I'm updating this and the XP HID Third Party DriverPacks now.

272

(20 replies, posted in 3rd Party Vista / 7 DriverPacks)

Looks good to me.

LSI_gen2.* files were replaced with sas2xp86.*

Your source files have become corrupted and you need to start over from scratch.
If you haven't already done so, delete your \QSC folder to prevent any older drivers/files from corrupting anything else.

Easy.  Don't integrate DriverPacks using DriverPacks BASE.  That process will break the "repair" function.
Instead use SAD2.  It will do what you want.

candles wrote:
Damnation wrote:

I'm just wondering why is this HWID

PCI\VEN_8086&DEV_24DF

Is used for both

Intel 82801ER/6300ESB SATA RAID 5.5

as well as

LSI Logic MegaRAID IDE for INTEL

in the masstorage.ini
is this a driver conflict? or is there a reason for this?

Yep, that is my wonderings too... Commenting out the MegaINTL line and it then suddenly works suggests to me that it is a conflict... But I am not an expert in these matters by a long shot!

It's not used for both.  One ends in "CC_104" while the other ends in SUBSYS_xxxxxxxx.  Totally different.
None of your HWIDs match the [L] section entries anyway so I'm not sure why that's a problem.

[L]
; This section has to be placed before [I4]
LSI Logic MegaRAID IDE for INTEL"
PCI\VEN_8086&DEV_24df&SUBSYS_34348086,PCI\VEN_8086&DEV_24df&SUBSYS_34328086,PCI\VEN_8086&DEV_24df&SUBSYS_34368086,PCI\VEN_8086&DEV_24df&SUBSYS_34388086,PCI\VEN_8086&DEV_24df&SUBSYS_343a8086,PCI\VEN_8086&DEV_24df&SUBSYS_343c8086,PCI\VEN_8086&DEV_24df&SUBSYS_343e8086,PCI\VEN_8086&DEV_24df&SUBSYS_344d8086,PCI\VEN_8086&DEV_24df&SUBSYS_34558086,PCI\VEN_8086&DEV_24df&SUBSYS_34578086,PCI\VEN_8086&DEV_24df&SUBSYS_34618086,PCI\VEN_8086&DEV_24df&SUBSYS_34638086,PCI\VEN_8086&DEV_24df&SUBSYS_34658086


[i]
Intel 82801ER/6300ESB SATA RAID 5.5
PCI\VEN_8086&DEV_24DF&CC_0104