Miles4

Mine is Windows XP Pro. Nothing out of the ordinary. I've used Nlite on same system in the past without any problem. The operating system (Windows XP Pro) I'm currently using and having the problem I installed using Nlite to build the unattended CD/DVD (just for the components removal, Options and Tweaks), including integration of the Intel Raid driver iastor without any problem.

Rebooting doesn't help. Didn't touch any policies. No firewall blocking. Note that there are a number of keys under the NliteTempReg key that I can access (before I reboot, which deletes the registry key), but I can't access the iastor key as noted above - I get an error message - and the subkeys under iastor listed in the Nlite error message don't exist - there are no subkeys under it at all. Any other thoughts? Why does Nlite have to write to the Registry any way?

I can't get there. Whenever I click or right click on the iastor key I get the error message "cannot open iastor: error while opening key". Plus the subkeys to which the Nlite error message refers do not exist - only the iastor key is there.

But I can't even access the "iaStor" key (b/c get access denied) to change the permission.

I forgot to add that in the Registry for the key there is only the "iaStor". The subkeys that are supposed to be under that in the referenced error message -"\Parameters\PnpInterface" - do not exist. Also, if I click on the "iaStor" key in the Registry, I get access denied.

Every time I try use Nlite to integrate my Intel raid driver I get the error message: "Access to the Registry Key `HKEY_LOCAL_MACHINE\NliteTempReg\ControlSet001\Services\iaStor\Parameters\PnpInterface' is denied. 1689" I've been able to integrate the Intel raid driver with Nlite in past without any problem but now I'm getting this error message every time. I've gotten the same error message whether I use Nlite 1.4 bet, 1.35 or 1.2. I've also tried it with earlier Intel Raid drivers that have been successful in the past. I've check that registry key and the entire NliteTempReg key and there is no permissions given even for Administrator (I'm signed on with administrator rights when I'm doing this). Given the permission doesn't help, though I'm not sure I'm able to give permission to all subkeys. How can I fix this? Thanks, Miles

Doesn't NLite do this?

This issue has something to do with the RyanPostSP2Updates and addons. If I do everything but use that and then burn the DVD image, it all works fine in Virtual Machine. If I then use RyanPostSP2Updates and addons and burn the same DVD image after that with about the same size, I start getting the error messages I noted before unless I reduce the size of the DVD. Anyone know what's causing this?

I am using Virtual Machine to test it and that's when I get the error messages. But if I reduce its size by deleting an app (NERO) to about 3.5 GBs, it installs fine without any errors. So, it doesn't seem to be an issue of what can actually burn (and I easily could use a DL DVD). It's something going on with the size. Any other thoughts out there?

joll69, I don't have any problem burning the DVD at the size I mention. My question is more whether the size I am burning can cause the error messages I'm getting. Are you saying that if I set the image as if it were a double-layer DVD (i.e., 8.5 GB capacity) and burn say 7 GBs that I won't get the error messages? In otherwords, are you saying I'm getting the error messages because I burning in excess of the a standard DVD's capacity, even though that DVD burns that amount without a problem? Thanks.

My DVD size for my uninstall is about 4.59 GB. The size on the disk says 4.59 GB (4,931,874,816 bytes. Using that I get an error message that varies; sometimes it refers to line 1 in inf in Winnt.sif and sometimes it refers to TXTSETUP.SIF. If I delete one of my apps to bring the size down to about 3.5 GB, it works without any errors. I've not yet determined what size works between 3.5 GB and 4.59 GB. Is there some size limit for an uninstall DVD (besides the disk capacity itself?

I used DPs driver pack (method 1) for chipset, graphics, nic and sound (but not mass storage). After the appearance of the F6 key and setup copies the initial files, I get the error message that it can't find iastor.sys, which is the intel raid mass storage driver for my system. If I use DPs driver pack method 2 and also install the mass storage driver pack and mass storage text mode, I don't get that error message. But I don't want to do that because I want a setup CD that is not unattended so I can use it if I ever need to repair windows after doing an unattended install. I know it's the DPs driverpack that's causing this because I tested the setup using only it. Any thoughts? Many thanks.

I used DPs driver pack (method 1) for chipset, graphics, nic and sound (but not mass storage). After the appearance of the F6 key and setup copies the initial files, I get the error message that it can't find iastor.sys, which is the intel raid mass storage driver for my system. If I use DPs driver pack method 2 and also install the mass storage driver pack, I don't get that error message. But I don't want to do that because I want a setup CD that is not unattended so I can use it if I ever need to repair windows after doing an unattended install. I know it's the DPs driverpack that's causing this because I tested the setup using only it. Any thoughts? Many thanks.

Thanks, Takeshi. It's not the CD. When I couldn't get the current one to work, I used an Unattended Cd that I know works. I then ISO'd it and it ran fine in VM. I think the problem is that I NLite before and after using RVM's update pack and addons with its integrator. I think using NLite for registry tweaks/options/patches after that screwed things up that RVM had done. That must be why the error message referenced "inf". I re-did the unattended but this time used NLite for everything I needed first, followed by RVM's intergration of updatePack and add-ons, then DPs_ROE drivers. Now it works fine. The Winnt.sif is idendtical to the one that was in the Unattended that didn't work, so I don't think Winnt.sif was causing the error but some mess up with the inf's in whatever windows read next.

Thanks, Oioldman. You're right, there's not a line at top in the actual winnt.sif. I'm not sure what l you meant by "a blank line where pnpdrivers ="? And I knew someone would ask me to use use code tags but the problem is, though I've seen them used, I don't know how to use them. I'm thinking that my problem is not the winnt.sif despite the fact that is what's mentioned. But, instead, it's some inf or in_ file that's read after that. Does anyone no what is read after the winnt.sif is read so I can look there? Many thanks.