Search options (Page 1 of 2)

All true.  And in doing all of my research with this the Forum, I did read up on Wim Leers.  It's like preparing for a job interview, you should always research the history of the company.  I think he and think a lot alike and are very interested in challenges.  This is called Motivation and why I enjoy being in the IT industry. 

nLite for me was a learning experience and honestly I no longer use it.  But I had a creation from 2009 that worked very well and I didn't want to re-create that from scratch.  Sometimes perfection is at its highest the 1st time.

Overflow, when I get my current rig up and running with XP, I'll create a new partition for Windows 7 x64 as a dual boot.  I also have another rig, Ivy Bridge Z77 Chipset, that will be getting Windows 8. Between these two I'll create a partition that I can work from as a platform to do anything I can help you with here.  I'll let you when that's ready.

Thank you.

OverFlow thank you for your voice.  It's nice to see others join in.  DriverPacks is always the last thing I do prior to creating and ISO. Also the source of DriverPacks is maintained in the OEM folder so replicating what I did 3 years ago was simple enough and I managed to reverse the process to give me a clean nLite source again. I new that I would not be adding hotfixes, or anything else, other than DriverPacks back to nLite. That would have bricked my original creation.  It just means more updates when I get into the OS.

This part is not true.  When you add TEXTMODE single driver through nLite, either before or after DriverPacks, and trust me I've tried both ways, the two sources conflict with each other because they both write to many of the same files. Not only that nLite adds iaStor.Sy_ and this folder NLDRV with the RST package in a subdirectory in the I386 folder.  They are referenced, I believe, in the txtsetup and dosnet, and a few other files, which DriverPacks seems to do as well.  So they appear to be receiving direction from two different sources and I think this is what causes the conflict.  When I tried using TEXTMODE Single Driver through nLite and then adding DriverPacks, I did not include MassStorage pack because I was certain this wouldn't work. But that being said, just including the Chipset, LAN, WLAN, and SoundB at the end WOULD not work.  It creates a BSOD even before Windows setup load files. The two broke each other.

I use to be very proficient with nLite and learned things through a lot of collaboration and have enjoyed the company of nLite along with the DriverPacks.  With nLite, if you do things in a correct and very specific order, you can rein in it's power. However, hardware has changed from those days and obviously XP 32 bit is becoming something of the past, and Intel has pretty much decided to write it out anyway, though MS will support is until 2014.

I've coaster-ed about 20 discs in the last few days in learning how DriverPacks really works with the help of damnation and Techdud. This was not a bad thing.  Ultimately the challenge was met, when I was told on other forums it was impossible.  That's why I joined this forum to learn and I also received an understanding of HWIDs and the conflicts they can cause.

Last edit for the night guys.  You, are Rockstars.  I couldn't remember where my key was so I decided to run a gambit and ran the modified storage MassStorage driver pack with my nLite version since I knew half of the battle was won as soon as the Windows install accepted the RAID driver.  I wasn't sure what was going to happen after the install whether or not I would be able to boot into Windows without that dreaded BSOD.  Great news to report.  Not only did my install install, but it booted right into Windows for the 1st time.  It was sweet to hear my sound card go active with the MS Chime.  And just to complete this story, I also ran the other driver packs needed, such as Lan, WLAN, SoundB, and Chipset with great success.  It was nice to look into Device Manager and not see so many exclamation marks.

I used the modified file MassStorage package provided, but removed the iaHci files and references.  I think this is what truly worked best.  I also believe this was close to the 1st question I had when I joined the site as to whether I could strip the pack completely down to only the new Intel 32bit RAID driver, which proved to be right.

Does this make me a DriverPack beta tester?  :-)  jk

Anyhow, before I go into the OS tomorrow and start installing the vendor drivers for my MB and Video card, I wanted to ask if there was anything else that you could think of to test, more for you guys than me, at this point.  I mean we had to completely destroy the MassStorage pack to get this to work.  Are you curious to know that if the right changes are made to the pack with the new information that we could get it to work?  But then it may not be much good to the general public since what we've done was support a single platform versus a Universal solution. 

I'll leave that up to you guys.  I'll check back into tomorrow morning for any response.

Again, thank you guys so much.  I was told many things weren't possible and yet, they all were, with the right attitude and determination, if for nothing more than to prove the naysayers wrong.  I also learned much from the multiple boards I signed up with in the last couple of weeks.

Having this one little modified pack may help others out who are in the same situation with a setup that is very close to mine with the X79 Sandy Bridge, wanting to use XP 32bit.  I thought when I left XP last year it was for good.  But with the type of Audio I process, the programs I  use are not compatible with Windows 7 x64 as they were betas and no longer written.  There have been no suitable replacements to date. 

Ciao - Larry

OK, I'll run this again.  I'll let you know shortly....

Whoops, I was editing when you replied...  If you can review and let me know what you think...

This was much faster since it was clean of nLite, but again it failed, couldn't find iaStorA, press any key to reboot.

Since I started working on this project a few weeks ago I have created more accounts than I can keep up with.  But here are the files you asked for plus the 32 bit Intel RST package I was provided that work in Single Driver mode as long as I select RAID only.

http://www.mediafire.com/?ya8ax823oc8y6 … 1e6iyutqu6

Again, thank you.

There is an iaStorA in the folder, I did not rename it.  I went ahead and deleted the information and tried again, but returned the same results as before, iaStorA could not be found.

As a side note, and just for giggles, I ran the XP disc I did using nLite in TEXTMODE single driver to see what the load preference was at the Windows Setup Screen while it was loading files.  I noticed that the C600 series loaded before any of the other Microsoft I386 drivers did.  When I monitored the DriverPack setup during Windows Setup loading files, it didn't show up at the beginning and was too fast for me to tell where and when it would have showed up.

I'm just trying to be helpful with my observation.

I'm beginning to think having the best of both worlds may be proving impossible.  I rarely give up, but this challenge is far greater and seems more complicated than it should be.

If only the Driver Base would allow the selection of only a Single Driver through its Textmode option this might be solved.  But I'm guessing that's not possible.

Any other worldly thoughts?

Just to be clear, I'm basically looking for WLAN, LAN, SOUNDB, and CHIPSET packs if I can incorporate the TEXTMODE Single Driver setup. The rest of the Mass Storage drivers I would be able to install from within the OS from the Vendor site.

Alright.  It will be about 20 minutes before I know since I have to integrate, create the ISO and try the setup.  Thanks.  I'll be back shortly...

I'll give it a try.  Will it matter that iaStorA differs from the RST I have with iaStor?

So here's what I'm going to try, but I don't think it will do much for me since I don't know these pack setups as well as you guys, the pros who do this.

I'm modifying the MassStorage INI to this:

[DriverPack]
platform="wnt5_x86-32"
name="MassStorage"
classes="hdc,SCSIAdapter"
rootdir="D\M"
driverCount=174
; OPTIONAL
; version 12.03
decompSize    = 52522718                 
compSize      =  8113177             

[I4]
; 3.0.1.7016
ms_count=1
ms_1_deviceName="Intel(R) C600 Series Chipset SATA RAID RST Controller"
ms_1_tag="iaStor"
ms_1_sysFile="iaStor.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2826&CC_0104,PCI\VEN_8086&DEV_1D02&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="wxp,w2k"

Looking at the hwids line, should this be modified to be what the hwids are listed as earlier in this thread?  If so, now how should this line look?

I will replace the contents of the I4 folder with the 32bit Intel RST RAID driver I have, that works in single driver mode to include only:  iaStor.cat, iaStor.inf, iaStor.sys, and txtsetup.oem - Would this seem to be correct? Are there any modifications to any of these files that should be made?  I'm thinking the txtsetup.oem should be modified only for the RAID driver I'm using.  I can rem the other lines. Sound alright?

Again, thank you guys.  This is simply a one off and against the norm I know.