Integrate KB971961, KB971633 and KB944338

[Fudeba]

Hello, I try to use hfslip-1.7.9_beta_m but not integrate these fix in Windows 2000 Professional SP4 Portuguese BR:

KB971961

KB971633

KB944338

It's not included in HFSLIP?

Thanks!

Edited October 10, 2009 by Fudeba

[tommyp]

Integrate or slipstream?

• KB971691 - a new version of jscript.dll (ver 5.6.0.8837)
  KB944338 - a new version of jscript.dll and vbscript.dll (both are 5.6.0.8835).
  KB971633 - is dependent on which directx you are using. Make sure you select the DX9 version if you are slipstreaming DX9. DX9 is a family of files, but the most important one I believe is quartz.dll. DX9 updates are 99% of the time just updates of quartz.dll.
  

I ran hfslip the other day, jscript.dll is 5.6.0.8837, vbscript.dll is 5.6.0.8835 and quartz.dll is 6.5.1.911. These are the latest and greatest of the above listed files. So to answer your Q, I see that hfslip is doing the job just right over here. Perhaps the hotfixes you downloaded are just bad downloads from msft? Post your zipped hfslip.log if you are running into probs.

FYI, the 5 in 6.5.1.xxx signifies dx9. If the 5 was replaced by a 1, (i.e. 6.1.9.xxx), it would signify DX7.

[Fudeba]

Integrate or slipstream?

• KB971691 - a new version of jscript.dll (ver 5.6.0.8837)
  KB944338 - a new version of jscript.dll and vbscript.dll (both are 5.6.0.8835).
  KB971633 - is dependent on which directx you are using. Make sure you select the DX9 version if you are slipstreaming DX9. DX9 is a family of files, but the most important one I believe is quartz.dll. DX9 updates are 99% of the time just updates of quartz.dll.
  

I ran hfslip the other day, jscript.dll is 5.6.0.8837, vbscript.dll is 5.6.0.8835 and quartz.dll is 6.5.1.911. These are the latest and greatest of the above listed files. So to answer your Q, I see that hfslip is doing the job just right over here. Perhaps the hotfixes you downloaded are just bad downloads from msft? Post your zipped hfslip.log if you are running into probs.

FYI, the 5 in 6.5.1.xxx signifies dx9. If the 5 was replaced by a 1, (i.e. 6.1.9.xxx), it would signify DX7.

Oops... sorry! I use splitstream option. Fixes placed in HF folder.

I have DX9 files placed in folder HFCABS.

What better way to splitstream WMP9 in windows 2k pro? I tried to put MPSetup.exe in folder HF, but get lot several errors during install. I make a silent install packet and run in GUIRUNONCE step. Work for me, but, is a better solution?

HFSLIP log attached:

HFSLIP.zip

Edit:

More problem... two DLL failed on install, based in compilation related on HFSLIP.LOG above. See:

Any ideas about it DLL fail?

Edited October 11, 2009 by Fudeba

[tommyp]

I won't compare your list to see if it's all up to snuff. However, as I stated in my previous post, you need to place the correct dx9 hotfix there. You still have the directx7 hotfix named Windows2000-KB971633-x86-PTB.EXE. You want the dx9 hotfix instead. Place the Windows2000-DirectX9-KB971633-x86-xxx.exe there instead (the xxx is the language). You also had a problem with jscript/vbscript. I can assume that the culprit is js56nptb.exe. I'm not quite sure where you got that file from, but it's an oldie that I haven't seen in quite some time because it's outdated.

You should really consider visiting the w2k hotfix thread, it's a stickied post in this forum. You have lots of non essential files in your HF folder. For example, there is only 3 IE6 hofixes required now, you have 10. There are 4 msxml hotfixes required now, you have 7. You also have a cab file in HF, which will be ignored. I also see a blast from the past - Windows2000-KB951698-v2-DX9-PTB.exe. That has been outdated for quite some time (it's a directx9 hotfix).

For WMP9, you need to download it from MSFT directly. I'll bet that you need to clean up your nonsense hotfixes, and run barebones to verify WMP9 functions before you populate the HFGUIRUNONCE and HFSVCPACK folders. The problem may lie in one of the programs you are installing. Sometimes you just gotta walk before running.

[Fudeba]

Ok, ok.... I deleted all fixes in HF and HFCABS folders, and downloads all again from http://www.vorck.com/windows/hotfixes_2000.html

removed js56nptb.exe from HFSVCPACK_SW2.

Problem now, is windows update via IE not start... and two dll faults mentioned above, persist.

Ideas?

HFSLIP Log:

HFSLIP.zip

[tommyp]

a) What do those pictures say in english?

B) Do you know what language of the IE6 cabs you downloaded? Your best bet is to make sure you got the language of your OS. Check out this link for IE6 cab language specific downloads. http://www.hfslip.org/hflists.html

Please look at the details of the two msapsspc.dll & msnsspc.dll files in the sourcess\i386 folder. Check the what the date is. I checked mine out and it appears that msapsspc.dll is left unchanged (same date as my source\i386 folder). My sourcess does not have msnsspc.dll because it's not a required component. IIRC, msnsspc isn't updated via hfslip anyways.

In troubleshooting mode, it makes things easier for me to help if you move some files elsewhere so they won't get parsed. The trick is to find the key file that "breaks" things. Like I said before, please remove all the files from HFGUIRUNONCE and HFSVCPACK. Also, it may be worthwhile to remove the HFSLIP_POST_SPEEDUP_V0.2.CMD from the hftools folder too. In HFCABS, please remove the MUAuth.cab, MuCatalogWebControl.cab, and muweb_site.cab files. You do not need to delete those files, just move them elsewhere so they don't get parsed.

[Fudeba]

Ok

Well, the pictures above say in free translation:

Error loading xxxxx.dll

Could not find the specified procedure.

IE6 has been downloaded as follows. I took the "ie6setup.exe" stub install on the Portuguese page of microsoft, I put in the folder C: \ IE6 \ and triggers the download with the following command:

"C:\ie6\ie6setup.exe" /c:"ie6wzd.exe /d /s:""#E"

Downloaded the setup files for IE6 for Windows 2000/XP in the current folder, I copied the necessary files to the folder HFCABS.

The installation of IE6 is in Portuguese-br, already made sure of it.

Files msapsspc.dll & msnsspc.dll are present both in SOURCE and SOURCESS folder and both have the same creation date:

MSAPSSPC.DL_ - 07/May/2001 20:00

MSNSSPC.DL_ - 07/May/2001 20:00

Both files were copied by HFSLIP, but have not been updated.

Removed ALL files from the HFGUIRUNONCE and HFSVCPACK. Also removed the files that you request (HFSLIP_POST_SPEEDUP_V0.2.CMD, MUAuth.cab, MuCatalogWebControl.cab and muweb_site.cab)

All were moved to a folder _REMOVED outside the HFSLIP folder to avoid any problem.

The problem with the two DLL mentioned above, persists. this problems surge after discard all files on HF folder and downloaded all new from link (http://www.vorck.com/windows/hotfixes_2000.html). All select is PTBR, except specific files we not have language select or is "global".

This error on at step "registering components", a few instants before "T-13" point.

And the Windows Update does not work, to boot using IE6, you receive the message (again in a free translation):

"Checking if your computer has the latest software update for Windows for use with the site ..." and... stop in this screen and not show butons to get updates. IE not lock, if reload work ok, or open other site, ex. google.

The problem of Windows Update, I believe is some failure or lack of components with the Acitive-X.

And... waiting for sugestions or ideas.

Edit:

Sorry... eheh HFSLIP.LOG here:

HFSLIP.zip

Edited October 12, 2009 by Fudeba

[tommyp]

Can you remove your custom explorer.exe and retest?

If that still fails, can you test your source to see if the problem is there? It seems that you are using a VM to do your testing, so this should be relatively easy. First, rename your hfanswer.ini. Next, delete your sourcess. Rename your source folder to sourcess. Run hfslip and instead of typing I have read the instructions, type MAKEISO instead. It will make an bootable iso. After that, rename your sourcess to source. Run the VM using the newly created ISO and see if the problem lies in your source.

[Fudeba]

Can you remove your custom explorer.exe and retest?

If that still fails, can you test your source to see if the problem is there? It seems that you are using a VM to do your testing, so this should be relatively easy. First, rename your hfanswer.ini. Next, delete your sourcess. Rename your source folder to sourcess. Run hfslip and instead of typing I have read the instructions, type MAKEISO instead. It will make an bootable iso. After that, rename your sourcess to source. Run the VM using the newly created ISO and see if the problem lies in your source.

Positive! I can remove custom explorer.exe, and to make more acuracy test, removed UNIATA, flpydisk.sy_, WINNT.SIF (custon) and restaured TXTSETUP.SIF to original. Removel also HFCLEANUP file.

Executing now HFSLIP only with hotfixes on HF folder, no more archives on other folder.

Now, install and NO fail in msapsspc.dll & msnsspc.dll.

Windows updade work ok, only ask to update engine to latest version of windows update.

On update, ask to KB973540 (WMP9 fix) and ask to (obvious...) for .NET 1.1, .NET 2.0 and SilverLight.

To test porpouse, also make .ISO from my folder source with this command:

CDIMAGE.EXE -lSP5POEM_BR -h -j1 -m -bD:\WIN2K\HFSLIP\HFTOOLS\BOOT.BIN D:\WIN2K\HFSLIP\SOURCE D:\WIN2K\HFSLIP\SP4.ISO

Tested ISO SP4.ISO and no problems during install, it's work fine, 100%.

Yes, I use Microsoft Virtual PC to test, it's much more practial and faster to tests.

Next Step?

[Fudeba]

Well .. to advance the next step put the files on original folders:

Placed KB973540 on HF folder

Placed SWFLASH.CAB, LegitCheckControl.cab, MUAuth.cab, MuCatalogWebControl.cab & MUWEB_SITE.CAB on HFCABS folder.

Pladed WINNT.SIF on REPLACE\I386 folder.

Downloaded latest version of windowsupdateagent30-x86.exe from:

http://download.windowsupdate.com/WindowsU...Agent30-x86.exe

And remade a new test. Results in a 30 minutes. (will edit this post afert get results and attach HFSLIP.LOG)

EDIT:

Very strange. The problem with two DLL faults only occurs if are using the file WINNT.SIF !!!

WinUpdate works ok, and no critical updates need, all splitstreamed ok.

Sample of my WINNT.SIF attached. And also HFSLIP.LOG (generated without winnt.sif)

You can see something strange in my Do? The strange thing is that this file worked perfectly before erasing the entire contents of the folder HF ...

HFSLIP.zip

winnt.zip

EDIT EUREKA!

Finally!!! I found the location of the real guilty of the problems with the two DLL.

Are some files that are in the \$OEM$\$$\System32, probably some DLL or Systernals programs that are causing conflict!

Now that I have located the problem, I can discover real guilty, although this requires a little work, but I'll find out what file that causes so much trouble.

Once you have the name of the victim, I post here. And.... consider to make a silent install packet to place Systenals software on folder, afert windows install, on GUIRUNONCE fase.

Edited October 13, 2009 by Fudeba

[tommyp]

I found that some of the newer sysinternals freebee programs don't quite work well with 2k. The older ones just seem to work with 2k. Sometimes you just have to make due with the old versions. I suppose you could try a newer version, extract it to its own folder and run the exe from there. Or in other words, keep it out of win\sys32. Just a dumb idea to try I guess.

[Fudeba]

I found that some of the newer sysinternals freebee programs don't quite work well with 2k. The older ones just seem to work with 2k. Sometimes you just have to make due with the old versions. I suppose you could try a newer version, extract it to its own folder and run the exe from there. Or in other words, keep it out of win\sys32. Just a dumb idea to try I guess.

Murphy is relentless ... See the list of updates released in 12/Ago/2009 for Windows 2000.

KB953297

KB974455

KB971110

KB890830

KB953300

KB973525

KB954155

KB974112

KB958869

KB969059

KB971486

KB974571

KB971108

GRRRRrrrrr......

Well, I'm creating an ISO with fixes now in the HF folder, we'll see if they will be included in splitstream.

As for suspicious files to my problem, really were some DLL's that extra was placed on the SYSTEM32 folder. I removed these files and the problem disappeared.

The most interesting is that this problem only started happening after using some new HOTFIXES.

To save space in CD, I realy consider to make a compressed pack to install systernal tools.

But first I will test all applications Systernals to make sure that all are compatible with Windows 2000, and which are not removed or reversed for older versions (I have the old versions saved on a CD-R).