nonno fabio Posted June 19, 2006 Share Posted June 19, 2006 (edited) after 2 years of successful unattended cds, suddenly I've got on both my pcs these fatal errors at setup.I haven't found a reason. I made no modifications to their structure, always working in the past: deleting unuseful directories (support, sbsi, docs, valueadd, lang, win9xupg, ecc.) create my own Winnt.sif file and $OEM$ directory, containing cmdlines.txt and runonceex.cmd file for installing a few applications.I say, it always worked but now during setup, at T-15 (registering components) appears the following error message, who says (sorry, I translate from Italian: don't know if it's the exact phrase): "unable to load internet connection wizard - unable to find Icfg95.dll"Sure! That file doesn't exist on xp cd... now why do you ask for it? If i click on OK, the setup goes on normally. But at the last restart, when Runonceex.cmd is execute, new messages appear: "the windows installer service could not be accessed. You may be running in safe mode or windows installer may not be correctly installed" when Runonceex.cmd runs a .msi file.And again: "RPC server is unavailable..." when XP tries to install the printer driver,I've made hundreds of attempts, but it's always the same: my unattended cd, always perfect till yesterday, now works only with SP2 slipstreamed and Winnt.Sif. If I modify everything more...error!The problem appears before cmdlines.txt processing, so I don't think it's a $oem$ problem, and it is the same on 2 different pc.I googled for it but never read of something similar...Systems are both Win XP SP2 Home Italian OEM. Attached is the template of my Winnt.sif file (i also tried to remove some strings but with no success)TnxWINNT.SIF Edited June 20, 2006 by nonno fabio Link to comment Share on other sites More sharing options...
T D Posted June 19, 2006 Share Posted June 19, 2006 Is this an upgrade installation? Cos there's a icfgnt5.dll in my i386 but not a 95. Did you upgrade from win 95 or something? Link to comment Share on other sites More sharing options...
nonno fabio Posted June 19, 2006 Author Share Posted June 19, 2006 absolutely no.I've made my tests always on blank fat32 formatted c: partition (no virtualpc).even in my CDs there's only icfgnt5.dll. I don't know neither what nor why asks me for that file. Link to comment Share on other sites More sharing options...
T D Posted June 19, 2006 Share Posted June 19, 2006 It's probably a redundant piece of junk leftover from somewhere. Open txtsetup.sif, dosnet.inf etc, look for all entries of icfg95.dll and del the whole line. Link to comment Share on other sites More sharing options...
nonno fabio Posted June 19, 2006 Author Share Posted June 19, 2006 (edited) i don't think so: all the files contained in I386 directory used during testing are exactly the same of the original windows cd (except winnt.sif and setupp.ini).However in txtsetup.sif, dosnet.inf, etc. there are no lines claiming for icfg95.dll, only for icfgnt.dll and icfgnt5.dll.all this look impossible but it's true: I've also thinked of an .iso burning error so i tried to recreate an iso of the original cd with the same sw (NLite) I used to create uacd. The new iso works like the original, the uacd instead shows those errors.It's driving me mad! Edited June 19, 2006 by nonno fabio Link to comment Share on other sites More sharing options...
JuMz Posted June 19, 2006 Share Posted June 19, 2006 If you are using RyanVM's update packs (an older one), take a look at this...http://www.ryanvm.net/forum/viewtopic.php?...ighlight=icfgnt Link to comment Share on other sites More sharing options...
T D Posted June 20, 2006 Share Posted June 20, 2006 Oh.That sort of clears it up. Link to comment Share on other sites More sharing options...
nonno fabio Posted June 20, 2006 Author Share Posted June 20, 2006 Very nice link, JuMz! :perhaps I find the solution there (now I've got no time to try...)....Modification of the signed inf files (e.g. swflash.inf or wmp.inf) causes the problem....Before seeing for the first time the error messages, I directly slipstreamed in the uaCD the new flash 9.0.2 files (flash.ocx and swflash.inf)I will inform you: tnx Link to comment Share on other sites More sharing options...
JuMz Posted June 20, 2006 Share Posted June 20, 2006 Very nice link, JuMz! :perhaps I find the solution there (now I've got no time to try...)....Modification of the signed inf files (e.g. swflash.inf or wmp.inf) causes the problem....Before seeing for the first time the error messages, I directly slipstreamed in the uaCD the new flash 9.0.2 files (flash.ocx and swflash.inf)I will inform you: tnxNo problem! Good luck! Link to comment Share on other sites More sharing options...
nonno fabio Posted June 20, 2006 Author Share Posted June 20, 2006 bingo!!! Solved. 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