1,576 Reply by mr_smartepants

(32 replies, posted in DriverPack Mass Storage)

I'm fixing it based on the entries of an untouched XP-pro txtsetup.sif 

"PCI\VEN_1000&DEV_0001" = symc810
"PCI\VEN_1000&DEV_0002" = symc8xx
"PCI\VEN_1000&DEV_0003" = symc8xx
"PCI\VEN_1000&DEV_0004" = symc8xx
"PCI\VEN_1000&DEV_0005" = symc8xx
"PCI\VEN_1000&DEV_0006" = symc8xx
"PCI\VEN_1000&DEV_000C" = symc8xx
"PCI\VEN_1000&DEV_000D" = symc8xx
"PCI\VEN_1000&DEV_000F" = symc8xx
"PCI\VEN_1000&DEV_0012" = sym_hi
"PCI\VEN_1000&DEV_000A" = sym_hi
"PCI\VEN_1000&DEV_000B" = sym_hi
"PCI\VEN_1000&DEV_0012&SUBSYS_001b0e11" = sym_hi
"PCI\VEN_1000&DEV_000b&SUBSYS_60040e11" = sym_hi

Go to forum: DriverPack Mass Storage

1,577 Reply by mr_smartepants

(32 replies, posted in DriverPack Mass Storage)

OOPS!
I'll fix that right away.  Thanks for the keen eye!

Go to forum: DriverPack Mass Storage

1,578 Reply by mr_smartepants

(13 replies, posted in BartPE - UBCD4Win - WinPE)

Well if the newer drivers don't work in PE, then just remove the folder for now.
As an alternative, you can edit the DriverPack LAN .ini and remove the semicolons from the [r4] section like this:

[R4]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "R4_realtek"
ms_1_sysfile 	= "Rtenicxp.sys"
ms_1_exc_skipIfOS="wxp,w2k3"

Go to forum: BartPE - UBCD4Win - WinPE

1,579 Reply by mr_smartepants

(17 replies, posted in DriverPack WLAN)

markstrelecki wrote:

Thanks again for the sterling work supporting a gargantuan project with superhuman technical support and limitless patience.

LOL, Thanks Mark. big_smile
Driver roll-back in progress.  Back to the drawing-board.

Go to forum: DriverPack WLAN

1,580 Reply by mr_smartepants

(39 replies, posted in DriverPack Graphics)

You've got email...again. wink

Go to forum: DriverPack Graphics

1,581 Reply by mr_smartepants

(30 replies, posted in DriverPack Graphics)

I've emailed it to you again.  The first email had a blank subject line. :oops:
This should also fix your ATI bug in the other thread.

Go to forum: DriverPack Graphics

1,582 Reply by mr_smartepants

(13 replies, posted in BartPE - UBCD4Win - WinPE)

Posting your HWIDs would be a good start.  I'm not going to delete an entire folder just because one user has a problem.  I may be able to weed out one HWID from the .inf though if it's duplicated elsewhere.
Your HWIDs are key.

Go to forum: BartPE - UBCD4Win - WinPE

1,583 Reply by mr_smartepants

(101 replies, posted in Feature Requests)

@MeOW.  If you are REALLY h*ll-bent on supporting XP64, the SAD2 utility I've developed MAY be modified to support it.  But I will not support XP64, it's a dead platform.
SAD2 file here: http://www.mediafire.com/file/dhc1d68r4 … -101203.7z
Do NOT pollute other threads with XP64 support requests, I'll delete them.

As a matter of fact, our support for all NT5-based platforms will be diminishing in the near future while we devote more time to NT6.
Sorry, but there are only so many hours in the day and I for one will only support the OS of choice for the vast majority of our users...that does not include XP64.

Go to forum: Feature Requests

1,584 Reply by mr_smartepants

(9 replies, posted in DriverPack Mass Storage)

Please read the "read before you post" linked in my signature.  Then post your DPs_BASE.log and HWID list using the utility also linked in my signature.
This will help us narrow down the problem with your system.

Go to forum: DriverPack Mass Storage

1,585 Reply by mr_smartepants

(121 replies, posted in Windows 7 Discussion)

That's because the *.thesneaky.com domain expired.  I'll update the link in a bit.
Mediafire link added.

Go to forum: Windows 7 Discussion

1,586 Reply by mr_smartepants

(30 replies, posted in DriverPack Graphics)

Odd.
Nvidia is updated in our release candidate. Can you test?  You have email...

Go to forum: DriverPack Graphics

1,587 Reply by mr_smartepants

(13 replies, posted in BartPE - UBCD4Win - WinPE)

dehuu76 wrote:

How can i fix this problem?

You just did. wink

Moving thread to BartPE section...

Go to forum: BartPE - UBCD4Win - WinPE

1,588 Reply by mr_smartepants

(17 replies, posted in DriverPack WLAN)

Fair enough.  I've always said that newer does not equal better.
Please post your HWID list when you get a chance so I can get to work updating (or downgrading?) the pack. wink
Maybe I can fix it so we have both.

Go to forum: DriverPack WLAN

1,589 Reply by mr_smartepants

(43 replies, posted in DriverPack Mass Storage)

Transcribed entries from here posted by "clockman":

devcon hwids *cc_01* *raid*

ACPI\NVRAIDBUS\3&267A616A&0
    Name: NVIDIA nForce RAID Controller
    Hardware ID's:
        ACPI\NVRAIDBUS
        *NVRAIDBUS
PCI\VEN_10DE&DEV_03EC&SUBSYS_82341043&REV_A2\3&267A616A&0&30
    Name: Standard Dual Channel PCI IDE Controller
    Hardware ID's:
        PCI\VEN_10DE&DEV_03EC&SUBSYS_82341043&REV_A2
        PCI\VEN_10DE&DEV_03EC&SUBSYS_82341043
        PCI\VEN_10DE&DEV_03EC&CC_01018A
        PCI\VEN_10DE&DEV_03EC&CC_0101
    Compatible ID's:
        PCI\VEN_10DE&DEV_03EC&REV_A2
        PCI\VEN_10DE&DEV_03EC
        PCI\VEN_10DE&CC_01018A
        PCI\VEN_10DE&CC_0101
        PCI\VEN_10DE
        PCI\CC_01018A
        PCI\CC_0101
PCI\VEN_10DE&DEV_03F6&SUBSYS_82341043&REV_A2\3&267A616A&0&40
    Name: NVIDIA nForce Serial ATA Controller
    Hardware ID's:
        PCI\VEN_10DE&DEV_03F6&SUBSYS_82341043&REV_A2
        PCI\VEN_10DE&DEV_03F6&SUBSYS_82341043
        PCI\VEN_10DE&DEV_03F6&CC_010485
        PCI\VEN_10DE&DEV_03F6&CC_0104
    Compatible ID's:
        PCI\VEN_10DE&DEV_03F6&REV_A2
        PCI\VEN_10DE&DEV_03F6
        PCI\VEN_10DE&CC_010485
        PCI\VEN_10DE&CC_0104
        PCI\VEN_10DE
        PCI\CC_010485
        PCI\CC_0104
PCI\VEN_10DE&DEV_03F6&SUBSYS_82341043&REV_A2\3&267A616A&0&41
    Name: NVIDIA nForce Serial ATA Controller
    Hardware ID's:
        PCI\VEN_10DE&DEV_03F6&SUBSYS_82341043&REV_A2
        PCI\VEN_10DE&DEV_03F6&SUBSYS_82341043
        PCI\VEN_10DE&DEV_03F6&CC_010485
        PCI\VEN_10DE&DEV_03F6&CC_0104
    Compatible ID's:
        PCI\VEN_10DE&DEV_03F6&REV_A2
        PCI\VEN_10DE&DEV_03F6
        PCI\VEN_10DE&CC_010485
        PCI\VEN_10DE&CC_0104
        PCI\VEN_10DE
        PCI\CC_010485
        PCI\CC_0104
PCI\VEN_1191&DEV_8040&SUBSYS_80401191&REV_02\4&25700A26&0&4020
    Name: SCSI Controller
    Hardware ID's:
        PCI\VEN_1191&DEV_8040&SUBSYS_80401191&REV_02
        PCI\VEN_1191&DEV_8040&SUBSYS_80401191
        PCI\VEN_1191&DEV_8040&CC_010000
        PCI\VEN_1191&DEV_8040&CC_0100
    Compatible ID's:
        PCI\VEN_1191&DEV_8040&REV_02
        PCI\VEN_1191&DEV_8040
        PCI\VEN_1191&CC_010000
        PCI\VEN_1191&CC_0100
        PCI\VEN_1191
        PCI\CC_010000
        PCI\CC_0100
SCSI\ARRAY&VEN_NVIDIA&PROD_RAID_DISK&REV_\4&BA1E648&0&000
    Name: NVIDIA nForce RAID Device
    Hardware ID's:
        SCSI\ArrayNVIDIA__Raid_Disk___________
        SCSI\ArrayNVIDIA__Raid_Disk_______
        SCSI\ArrayNVIDIA__
        SCSI\NVIDIA__Raid_Disk________
        NVIDIA__Raid_Disk________
        ScsiArray
    Compatible ID's:
        SCSI\Array
        SCSI\RAW
SCSI\ARRAY&VEN_NVIDIA&PROD_RAID_DISK&REV_\4&BA1E648&0&110
    Name: NVIDIA nForce RAID Device
    Hardware ID's:
        SCSI\ArrayNVIDIA__Raid_Disk___________
        SCSI\ArrayNVIDIA__Raid_Disk_______
        SCSI\ArrayNVIDIA__
        SCSI\NVIDIA__Raid_Disk________
        NVIDIA__Raid_Disk________
        ScsiArray
    Compatible ID's:
        SCSI\Array
        SCSI\RAW

Windows XP Home SP3

Pack 1=4 instances of Unknown DIsk (There is no disk in this drive)
Pack 2=4 instances of Unknown DIsk (There is no disk in this drive)
Pack 3= success
Pack 4=4 instances of Unknown DIsk (There is no disk in this drive) then BSOD after F3 to quit.
Pack 5=4 instances of Unknown DIsk (There is no disk in this drive) then BSOD after F3 to quit.
Pack 6=4 instances of Unknown DIsk (There is no disk in this drive)
Pack 7=4 instances of Unknown DIsk (There is no disk in this drive)
Pack 8=4 instances of Unknown DIsk (There is no disk in this drive)
Pack 9=4 instances of Unknown DIsk (There is no disk in this drive) then BSOD after F3 to quit
Pack 10=Success
Pack 11=Success
Pack 12=4 instances of Unknown Disk (There is no disk in this drive)
Pack 13=4 instances of Unknown Disk (there is no disk in this drive)
Pack 14=4 instances of Unknown Disk (there is no disk in this drive)
Pack 15=4 instances of Unknown Disk (there is no disk in this drive)
Pack 16=4 instances of Unknown Disk (there is no disk in this drive) then BSOD after F3 to quit
Pack 17=4 instances of Unknown Disk (there is no disk in this drive) then BSOD after F3 to quit
Pack 18=4 instances of Unknown Disk (there is no disk in this drive)

All BSODs, as far as I remember, from setupdd.sys.

Each test cycle took 10 minutes to complete, including two reboots of the PC.

I'm using the first 2 of the 4 SATA connections as a striped raid array.
Device manager has the raid controller as ACPI\NVRAIDBUS\3&267A616A&0
and 2 NVIDIA nForce Serial ATA Controllers PCI\VEN_10DE&DEV_03F6&SUBSYS_82341043&REV_A2\3&&267A616A&0&40

The DVD is on the PATA interface.

Go to forum: DriverPack Mass Storage

1,590 Reply by mr_smartepants

(20 replies, posted in DriverPack Mass Storage)

For your test, did you have the drives as individuals or paired into a RAID?  If paired, the array was seen using test pack #3, 10 & 11 correct?

clockman wrote:

The other queries will be harder to sort out as the PC on which I run the tests is also my business machine so I can only go as far as the windows setup screen to see if partitions are visible.

That's fine.  We're only testing the .ini (txtmode) entries at this point.  Your test results will allow me to fine-tune the dpms for your HWIDs.
Unfortunately, we'll need others with different HWIDs to follow your example.

I'll transcribe your posts into the other testing thread for continuity.
THANK YOU! smile

Go to forum: DriverPack Mass Storage

1,591 Reply by mr_smartepants

(17 replies, posted in DriverPack WLAN)

Just copy/paste the contents of the logs to another post.  We'll need the DPs_BASE.log and the list of HWIDs (utility in my signature).
The broadcom drivers had a major upgrade from the past release.  We may need to roll them back.

Go to forum: DriverPack WLAN

1,592 Reply by mr_smartepants

(16 replies, posted in DriverPack Mass Storage)

In my opinion, DriverPack Chipset should ALWAYS be included.  This is because it loads the drivers for the motherboard components.  If the drivers for the motherboard components aren't recognized correctly, then the secondary components (sound, LAN, Mass Storage, etc) that connect through the board chipset will also not be recognized correctly.

Go to forum: DriverPack Mass Storage

1,593 Reply by mr_smartepants

(13 replies, posted in 3rd Party DriverPacks)

...and the circle of life continues! big_smile

Go to forum: 3rd Party DriverPacks

1,594 Reply by mr_smartepants

(16 replies, posted in DriverPack Mass Storage)

vipejc wrote:

1) Do motherboards that use AMD processors use the Intel SATA AHCI controller driver, or AMD SATA AHCI controller driver?

2) Doesn't your MassStorage DriverPack for XP already include the Intel SATA AHCI Controller Driver, Matrix Storage Manager, and Rapid Storage Technology; and therefore I shouldn't use nLite and only use your DriverPacks BASE to slipstream the drivers into my XP install disc?

3) Is it possible to download the "ataport.sys" driver and its associated drivers for Vista, and integrate them into the XP install disc as a generic SATA driver, or could this cause an instability?

1) Possibly.  It depends on the preference of the board manufacturer and what "chip-set" they choose.  Most modern boards have the SATA controller built into the "South Bridge" chip or have discrete chips.  So if your main "chip-set" is from Intel, AMD or Nvidia then chances are high that the SATA controller is also from that same OEM.  Other controllers are available (Jmicron, Marvell, HighPoint, etc.)

2) Correct.  The best course of action is to include ZERO drivers with nlite and integrate DriverPacks in your source using DriverPacks BASE.

3) While possible, it's certainly NOT recommended.  Using system files from other OS types is definitely asking for trouble (and possibly illegal).

Go to forum: DriverPack Mass Storage

1,595 Reply by mr_smartepants

(20 replies, posted in DriverPack Mass Storage)

cdob wrote:

Pack 3= success

This uses nvatabus.sys and nvraid.sys.
Which HardwareIds do you get running nvatabus.sys?
Do you get HardwareID "SCSI\ArrayNVIDIA__Raid_Disk___________"  still ?

Actually test pack #3 only uses nvatabus.sys in the .ini.  The nvraid.sys file is ignored during the txtmode setup.

He's doing well.  He's providing all the answers that I've asked.  We can refine the questions once the test sequence is completed by going back to specific test packs and asking specific questions.

Go to forum: DriverPack Mass Storage

1,596 Reply by mr_smartepants

(16 replies, posted in DriverPack Mass Storage)

vipejc wrote:

1) Which of the three drivers will I need?
2) Do the MassStorage DriverPacks for Windows 2000, XP and 2003 include all SATA drivers?
3) If so, would it be better to download the most recent MassStorage DriverPack for XP to achieve my goal?

1) All
2) Yes (but if you find one that's missing, we'll add it)
3) Yes. wink

Don't use nlite to integrate drivers.  That's a bad idea.  Use our DriverPacks BASE instead.  It's so much nicer! smile

Go to forum: DriverPack Mass Storage

1,597 Reply by mr_smartepants

(20 replies, posted in DriverPack Mass Storage)

OK perfect! smile
Keep going, you're providing valuable info.  Honestly!

Go to forum: DriverPack Mass Storage

1,598 Reply by mr_smartepants

(9 replies, posted in DriverPack Mass Storage)

Implemented in dpms 11.01

Go to forum: DriverPack Mass Storage

1,599 Reply by mr_smartepants

(6 replies, posted in DriverPack Sound)

Upload should be done in about 15 min.  Links will be in the testing team forums.

Go to forum: DriverPack Sound

1,600 Reply by mr_smartepants

(7 replies, posted in DriverPack Sound)

Implemented in DriverPack Sound B 11.01r1

I17\ IDT High Definition Audio CODEC (HP) DriverVer=09/08/2010,5.10.6300.0

Go to forum: DriverPack Sound