Jump to content

Windows 2000 "Hotstream" Project


Gurgelmeyer

Recommended Posts

@At0mic - Thanks - I appreciate it a lot :)

@The BigSabowski - Thanks to you too :) - about the MSURP1: you dont necessarily want it. It shows up on WU because

- I don't include the FS Filter Driver - a very DRM-friendly component, which runs in kernel mode and was introduced by the MSURP1 - three days before mainstream support ended. It has never been part of w2k anyway.

- I rolled back the HALMACPI.DLL to a previous post-sp4 version. MS probably won't fix the CPU/HALT problem (can't even seem to find a KB on it), and the problems which are fixed in the URP1 HALMACPI are also fixed in the post-sp4 version included.

Otherwise the MS URP1 is fully included. But anyone who wants want better DRM support should be allowed to dl the official MS URP1 - I'm deliberately not doing anything to suppress it on WU B)

@x243 - Those packages are only temporary until USP 5.1 - but try /q /n /z :)

Best regards

Gurgelmeyer

Link to comment
Share on other sites


@War59312 - Not sure what you did, but today I am able to download, no problems.  Thanks a bunch - been excited to try this out!!

New IP address maybe. :unsure:

And no appariently they dont ban the entire ISP just ranges that are known to belong to the abusers. At least that's how it looks to me looking at the logs ATM. BTW trust me you would know if I banned you. ;) Nice 404 or 403 page, depending on how I ban you. :yes:

Or if I feel nice. :lol:

http://willsdownloads.com/errors/banned.php

Edited by war59312
Link to comment
Share on other sites

You're welcome ;)

Any roumours about the re-issued MS URP1 yet? I'm planning a Service Release 1 of USP 5.0 when the time comes - I also got a handful of August 2005 hotfixes for USP 5.0 SR-1 that wont be part of the reissued MS URP1 (THANK YOU TO YOU-KNOW-WHO-YOU-ARE - you ROCK :thumbup). Fixed a minor error in MS URP1 (it suppresses OE55/Q823353 on WU, but doesn't include all the shared files from this update).

Otherwise I'm working on version 5.1 - this one will include BITS 2.0, MSI 3.1, WUv6 ActiveX controls, IE6, more security updates etc.

Best regards,

Gurgelmeyer B)

Link to comment
Share on other sites

Perhaps I'm doing something wrong, but I can't install the Recovery Console locally using a slipstreamed SP5 disc. At first I thought it was because I used nLite to remove some features, but even using a complete CD, I can't get it to install. The error is that "setup was unable to build the list of files to be copied" the data is invalid. I always install the Recovery Console locally at the guirunonce point and it has always worked.

Link to comment
Share on other sites

Do you mean it doesn't work during a "x:\winnt32 /cmdcons /unattend" installation or when Windows itself is installed unattended? I was not able to install the Recovery Console even using "x:\winnt32 /cmdcons."

Currently I'm running Windows XP due to another problem I found with SP5, which may or may not be related to nLite's downsizing of the source. Last night when I thought I had the "perfect" SP5 unattended CD, I decided to burn it and install it on my main machine. During the initial stages of textmode setup, Windows would not detect the size of my 200GB harddrives correctly. They were limited to 131xxxMB (i.e. 128GB) and I could not partition the drive correctly. So I made one 128GB NTFS partition and let Windows install. I found that GUI mode WIndows detected the drives capacity just fine. I figured there may be a problem with the atapi.sys, or is there another file that governs drive detection during textmode setup? The problem didn't appear in the multiple trials I did in Virtual PC, but then I was working with only a 16GB virtual hard disk. I've tried slipstreaming SP5 from a original (no SPs) Windows 2000 source, and then also slipstreaming SP5 into a Windows 2000 SP4 source, but the drives are still detected as 128GB in textmode.

As for WINNT32.log, this is all that appears after trying to install the Recovery Console:

Detected 192 MBytes of memory.

Edited by x243
Link to comment
Share on other sites

Hi :)

Usually all ATAPI drives are limited to 127GB in W2K - this is a known limitation (nothing to do with nLite or USP5). You may however enable 48 bit LBA (>127GB support) in SP3 and later by adding the registry setting described here:

http://support.microsoft.com/default.aspx?...kb;en-us;305098

(It might be possible to edit the SETUPREG.HIV to enable 48 bit LBA from text mode setup and onwards.)

I have no trouble with i386\winnt32.exe /cmdcons - strange :blink: I'll keep testing though - and if there's a bug I'll find it!! Trust me ;)

Best regards

Gurgemleyer B)

Link to comment
Share on other sites

I haven't used Windows 2000 since I went AMD 64 last year. I could almost swear though that I never had a problem in textmode with drives larger than 128GB... I have been using 160GB and larger drives for several years now and Win2k was my OS of choice until last year. Editing the LBA in HIVE file was something I had thought of, but does that actually have any effect in textmode?

Link to comment
Share on other sites

That went well - now booting W2K from a 160GB system partition - are we really the first to think about this?? Maybe - anyway, it's a nice feature for USP 5.1 :D

Anyway - also tested the winnt32.exe /cmdcons /unattended from GuiRunOnce - it does seem to work. Are you sure you expanded the svcpack.in_ before you did anything else with the slipstreamed image? It is not empty - it installs an awful lot of .cat's.

Best regards,

Gurgelmeyer B)

Link to comment
Share on other sites

I'm not sure what you're saying about svcpack.in_. Do you mean the inf file needs to be extracted into the i386 directory, or it needs to be cleared completely? I was under the impression that changing anything in that file would cause a problem during installation, let alone during a Recovery Console install.

Link to comment
Share on other sites

I think I've narrowed it down. nlite is causing the Recovery Console problem. If you choose to remove Windows 2000's SCSI drivers (I never use a single one of them), it screws up the Recovery Console file list later on. There must be a remnant of the file list in some SIF file or something even after nlite removes them. I removed more than just the SCSI drivers, but I'm pretty sure that is where the problem lies.

Edited by x243
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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