Daemonforce

Get a router/hub/switch. Look into those.

Are you running these programs in compatibility mode?

I would find WinPE to be rather useful here for some reason. =/ To format your setup you need: A Windows XP installation media (the CD! o_O) Some experience with any of the commands: fdisk, format, diskpart Your BIOS password if it is password protected Knowledge on how to select what devices your computer boots from and the order First...You want to reboot the computer so that it POSTs and you need to enter your BIOS menu. You need to find the setting that chooses the boot order. It is important that you set it to boot CD/optical and maybe removable devices before any hard disks or you won't get much difference from what you have now. From here it's up to you. You can get a boot floppy with DOS and run fdisk/format or maybe get the Partition Magic disks and format the drive or you could just boot the Windows XP CD and go through the setup process. If you have a real bad situation here you could boot a WinPE disc and move stuff around before formatting. Keep in mind that your current knowledge has put you in a really stupid situation if you don't understand the information that I'm feeding you. Maybe you'll think twice about installing a beta OS in your production environment.

I know there's a manual way and it's an entry in WINNT.SIF. I forget what it's called though. Unattend=Yes ? EDIT: After further examination I have discovered that the name changed. http://www.msfn.org/board/index.php?showtopic=16988 Apparently it is UnattendSwitch=Yes I really need to remember this one. I am creating a corporate tool and it's extremely important that I don't see this screen pop up on 200 computers.

HKCU,Control Panel\Colors "Background" Go nuts.

I don't understand the flag or the translation. You want to change how the boot screen appears?

It's still going.....o.O *Notes that I'm a dialup user* Not a very good joke for someone frustrated with bandwidth all the time. That README.TXT takes the cake...

It has been done. Several years ago. o_O

It's worth messing with to understand the hell you'll be dealing with soon. It will be truly worth it when it is part of Vista when it's a fully packaged product. Also I suggest vmware. I have never had any luck with Virtual PC and others tend to report bizarre problems with it. I have never had a problem with vmware.

Are you absolutely sure you're using /INRAM?

Gee Gee Bay Bee. Ahahaahahaahahaaha!

Those are not identical specs with exception of a processor. THAT would be my legacy box that has an ASUS P5A-B. I can put anything from an AMD K6 to a Rise MP6 in this box. Also, your ram will more than likely make the winner of this decisive battle. Another variable has to do with the kind of preparations done before benchmarking. I believe the Prescott would win.

I know 8.0.22 works perfectly. I haven't exactly tested it on 8.0.24 just yet. What i stated above assumes that SP2 is integrated into Windows XP Professional/Media Center/Home/TabletPC. The key point is that Flash 6 is already part of service pack 2 and txtsetup/dosnet already sees the files. I don't integrate things like GetFlash or the manifest files because I already have the components. There was a problem when moving from Flash 6 to 8 when leaving the INF alone(or replacing it with the one in the new CAB)...In my experience it's best just to update the build number in the INF and be done with it. I'm already in the middle of something this week and I'll be able to test the full replacement idea later.

It may be dumb but it remains valid. I laugh every time this thread gets bumped to the top. Every one of his posts remind me of the mighty Gene Ray.

I have been able to add several linux distributions to my DVD but there is one problem that I've been trying to deal with all week: PHLAK 0.3. I have had problem after problem when adding this build, mainly because of GRUB and the weird effect my boot image has on it. I have gotten PHLAK 0.2-1 to successfully work in a multiboot without ANY problem. I have worked with the small release for a while and now want to move up to 0.3. The first time I tried booting PHLAK 0.3 in CD Shell I got a prompt with a missing "linux" error. The next revision got it working but it couldn't find the file system. Erasing about 18 disk entries(hdb, hdc, hdd, hde...) with SCSI parameters fixed this issue. Now PHLAK 0.3 finds the file system on hdc, reaches the GUI then immediately goes back to command line and runs the shutdown process before rebooting vmware. It took me 4 days to fix the missing file system problem by finding the garbage in SYSLINUX.CFG. I still can't get GRUB to load(just a command boot: _) and I don't want to use the PHLAK 0.2-1 loader to be doing this if that's possible. Has anyone here actually gotten PHLAK 0.3 working in CD Shell without a problem? I seriously need help with this.

You have....A socket 8? How come I've never heard of that? The oldest computer I've seen around here is a Socket 7. Mine is a Super. Those had a range of Intel 120 MMX chips all the way up to the legendary AMD K6-2/550. A Socket 8 sounds like one of those old 66-75MHz builds that could use the turbo feature. I think you would enjoy a permanent overclock with one of those(God willing). I've gotten a 300MHz AMD K6-2 to 400MHz stable. I've also gotten a 233MHz Intel Pentium MMX to 300MHz stable(with voltage all the way to 3.5v). I would say you could probably get one of those 75MHz chips to 90MHz stable, but I don't know if a board from a brand name computer could handle that. Planning on making a router? EDIT: Wait....Those were made after my chip. This means you'll probably have some 300MHz chip! I'm betting on a 400MHz stable clock. Go go go!

Normally the newer swflash INF would cause the flash stuff not to install with the OS. Are we finally at a point newer than Flash 8 r22? *downloads CAB* Ah sweet! Uber new flash! It looks like they finally made the INF compatible with Windows integration too. I suggest you replace: SWFLASH.IN_ FLASH.OC_ and you're done.

It sounds like he just wants to use WinPE all over the network.

The only way you can "remove" the activation process is with a volume key. If you want to skip the out of box experience, an unattend setting can do that.

WinPE > Blue Screen of Installation GG kthnx no re.

I have the horrible habit of using the administrator account. =/

Mount it in Daemon Tools or some virtual device and hit install. All of the required files are extracted to the drive root so you won't need the disc for installing.

Nice post time. I don't believe backwards compatibility with 32-Bit binaries has ever been a concern on a 64-Bit computer. If you can run DOS like the rest of the legacy equipment, you should be able to run a 32-Bit operating system just as easily as my 32-Bit rig.

Correct. You have a cluster. It could be two boxes....It could be more. The point is that there is more than one. Virtual machines don't cut it until you need to go back to something. Box 1: Windows Server 2003 Enterprise (DOMAIN CONTROLLER) Box 2: Windows Server 2003 Enterprise (DOMAIN CONTROLLER) Box 1 is the primary domain controller and uses IIS 6.0 as the primary web server Box 2 is the backup domain controller and uses IIS 6.0 as the backup web server *Update prompt on box 1 and box 2* *shutoff IIS on box 1* *install updates on box 1* *reboot box1* From this point box 2 takes over as a failover server All requests made to box 2 are made on box 2 When box 1 is finished rebooting, start it up and restart IIS. Check for any problems and fix them before servicing box 2. I remember Service Pack 1 killed the FTP service in IIS and I still can't figure out how to fix that. You might run into a similar problem after an update, so check for any possible problems after a reboot.

No it's not. If I use your method then it doesn't work. It's for a different scenario anyway.