Daemonforce

OMFG thank you! :'( Ahahhaha! I've needed this for a long time.

It doesn't matter. I'll probably wind up getting a copy by any means necessary and then toss it after I have VistaPE. Vista isn't for me and it isn't for anyone that knows what they're doing or anyone that knows anything about "security." I just need it to improve on recovery standards. Every few years one of these Microsoft Windows NT operating systems are released. It's always one step back and two steps forward(in that order). Yet it's always half a step away from p***ing me off along with the entire developer room since nothing runs correctly until the first service pack is released. What a pain. I'll be up to Windows XP SP6 before I ever switch to Vista.

NT 4 is the only reason anyone could ever understand this statement. Fdisk format reinstall, doo dah! DOO DAH! You should keep everything managed on a reliable OS anyway and to be even more specific: Completely OFF of the boot drive. With the stuff we can put NT4 on, we don't need paging files anymore. With the old crap like 66MHz boxes...NT4 could be challenged. I found this somewhere... Pseudo slipstream in WinNT4 The slipstreaming of service packs is not available with WinNT4, as it was first introduced with Win2k. But it is still possible to do some tricks: Update these files on the install-image with files from the service pack (SP4+), as it will enable AGP support, remove 8gb limitation etc. atapi.sys fastfat.sys gdi32.dll hal.dll hal486c.dll halapic.dll halast.dll halcbus.dll halcbusm.dll halmca.dll halmps.dll halmpsm.dll halncr.dll haloli.dll halsp.dll halwyse7.dll kernel32.dll ndis.sys ntdll.dll ntkrnlmp.exe ntoskrnl.exe SETUPDD.SYS tcpcfg.dll user32.dll win32k.sys winsrv.dll Install the service pack unattended (SP4+) Place the service-pack file in this directory: X:\i386\$OEM$\SP4 Create a text file CMDLINES.TXT in this directory: X:\i386\$OEM$ Open the text file CMDLINES.TXT and add these lines: [Commands] ".\sp4\sp4i386.exe -z -u" More Info MS KB Q168814 Make a shared directory with the original WinNT4 install files and extract the contents of the service pack to this directory. Then use the shared directory when adding components (after install), so you don't have to apply the service pack for every change. That's great, but what if it's just going to be a single machine or the master computer(ew!)? I'm going to find a way to integrate the full service packs manually if I have to.

I have a copy of Windows NT 4.0 Server +SP1 and I've been trying to get it into a stage where it can be tested in VMware without any hassle. I have been looking for guides on updating this old OS and how to update it, but all I find is the $OEM$ method. I don't like that. I want to create a direct integration the way service packs effect post-Win2000 distributions. I was wondering if anyone is willing to post a guide on how to do this since I find a few complications along the way. Windows 2000 doesn't have IE6 pre-packaged, so I'm probably going to run into that crap and try tricking XPCREATE into updating IE5/6 into NT4... Oh wait yeah I am, because I keep finding stuff that says NT can't do a direct update from pre-SP3 straight to SP6a. I currently have these: NT 4.0 Server +IE4.0 +SP1 (FPP) Service Pack 4 Service Pack 6 Internet Explorer 6 redistribution package nLite XPCREATE HFSLIP Enough courage to mess with DOSNET and TXTSETUP if and when necessary. Flash 8 VMware A lot of time Something tells me that IE6 isn't going to be compatible with this project right off the bat and I'm going to need to hunt down IE5 redistribution files...I'm not so concerned about functionality between the server and Microsoft, as long as everything else works the way it's intended. I would like to begin by integrating the appropriate service pack to annihilate any installation issues that SP1 gives me and then slipstream IE5/6 if necessary/possible and then integrate SP6 if the first step isn't already taken care of. I see ONE guide that claims it's safe to overwrite the primitive TXTSETUP files to fix installation procedures, but it's a bit hazy to say the least. Has anyone else thought about trying this and what steps should I be taking before attempting to make a new build? I know this can be done because I've seen it done before. I just never cared for it because I didn't have NT 4 at the time. It looks like NT 4 would have been my choice OS to start out with instead of Win95 back in...The day. This OS may still be in the graveyard, but not according to 30% of small businesses that are short on upgrade funds. o.O

Ok from what it appears, the Data tag was killing it. I have my setup disc in debug mode and I removed the Data tag. Now it just hangs with setup options and a message at the bottom Searching for previous versions of Microsoft Windows. Does anyone know what's going on here? =/

It failed again. o.O I can't figure out what I'm doing wrong. I tried getting the assisted unattend file going and it failed too! WTFz0rz?! :'( I guess NT can't be setup with an unattend after all. =/

*pokes SP1 integrated installer* o_O I am well aware of this, but it's unsupported anyway. The CD name suggests I have the NT Alpha. Yeah those are perfectly valid according to NT's OPK. It would be nice if there was a sticky in the Unattend forum of all the available codes and switches for WINNT.SIF. I'm thinking I'm missing a parameter instead of having invalid info, but I could be wrong. The SIF I posted is a valid export of NT's Setup Manager. It's crashing the text portion of setup! WTF? =/

I knew there was something missing and I didn't expect it to be that. =/ I'll try it though. My topic subtitle contains NT4 Server and that's part it. I have the NT4A disc that appears to allow installation on ANY computer. o_O Alpha, i386, MIPS, PPC...If you look in the support folder you'll find the OPK for it. If the problem is that it doesn't produce that vital tag that you mentioned, there may be a serious problem...Oh well...Revisions go unfixed without me. Are you sure about that? =/ There must be a way to at least slipstream it manually. Ew. O_o

Hey I've been trying to get through a really weird problem today where my unattend file is causing a crash one way or another upon disk drive detection in vmware. I try narrowing down the problem but I still can't get anywhere with it. Txtsetup crashes at setupdd.sys with this file: [Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes" [unattended] OemPreinstall = yes NoWaitAfterTextMode = 1 NoWaitAfterGUIMode = 1 FileSystem = NTFS ExtendOEMPartition = 1 KeyboardLayout = "US-International" [userData] FullName = "Windows User" OrgName = "" ComputerName = * [GuiUnattended] OemSkipWelcome = 1 OEMBlankAdminPassword = 1 TimeZone = "(GMT-08:00) Pacific Time (US & Canada); Tijuana" [Display] ConfigureAtLogon = 0 BitsPerPel = 16 XResolution = 1024 YResolution = 768 VRefresh = 60 AutoConfirm = 1 [Network] DetectAdapters = "" InstallProtocols = ProtocolsSection InstallServices = ServicesSection JoinWorkgroup = WORKGROUP I know there is either something missing or I'm making an invalid arguement somewhere because something is wrong with it. Does anyone know what I'm doing wrong? Oh yeah, on an unrelated note has anyone found a way to integrate SP6 into Windows NT? I really need to do that. =/

Thanks...That's all I needed to know.

Ahaha! <3! No it's vague because it isn't mentioned what they apply to. Sure 10 hotfixes is no big deal on XP Pro, but what about Windows 2000 Pro? Windows 2000 Adv Server? Windows XP MCE? Windows Server 2003....... 10 things is simple as long as it isn't 10 things that can go wrong and 10 things to check. =/

Ahahahahaha! Great topic, horrible poll. I use a virtual machine for testing new builds with hotfix integration and I release them as test candidates. To be honest I not only reinstall Windows but several flavors of Windows each day. The host operating system gets reinstalled once a year on my network controller and whenever I feel like it on my development box. That comes out to about once every 6 months. I look for performance gains when using virtual machines. So far MCE2005 gives absolutely no problems as the host OS. Windows XP Home limits me too much while Pro is a memory hog...I wonder why. o.O

I've been busy this month preparing fully unattended corporate installations for all of my Windows NT discs so that I don't have to play licensing games every time there are several new computers built or brought in that have no OS installed. I have found that changing setup information to read corp keys just makes the question go away entirely. I have a corp key for XP Pro and a corp key for Windows Server 2003, but what I've noticed is that XP MCE/TPC are different with this procedure. I set them up to take corp keys and I test the installation but I get prompted with a 60 day grace period. I'm just wondering if there are any real corp keys for MCE and TPC. It would be great to know this once and for all. It would be a great help if any keys like this actually exist and behave like my XP Pro and 03 corp keys.

Setup a virtual machine for him to destroy instead. That's what I do with all of my guests that connect to this machine. Since I test so many distributions with vmware, it also seems like a good tool to remove the boat from the leak. Or just ban his a**. That ISTbar is some nasty spyware. The real problems arise after getting rid of it, so I usually just reformat. =/

This is what bothers me about SATA devices. I didn't feel any safer about hot-pluggable until I noticed it on the exterior of a mainboard panel. Hot-swap or hot-kill? USB doesn't bother me as much because the components ya know...Don't actually go inside of a computer. O_o

To be honest, with my experience I say it could be any number of things. Anything from a faulty ram/files to something sent over the network. We won't know until the bluescreen.

Computer Properties > Advanced > Startup and Recovery > Automatic Restart TURN IT OFF! *waits on sarav to go hal again*

I don't see the point. =/

I have the code for it but TXTSetup still screws up copying in BSOI. The files copy over though. Either way it doesn't matter. I still get prompted to install WGA. What really kills this is I don't know how to install INFs as a script and installing the WGA INF fails anyway. =/

I found some information that only states the obvious. I think I just figured out my install problem though. I'll test it tonight. Grrr...Same error. I don't want to start messing with install packs or any preset stuff. I just want to know the TXTSETUP parameters to install LegitCheckControl.DLL and GWFSPIDGen.DLL from %cdroot%\i386 directly into %Windows%\System32. Setup wangsturbates during setup because it can't find my files. I once had it at the point where setup wouldn't halt and the file copied over, but I was missing the other file and I got prompted to install WGA again. Test 2 ----------- Ok screw that...TXTSETUP is griping about legitche.dll(My rename:)) and it copies over anyway. I decided to just skip the file and boot into PE and notepad sees the file at T-39! WTF?! o_O

FTP Nothing is wrong with it. It's just that the FTP part of IIS is fux0r3d once SP1 is installed. I have no idea why this happens. People used to be able to access my FTP, Now they just get OK'd and then the connection immediately gets KO'd. x_X' I don't have this problem in Windows .NET Server or Windows Server 2003 pre-SP1.

2000 is ok but old. At least it like clustering. 2003 just p***es me off to no end. It doesn't belong on an old 400MHz K6 box and I'm starting to believe it's time to upgrade and overclock a 550 just to keep up with minimum requirements(SQL Express) and speed resources. >.<' I have a 2003 box switching back and forth every month at home set as either a web server or domain controller. For some reason FTP is broken in IIS 6.0 in Windows Server 2003 but it's absolutely perfect in Windows .NET Server 2003. What a failure. Now I know SP1 did something to it. >.<' It's also a problem

It's actually a great backup storage and web server on a domain. I didn't get Windows 2000 Advanced Server until later, so the upgrade will probably happen. I make it my duty to support a minimum OS count: 3 Windows workstations 3 Windows servers 2 live distributions Just waiting for Longhorn server so I can toss NT 4. NT 4 doesn't eat a lot of resources though.

*bump* No one can point me in any direction with this? I'm open to any suggestions. How does HFSLIP and XPCREATE integrate CABs into installations? =/

I was wondering why this was only happening on NT 4.0. o_O Are there more parameters for partitioning or is this it? Oh yeah, remember to make that Unattend.txt into a WINNT.SIF.