Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

FDV fileset for windows 2000 server

- - - - -

  • Please log in to reply
18 replies to this topic

#1
nh_wzg

nh_wzg

    Newbie

  • Member
  • 21 posts
  • Joined 03-June 06
1.FDV fileset for windows 2000 server dl from:http://www.vorck.com/windows/data/fdvfiles-srv.zip
2.HFSLIP 1.7.9 dl from:http://hfslip.org/HFSLIP_static.php
3.Log file contant:
                 This file is automatically generated by HFSLIP
   Use of HFSLIP for anything other than personal non-commercial purposes 
                            is strictly prohibited.
                         Copyright(C) TommyP 2005-2009

====================HOW TO REPORT A PROBLEM AND GENERAL INFO===================

       If running into problems, refer to http://hfslip.org/support.html

      HFSLIP support forum: http://msfn.org/board/index.php?showforum=129

 Updated hotfix lists: http://www.msfn.org/board/windows-updates-t126410.html

===============================================================================

Host OS         - Windows 2000

HFSLIP Version  - 1.7.9, build 091109

HFSLIP Path     - H:\hfslip\

OS in SOURCESS  - Windows 2000 Server SP4 English

Drivers         - DRIVER.CAB Updated

CD Install Path - Default

CDTAG           - CDROM_NT.5

Mods            - FDV Fileset

===============================================================================
Files in your HF folder:
gdiplus_dnld.exe
IE5.01sp4-KB938127-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB947864-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB948881-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB956390-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB958215-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB960714-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB963027-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB969897-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB972260-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB974455-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB976325-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB976749-Windows2000sp4-x86-ENU.exe
IE5.01sp4-KB978207-Windows2000sp4-x86-ENU.exe
KB832414_MSXML2.5_x86.exe
MDAC_TYP.EXE
MDAC281-KB927779-x86-ENU.exe
msxml2.msi
msxml2sp6-kb887606-x86-enu.exe
msxml4-KB941833-enu.exe
msxml4-KB954430-enu.exe
msxml6-KB933579-enu-x86.exe
msxml6-KB954459-enu-x86.exe
OE5.5sp2-KB951066-Windows2000-x86-ENU.exe
OE5.5sp2-KB973354-Windows2000-x86-ENU.exe
rootsupd_fe44934fd80dd11fec2f0f9b24431658a4f6d589.exe
Windows2000-KB842773-x86-ENU.EXE
Windows2000-KB891861-v2-x86-ENU.EXE
Windows2000-KB893756-x86-ENU.EXE
Windows2000-KB896358-x86-ENU.EXE
Windows2000-KB896423-x86-ENU.EXE
Windows2000-KB899587-x86-ENU.EXE
Windows2000-KB899589-x86-ENU.EXE
Windows2000-KB900725-x86-ENU.EXE
Windows2000-KB901017-x86-ENU.EXE
Windows2000-KB901214-x86-ENU.EXE
Windows2000-KB905414-x86-ENU.EXE
Windows2000-KB905749-x86-ENU.EXE
Windows2000-KB908506-x86-ENU.EXE
Windows2000-KB908519-x86-ENU.EXE
Windows2000-KB908531-v2-x86-ENU.EXE
Windows2000-KB911280-v2-x86-ENU.EXE
Windows2000-KB913580-x86-ENU.EXE
Windows2000-KB914388-x86-ENU.EXE
Windows2000-KB914389-x86-ENU.EXE
Windows2000-KB917008-x86-ENU.EXE
Windows2000-KB917537-x86-ENU.EXE
Windows2000-KB918118-x86-ENU.EXE
Windows2000-KB920213-x86-ENU.EXE
Windows2000-KB920670-x86-ENU.EXE
Windows2000-KB920683-x86-ENU.EXE
Windows2000-KB920685-x86-ENU.EXE
Windows2000-KB921398-x86-ENU.EXE
Windows2000-KB922582-x86-ENU.EXE
Windows2000-KB923191-x86-ENU.EXE
Windows2000-KB923414-x86-ENU.EXE
Windows2000-KB923561-x86-ENU.EXE
Windows2000-KB923810-x86-ENU.EXE
Windows2000-KB923980-x86-ENU.EXE
Windows2000-KB924270-x86-ENU.EXE
Windows2000-KB924667-x86-ENU.EXE
Windows2000-KB925902-x86-ENU.EXE
Windows2000-KB926121-x86-ENU.EXE
Windows2000-KB926122-x86-ENU.EXE
Windows2000-KB926247-x86-ENU.EXE
Windows2000-KB926436-x86-ENU.EXE
Windows2000-KB927891-x86-ENU.EXE
Windows2000-KB928843-x86-ENU.EXE
Windows2000-KB930178-x86-ENU.EXE
Windows2000-KB931784-x86-ENU.EXE
Windows2000-KB933729-x86-ENU.EXE
Windows2000-KB935839-x86-ENU.EXE
Windows2000-KB935840-x86-ENU.EXE
Windows2000-KB937894-x86-ENU.EXE
Windows2000-KB938827-x86-ENU.EXE
Windows2000-KB941568-x86-ENU.EXE
Windows2000-KB941644-x86-ENU.EXE
Windows2000-KB941693-x86-ENU.EXE
Windows2000-KB942831-x86-ENU.EXE
Windows2000-KB943055-x86-ENU.EXE
Windows2000-KB943484-x86-ENU.EXE
Windows2000-KB943485-x86-ENU.EXE
Windows2000-KB944338-x86-ENU.EXE
Windows2000-KB945553-x86-ENU.EXE
Windows2000-KB948590-x86-ENU.EXE
Windows2000-KB950749-x86-ENU.EXE
Windows2000-KB950974-x86-ENU.EXE
Windows2000-KB951071-x86-ENU.EXE
Windows2000-KB951698-x86-ENU.EXE
Windows2000-KB952004-x86-ENU.EXE
Windows2000-KB952954-x86-ENU.EXE
Windows2000-KB953155-x86-ENU.EXE
Windows2000-KB954211-x86-ENU.EXE
Windows2000-KB955069-x86-ENU.EXE
Windows2000-KB956391-x86-ENU.EXE
Windows2000-KB956802-x86-ENU.EXE
Windows2000-KB956844-x86-ENU.EXE
Windows2000-KB957095-x86-ENU.EXE
Windows2000-KB957097-x86-ENU.EXE
Windows2000-KB957280-x86-ENU.EXE
Windows2000-KB958644-x86-ENU.EXE
Windows2000-KB958687-x86-ENU.EXE
Windows2000-KB958690-x86-ENU.EXE
Windows2000-KB959426-x86-ENU.EXE
Windows2000-KB960225-x86-ENU.EXE
Windows2000-KB960715-x86-ENU.EXE
Windows2000-KB960803-x86-ENU.EXE
Windows2000-KB960859-x86-ENU.EXE
Windows2000-KB961063-x86-ENU.EXE
Windows2000-KB961064-x86-ENU.EXE
Windows2000-KB961371-V2-x86-ENU.EXE
Windows2000-KB961501-x86-ENU.EXE
Windows2000-KB967715-x86-ENU.EXE
Windows2000-KB968537-x86-ENU.EXE
Windows2000-KB969059-x86-ENU.EXE
Windows2000-KB969805-x86-ENU.EXE
Windows2000-KB969883-x86-ENU.EXE
Windows2000-KB969898-x86-ENU.EXE
Windows2000-KB969947-x86-ENU.EXE
Windows2000-KB970238-x86-ENU.EXE
Windows2000-KB970483-x86-ENU.EXE
Windows2000-KB971032-x86-ENU.EXE
Windows2000-KB971486-x86-ENU.EXE
Windows2000-KB971557-x86-ENU.EXE
Windows2000-KB971633-x86-ENU.EXE
Windows2000-KB971961-x86-ENU.EXE
Windows2000-KB972270-x86-ENU.EXE
Windows2000-KB973037-x86-ENU.EXE
Windows2000-KB973346-x86-ENU.EXE
Windows2000-KB973507-x86-ENU.EXE
Windows2000-KB973525-x86-ENU.EXE
Windows2000-KB973869-x86-ENU.EXE
Windows2000-KB974318-x86-ENU.EXE
Windows2000-KB974392-x86-ENU.EXE
Windows2000-KB974571-x86-ENU.EXE
Windows2000-KB974783-x86-ENU.EXE
WindowsInstaller-KB893803-v2-x86.exe
Windows-KB890830-V1.33.exe
windows-kb890830-v3.4.exe
Windows-KB909520-v1.000-x86-ENU.exe
WindowsRightsManagementServicesSP2-KB917275-Client-ENU-x86.exe
WindowsUpdateAgent30-x86.exe

Files in your HFCABS folder:

Files in your HFGUIRUNONCE folder:
UPHClean-Setup.msi

Files in your HFSVCPACK folder:

Files in your HFSVCPACK_SW1 folder:

Files in your HFSVCPACK_SW2 folder:

Files in your HFTOOLS folder:
7za.exe
bbie.exe
BOOT.BIN
cmdow.exe
cygwin1.dll
EXTRACT.EXE
HFANSWER.INI
HFSLIP_PRE_TZ4.CAB
HFSLIP_PRE_TZ4.CMD
mkisofs.exe
modifyPE.exe
reg.exe

Files in your REPLACE folder:

===============================================================================
HFSLIP run time: 21m35s
4.After the installation i still find the ie in the os.

Can anyone point out my mistake ?

Or just told me your successful experience with your HFSLIP.LOG.

Thanks a lot.


How to remove advertisement from MSFN

#2
fdv

fdv

    MSFN Expert

  • Developer
  • 1,111 posts
  • Joined 16-July 04
  • OS:Windows 7 x64
  • Country: Country Flag
From a fix standpoint, it looks like too many IE hotfixes in HF... I think many of those are obsolete.

But the main problem: what happens when you type a URL into an explorer window? Is SHDOCLC.DLL on the system?

The server fileset is very old, and it may have left an IE icon on the desktop. (Which should not function).

Try this mod

This will require some work on your part: inside you need to:
1. delete the existing two TXTSETUP and LAYOUT files that are for workstation (pro)
2. rename the TXTSETUP.server and LAYOUT.server files to remove the "server"
3. proceed from there

I thin you see what I mean. I just modified TXT... and LAY... and threw them into the existing set 9. See how that works.

I did this just now. Aren't you lucky :lol:

#3
nh_wzg

nh_wzg

    Newbie

  • Member
  • 21 posts
  • Joined 03-June 06

This will require some work on your part: inside you need to:
1. delete the existing two TXTSETUP and LAYOUT files that are for workstation (pro)
2. rename the TXTSETUP.server and LAYOUT.server files to remove the "server"
3. proceed from there

I thin you see what I mean. I just modified TXT... and LAY... and threw them into the existing set 9. See how that works.


After dl the new version fileset for w2k srv and del&rename some file,I got the new iso to test.

But I failed again.

Installation process error:

The entry "ncrc710.sys" in the [SourceDiskFiles] section of the INF file is corrupt or Missing.

Setup cannot continue. Press any key to exit.

Thanks a lot for FDV's fileset,it make me dig into the os again.

#4
fdv

fdv

    MSFN Expert

  • Developer
  • 1,111 posts
  • Joined 16-July 04
  • OS:Windows 7 x64
  • Country: Country Flag
Sorry about that, man.

The only reason that should come up is having a Compaq SCSI controller dating back from about 1998. You could uncomment the file in TXT... and LAY...

I was pretty careful when I made these, way back.
I even put in a file called FILES-SRVR.TXT to check against. It is possible I somehow missed something, but if it does NOT copy, and the system calls for it, then the installer wants to see it, and the only reason that I can think of right now is if it's actually needed by a device.

#5
nh_wzg

nh_wzg

    Newbie

  • Member
  • 21 posts
  • Joined 03-June 06
1.After uncommented files following the cd can boot normally.
ncrc710.sys
lp6nds35.sys
ql2100.sys
2.In the restart installing process,files following have to skip to continue the installation:
comntwks.inf
dtcntwks.inf
ntapm.inf
setup_w.bmp
winnt.bmp
winnt256.bmp
3.But i get the error message at last:
Setup can not set the required windows 2000 configuration information.
This indicates an internal Setup error.
Contact your system administrator.
4.I can not boot the os normal.
Invalid boot.ini.
Boot from c:\winnt...
In the starting windows window
Windows 2000 could not start because the following file is missing or corrupt:\winnt\system32\config\SYSTEM

You can attempt to repair this file by starting Windows 2000 Setup using the original Setup floppy disk or CD-ROM.
Select 'r' at the first screen to start repair.

Thanks for your helps.

Edited by nh_wzg, 10 March 2010 - 04:58 AM.


#6
fdv

fdv

    MSFN Expert

  • Developer
  • 1,111 posts
  • Joined 16-July 04
  • OS:Windows 7 x64
  • Country: Country Flag
ok, I think I know what the problem is. give me some time to make some fixes hopefully by weeks' end.

#7
nh_wzg

nh_wzg

    Newbie

  • Member
  • 21 posts
  • Joined 03-June 06

2.In the restart installing process,files following have to skip to continue the installation:

comntwks.inf
dtcntwks.inf
ntapm.inf
setup_w.bmp
winnt.bmp
winnt256.bmp


comntwks.inf
dtcntwks.inf
setup_w.bmp

1.Because all the listed files are all for workstation,I commented them all in LAY... & TXT...,and changed to appropriated files for server.

ntapm.inf
winnt.bmp
winnt256.bmp

I could not find listed files in server CD,then I commented them all in LAY... & TXT...,and make the ISO.

2.But i get the error message at last:
Setup can not set the required windows 2000 configuration information.
This indicates an internal Setup error.
Contact your system administrator.

Still i could not get any clues to deal with them.

Anyone can help me?

Edited by nh_wzg, 17 March 2010 - 12:15 AM.


#8
Hu$tle

Hu$tle

    Junior

  • Banned
  • Pip
  • 86 posts
  • Joined 29-June 06
Are you ever going to fix this fileset or you don't care?

#9
bphlpt

bphlpt

    MSFN Addict

  • Member
  • PipPipPipPipPipPipPip
  • 1,801 posts
  • Joined 12-May 07
  • OS:none specified
  • Country: Country Flag
Hu$tle - If you hope to ever get any response, much less help from fdv, you're going to have to learn to be a lot more polite and patient. It is perfectly OK to remind someone that you had understood that they had said that they intended to look into something, so you were assuming that either you had misunderstood or that real life had gotten in the way, and you were hoping they were OK, because you really appreciate all that they have done for everyone in this forum, for free, out of the goodness of their heart, and you acknowledge their brilliance, and you know that you are not worthy to even be bothering them about this trivial thing, and Gee, you were wondering if you might be able to do something for them to make their life easier, but you do NOT, under ANY circumstances be as rude as you just were. Now apologize! And mean it!

Cheers and Regards

Posted Image


#10
fdv

fdv

    MSFN Expert

  • Developer
  • 1,111 posts
  • Joined 16-July 04
  • OS:Windows 7 x64
  • Country: Country Flag
bphlpt has great advice for you.

I'm in graduate school, I work (in IT!) up to 10 hours a day, I have two young kids at home.
Lots going on. There are other guys on MSFN that gave up their projects because of a lot less -- "just" getting married or "just" having a kid.

And, of course, just as Tom does, I work for "free" (at a personal cost only to me).

So, yeah. It's probably something you can file under don't really care. I'll get to it, but I'm kinda busy ATM, and it's something I'd last worked on AGES ago. So it's not like the material is fresh in my mind. I have to go back and retrofit 2000 Pro material to Server and I thought it wouldn't take so long. I was wrong, it will take some time, and it won't be as thorough as 2000 Pro was. It will be more like my 2003 set that I just released a few days ago and linked to in another post.

Traveling to NYC tomorrow until Monday then working late Mon-Wed so I will not be able to look at any of that for a while. It's complex, my friend. It's not just deleting files referenced in INFs like nLite. It's careful testing and a LOT of isosizing. When most guys around MSFN have a fire under their chair they take a do it yourself approach. It IS possible if you edit SYSOC and SYSSETUP and work to compare my TXTSETUP files. If YOU want to do it, I'll host it. Otherwise it's a waiting game since no one else would use it, it's had maybe less than 20 downloads in years, and I'd be doing the work essentially for just you. So I'm putting out a welcome mat for you to give an assist. This is something I'll have to do largely from the top down all over again. So you will no doubt understand why I am in no rush and do this catch as catch can.

#11
nh_wzg

nh_wzg

    Newbie

  • Member
  • 21 posts
  • Joined 03-June 06
Today I have some time to try the old version fdvset for wnidows 2000 server with sp4.

Step 1.I overwited the files in \i386 with fdvfileset directly.Then I made the iso file and installed it in vmware.

Step 2.After skipped "ntapm.inf" in file copying process , selected the "ftp.mib" direct to virtual CD\i386\ftp.mi_ manually, canceled the "desktop.scf" copying , I installed windows 2000 server with fdvset successfully. IE had been removed and with no any new windows 2000 updates on it.

So keep the interest in this old os and make fun in the research.

#12
PROBLEMCHYLD

PROBLEMCHYLD

    The Resurrector for old Windows OS

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,532 posts
  • Joined 07-October 05
  • OS:98SE
  • Country: Country Flag
What happen to the 2000 server fileset on your site? I don't have my 2000 server yet but it should be here by Thursday.
I want to test it out when my cd comes. Thanks

Believe God is the Alpha and Omega.
Believe Jesus Christ died for our sins.
Repent for your sins now or there will be
BLOOD

The Path to God


U98SESP3 03-11-2013


#13
nh_wzg

nh_wzg

    Newbie

  • Member
  • 21 posts
  • Joined 03-June 06
I downloaded the oldest windows 2000 server fileset in my HD from fdv site long time ago.

If you could not find this version in fdv site i thought a new version maybe is coming up.

If you wanted to test with the old version you can sent me a mail for it.

Edited by nh_wzg, 03 October 2011 - 04:29 AM.


#14
ebernard

ebernard

    Newbie

  • Member
  • 14 posts
  • Joined 30-July 06

Donator

Hi,
I got the same error message with Windows 2000 Pro (workstation):

Setup can not set the required windows 2000 configuration information.
This indicates an internal Setup error.
Contact your system administrator.


I used hfslip-1.7.9.cmd and the file set fdvfiles-win2k.zip,
which FdV kindly sent me on April 22, 2010 and has size of 3.172.851 bytes.

Attached is the HFSLIP.LOG, which shows I tried to use IE6 updates.
The reason I included IE6 updates is: I need to install Norman Security Suite, which refused on my slipstream CD-installation with only the IE5 updates.
FdV himself suggested this specific program may need the IE6-versions of some system files. I'm not capable to find out which IE6-update-files I would need to accomplish that, so I took them all.
Apart from the IE6-updates, I included:
  • DirectX9c (standard),
  • MDAC,
  • MSXML,
  • rootsupd.exe,
  • UPHClean-Setup.msi
  • script-updates: only 5.6 (which is in IE6)
  • In 'Replace' I put the NTLDR and NTDETECT.COM from Windows XP, required to facilitate dual boot

Can anybody please tell me what I have done wrong?

Thanks in advance for your time and attention!

kind regards
Eveline

Edited by ebernard, 01 June 2010 - 03:10 PM.


#15
PROBLEMCHYLD

PROBLEMCHYLD

    The Resurrector for old Windows OS

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,532 posts
  • Joined 07-October 05
  • OS:98SE
  • Country: Country Flag
?

Edited by PROBLEMCHYLD, 24 September 2011 - 12:02 PM.

Believe God is the Alpha and Omega.
Believe Jesus Christ died for our sins.
Repent for your sins now or there will be
BLOOD

The Path to God


U98SESP3 03-11-2013


#16
PROBLEMCHYLD

PROBLEMCHYLD

    The Resurrector for old Windows OS

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,532 posts
  • Joined 07-October 05
  • OS:98SE
  • Country: Country Flag
?

Edited by PROBLEMCHYLD, 24 September 2011 - 12:01 PM.

Believe God is the Alpha and Omega.
Believe Jesus Christ died for our sins.
Repent for your sins now or there will be
BLOOD

The Path to God


U98SESP3 03-11-2013


#17
PROBLEMCHYLD

PROBLEMCHYLD

    The Resurrector for old Windows OS

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,532 posts
  • Joined 07-October 05
  • OS:98SE
  • Country: Country Flag
?

Edited by PROBLEMCHYLD, 24 September 2011 - 12:01 PM.

Believe God is the Alpha and Omega.
Believe Jesus Christ died for our sins.
Repent for your sins now or there will be
BLOOD

The Path to God


U98SESP3 03-11-2013


#18
PROBLEMCHYLD

PROBLEMCHYLD

    The Resurrector for old Windows OS

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,532 posts
  • Joined 07-October 05
  • OS:98SE
  • Country: Country Flag

Today I have some time to try the old version fdvset for wnidows 2000 server with sp4.

Step 1.I overwited the files in \i386 with fdvfileset directly.Then I made the iso file and installed it in vmware.

Step 2.After skipped "ntapm.inf" in file copying process , selected the "ftp.mib" direct to virtual CD\i386\ftp.mi_ manually, canceled the "desktop.scf" copying , I installed windows 2000 server with fdvset successfully. IE had been removed and with no any new windows 2000 updates on it.

So keep the interest in this old os and make fun in the research.

If you take the desktop file from fdvfiles-win2k.zip
the ntapm.in_ file from Windows 2000 Pro then you should not get any errors.

Believe God is the Alpha and Omega.
Believe Jesus Christ died for our sins.
Repent for your sins now or there will be
BLOOD

The Path to God


U98SESP3 03-11-2013


#19
PROBLEMCHYLD

PROBLEMCHYLD

    The Resurrector for old Windows OS

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,532 posts
  • Joined 07-October 05
  • OS:98SE
  • Country: Country Flag
New topic

Edited by PROBLEMCHYLD, 05 June 2012 - 10:07 AM.

Believe God is the Alpha and Omega.
Believe Jesus Christ died for our sins.
Repent for your sins now or there will be
BLOOD

The Path to God


U98SESP3 03-11-2013





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users