Nakatomi2010

I'm using 6.58 on an MSI Neo4 Platinum/SLi board... nForce 4 chipset...

Well love, when you're on a college campus such as I am you'll find that a certain number of tasks need to be done to mesh your computer with the network. Best to get them out of the way and not even know about them, you know? I have things setup so that the default user (me) on auto-login is also conveniently my matching username and password on the network, which means on first login I can run a script that authenticates with the network, maps network drives, changes local users so their home directories are happily living on network drive H:\, syncs network time, loads Firefox's installer from a network source, loads Sophos anti-virus from a network source, loads Eudora from a network source, and etc... Very, very handy. What happens if your network fails?

Not to mention 64Bit users who have a 64bit machine for guinea pigging with... I've thought about making a 64bit driverpack, decided against it until I start seeing more 64-bit machines for repairs....

My policy has always been, and always will be, you don't really have a choice, if it's going to become the industry standard, switch, otherwise you'll start running into issues later on... It's not worth staying with old software...

If you're running XP run regedit and do a search for "Home Edition" or "Professional" depending on your version and see wat comes up, tell someone to look in their version see if they have the same key, confirm it on about 5 machines, then assume it... HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\x86_Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries_6595b64144ccf1df_6.0.0.0_x-ww_ff9986d7\Codebases\OS Try that....

@5eraph: It works sure, but does it work integrated into the setup process? This is where a good chunk of the issue is coming from, I got it working in the SETUP process, so that it doesn't blue screen when initiating setup, or cause the problem I described earlier where once Windows XP was installed I got constant "Found new hardwares" on every boot up....

My post wasn't meant to be funny, it's quite true... Every now and then people just wake up one day and go "Whoa, why don't I do this" anf poof, a new method is born... Afterall, we're all trying to make this as quick and painless as possible.... I was just trying to help by suggesting you give him more information than he might need, primarily because circumstances aurrounding a problem can reveal a larger solution.

Yeah... Also, as a side note, the switchless installer can't be done using the same method I use for the .Net 1, which is putting it into the svcpack.inf file..... Still not 100% sure on the 64-bit one, I went to try but it didn't install the OS right.... Go figure...

So it would probably be wise for me to integrate both .NET 1/1.1 and 2.0 onto my DVD as I use it to install Windows on a variety of Customer units.....?

Can I put your file in the svcpack directory and have it called through the svcpack.inf, or should I make this one have a new entry in WPI? (I've been putting the .NET 1 in the svcpack directory....) I'll tell you if you're 64-bit version works in a few moments as I'm now integrating these into my DVD....

Figurees... The day I FINALLY get my Multiboot DVD in it's sweet spot Microsoft releases this thing, and now I have to go in and make a small change... Oh weell, I least I heelped Bashrat solvee the nForcee Mass Storagee problem... And yes the keyboard I'm using is adding extra e's heree aree theere... Sorry.... *sigh*

If you plan on using those newer drivers from the nVidia site, may I request to test them first please? Since we've kinda discovered how to make the nForce work, any chance of a small fix for now? Or would you rather test the newer drivers?

Also depends on whatt you're using it for.... I had to nLite one of mine to a very nominal size and pretty much had no room for adding more drivers, a couple of releases ago... I abanded making an Unattended XP CD with all the drivers on it awhile back, I now only making multiboot DVDs, prmiarily because you can fit so much more onto them.... For example, my DVD is labeled as "Windows XP Solutions DVD" and it is labeled this because it has XP Home Edition (VLM, OEM, Retail), Professional (OEM, VLM, Retail), Media Center Edition 2005, and x64 Edition... 8 different versions of Windows XP, and for each version there are Compelte Unattened, Semi unattended, and attended, so 24 boot sectors... Not to mention I've got Ultimate Boot CD For Windows, a PE from a friend of mine, ERD Commander 2005, Ghost and the Linux NT Password Changer utility... This DVD has ALL the driver packs integrated into it, and I've also got a bunch of software being installed as well... And have the Autopatcher utility on the DVD to allow me to update the Corporate copies of XP without having to validate the key (For some customer units who got their computer from a friends, a disreputable sales store, etc etc...) All in all, from a technician's stand point, there's not much I can't do when it comes to XP.....

I run WPI.cmd and BTS_DPs_finish.cmd both through GUIrunonce...

I imagine both are relavent as minor changes always occur because of brilliant new methods of coding, which occasionally end up making somethings go a bit wonky....

No, I tried that already and it didn't work (One of the first things I tried since it wasn't there) Or do you mean use the newer one?... I'm using the original Mass storage pack right now with those three older files in the i386 directory... I'll try using an updated ncchflt.sys on the next burn.... Also remember, I'm using Method 2, on a multiboot DVD....

/whimpers.... You can try that one, but if it doesn't work I say we just stick with this one, since you know... It works.... For me at least.......

W710NMS Version 3.0 I say let the Intel people discover their OWN solution... I found this one, it's mine...

ATA/ATAPI Devices --NVIDIA nForce 4 ADMA Controller --NVIDIA nForce 4 ADMA Controller --NVIDIA nForce 4 Parallel ATA Controller SCSI and RAID Controllers --NVIDIA nForce RAID Class Controller And yes the ADMA is listed twice... And that's correct, the only directory left in the D/M/N/ directory is the 123 directory... The HWIDs are attached in the .txt Also, as a small side note, the onboard (Yes, integrated into the mainboard) SB Live is showing up the drivers aren't installed.... Not sure if they're different than the ones you have or not, but it's Code 28 on my end... Also, that Video card is the one that spits out the nv4_mini.sys error I reported... hwids.txt

http://www.msicomputer.com/product/p_spec....um/SLI&class=mb MSI Neo4 Platinum/SLI nForce 4 SLI Chipset... Tell mehow to grab the HWIDs and I'll grab them for you....

I asked you to be a little more specific.... I fixed it though.... Here's how... I deleted all the directories except for the '123' directory inside the nVidia Mass Storaeg directory, then I replaced the NVatabus.sys and nvraid.sys drivers with the ones I used on my CD (Which are the same ones from the 123 directory) AND I added a single other file which is not referenced in the txtsetup.sif but IS REQIRED apparently, it's the NVCCHFLT.SYS file... It needed to be in the i386 directory as well... BAM it works like a charm.... Now I just need to fix the video problem.... Sorry bashrat, but I had to modify your driver pack .7z to fix it... BUT it's fixed, so you'll need to modify your Multiboot tool to copy the NVCCHFLT.SYS file to the temp as well as the other tools to copy that file into the i386... Again, it's not referenced, but IS required... AND I also tried to just copy that one file over while the 4a directories and such were still there, didn't work... Gave me the same problem as before... If my explanation isn't very good, just ask I'll try to clear it up... Edit: I remembered this solution because that same file was my headache when I originally did it....

I suppose the biggest frustrating note for mw is that the machine I'd been using as a guinea pig is gone, we sold it... And now I'm having to use this other machine... Which in means that although my old CD worked, it did not work on this particular machine (In that it was designed for a different one) So you're saying to take the ones I used on my CD and overwrite yours? I've deleted all but the 123 directory from the nVidia driverpack set... In theory that might do something, or nothing.... I'm sure it's not as easy as I made it sound... I don't believe this is a problem with the text setup environment, I believe this is more of a problem of when Windows loads it's own internal drivers that it's going to be using more permanently.... Edit: Does order matter in the txtsetup.sif? Because I'm comparing mine against yours and your HWID's are reversed... Mine star with: PCI\VEN_10DE&DEV_008E = "nvatabus" while yours is: PCI\VEN_10DE&DEV_0055 = "nvatabus" Also, GenNvRaidDisk = "nvraid" *_NVRAIDBUS = "nvraid" *NVRAIDBUS = "nvraid" Comes AFTER the nvatabus section in mine... If order makes no difference then nevermind... I'm just actively trying to solve this problem... It's been a thorn in my side and I want to see it resolved... 2nd Edit: Well, the order of it didn't make a difference.... hmmm....

No... You need 64-bit drivers, but 32 bit software will work, but not ALL 32-bit software....

I can only try it while I'm at work (10am to 6pm EST)... You can send it on the weekend but I wont be able to try it until Monday... If you tell me what to remove from the txtsetup.sif I can make the modifications... In theory it should be as simple as telling it to the older versions... Kinda like deleting the old ones.. Unless I'm thinking too simple...

5.10.2600.0518 2/11/2005 If you have an FTP I can zip what I have and send it your way... Edit: http://www.msfn.org/board/index.php?showtopic=49505&hl= This should be the thread that allowed me to get the nVidia drivers working... Waaaay back.... I never tried to update the drivers....