fragbert Posted March 20, 2007 Share Posted March 20, 2007 (edited) UPDATE: I get these same errors using nlite on an untouched XP SP2 installation source! Same source I've been using for about two years now. This is without any driverpacks or updatepacks whatsoever. Yikes!Hi, I am at odds with the Tweaks section of Nlite. For a span of about a year I have been fortunate enough to have success with combining nlite, ryanvm's update pack integration, and BTS's driver packs for my unattended XP installations. My dealings with nlite were strictly in the Setup portion (Unattended, Options, and Tweaks tabs). However since the last few update packs, I have not been able to get nlite and ryanvm's packs to play nice - and ONLY if I use the tweaks section. I use a few explorer, start menu, task bar, and comand prompt tweaks - that's it (no "red" advanced tweaks either). What results is the dreaded framedyn.dll and srclient.dll errors along with a messed up start menu and IE icon replaced with the internet setttings cpl.I'm so used to the minor explorer/startmenu/taskbar tweaks from nlite, it will be hard to give up, but unfortunately for me the ryanvm update pack is more important for now. I am wondering if any of you have an alternative method/program for adding these tweaks to an unattended install source? Maybe a simple .reg from RunOnceEx?Of course I'm open to diagnosing the problem but I don't think that will go far...Here is my Last Session.ini[Main]Env = 1.3 - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 2Target = Windows XP Professional SP:2 - 5.1.2600.2180 - English (United States)[Tasks]Tweaks[Components];# Compatibility #[KeepFiles]msconfig.exe[RemoveFiles]clock.aviyahoo.bmpswtchbrd.bmp[Options]ProfilesDir = "%SystemDrive%\Documents and Settings"TargetPath = "WINDOWS"temp_dir = %USERPROFILE%\Local Settings\TempAdvTweaks[Patches][Services2][Tweaks]Explorer-Add 'Command Prompt' to folder context menuExplorer-Advanced Search: preconfigure optionsExplorer-Classic Control PanelExplorer-Disable Search AssistantExplorer-Display the contents of system foldersExplorer-Launch folder windows in a seperate processExplorer-Show Drive Letters in front of Drive NamesExplorer-Show extensions of known file-typesExplorer-Show hidden files and foldersExplorer-Show protected operating system filesExplorer-Show Statusbar in all windowsExplorer-Show the full path in the Address BarExplorer-Use small icons in Explorer barPerformance-Minimal Power ManagementPerformance-Use Windows classic folders / No Tasks SidepanelSecurity-Screensaver Password-Protection-EnabledStart Menu-Add Administrative Tools menuStart Menu-Control Panel-Display as a menuStart Menu-My Documents-Display as a menuStart Menu-My Music-Don't display this itemStart Menu-My Network Places-Don't display this itemStart Menu-My Pictures-Don't display this itemStart Menu-Network Connections-Don't display this itemStart Menu-Reduce popup delayStart Menu-Remove Set Program Access and DefaultsStart Menu-Remove Windows Catalog shortcutStart Menu-Remove Windows Update shortcutStart Menu-Show IE FavoritesTaskbar-Disable Hide inactive iconsWindows Media Player-Accept Privacy Statement[Unattended]ComputerType = DefaultMaximumDataStorePercentOfDisk = 12RestorePointLife = 30DesktopTheme = Default||AutoUDay = 5AutoUHour = 15ProgFilesPath = "\Program Files"[NetAdapter1]connname = ""macaddress = ""ipaddress = "192.168.0.1"subnetmask = "255.255.255.0"defaultgateway = ""dnsserver1 = ""dnsserver2 = ""winsserver = ""netbiossetting = "0"ipxnetworknumber = "00000000"ipxnetworkframetype = "0xFF"[GuiRunOnce][Drivers][Hotfixes] Edited March 20, 2007 by fragbert Link to comment Share on other sites More sharing options...
fragbert Posted March 20, 2007 Author Share Posted March 20, 2007 Edited to reflect general problem without updatepacks. Link to comment Share on other sites More sharing options...
nuhi Posted March 20, 2007 Share Posted March 20, 2007 Tested your preset and it went fine.That error tells me that some other modification tampered with system files and haven't patched what needed to be patched.If you want to easily solve that try to either remove one component with nlite or use one of the patches in the Options page then nLite will take care of the patching.Just to be clear I strongly believe that nLite on it's own isn't responsible for the error. If you are again sure in otherwise then please try to be more specific how to get that error because only preset didn't do it. Link to comment Share on other sites More sharing options...
fragbert Posted March 20, 2007 Author Share Posted March 20, 2007 Tested your preset and it went fine.That error tells me that some other modification tampered with system files and haven't patched what needed to be patched.If you want to easily solve that try to either remove one component with nlite or use one of the patches in the Options page then nLite will take care of the patching.Just to be clear I strongly believe that nLite on it's own isn't responsible for the error. If you are again sure in otherwise then please try to be more specific how to get that error because only preset didn't do it.I don't rule out the possibilty that my "clean" XP SP2 source may have been inadvertently modded or tampered - the trouble is were to look? I followed your instructions by removing one component (games) and also used an option patch (TCPIP to 100 connections), and this time no error! Ok this is a good step in the right direction, what next?Thanks! Link to comment Share on other sites More sharing options...
nuhi Posted March 21, 2007 Share Posted March 21, 2007 Recopy from the original CD, or ISO and use only nLite on it, don't do anything manually nor with some other tool just to see does it break.Also if it breaks again on only tweaks then try not even tweaks, just create ISO and see if that fails.Of course use virtual machines for this, no need to spend CDs or mess with your real partitions. Link to comment Share on other sites More sharing options...
fragbert Posted March 22, 2007 Author Share Posted March 22, 2007 Recopy from the original CD, or ISO and use only nLite on it, don't do anything manually nor with some other tool just to see does it break.Also if it breaks again on only tweaks then try not even tweaks, just create ISO and see if that fails.Of course use virtual machines for this, no need to spend CDs or mess with your real partitions.OK here is what happened:Integrate SP2 to my original VLK XP CD using Nlite - no problems applying anything else afterwards.Manually integrate SP2 first using sp2.exe s:<source>, then use nlite to apply one single tweak (command prompt from explorer) - .dll errors.Manually integrate SP2 using above method, then use nlite to apply said tweak AND adding an option (TCPIP connects to 100) - no problems.Any ideas? Link to comment Share on other sites More sharing options...
newsposter Posted March 23, 2007 Share Posted March 23, 2007 did you download a fresh sp2 installer from MSFT? Link to comment Share on other sites More sharing options...
fragbert Posted March 23, 2007 Author Share Posted March 23, 2007 (edited) did you download a fresh sp2 installer from MSFT?Yes. Not that it matters, if it was remotely corrupt it would not install due to a hash failure.UPDATE: And I get the DLL errors on a naked XP RTM (no service packs), the original VLK media sent directly from MS - again after applying just one tweak. Edited March 23, 2007 by fragbert Link to comment Share on other sites More sharing options...
xpman Posted April 3, 2007 Share Posted April 3, 2007 I have been having this problem (among other things missing) for some time now, and searching the forum only revealed other people having the same problem, lots of advice and ideas - but no solution.In my case, I also just have slipstreamed SP2 into a copy of my original medium. Then I use nLite to integrate the hotfixes, nothing more. Still, it seems nLite removes the dll (and logoff.exe) for some reason. I even tried to just select hotfix integration but not actually add any hotfix - same result.Currently, I am experimenting with simply adding framedyn.dll to the keep list (along with logoff.exe), but it's beyond me why that should be necessary in the first place if I don't do any space-optimization. Link to comment Share on other sites More sharing options...
fragbert Posted April 4, 2007 Author Share Posted April 4, 2007 (edited) I have been having this problem (among other things missing) for some time now, and searching the forum only revealed other people having the same problem, lots of advice and ideas - but no solution.In my case, I also just have slipstreamed SP2 into a copy of my original medium. Then I use nLite to integrate the hotfixes, nothing more. Still, it seems nLite removes the dll (and logoff.exe) for some reason. I even tried to just select hotfix integration but not actually add any hotfix - same result.Currently, I am experimenting with simply adding framedyn.dll to the keep list (along with logoff.exe), but it's beyond me why that should be necessary in the first place if I don't do any space-optimization.Glad to see I am not alone here What is very strange is that I can avoid this problem by either integrating SP2 using Nlite - or if I had manually integrated SP2 beforehand, I select the options tab but dont actually change anything and Nlite will go through a "processing files" stage. No clue on what it is actually processing but that prevents the .dll errors if I chose to utilize any tweaks. Edited April 4, 2007 by fragbert Link to comment Share on other sites More sharing options...
tap52384 Posted April 4, 2007 Share Posted April 4, 2007 Try putting the file in your keep box under components. Link to comment Share on other sites More sharing options...
xpman Posted April 15, 2007 Share Posted April 15, 2007 To be sure, I added framedyn.dll in the keep box and copied it into $$\system32 in the $OEM$ directory. After installing, the file is actually there (although I have not found out why since I made two changes at once).However, the error still occurs (so my guess is that it's just copied from the $OEM$ directory but not really registered).For reference, here's my session.ini file:[Main]Env = 1.3 - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 1Target = Windows XP Professional SP:2 - 5.1.2600.2180 - English (United States)[Tasks]Remove ComponentsHotfixes and Update PacksOptions[Components];# Compatibility #[KeepFiles]msconfig.exeframedyn.dlllogoff.exe[RemoveFiles][Options]CABNoHighProfilesDir = "%SystemDrive%\Documents and Settings"TargetPath = "WINDOWS"temp_dir = %USERPROFILE%\Local Settings\Temp[Patches][Services2][Tweaks][Unattended]ComputerType = DefaultMaximumDataStorePercentOfDisk = 12RestorePointLife = 30DesktopTheme = Default||AutoUDay = 5AutoUHour = 15ProgFilesPath = "\Program Files"[NetAdapter1]connname = ""macaddress = ""ipaddress = "192.168.0.1"subnetmask = "255.255.255.0"defaultgateway = ""dnsserver1 = ""dnsserver2 = ""winsserver = ""netbiossetting = "0"ipxnetworknumber = "00000000"ipxnetworkframetype = "0xFF"[GuiRunOnce][Drivers][Hotfixes]F:\os\nLite Integrable Hotfixes\windowsxp-kb924667-x86-enu_9016dbabca407c3278219baba256111e131330a3.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb834707-x86-enu_6cf07c9c17963993b56d3e7502fac060123e3181.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb873339-x86-enu_fd28098f5f0e8e629e5b7f64e5cd6b6b722a35a7.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb885835-x86-enu_920ecebf9cd90610ec67a305820f98e4186ca748.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb885836-x86-enu_f87074f42947ee275445bdd34dda472871ed3b41.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb890175-x86-enu_7ba9247b3c47f90ac07fcc4c3227b9a48c8366b0.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb888302-x86-enu_5c4ef905021d66aa78d9f5f112e5d05c40b1a909.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb890047-x86-enu_b11cd51a47917fb48a3ff5ea232a11076d37875e.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb887472-x86-enu_5edc4ccc759d65f4afba8542435172ed54515135.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb885250-x86-enu_1ad483d726bd6ecbf5dbf2cec4720e737a7f7f67.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb873333-x86-enu_3d9a08de2dea62e11a96e38b5b0c43c802f4858b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb891781-x86-enu_32b11076df0189adeb0f36ce3bf7baa01cff1c29.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb867282-x86-enu_d7820c84f525a3eb3699a7f1d6b3ed84ff24b91d.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb888113-x86-enu_b003447509dec5510e25366e2e02eae477ded11a.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb893086-x86-enu_a2e913a0520492a1013d8653626eae6fa05fac7c.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb890923-x86-enu_c373b614a40a2ce85af9e795ad8955e585609301.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb890859-x86-enu_813f47d987b772bacae20e7dec9b5f6f16079303.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb890046-x86-enu_432bf46f62aeaecc0e519af31d74723096f9b201.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb896358-x86-enu_42b05278a6f2ee006072af8830c103eab2ce045f.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb896422-x86-enu_4151843be8f1d81514b35bd5480232544f4787ba.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb896428-x86-enu_24f66bc1e3b8107ec580ba2c53148a69dbc606a0.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb883939-x86-enu_59c2da5550bdbb6696552ef5bab50ff05939e962.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb893066-v2-x86-enu_3d2029a4300c0b7943b20c1287c8143087045d52.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb901214-x86-enu_2838831de819dad80ea0edaf5fb1e0bfb3c026c0.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb903235-x86-enu_4759bc9ceeb4c84401264cd925a037e9e00f4e60.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb896727-x86-enu_d7e428a183c8a82e7d9ce2b80858e66b05e2854c.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb899588-x86-enu_4942c9ff7c7fe8af13ff202c234496ce91635ae1.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb893756-x86-enu_0fff59c5188cc15ec8f138fda97cb8be1e22da66.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb899591-x86-enu_3022d995581878f4017098b693b4ba35f99dee5c.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb899587-x86-enu_95ef03f0da9761b044b9a98d445af90266777ea8.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb896423-x86-enu_baba29a9d96e44e3f55045f749cc82cfa4038f0b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb896688-x86-enu_746342fe31abfc7a4fb3ea180cf08dc65c2c6a95.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb902400-x86-enu_a51d743a1925dd0216160daaf9fc4c7a42a27e53.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb899589-x86-enu_4a281c5b3b826b3ae76e502cbeae6410f0407651.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb900725-x86-enu_21b409882b7f51a9d09c32bd698504fadb9fc433.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb901017-x86-enu_04c459695f9018fd31c762bb0a8250cb0506061b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb905749-x86-enu_3f44b68f7e0a0e6332dd18997e134beab1027c73.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb905414-x86-enu_9e8fa8909332653de951edcfdb691f2aa148eb1b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb896424-x86-enu_bc0a35c5dd2dded71405dab707d0c61831b2a58f.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb905915-x86-enu_b7a56a560ef3192731696c3288e6ba974c9529ee.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb904706-v2-x86-enu_ec909ee2bab6b15d7d3545a1eaf07bbb066e038b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb912919-x86-enu_a4b4638c85d74c1d9ceaf63189ad46aa34f60293.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb908519-x86-enu_ea7ea742f9a3632f1090eab8c66b3fe7735c084f.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb913446-x86-enu_b41b0b8eb6e36b74499a588fb5e6a88a2c5e6317.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb911927-x86-enu_db8cbad537f3f0453deac488f8eb629b3c3a832b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb901190-x86-enu_2497a4e9957ddf13e2343858608f89ef6132efb2.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb911567-x86-enu_3322015f70b63fd2c82af81148ed88055a6f7e5b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb911562-x86-enu_7d16ad9701607a354e0ca2602a3fef485c8d9929.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb913580-x86-enu_f57aa2fdaf623d8b0231fc928c00ad8498d37c76.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb912812-x86-enu_6f395a56db4853c26daaad24fd992497278fba82.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb908531-v2-x86-enu_0f04352bbc21b3c173cc8dd8c9e63c082b34b676.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb917344-x86-enu_9c0c688c3e5c11a1b2ce0666117dc193823367b0.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb914389-x86-enu_8c44336e9e4f287891ac384bee0219e9c2224523.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb917537-x86-enu_a4dbb2338b97e63f46d45f1d69aa6a7908269b13.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb917953-x86-enu_a1c66e00d1a487f25ca16af5a7f858858136c228.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb917159-x86-enu_5ed838e18ceae61a8d94f8c4be2462a8e19212d7.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb916281-x86-enu_db93384fa2f9b7b1c8b93456381fa7b654636ae0.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb914388-x86-enu_21992f2ad7f7fd8ab28e854ce364ebc4f8baf810.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb918439-x86-enu_056bf5d0c049e0e8e799593b3508627ee8557dc1.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb911280-v2-x86-enu_3a49ae105416eb7b37dbbaccbedc9c20069ef1d9.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb921883-x86-enu_80bd35bdac09cbe1974111ee623b36f016b639be.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb917422-x86-enu_8a32d9119235c80bc6a82793403e0e5443c36789.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb922616-x86-enu_cf1ee106a318c1fe135978f94ec0867312cea73b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb920670-x86-enu_a71ac163b276057101fe92739c06c6e6d143ccf8.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb920683-x86-enu_ef1482c5b88557e56563dace9b7549ebf6d7f9c7.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb921398-x86-enu_47a6965d63200295eb57c1d7a5440d26c43d90d1.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb920214-x86-enu_3f16a756fc5763565e1f824f8519690fa18012a5.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb918899-x86-enu_c0d1d367b24bd3fe6f2068a5459d5483bb35ba39.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb920685-x86-enu_be0e9cea96e2ad48394aebe90d48edcc36ac38d5.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb919007-x86-enu_dc2307d635a64c87bbf1f216442104ef4b4ada0b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb925486-x86-enu_b23791745d2206a9333cf2da9e683c3366b067ce.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb922760-x86-enu_07543630cd9b3013862a2d79a95cf0e1e51803ca.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb922819-x86-enu_e4dceecdd4a72e5ad91cc78fe5f4572f91ee5db0.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb924496-x86-enu_f1e2421551a739eae947590735fb3f4abec82c22.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb923191-x86-enu_9d2cfed124f1f50804c20a6e8a881f84c266745f.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb924191-x86-enu_5e3ee7c5954da4cd38a5121623c05d617e547951.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb923414-x86-enu_ed2b1047badbd832a971a76ca7ef4519d1a444f4.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb920213-x86-enu_02cb394147b09e8926b4f8334feeff4b8fa4b33b.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb923980-x86-enu_1f04bf1859d5ba3761e482dbbd48f3795001e391.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb924270-x86-enu_3b1af30dc7a2f51f60a415eaf2cc01f9bf779dab.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb926436-x86-enu_98f46d49f189f01c14a7d5360d794da20edae885.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb923694-x86-enu_2b3f0e26ab0560c97bd33ea33022161268342a5d.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb926247-x86-enu_f465277dda6008156bb6f81bc77c72253a91d303.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb926255-x86-enu_1737b8dde544dbbc79dddd6f123291b781313c04.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb925454-x86-enu_968e709977724060e4d290bece1b6e67f5a078c1.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb923689-x86-enu_056c15e845cdf1027b2ea920e97ab8f4319c4bc6.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb929969-x86-enu_1237547f1cb90f54269bdb73c9985f263e85d48c.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb928255-x86-enu_d29dfbbe228e49f746a947eeb4880e980b76d53d.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb928090-x86-enu_3b58f59e0ee806789746335bfdab293a0d5f5b88.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb928843-x86-enu_80eb8779856aefa25bceab8926940fbdebabdc23.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb927802-x86-enu_94703f4083a9d9d6633d9134d0d0a85bfc405f3a.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb931836-x86-enu_88800ae7ce66933f34a490ba2e58d51822078c6d.exeF:\os\nLite Integrable Hotfixes\windowsxp-kb927779-x86-enu_ec7986f2b0afe9cc7f53a48b6582169a77d9515e.exe Link to comment Share on other sites More sharing options...
Mandarin Posted April 17, 2007 Share Posted April 17, 2007 I'm getting this error for the first time after doing loads of nLited CDs previously with no issues. Can't add much other than it has nothing to do with SP2 cos my original CD has SP2 built in so I am not adding it at any stage. Link to comment Share on other sites More sharing options...
Mandarin Posted April 19, 2007 Share Posted April 19, 2007 Just to add to this further it is beginning to look like a problem with compatibility with nLite and Ryans update pack. Each works perfectly OK on its own but the issue comes when using Signet's Integrator and nLite, but only since the new pack came out - never had an issue with the March update pack or any before that.I normally use the Integrator to add the latest update pack then nLite the resulting folder to reduce its size and apply a load of tweaks - the same basic setup I have used for over a year. Then I add any other addons that I need using the Integrator again before making the ISO with nLite when I am finished.If I just add the update pack with the integrator and just run nLite with no additonal addons it works. Add even a single addon and the install breaks - even with addons that I have used for a long time so know that they are fine.As a final check I just finished running the whole lot in nLite alone with no integrator involved and got the same failure - so the only common factor is the new update pack.Going to try dropping back to the March pack and try it again and if the errors go away it sort of proves where the problem then lays. Link to comment Share on other sites More sharing options...
underxp Posted April 19, 2007 Share Posted April 19, 2007 (edited) I have the same problem. I used Nlite for integrate AddOns only, without nothing more. I'm using Nlite for years, and this is the first time that i see this problem. The source is fine, because I probe creating an install disk without nlite and Windows install OK. My source have IE7 and WMP11 slipstreamed, can be a problem of Nlite with IE7 or WMP11 ? I'm using Windows XP SP2 Spanish Corporate. My source is full patched with HFSlip and after it I applied Booggy WMP11 Slipstreamer. This is my session.ini:[Main]Env = 1.3 - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 2Target = Windows XP Professional SP:2 - 5.1.2600.2180 - Español - España (alfabetización internacional)[Tasks]Hotfixes and Update PacksCreate a Bootable ISO[Components];# Compatibilidad #[KeepFiles]msconfig.exe[RemoveFiles]clock.aviyahoo.bmpswtchbrd.bmp[Options]ProfilesDir = "%SystemDrive%\Documents and Settings"TargetPath = "WINDOWS"temp_dir = %USERPROFILE%\Configuración local\TempAdvTweaks[Patches][Services2][Tweaks][Unattended]ComputerType = Por DefectoMaximumDataStorePercentOfDisk = 12RestorePointLife = 30DesktopTheme = Por Defecto||AutoUDay = 5AutoUHour = 15ProgFilesPath = "\Archivos de programa"[NetAdapter1]connname = ""macaddress = ""ipaddress = "192.168.0.1"subnetmask = "255.255.255.0"defaultgateway = ""dnsserver1 = ""dnsserver2 = ""winsserver = ""netbiossetting = "0"ipxnetworknumber = "00000000"ipxnetworkframetype = "0xFF"[GuiRunOnce][Drivers][Hotfixes]F:\Download\Nlite & hfslip\Favoritos\Kels_Runtimes_addon_v2.6.CABF:\Download\Nlite & hfslip\Favoritos\FOXY_NIRSOFT_COLLECTION_LARGE_ADDON_V1.2.CABF:\Download\Nlite & hfslip\Favoritos\CMDHere_addon_v1.3.cabF:\Download\Nlite & hfslip\Favoritos\Gustavo_comm_Addon.cabF:\Download\Nlite & hfslip\Favoritos\FonttPack_AddOn.CABF:\Download\Nlite & hfslip\Favoritos\Foxit_Reader_AddOn.cabF:\Download\Nlite & hfslip\Favoritos\Pserv_QuickLaunch_Addon_v2.6.cabF:\Download\Nlite & hfslip\Favoritos\Sysinternals-v2.9a_addon.cabF:\Download\Nlite & hfslip\Favoritos\WinRAR_37b7_AddOn.cabF:\Download\Nlite & hfslip\Favoritos\Kels_CPLBonus_addon_v5.6.CABF:\Download\Nlite & hfslip\Favoritos\Kels_Uber_Addon_v9.9a.CABF:\Download\Nlite & hfslip\Favoritos\Kels_UserPass2_addon_v1.1.CABF:\Download\Nlite & hfslip\Favoritos\Kels_VistaDriveIndicator_addon_v2_uninstallable.CABF:\Download\Nlite & hfslip\Favoritos\NR_DesktopIcons_Addon.cabF:\Download\Nlite & hfslip\Favoritos\Ricks_CCleaner_AddOn_v1.39.502.rarF:\Download\Nlite & hfslip\Favoritos\Ricks_Paint.Net_Addon_v3.05.rarF:\Download\Nlite & hfslip\Favoritos\Kels_Visual_Styles_addon_favs.CABUPDATE: iexplore.exe is missing from C:\Program Files\Internet Explorer !!!!! Is this anormal or not ? I think that NLite screwed the IE7 installation files slipstreamed with HFSlip. And none of AddOns is installed !!!!! Strange error ?????? Edited April 19, 2007 by underxp Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now