Jump to content

Nlite 1.4beta Win2K integration issues.


mikesw

Recommended Posts

I’ve attached my session.ini files in the order shown below. Each one is for a

different year. I don’t have any problems for the Win2K hotfixes for FY’2003,

but I have issues with FY’2004. (note: I integrated the 2003 list first followed

by the 2004 fix) The problems seem to occur after Nlite says it

needs to expand the cab files and direct integration is performed. I’m using Nlite 1.4beta.

The first error is in Kb835732

“H-The file ‘C:\ZRMPEOM_EN\ntkrpamp.exe already exists’”

“Please report this error if its unexpected”.

……

The version on the ntkrpamp.exe in the hotemp directory is v5.0.2195.6902

Whereas the one in sp4temp is v5.0.2195.6717.

After redoing with a new Win2kSp4 install, I get a little further until KB841356

Where it states.

“H-The file ‘C:\ZRMPOEM_EN\shlwapi.dll already exists”’

“Please report this error if its unexpected.

NUHI, please add an audit log trace file to NLITE1.4beta so that one can

Send the steps NLite is doing when it errors out. Ie.

A ) open KB…….file

B ) extracting cab files filenamecab

C ) filename ‘filea’ version ‘a.aa’ is older than “fileb’ version ‘b.bb’ , or,

D ) filename ‘filea’ version ‘a.aa’ is newer than ‘fileb’ version ‘b.bb’

E ) disgarding filea

F ) updating and overwriting ‘fileb’

G) closing KB….file

H ) compressing cab files and completion message

I) etc.

2003 INI FILES

[Main]

Env = 1.4 beta - 2.0.50727.832.Microsoft Windows NT 5.1.2600 Service Pack 2

Target = Windows 2000 Professional SP:4 - 5.0.2195.6717 - English (United States)

[Tasks]

Hotfixes and Update Packs

[Components]

;# Compatibility #

[KeepFiles]

msconfig.exe

[RemoveFiles]

clock.avi

yahoo.bmp

swtchbrd.bmp

[Options]

ProfilesDir = "%SystemDrive%\Documents and Settings"

TargetPath = "WINNT"

temp_dir = %USERPROFILE%\Local Settings\Temp

AdvTweaks

[Patches]

[services2]

[Tweaks]

[unattended]

ComputerType = Default

CustomLocales

MaximumDataStorePercentOfDisk = 12

RestorePointLife = 30

DesktopTheme = Default||

AutoUDay = 5

AutoUHour = 15

ProgFilesPath = "\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]

HotfixingReports

C:\Win2K_patches\2003\intg\Windows2000-KB329115-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB819745-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB820888-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB822831-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB823182-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB823559-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB823980-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB824105-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB824141-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB824146-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB825119-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB826232-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB828035-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB828749-x86-ENU.exe

C:\Win2K_patches\2003\intg\Windows2000-KB829558-x86-ENU.exe

2004 INI FILES

[Main]

Env = 1.4 beta - 2.0.50727.832.Microsoft Windows NT 5.1.2600 Service Pack 2

Target = Windows 2000 Professional SP:4 - 5.0.2195.6717 - English (United States)

[Tasks]

Hotfixes and Update Packs

[Components]

;# Compatibility #

[KeepFiles]

msconfig.exe

[RemoveFiles]

clock.avi

yahoo.bmp

swtchbrd.bmp

[Options]

ProfilesDir = "%SystemDrive%\Documents and Settings"

TargetPath = "WINNT"

temp_dir = %USERPROFILE%\Local Settings\Temp

AdvTweaks

[Patches]

[services2]

[Tweaks]

[unattended]

ComputerType = Default

CustomLocales

MaximumDataStorePercentOfDisk = 12

RestorePointLife = 30

DesktopTheme = Default||

AutoUDay = 5

AutoUHour = 15

ProgFilesPath = "\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]

HotfixingReports

C:\Win2K_patches\2004\intg\Windows2000-KB821887-x86-ENU.exe

C:\Win2K_patches\2004\intg\WindowsMedia41-KB822343-ENU.exe

C:\Win2K_patches\2004\intg\Windows2000-KB824151-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB828028-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB828741-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB830352-x86-ENU.EXE

C:\Win2K_patches\2004\intg\WindowsMedia41-KB832359-ENU.exe

C:\Win2K_patches\2004\intg\Windows2000-KB835732-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB837001-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB838989-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB839643-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB839645-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB840315-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB840987-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB841356-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB841533-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB841872-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB841873-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB842526-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB842933-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB870763-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB873339-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB883114-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB883935-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB885835-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB885836-x86-ENU.EXE

C:\Win2K_patches\2004\intg\Windows2000-KB887811-x86-ENU.EXE

C:\Win2K_patches\2004\intg\WindowsMedia-Q828026-x86-ENU.exe

Presently, I'm pretty frustrated since I'm not making very much progress integrating

hotfixes/updates into Windows 2K Professional using NLITE. :angry:

Edited by mikesw
Link to comment
Share on other sites


@agi,

used Nlite to integrate Win2K SP4. This is used as my reference copy to start

the hotfix integration. Hence, I have a copy of Win2kSP4 integrated in another

directory. If the Nlite bombs out, I delete the directory contents in c:\ZRMPOEM_EN

and copy all the files for Win2KSP4 integrated to this directory and start again

with the year 2003, followed by 2004.

I didn't do anything with SFC on the WinXP SP2 system I'm running Nlite on as I try

to integrate the hotfixes into Win2K sp4.

I haven't been able to get to the iso part of the Win2KSp4 +hotfixes yet.

Link to comment
Share on other sites

http://tracker.ryanvm.net/detail?id=59 WIll update your system to like september of last year!!! (Plus a coupla extras)

I dont remember how many fixes you will need after that but it is a much smaller amount than you are trying to do now...

Please give it a try it is just like an official service pack and contains ie6 plus large drive support 48bit adressing.

Plus several minor tweaks. Alot of work went into it and sadly the author has gone mia with the compiler so we cannot continue it.

After integrating this run a install in like VM or on another machine goto WU (Windows update) And get the kb numbers for the fixes you need to finish your updating.

Plus get a hold of me on mesenger Kelsenellenelvian - @ - hotmail.com for a coupla more extras...

Link to comment
Share on other sites

@raghul

I've tried nlite 1.3.5 too, and it does the same thing.

Note: the files that it says it already has happen at random. So lets say

the first time through it errors out on a file. If a restart from scratch, it may error out

on another file within the same KB file or some other KB file later on based on the order

of the filenames in the list. So it's hard to narrow down what may be causing it since the

problem moves around.

@kelsenel

Thanks for the info. :) However I'll do this as my last resort for now. I'm trying to use Nlite

to do it, and if I can't get it to do what I want, then I report bugs to be fixed.

Otherwise, how will Nlite be fixed if no one reports bugs/problems. :)

So, nuhi, if you are reading along, please suggest some possible ways to isolate the problem.

So, I'll keep plugin away for a little bit.

Note: To all, this randomness of "file already exists" for various KB's also occurs when I try to

integrate hotfixes into WINXP SP2 too. So it isn't isolated to Win2K SP4 only.....

Note2: when it does error out with the message above, it then finalizes the integration, but it

leaves the problem file that "already exists" in the root directory of the WIN OS files being

integrated. In this case c:\ZRMPOEM_EN.

Edited by mikesw
Link to comment
Share on other sites

If the Nlite bombs out, I delete the directory contents in c:\ZRMPOEM_EN

and copy all the files for Win2KSP4 integrated to this directory and start again

with the year 2003, followed by 2004.

Please correct me, if get this sentence wrong.

You´re using a soucrcedisc with SP4, that has been created by using nlite to integrate the SP.

Did you check any other option besides "integrate SP4", when you did this ?

Afterwards you´re running your 2003 preset on this source and after that, the 2004 preset on the same source ?

Agi

Link to comment
Share on other sites

Yes ,I used Nlite to integrate Win2K SP1 source disk with SP4. All Nlite defaults were used.

I then kept this in c:\ZRMPOEM_EN_SP4 so that when I run into problems integrating the hotfixes

with a copy in directory c:\ZRMPOEM_EN , I can then delete it and start again by copying

the SP4 directory copy over to the c:\ZRMPOEM_EN one. This helps me to speed things up

so I don't have to keep re-integrating SP4. All hotfix and security updates are integrated and

performed on the C:\ZRMPOEM_EN directory only.

The same was done for WInXP SP2 but in c:\WINXP_EN and C:\WINXP_EN_SP2

After the copy of the integrated ..EN_SP4 to the integration directory ...EN, I then select a different directory

for the 2003 fixes and sort them in numeric order and integrate them. After that, I exit and then re-enter NLITE.

I then select another directory for the 2004 fixes and sort them too in numeric order and integrate them. At this

point the cab files are again expanded and then the random file "already exists" error occurs. See session files

that show the hotfix directory and filename numeric order that was done in this post.

PS:

I've replaced my JAVA JRE 6 update 2 with JRE 5 update 11 and am now at JRE 5 update 6.

Nothing made a difference for the Nlite integration problem. I guess this isn't the issue.

Link to comment
Share on other sites

Ah that´s, what I thought !

You made some basic mistakes.

Never select anything else, but "integrate servicepack", if you want to use the folder later on, as a clean source.

Never run nlite multiple times on the same source.

To get a fully patched, uptodate W2K, you now have two choiches, but unfotuanately, both require to start from scratch.

Sorry, but it´s neccessary.

The first one is Kelsenellenelvian´s Tip.

Use nlite and integrate the SP4, Ryans addon, apply tweaks, drivers, remove components and create an iso in one go.

The disadvantage is, you have to use Windowsupdate later on.

The second one (that I prefer and regularly use) is a little bit more complicated, so be warned.

Use HFSLIP and Tomcat76´es page ( http://users.telenet.be/tc76/winup/_win2k.html ) to create the source and use nlite afterwards to integrate drivers, remove components, apply tweaks and configure the unattendsettings.

Even if you use the first one, Tomcat´s page gives you a pretty neat list of the actual updates, but the problem is, not all of them can be used for nlite.

Hope, this was a little bit helpful,

Agi

Link to comment
Share on other sites

Ah that´s, what I thought !

You made some basic mistakes.

Never select anything else, but "integrate servicepack", if you want to use the folder later on, as a clean source.

Never run nlite multiple times on the same source.

=

I'm a little confused with what you said above. I started with Win2K SP1 and when I used Nlite I selected

"Integrate servicepack". It then asked for the file by browsing to the location where the SP4 file was. I

selected the file, and Nlite integrated it into SP1 which was already copied to c:\ZRMPOEM_EN. After the

integration of SP4 the end-result was in C:\ZRMPOEM_EN. I then copied it to c:\ZRMPOEM_EN_SP4 for later

use. That is after Nlite complained about file already exists, I deleted the contents of c:\ZRMPOEM_EN

and copied the c:\ZRMPOEM_EN_SP4 to this directory and started the hotfix integration again since SP4

was already integrated.

As far as Nliting multiple times on SP4. Well, all I'm doing is giving a few files at a time (year 2003) and then

another set (year 2004) etc until I'm at Year 2007. If I give it all the files from 2003-2007 at once, it means

I spent alot of time integrating the files only to abort somewhere in the middle whereas with a few at a time,

I would spend very little time integrating and yet be able to quickly isolate the year that a hotfix is giving me

problems. This also builds my confidence that Nlite is working properly. Had Nlite integrated ok from 2003 to

2007 in one year increments, I could start again (on a fresh copy) and do everything at once from 2003-2007

knowing it would work without problem. So it's not like I'm trying to use Nlite to integrate hofixes on a

corrupt or partially completed integration due to past aborts. I always start fresh from the beginning using

the integrated SP4 copy that I made before starting the hotfix updates again from 2003 onwards.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...