Integrating Massive Gigabyte Update with XP

[HoppaLong]

Like a lot of apps, you see them listed while you're Googling, they look

interesting but you never stop to investigate. I'm a newbie to nLite,

but maybe it can do a job I can't do myself.

For months I was having a problem with several new eSATA drives and

XP Pro_SP3. Xp could not write to these drives for more than a few

seconds without a "delayed write failed." Microsoft published several kb

articles about the problem. Their solutions didn't work. Gigabyte added

a large mobo update to their site which finally resolved all the problems

I was having. It includes files for the chipset, vga, and sata raid.

The package is a confusing mix of files and folders. Name a type of file,

it's in this package! Cabs, dlls, several executables, etc.

I'm a big fan of BartPE. If I could, I would extract the critical files from

this package and add them as drivers or a plugin. Most Bart users copy

all the files from the XP install CD into a folder so PEbuilder can quickly

create the ISO needed to burn the Bart CD.

Selecting the correct files from this massive package is not possible

for ordinary mortals like me! Is nLite smart enough to integrate this

package into the XP files, without having to indivdually select each file?

If I could get this update from Gigabyte onto a Bart CD I would finally

be able to use my eSATA drives from outside of the "real" Windows

environment. There is no better way to make backups that are 100%

reliable.

I hope I'm not barking up the wrong tree.

Thanks nLite folks!

[strel]

If there's .inf files try using Roufneck's DrvComp. Then try using the output with nlite.

[g-force]

If you tell nLite to integrate "whole Folder" @ "Driver Integration",

nlite looks up for INF-Files. If nLite get one, it`ll integrate the whole folder

which is beside this INF. If YOU are smart enogh, you point nLite to the folder

that only contains the real Driver-Files (maybe it is namesd like this).

Be aware of x86 and x64, older and newer OS when you choose the folder.

[cdob]

For months I was having a problem with several new eSATA drives and XP Pro_SP3. Xp could not write to these drives for more than a few seconds without a "delayed write failed."

This maybe hardware too. Try a shorter cable too.

Gigabyte added a large mobo update to their site which finally resolved all the problems

I was having. It includes files for the chipset, vga, and sata raid.

Which mobo do you use? Which mobo update do you use?

nLite dosn't support PEBuilder requirements.

[HoppaLong]

I'm not a newbie at all when it comes to hardware problems.

I've been building these boxes for decades. I'm a partner is a

small business. This problem happened with a desktop in

my home office. We have a dozen desktops in our offices.

I tested these eSATA drives with the best quality 3ft. cables on

six of the twelve desktops. The same problem reared its ugly

head with two of the six.

You may be familiar with CNET's resident computer genius,

Bob Proffitt. I emailed him about this problem. He said that

several of the desktops in his offices that ran XP had the same

"delayed write failed" with eSATA drives. He could never come

up with a workable solution! Believe me, I was feeling really bad

about this problem until Mr. Proffitt let me know I wasn't alone.

Yes, g-force and strel, there certainly are inf files! If the package

contained inf's and a bunch of drivers I wouldn't need an app like

nLite. The drivers are mixed in with hundreds of other files, several

folders deep. There is a folder named "drivers" but it's not the only

folder that contains drivers, unfortunately. Gigabyte just dumped

a bunch of files and folders into a package without explaining anything.

Each folder has one or more setup files. Enough to make you a little

crazy!

If I can use nLite's driver integration or DrvComp to create an ISO

with all the XP files integrated with the Gigabyte drivers that should

do the job. DrvComp may be just what I need.

I felt lucky that I was able to get these drives to work with my home

desktop. Until I came across nLite, I didn't think there was any

chance of getting this update onto a Bart CD. I'll definitely give it

a try.

Thanks guys!

[g-force]

Maybe DoubleDriver does the job.

You install every driver one time manually,

then let DoubleDriver extract the drivers out of your running system.

Take a look at these new folders that DoubleDriver created.

Every Driver should be seperated in it`s own folder,

all unneeded files should been gone.

Edited September 13, 2009 by g-force