Talk:Windows Server 2003 build 3615

OK. I copied the file 3615 build driver.cab to build 3604 from the file driver.cab copied the file only ntkrpamp.exe, ntkrnlmp.exe, and ntoskrnl.exe. The ntdll.dll file from driver.cab I can not find. If ntdll.dll is missing from driver.cab. I can first delete from 3604 build files ntkrnlmp.ex_ and ntoskrnl.ex_. I can copy the driver.cab and ntdll.dll files from this build 3615 to the 3604 build and then from the driver.cab 3615 file I copy ntkrpamp.exe, ntkrnlmp.exe, and ntoskrnl.exe. I will be grateful in advance.
 * NTDLL.DLL is in DRIVER.CAB, maybe your copy is broken.--Winins (talk) 16:49, 10 October 2019 (UTC)

OK. I copied the driver.cab and ntdll.dll files from this build 3615 to build 3604, then copied the files from dirver.cab 3615, ntkrnlmp.exe, ntoskrnl.exe, ntkrpamp.exe. and the build should be installed.

Hey releaked
I found uncorrupted copy build 3615. please see https://archive.org/download/windows-.net-whistler-server 16:15, 6 May 2020 (UTC)
 * I had a look. There are the same corrupt copies. For all three editions: Enterprise, standard and web server. BenjiMadden7850 (talk) 16:45, 6 May 2020 (UTC)
 * I checked one file from build 3615. 100% full ISO-image. 195.191.235.159 16:49, 6 May 2020 (UTC)
 * We need an uncorrupted copy of build 3615. 195.191.235.159 16:55, 6 May 2020 (UTC)
 * In case you haven't got the idea. Check I386/EULA.TXT in web server, and VALUEADD/VALUEADD.HTM in all three editions. Then take a look in 3621's (uncorrupted) VALUEADD/VALUEADD.HTM. These are just the same corrupted 3615 isos we have seen before...
 * BenjiMadden7850 (talk) 16:59, 6 May 2020 (UTC)
 * Just take these files and start the installation? 195.191.235.159 17:00, 6 May 2020 (UTC)