OK, I did a clean rebuild from scratch and tested it on MS Virtual PC 2007 and it seems to be OK.
Too bad they do not have a way to configure specific hardware in Virtual PC.

OK, it installs with no errors, but I do notice that it take about 5 minutes on KTD and finisher before the first bootup.
I don't ever remember that screen taking that long before.
Is that within the range of 'normal'?

I notice that build 7094 is about 400KB smaller than 7091.
Is that correct?

HOLY CRAP Jaak!
I just noticed the part about Quick Stream Cache
That likely explains A LOT of the problems that I started having with the Bâshrat the Sneaky driverpacks for the last several months.

I'm going to start over from scratch and enable Quick Stream Cache and see if some of my problems don't mysteriously go away.

SWEET!
I'll try it again.
Thanks for hanging with me on this Jaak.

Yes, I always do it with QSC disabled by default since the installer says that is reccomended for method 2.

Right after text mode, I get a mesage:

The file percsas.sys cannot be found
Press any key to continue

when I hit any key, I get told that setup has failed

Got it!

I'll build this and let you know.
Thanks again!

Sure, no problem.
If you can use any of my info for the next update, let me know and I'll test it out on the machine to see if it works OK.
Just remember that now I have a card that is flashed to the latest BIOS provided by SiL for the 3112 and NOT the original Adaptec 1205SA BIOS.
I don't know if that makes a difference or not but if anyone out there has an Adaptec 1205SA, they probably should flash it to BIOS 4.2.83 anyways, using the DOS method I described above.
That BIOS, and the BIOS update utility for DOS, are available here: http://www.siliconimage.com/support/sup … sid=0&

OK, this is what I found in my OEM file on that disk.
I'll assume that these are all the driverpack drivers I added, because I didn't add any other drivers than what is offered here.

DPC7041.7z - Chipset
DPL704.7z - LAN
DPM704.7z - Mass Storage
DPW704.7z - WiFi

I'm surprised I got anywhere with it either and I only tried it out of desperation and the sheer coincidence that I put that CD up with my old windows 2000 disks.
I found that CD and said what the h*ll and it actually installed!
That was only AFTER the BIOS re-flash.

The CD is dated May 15th, 2007. That would be the day I made it and it would have been whatever the most recent Mass Storage driver build existed on that date.
I'll pop the CD in my machine and see if I can get a clue as to what the exact driver build was.
Hang on...

You might be right!
What's the procedure for that after I have unpacked and edited them?
Do I just select BOTH files and then tell 7z to "add them to archive"?

I finally got this thing to work by re-flashing to the newest BIOS provided by SiL for the 3112 by using a bootable DOS floppy (simply made in XP) and then I added the SiL 3112 flash utility and .bin file to the floppy, booting into DOS from the floppy and the running the flash utility.
I couldn't get it to flash by using the other two methods from within Windows XP.
I then grabbed an old driverpack CD I made back on May 15th and got the thing to finally install windows and then updated the driver and restarted.
Finally it worked and now I have an Adaptec 1205SA card that I can eventually use in Vista if I ever decide to go that way.

I re-did everything and I still keep getting that same error.

Would that explain why I get this error message when I try to integrate the driver pack:

"No settings file found for DriverPack MassStorage: the file "E:\Driverpacks\tmp\DPMtmp\Driverpack_MassStorage_wnt5_x86-32.ini" could not be found!"

OK, thank you for your help!

I downloaded the file you linked to, unpacked it with 7z, then I downloaded the driverpack for mass storage, unpacked that with 7z.
I then replaced the files from the link, to the unpacked mass storage 3112 drivers located at D\M\S\4
, then I added the S4 text (between S-3 and S-4 - the S4 part was missing) to the file "DriverPack_MassStorage_wnt5_x86-32.ini"

I'll give it a try!
Thanks.

If I have any problems I'll check back, or if I got anything wrong, please let me know.
If this works, I'll let you know too! smile

It will boot, find the hard drive and even let me partition, format and install the first part of Windows XP, but blue screens immediately (Stop 0x0000007B) after the first restart at the end of the textmode portion of the XP install.

Since it is a SiL 3112 based card, the driver pack installs the SiL drivers, and in the past that was good enough, but since SiL has released a later BIOS for the 3112 (that I cannot flash onto the 1205SA - If you know how to do that to the 1205SA card please let me know) and an associated new driver for that new BIOS, it no-longer works at all.
Somehow the 1205SA is getting incorrectly detected as a generic SiL 3112, and installing the drivers for the later BIOS version of the SiL3112.
Is there a work-around for this until that problem can be fixed in a later mass storage driver pack?

Adaptec 1205SA site: http://www.adaptec.com/en-US/support/sa … SH-1205SA/
1205SA Drivers: http://www.adaptec.com/en-US/speed/sata … 41_exe.htm

SiL 3112 BIOS and driver info: http://www.siliconimage.com/support/sup … sid=4&

Thank you.

New working link for modem drivers
http://3rdpartydriverpacks.thesneaky.co … 2_70815.7z

Hey Helmi, could you put a working link at the beginning of this thread to this thread http://forum.driverpacks.net/viewtopic.php?id=587

Thanks!

I got the same thing.
I also can't get to any of the driver packs either as well as a new Base.

IE7 and Fx both just load a blank page.

Maybe they are doing maintenance on the site?

Drivers for Juli@ are located here:
Unified Driver .974 (all versions of Windows inc 64): http://85.25.144.200/download/ESI/Juli@ … v0_974.zip
Driver and Controll Panel 1.21 : http://85.25.144.200/download/ESI/Juli@/Juli@-v1_21.zip

Drivers for Maya 44 are located here:
http://download.esi-audio.com/?p=14&g=1&l=en

Thanks for the tip, I'll take another look.

I re-did the integration and now I'm waiting for MS VM to install and I'll see if this gets fixed.
Are there any common reasons why a Winnt.sif file would ignore some of the answer file info?

Thanks Bashrat!

I was told that the Bâshrat the Sneaky Driverpack integrator overwrites the existing WINNT.SIF file in the i386 folder.
Is this true?

I noticed that all of my parameters that were in my WINNT.SIF are now not there, but some of that information now seems to have been moved over to my UNATTEND.TXT file also in the i386 folder. Specifically stuff like my key code info and timezone info but mt networking parameters were reverted back to the XP default settings.

Can I go back into either the WINNT.SIF and UNATTEND.TXT files and simply add back in my settings or setup info?
If so, which file should I edit?
Will I need to edit both of them?

Thanks!

Thank you Debugger. smile
Please post what you discover.
Is there an easy way for me to include these drivers in my OEMtextsetup and still keep the Bashrat Mass-storage drivers?

That's possible in that I heard that some things may have changed since the board was introduced.
The board that we are having a problem with is the Intel DP965LT.

I did find some info on doing unattended installs.
http://www.intel.com/support/chipsets/i … 020825.htm

My previous post on this just got eaten.

OK, I'll try again.

There is a problem with the mass storage driver pack and how retail "boxed" Intel boards see the text install drivers while using method 2.

You can take a look here and see. Item number two is A LOT more than just the chipset inf drivers like it used to be.
To get to the drivers you have to do a command line extraction with the (-a-a) flags
http://downloadfinder.intel.com/scripts … %20Systems

Is there a way to install them in silent mode (along with the rest of my Bashrat mass-storage drivers) without ruining the rest of the mass storage drivers and if so, can anyone point me to some directions?
This is a big problem if you are assembling a band new computer or just bought a new hard drive (and are using the on-board SATA) and don't have an existing Windows XP installation to fall back on.

Thanks!