nLite creating corrupt registry entry

[boyhowdy]

During 'Driver Integeration' when nlite is building the installation it throws an error reading: "Access to the registry key 'HKEY_LOCAL_MACHINE\NliteTempReg\ControlSet001\Services\viamraid\Parameters\PnpInterface' is denied. In regedit I cannot open the viamraid key (or anything below it, obviously) - says it is corrupted. My normal user account has admin rights on this machine, but I've logged in to the local administrator account and tried it as well. The driver it's failing on is the SATA controller driver for the VIA 8237 chipset provided by mainboard manufacturer (board: MSI PT880 Neo-FSR) and is the whole reason I'm using nlite in the first place. I have tried downloading the driver again from different mirrors and in different packages in case it is a problem with the file itself, but it appears that since the reg key is corrupted it doesn't matter what file I use. It's worth mentioning that I successfully slipstreamed this driver earlier on another machine, but that machine is now unusable since the install failed b/c setup couldn't format the new partitions I set up due to a memory shortage (as though 1GB isn't enough - I understand this is a known issue w/ the dev). I really, really, really do not want to go through the nlite process again (this will be the twelfth time in the last few days) and I certainly don't want to end up with corrupted registry entries that I can't delete on my last remaining box. Can anyone help?

[nuhi]

Corrupted registry entries...ever tried rebooting? Those are only temporary, next time reboot or just unload it.

Anyway since your OS is somehow bugged and doesn't let nlite to do it's job then don't use it. Try some other MSFN subforum and do it manually.

However if your statement that you don't want to try nlite again isn't what you ment then post a link to that driver and I'll try it.

[boyhowdy]

Yeah, I finally figured out that rebooting clears the reg entries, each time I try to slipstream the driver it creates the bad entry again.

I got it to slipstream by using the PNP version of the driver. To be honest, I have no idea what that means (nor textmode for that matter). But I'm going to try to install again and see how it goes.

The driver is available @ http://www.msi.com.tw/program/support/driv...=527&kind=1

It's in three different packages on that page, but the first one ("VIA VT8237® SATA RAID Driver (For floppy driver)") should do the job. As I said, I don't think it's the driver since I was able to slipstream it before (something wonky with the PC I'm using now?)

EDIT: PNP drivers didn't work. When setup is done loading drivers and starts "loading Windows" it bombs and reboots the machine (no error messages).

Edited March 4, 2007 by boyhowdy

[nuhi]

I just tried to integrate it and it integrates fine. Weird.

But you could install the windows without it as well or you actually used the floppy while testing the PNP mode?

Or you used that half-integrated driver on top of it all? (that would explain the reboot)

My previous motherboard had this controller and all was fine so this is really unexpected. Maybe you installed some new protection software which could have blocked the registry access...let me know if you find the reason.

[boyhowdy]

I don't have a floppy drive and setup doesn't recognize my hdds without the driver. I'm pretty much hosed at this point. Do you know where there are instructions for manually slipstreaming the drivers? I'd like to use my customized installation as is and add the sata drivers manually before burning the disc. Is that possible?

[nuhi]

Well of course but I don't know where the instructions are, just search them on the MSFN forums, I seen them before.

[boyhowdy]

I gave up on slipstreaming, bought a floppy drive, put the drivers on it (removed from nlite setup) and every looks just fine... I load the drivers from the floppy, set up my disk partitions, format the partition.... and I'm back at square one with setup unable to format due to insufficient memory or corrupted files (neither of which is the actual case). I read elsewhere on the MSFN forums that someone had this issue with x64 and it ended up being a "SATA driver integration" issue. So, I create another set up disc, remove all the VIA drivers that have to do with sata or raid and try again. Same thing. Any ideas?