BikinDutchman
Content Type
Profiles
Forums
Events
Posts posted by BikinDutchman
-
-
I do not know what is exactly on CD2, and am not sure what you exactly want to do. But I had a (somewhat) similar situation.
Assuming you call the folder with the CD1 contents W2K3R2. You may try to copy the contents of CD2 into that folder and watch out that no file is replaced by a file with the same name but different function. After that you can use nLite to make an ISO of the folder with the combined files, and burn a DVD.
0 -
I just did the following comparison (all direct slipstreams):
RTM -> SP3
RTM -> SP2 -> SP3
I compared all files with a synchronization program (ViceVersa pro). The differences were in the following files:
-GUITRN_A.DL_, MIGISM_A.DL_, MIGWIZ_A.EX_, MMC.CH_, MSTSC.CH_, MSTSC.EX_, MSTSCAX.DL_, RDSKTPW.CH_, SCRIPT_A.DL_, SYSMOD_A.DL_,
-TSCUPGRD.EX_, XPTHT41W.HT_
For now I assume that all those files are obsolete (otherwise they would have been updated to the same version, why would MS skip just these few)
Also SP2.CAB is left in after SP2 but can be deleted in SP3.
Edit: I also found that MSRDP.CA_ is no longer updated in SP3 and can be deleted if the msrdp.cab line in DOSNET.inf is deleted as well. And there is more... keep reading my posts.
These guys and gals from MS keep surprising us with their "easter eggs". Maybe they are preparing a service pack for this SP3.
I had not the slightest trouble with a vanilla RTM -> SP3 install after deleting all those obsolete files (making "RTM -> SP3" and "RTM -> SP2 -> SP3" identical).
0 -
Did you remove the read only attribute for all files?
0 -
I did not study them all but it seems these are all errors related to devices that cannot be installed early on.
Some of them may eventually show up with a yellow bang in the device manager.
The "cannot be copied to" errors are much more serious and I do not see a single one of them in your case.
0 -
All: I worked with nLite 1.4.5.b2
This is a work in progress. At this point I can only recommend to delete (comment out) the following files in TXTSETUP.sif:
-napprov.mof, napschem.mof, rsop.mof, wscenter.mof, and rsop.mfl
There may be more but for me it solved the problem, and it does not affect the CD installs
0 -
i hope there is a solution to this soon!! i hope nuhi is reading this !!
Pallavsuri: Nuhi is working on this.
There is a solution: look into setuplog.txt and find the copy error. After that edit TXTSETUP.sif to remove the name of the file that is causing the copy error.
For more details see my own answer to my post.
0 -
Do you use WPA security?
-Look for KB917021 and install it on all your wireless clients.
Are all laptops in the same workgroup?
Do you have NetBIOS enabled?
0 -
I need to clarify that my WinNT32 install is started from a partition, there is no CD involved. But that causes only one small part of the problems.
As mentioned, I applied just one tweak with nLite (WMP privacy) and that was causing quite some files edited and a disastrous installation. I found the causes:
-For this case nLite does not add nLite.inf to DOSNET.inf and TXTSETUP.sif so that (without) CD, nLite.inf cannot be found during installation. This causes a crash when sysocmgr tries to execute nLite.inf (and cannot find it).
-The DEFLTWK.IN_, HIVEDEF.INF, HIVESFT.INF files are just cleaned up by nLite. Comments, empty lines, etc. Good
.The above nLite.inf problem does not occur for more comprehensive installations but in that case another problem occurs (note WinNT32 only):
-Copying of files stops if certain WBEM files cannot be copied: napprov.mof, napschem.mof, rsop.mof, wscenter.mof, and rsop.mfl.
-This can be detected by searching for "could not be copied to" in Windows\Setuplog.txt. Without fatal copying errors "setup has completed copying" should be found.
-I do not know what the problem is, it looks like the WBEM files are actually copied (earlier?) and the error may just be an overwrite problem.
-I fixed this by taking the above file names out of TXTSETUP.sif.
-Looking at other posts, I believe that WBEM copy errors might be causing several other problems. I may be worth to keep tracking this.
0 -
You can put your files in:
$oem$\$Docs\All Users\Desktop
or:
$oem$\$Docs\Your Account\Desktop
Good luck,
0 -
Kel, no I did it under WinXP SP3, if I make a CD and do a CD install in Virtual PC it works fine
-the problems come with WinNT32 install on a real PC.
I slipstreamed WinXP RTM -> WinXP SP3, followed by nLite
-I will try WinXP RTM > WinXP SP2 > WinXP SP3 > nLite tonight
0 -
I am a happy nLite user, integrated Xable, Boooggy a few things more, and a lot of simple drivers.
With SP2 everything worked out perfect, and for several reasons I preferred to use WinNT32 installs.
-They are a little different, more sensitive to tweaks than CD installs, but yet everything looked good.
Under SP3 I tried to do more or less the same, and CD installs are perfect as before with IE7 integration, Boooggy, Xable, etc
However when I use the same nLited WinXP SP3 with WinNT32 installation, hell breaks loose.
-Lots of files missing, disfunctionality, signing errors, and no Calc.exe to name one of the most visible!
-I also tried a WinNT32 installation with Vanilla WinXP SP3 and no problems there!
Just for the sake of testing, I applied only one tweak with nLite: the WMP privacy statement. This resulted similar trouble and the error log as uploaded.
I looked into the differences between the installations before and after nLite and found changes to the following files:
-DEFLTWK,IN_, HIVEDEF.INF, HIVESFT.INF, SYSOC.IN_. The first two shrank by 10%, and all that for one simple tweak.
I understand well we are in the transition from SP2 to SP3, that things are difficult, so maybe I miss something:
-Does someone have a similar experience? Even tested this? Do I need to upload all nLited files?
I will greatly appreciate some insight into this problem.
0 -
I just saw that WinXP SP3 is pulled by MS because of problems with RMS, see here.
Well I can also add something to the mix:
-Slipstreaming WinXP RTM (gold) with SP3 leaves the old WINNTBBU.dl_ in but updates WINNTBBU.dll.
-As a result CD installs use the (new) WINNTBBU.dll and
-Winnt32 installs, of course, use the old WINNTBBU.dl_ with a signing error as bonus.
All this after (how many?) months of beta testing
.The fix: just delete the old WINNTBBU.dl_
. (WINNTBBU provides the interesting background while installing in GUI mode
)0 -
Newsposter, look here.
For more detail you need to use Orca to look into the installer (VSE850.msi) data base to see what properties can be changed from the command line. These are generally capitalized (such as ALLUSERS).
0 -
Disable: it cannot be used by any program. The service is still listed under Computer Management > Services.
-Theoretically you are the only one in control and can do the enable/disable under Services.
-nLite can disable, does not remove.
Remove: you effectively uninstall, the files are gone, the service is no longer listed under services. You cannot uninstall under Computer Management > Services. Instead:
-sc delete <service name>
-reboot
All this is a little off topic, but OK there is some relation with nLite
0 -
Rhor,
I tried and got the Missing Shortcut window as usual. But I do not remove anything.
My guess is that the component with "Missing Shortcut" removed, it should be explorer-related but what?
Maybe the guru's know, otherwise you have to bisect: cut removal list in half, test, repeat with the problem half etc. Pretty efficient actually.
0 -
Rohr,
What are the properties of that shortcut? Can you see them anyway? As many details as you can get.
0 -
Thanks Boooggy,
I will try.
Is there any hope we get a version that does not require turning of sfx?
I know what you think about x64 but yet...
0 -
I tested it with a WinNT32 install but got copy errors during textmode and GUI mode setup and aborted the setup.
I did not get those copy errors with the Boooggy version, but also that caused problems after installation.
-This may be due to MS IE7 installer integration with nLite.
0 -
Hi Nuhi,
I integrated the MS IE7 installer and some hotfixes in WinXP x64 SP2, see attached.
I performed a WinNT32 installation and everything looks fine.
But when I execute IE7, I get a message that IE7 is not the default browser. (I did not install any other browser.)
-After responding Yes to make it default everything works fine.
This small issue causes a problem with Windows Update before IE7: nothing happens, you have to make IE7 default first.
0 -
Hi Nuhi,
If I apply Nlite driver integration >1 times I get that number of NLDRV lines under [OptionalSrcDirs].
Likely not a problem but you might want to fix it in the next release
.Also good job with new hotfix integration in 1.4.5 beta
0 -
x64: Setuperr.log errors:
Hi Boooggy,
I looked into this a little more, I know you hate x64 but please keep reading.
I had more luck using the Integrator BEFORE nLite.
-So I started with a fresh x64 SP2 and applied the integrator with all fixes.
-After that I applied nLite with the attached settings.
Afer installation WITH WinNT32 a had a functional system with only one line in setuperr.log:
Error:
Setup was unable to process some components because of the following error in section InstallWMP7 of information file wmp.inf:
The data is invalid.
***I can probably live with that but do not know what it means.
And btw the "Play All" problem with x64 is now gone
0 -
$OEM$
0 -
Yup, you got it!
0 -
If you copy from CD, your copied files can be read-only. Did you check that?
0
.
)
SP1.cab, SP2.cab, SP3.cab
in nLite
Posted
I did an integration RTM -> SP2 -> SP3 and deleted SP2.cab.
After that not the slightest problem
.