Daemonforce

Yeah I have a problem and its name is Dxdiag. o_O Also missing pieces from the would-be-broken Windows 2000 OS. I'm assuming you use msconfig just for startup services instead of boot commands, driver assignment, system services, 16-bit support... I'm not going to argue. I'm too lazy. =/

OMFG! GreenMachine's XPCREATE utility does exactly what I want for Win2K! o_O GreenMachine > foos <3! It worked flawlessly and very clean on Professional. Now I'm going to do the same on Advanced Server. ' I don't need any of this help for my XP builds, but I'm going to see if XPCREATE does a better job than manual integration. I like this a lot. I get a very clean hotfix/sp/utilities upgrade straight from installation and the control panel records each of these as they're added. I started looking around for anything it could have possibly missed and everything went without a halt. I get that nice unwrapped-from-box feeling as it installs and IE6 even pops up that it's carrying out the installation procedure. Even better I got the .NET package integrated with it. There isn't a mess of INF files scattered in the i386, OMFG! DirectX9c & WMP9 actually installed too! O_O But I get two errors in dxdiag. It seems to be a problem with Win2K and the DX9c redistribution. Some security updates will whine even if I integrate them: Security Update for Microsoft Data Access Components (KB832483) Security Updates for Windows 2000 (KB899587) Security Update for Windows Journal Viewer (KB886179) Windows Malicious Software Removal Tool - September 2005 (KB890830) I don't understand why for those first three, but I'm fine with this. At least 5MB of network activity from a new installation won't be as bad as 70MB from said installation. It's bad enough I'm forging my own resource on a dialup connection, imagine how long this would take on about 40 machines all sharing a DSL connection. Ewwies. x_X' Anyway...This.........Rocks! o_O DX9c is the only issue and it's probably some problem with the source. I'm going to try integrating dx9a this time. Weeeeeeeeeeeeee!

I want to do the same for Vista beta 2, but I don't see any way of getting any version of the Ximage utility to work on any of my Longhorn builds. I'm pretty much going to have to get beta 1 to extract a 5xxx built LonghornPE. Is there any way of getting the bootmgr to point to an already open LHPE? I believe the contents are in the open as soon as you boot the DVD and can be copied to a network share. Has anyone tried extracting LHPE from builds later than beta 1?

Yeah...My network is pretty bogged down right now(Gee I wonder why! ) and I want the last week of my life back. =/ Updating has just been one big problematic hassle and it shouldn't be. Right now I'm thinking of dropping support for Win2K family permanently. Not even Windows NT or XP are this bad.

Yeah I'll admit it's a hassle. Hell I don't even use the .NET/W2K3 PE and I know my current one is better. 4051 PE is a bit out of the now, but it's reliable for what I do with it, and I like it. There aren't a lot of people that can actually say that and mean it. Personally I'm thinking of going back to this crappy PE because of compatibility...Which shouldn't even be an issue.

Yeah...Type 1 and type 2 hotfixes. The kind that do not integrate are pretty obvious, but I need to figure out how to slipstream them anyway. I don't either. I don't even use Win2K. I'm just trying to keep WU happy. ...................... And....The local network. o.o' You'd be surprised how annoying a single 1MB file x20+ can kill activity every second Tuesday when your main connection suddenly has bandwidth lower than 10KB/s. Not needed for me. So far so good. I just need to figure out hot HFSLIP did it and I'll be fine. Link! NOW! o_O

Billboard? o_O You mean that thingy that displays WINDOWS 2000 $FLAVOR on a white background? o_O I'm very unorthodox with everything I do, but I believe what you're looking for exists in msgina.dll! Do NOT copy over! o_O Just load shell32's icons over from vista's shell32.dll archive.

Yeah. I know it's a pain, but this isn't working. It needs to be done! ' If I knew how to slipstream Type-2 packages, I could restart from there. Oh yeah...I won't have to create the INFs for reg entries.

Windows 2000 doesn't have an msconfig. Here's an idea, go get your XP CD and rip the msconfig from that or better yet an XP beta. If you don't want msconfig from XP, just run startup.exe instead. It's somewhere on that XP disc. o_O

Windows Media Player 9 didn't install. Plus the registry has signs of HFSLIP. Ew. x_X' I'm going to attempt to integrate only DirectX, IE6 and WMP9 this time. Then I'm going to see if I can eliminate all traces of HFSLIP to clean up the installation. Then manual hotfix integration. This is exactly why I didn't want to use HFLSLIP in the first place. Too much to reorganize.

So far so good. Nothing pops up during Start Menu Installation. During Component Registration a big black HFSLIP prompt comes up and completes the hotfix process. Any way of shoving that into the background or making it run silently in an unattend? o.o

I grabbed it from my network drive. It's fine. Now I need to figure out why my network is crapping out. Ok I completed installation of SP4 and removed the SP4 installation path before running HFSLIP again. It seems to have worked without any errors generated. DX9C integrated, IE6 integrated, WMP9 integrated...Now I need to test this and see if I get any errors in setup. In which case I'll just remove Outlook and Internet Explorer completely. I'm sick of covering my a** at the end of every year just because of a bunch of screwups in Microsoft that can't release a single KB to be integrated without it being a hassle. I'm going to test my "SP5" ISO in VMWare now. Oh yeah...Nice HFSLIP INFs in the i386. There needs to be a better way to organize this crap so it looks like Microsoft actually released an SP5. I guess it's not going to happen until I start editing files. o_O

It's integrated into Windows XP, there should be a way of doing the same for Windows 2000. It's not just replacing CABs thing. Daemonforce I advise you to give HFSLIP one more try. It's not as complicated as it looks at first. Just run the script and place files in the folders that appear after first click on it according to the instructions on fdv's page. The script will integrate nearly all you want automatically (IE6 and DX9c, WMP9 should to be installed separatelly). If you don't want hot-fixes just don't use them (there is only one exception - Windows2000-KB891861-v2-x86-ENU.EXE is needed for integrating IE with this script). The script will INTEGRATE directly in the source (there won't be any install packages in any folders on your disk if you want). It works for many users and if you have any questions or issues just ask in HFSLIP Forum, tommyp and fdv are very responsive and will help you. If you need very simple instructions I can help you also I'm going to try this again...But it's not going to be pretty. x_X' It's pretty **** bad when a serious problem is a web browser...

That's for installing the setup on a network drive! I want to integrate Internet Explorer 6+SP1 directly into Windows 2000 Professional!

Thanks...Now I just need a way of slipstreaming IE6SP1 into a new Windows 2000 archive. I'm not going through HFSLIP because of the complications. I would be happy enough with IE6, DX9c and WMP9 slipstreamed. I'm going to look at how to replace CABs. o_O

No you may not. Too big. First I need to find the full IE6 distribution package for integration. I don't know where to find the Network Installation file on Microsoft's site.

I've been attempting to make a FullUnattend installation of Win2KPro_EN and I noticed that I've run into quite a critical problem: It's old. ...................... I have the original ISO and I'm slipstreaming service packs and updates into new archives and running them in VMWare. After the SP4 slipstream and integrated hotfixes in this order: KB842773 KB894320 KB893803 KB890046 KB893066 KB896358 KB896422 KB897715 KB883939 KB891861 KB901214 I receive two errors in setup: inetcomm.dll corrupt/missing in C:\%WINDOWS%\System32 msoe.dll corrupt/missing in C:\Program Files\Outlook Express ............... It's not that I have a problem with Outlook express....Or these errors....I don't even use Outlook. That's not the problem. It's a FullUnattend! I don't want 20+ machines synchronously halting roughly 10 minutes in setup just for someone to hit the spacebar twice just to complete setup over a large network. I want the following updates integrated in my Win2K installation without any halts or issues right after Windows 2000 is deployed(if that's at all possible): +.NET Framework 2.0 +All "critical" updates that Windows Update utility whines about post SP4 (Is there a particular order?) +DirectX 9C Redistribution +Internet Explorer 6 with or without SP1 (I can't find either) +Java 2 Redistribution +Microsoft Anti-spyware +MSN Messenger +Nero 6.6 +Quicktime 7 +Shockwave +SQL Express +Symantec Antivirus CE 10 +VB6 Runtime +WinACE/WinRAR +Windows Journal Update +Windows Media Player 10 It's a lot to ask, but I was wondering if anyone could at least list the Windows 2000 updates I need and in some particular order.

If you delete these files, then most likely yes. Are you making a new bootscreen or something that actually changes upon detection? =/

You can hack away the minimum installation requirement, but you'll never hack away the minimum runtime requirements. I believe an NT kernel needs a bare minimum of 8MB ram to run at all. You obviously exceed that, but it isn't much. Are you able to put any more ram modules in your laptop? Welcome to Win2K Stripped Edition.

I wouldn't remove them. I would edit them. ....................... Come on...An NT OS kernel that can change bootscreen appearance upon ACPI/MPS detection...That could be fun. Especially in an environment with several unique computers using the same OS kernel.

You mean I get no access to the WIM file. The ximage tool is too old and I can't even mount the images.

Might as well read SOMETHING when it's installing for half an hour and bloating it for three. =/ Keke! ^-^ This is a problem. I want to edit the Install.WIM to get rid of the crap I don't need, and rip the boot.WIM to extract the rest of the new WinPE. I have WAIK, I have the OPK, but I don't see where an ximage that can open 5219's WIM files is going to come from. I have Longhorn builds: 4051 4074 5219 I have Ximage builds 4008 and 5112. I haven't been able to extract any of these images using Ximage or any 3rd party program.

Is there any way to turn the whole CD into one big ramdisk? A virtual disk is one thing....Having it act like a Knoppix environment is another.

I would just like to state that this does not work in build 5219. I've had errors from NTLDR missing to Cannot Find BOOTMGR to an invalid Windows path with boot.ini. I've gotten it to go to the bootloader but that's it. It just loads and loads. So far switching it back to ramdisk or changing even a single character in your boot.ini makes it problematic. I'm thinking I should just get build 5112 and shut up. You got explorer to load successfully?! I couldn't get the start menu to load at all in 4051PE or 4074PE. It took me a while to get it working with XP Pro's PE. Has anyone been able to extract WinPE from build 5219 yet?!

I guess what I post in the WinPE forum is irrelevant because the post ratio is 1:9999 views. Has anyone successfully built WinPE from Longhorn PDC and HEC? I'm getting the PDC WinPE environment to work perfectly, but the HEC environment has no mouse support. Has anyone figured out why this is? Also I want to use Explorer as my main shell. Any guides available?