FDV Fileset and Windows 2000 Server

[orge]

Hi,

I'm trying to use the fdv fileset with win 2k server, but I'm having some difficulties. I'm using hflsip to patch and update the source with the appropriate hotfixes. However, when I run the patched installation it installs professional instead of the server version. This is probably an error relating to the txtsetup.sif and layout.inf files which are overwritten by the fdv patch. I'm going to try removing these files from the fdv fileset, to make sure, but I'm guessing that there's probably some changes which I need to replicate to the server equivalents.

Thanks,

James

Edited February 23, 2006 by orge

[Tomcat76]

If it's just that, then it's pretty easy to solve. Do a find/replace in both files...

cdrom_ip.5 --> cdrom_is.5

Windows 2000 Professional --> Windows 2000 Server

You might need to use the original SETUPP.INI file as well but I'm not sure of that.

[orge]

If it's just that, then it's pretty easy to solve. Do a find/replace in both files...

cdrom_ip.5 --> cdrom_is.5

Windows 2000 Professional --> Windows 2000 Server

You might need to use the original SETUPP.INI file as well but I'm not sure of that.

Ok. I'm actually using this image over ris, so I hadn't had noticed any problems with the cdrom files. Good call on the professional -> server and setupp.ini files though.

However, it appears that the problem lies with my txtsetup.sif and, maybe, layout.inf files

I tried to replicate lines which were commented out in Fred's files, but I'm getting the following error at the start of the "yellow bar" phase:

The following value in the .SIF file used by Setup is corrupted or missing:

Value 0 on the line 0 in section [sourceDisksFiles]

Setup cannot continue. To quit Setup press F3.

I've googled the error msg, but haven't managed to dig anything up. Since it's working with the original files, I'll cut/paste/run until I find the offending line.

Cheers for you help,

James

Edited February 24, 2006 by orge

[tommyp]

It a bit more than the dosnet and txtsetup files. You need to also check the sysoc.inf and syssetup.inf files as well.

[orge]

Ok. There was some kind of "bug" in my txtsetup.sif file, but I've managed to get it working now. I had another couple of glitches during the setup, but nothing terminal.

Whilst this was mostly straightforward, it was a bit of a pain commenting out the lines in the txtsetup file. I can see how you could write a script for most of the entries, but there's a few cases where the names between server/professional versions change. Consequently, its more thorough to do it by hand - this took over an hour!

Do you think there is any demand for these files? If there was, I'd want to tidy them up a little and resolve the glitches. Otherwise, that's a wrap.

Cheers,

James

[tommyp]

I don't think there is a need for modified files. There is something called HFCLEANUP that can be used to do the same thing. .... well 95% of the FDV fileset. The HFCLEANUP works with 2k, xp and 2003. Give me a few days to test.

Edited February 24, 2006 by tommyp

[Tomcat76]

However, it appears that the problem lies with my txtsetup.sif and, maybe, layout.inf files

That's exactly what I was saying. Open TXTSETUP.SIF and LAYOUT.INF in Notepad (for example), then replace every instance of "cdrom_ip.5" with "cdrom_is.5" and every instance of "Windows 2000 Professional" with "Windows 2000 Server". DOSNET.INF should be fine. I haven't checked the other files that TommyP mentions. Edited February 24, 2006 by Tomcat76

[orge]

I don't think there is a need for modified files. There is something called HFCLEANUP that can be used to do the same thing. .... well 95% of the FDV fileset. The HFCLEANUP works with 2k, xp and 2003. Give me a few days to test.

Ok. I'm getting errors with my modified syssetup.in_ and sysoc.in_. So, maybe it would be easier to let the hflcleanup routines take care of most of this. Do you know which files in the fdv fileset I need to keep if I want to removie i.e, though?

Cheers,

James

[orge]

I've got this working with hfcleanup, but it's not quite as clean as the original fdv files. Is there a list of files/settings which relate solely to removing ie? I can't find anything on the board and the comments in FDV's files don't appear to group them by this function.

On a plus note, using HFCLEANUP does give a lot more control over the source. This was much appreciated as a dependency means that I will probably have to retain IIS

Good work guys.

James

[orge]

I'm still having some problems with this...

I've tried it just about everyway you can imagine. I've had a go at producing an fdv fileset from server's files - I've commented out the following files from layout.inf (L), txtsetup.sif (T) and syssetup.inf (SS):

asctrls.ocx L + T

cdfview.dll L + T

iepeers.dll L + T + SS

iesetup.dll L + T

ieuinit.inf L + T

imgutil.dll L + T + SS

inetcpl.cpl L + T + SS

inetcplc.dll L + T

inseng.dll L + T + SS

mshta.exe L + T

mshtml.dll L + T + SS

mshtmled.dll L + T + SS

mshtmler.dll L + T

mshtml.tlb L + T

msieftp.dll L + T + SS

occache.dll L + T + SS

webcheck.dll L + T + SS

However, the installer chokes at the start of txtsetup with this (unhelpful) error:

The following value in the .SIF file used by Setup is corrupted or missing:

Value 0 on the line 0 in section [sourceDisksFiles]

Setup cannot continue. To quit Setup press F3.

If I use hfcleanup in conjunction with these files, then I don't get an error at this stage, but the installer chokes later on when it tries to access the syssetup.inf file - after checking the source, I can see that this is because it is blank??

Having tried almost every combination I can think of, I'm at a loss as to what is wrong.

Thanks for your help,

James

[orge]

Sorry, my mistake...

Edited March 6, 2006 by orge