As a quick experiment, I took an XP Pro OEM SP3 image and only integrated the MS v11.09 driver. I did get one of those DSPdsblr popups during the install, but seen elsewhere on here that it's okay. And of course I got the 7B since there's not much Intel stuff changed since 11.08. I'll experiment with older drivers packs. It helps burning to a CD-RW. smile

OverFlow wrote:

Reporting the HWIDs of a failed driver install is a HUGE help towards making the DriverPacks work on all hardware. big_smile
Even better if you can additionally report to us you know of a previous DriverPacks version that worked.
Best case is if you can also point us to a new / updated driver that you know works. (tested known good)

Okay, I found an affected system. An HP Media Center PC, HP Pavilion m7650n. I can boot into mini XP and run CPU-Z.

Here's a link to the CPU-Z report: http://textuploader.com/?p=6&id=9JkMU

No sure if there's anything useful in that.

EDIT: v11.07 has the issue too.

OverFlow wrote:

Reporting the HWIDs of a failed driver install is a HUGE help towards making the DriverPacks work on all hardware. big_smile
Even better if you can additionally report to us you know of a previous DriverPacks version that worked.
Best case is if you can also point us to a new / updated driver that you know works. (tested known good)

We are a small team with very limited hardware to test on...
We can't fix it if we don't know what's broke and we can only test a VERY small portion of the drivers in the packs.
We can't tell if our changes fix an issue if you don't reply and tell us if our changes worked.
YOU are a very important member of our team to big_smile.

Okay, if I run across another system that 7Bs, I'll try to grab the IDs. What's the easiest, fastest, and/or best method to grab the IDs for ya? It's a little inconvenient to keep testing discs on a system when it's unknown if it's going to work. As I need to get these things outa here as quick as possible. My old discs just worked fine on a hundred or more systems. Maybe 3 or so had an issue with not seeing the HD in text mode.

I suppose it only wastes about 30-60 minutes if it fails and I end up having to use a previous disc. Because I'm pretty sure it goes all the way through the GUI setup, then BSODs on the reboot. The test system I grabbed yesterday actually worked all the way through. hmm So nothing on hand to test with right now. I may just make a new disc using only an old mass storage pack. As the most important thing of the discs is having all the windows updates integrated. Thanks for the work you and your team provide for us. It's much appreciated.

I've seen the 7B issue too on a couple different computers. I work in a computer shop, and I've recently made a new updated August disc. So far XP Pro and my MCE disc exhibit the same 7B failure. It seems to happen on a machine with Intel AHCI chips, using IDE or AHCI mode. Tried it on a Dell Dimension 4700 with just normal Intel SATA controllers, and it installs fine. I don't have the affected computers here anymore. I just ended up using a previous disc I made from December. I could experiment with older releases to see when the bug was introduced, but then I would have to keep burning discs, as the installs always work fine using VMWare.

I have a few spare junk computers in the back that I can experiment on. Hopefully one of them have the affected SATA chipset, then I can grab some IDs or whatever.

But what would have changed in the Mass Storage driver pack if an earlier version used to work? I need these discs to work on all chipsets.

Thanks.

I don't use that method. And I don't seem to have any issues. I had to do a lot of trial and errors.

I start with a clean SP3 image.
Integrate custom stuff with RyanVM and modify some files manually for more customization .
Modify with nLite and integrate an updated AIO update pack so updates are current.
Then run DPsBASE to integrate all available drivers.
Then I create an ISO.

This process for me has the most success.

31

(67 replies, posted in Vista / 7 DriverPack LAN)

mr_smartepants wrote:

Got it fixed...testing now...

Alright, thanks. BTW, I know this is not the correct section, I couldn't find one for the touchpad driver, but the "DP_Touchpad_Mouse_wnt6-x86_1003.7z" driver seems to crash my installs all the time. So I just don't use it. Not sure if it's just me, as the driver pack is very old, I figured someone would have mentioned it last year. No biggie though.

32

(67 replies, posted in Vista / 7 DriverPack LAN)

mr_smartepants wrote:

OK, thanks for reporting.  I'll get it fixed.  The problem is a mismatch in version numbers.  That's the ONE Intel folder I didn't update. sad
Of course the one time I don't test in Vista...

Cool, thanks for the fast response. I was able to remove 6 files from the Intel\5 directory to get it to work, if this helps any.
Ifcoemp.cat
ifcoemp.inf
Ifcoepr.cat
ifcoepr.inf
Ifcoevb.cat
ifcoevb.inf

33

(67 replies, posted in Vista / 7 DriverPack LAN)

Alright, it's definitely the DP_LAN_wnt6-x86_1103 driver package.

I took a fresh Vista (AIO) SP0 image and only integrated the above driver using Vista-Tool v1.0 and created an ISO with the same utility and I get the same error message.
Maybe if I delete the Intel/5 directory I'll have better success.

EDIT: Deleting "x86\L\Intel\5" from this driver pack fixed the bug. Now I can successfully integrate this driver into my disc again.

34

(67 replies, posted in Vista / 7 DriverPack LAN)

I integrated the drivers again into a fresh Vista SP0 (AIO) image and I get the same error. I am trying to integrate all the drivers provided in the download section for Vista x86.

The message is :
------------
Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
blah blah etc etc...

File: ifp60x32.sys
Status: 0xc0000098
Info: Windows failed to load because a required file is missing, or corrupt.
------------

So I wonder if maybe another driver is at fault, like a MassStorage driver or something that's not letting it access the OS during the install. I'm trying to install this OS in a virtual machine using VMware Player. It also fails if I burn to CD and try on a real computer.

I've used this same process when I had downloaded drivers from November 2010 and integrated drivers using Vista-Tool v1.0.

35

(67 replies, posted in Vista / 7 DriverPack LAN)

Not sure if it's just me or not, but I'm having a problem with the new 11.03 drivers.
I'm getting a IFP60X32.sys may be corrupt message from the Intel/5 directory.
But I am integrating these into an already updated Vista SP1 image I made from November.
I will have to try from a fresh image to see if I have better success.

36

(36 replies, posted in Vista-Tool)

The link for v2.0 beta 3 does not work. Does anyone have a link for this file?
I'm a little late to the game here, but I'm in the process of creating an updated Vista disc.
I've recently finished my nLite disc for XP, all updated and perfectly customized, now I'm moving to Vista, then after this I'll look into 7.

EDIT: I suppose I'll just have to use v1.0. sad