Slashdot Mirror

TClock3 is plenty enough for me.

For Win XP yes, that is, until they make a new installer for it, based on Vista's (been hearing about this lately), which they will do mainly to support the new deployment techniques replacing RIS. Vista doesn't need a floppy for drivers (the installer uses WinPE, and can load drivers from just about anything, including USB memory sticks). Meanwhile, you can integrate driver packs (including mass storage adapters) or just your own drivers on your XP install disc, and you won't have to provide a floppy anymore. It's not as hard as it may sound, and it only takes a few minutes to do. Go to MSFN if you need information on things like this, and lots more (unattended installs too, which save a lot of time)

Personally, I haven't had a floppy in any of my PCs for at least 5 years. For the odd time I needed a win98 boot floppy or such, then I have floppy images on several bootable DVDs (there's lots of them out there if you're too lazy to do it yourself or don't know how).

However, I still have an old floppy drive (and a trusty LS120) somewhere on a shelf, for the odd time it might come in handy (rescue data, reflash a BIOS from dos - although I prefer to do that from a hard disk as floppies are unreliable, and things like that).

If I recall correctly, an upgrade install looks for an existing install on your PC, not the install media. So just try installng on the current system. Of course, back up your Linux files in case they get nuked.

Also, some "upgrades" don't check anytnng at all, it's just the terms of sale.

If that doesn;t work, the best place to ask questions on this topic is the MSFN forum.

The time required to get Windows 2000 going is a complete waste. Go for Windows98SE, download following programs to keep it safe:

1. Zonealarm with antivirus.
2. http://www.msfn.org/board/index.php?showtopic=8080 0&st=0
3. Use firefox as your primary browser.
4. New games will not run, but games till 2004 may run.
5. Maximum Ram on Windows98SE is 512 MB
6. Post all your queries at MSFN.

Even better is to make an unattended install disk (using a tool like nlite, or following the directions from a site like http://unattended.msfn.org/unattended.xp/) which includes the proper service pack, drivers AND registry tweak.

You'll find this helpful if you do.

How to convert your Windows Server 2003...
to a Workstation!

Themes can stay off ;) but there is some stuff that you'll want to enable to speed the system up a bit.

Do be forewarned, pretty much all of the logitech products need some coaxing to install on 2k3 because they have these annoying os checks. Virtually everything else (some games also have the checks) runs fine.

From what I have read, No.

Basically, they are dropping support for anything prior to Win2k. They have no developers who either have the knowledge to work on pre-Win2k OS's or the ones they have are overburdened with other responsibilities.

They need someone who knows how to code for pre-Win2k machines.

Here is the link to a discussion on MSFN forums. The poster ivanbuto started this thread to attempt to find someone who could look into extending support.
http://www.msfn.org/board/lofiversion/index.php/t7 2957.html

And here is the Bugzilla discussion in which he started asking questions about this.
https://bugzilla.mozilla.org/show_bug.cgi?id=33027 6

That Bugzilla discussion gives pointers on what one can do to get Pre-Win2k support implemented. You just have to weed those out. It also lists a dev who is willing to review a patch that would give Pre-Win2k support.

Check out Microsoft Forum Network http://www.msfn.org/ for more do-it-yourself guides and forums dedicated to pre-building customized CDs/DVDs.

Jonah HEX

nlite integrates ALL patches, fixes, hotfixes, etc

A word of warning: nLite will SCREW UP a Windows XP installation.

We used to use it to create custom automated installation CDs for the various computers in our department, until we noticed a number of inexplicable problems start showing up. Unable to find drivers, Administrator permissions required to access USB devices, etc. We were confounded at first, but soon traced it back to nLite. I spent a couple hours with an RTM XP disc and created our custom CD by hand and we've never had problems since.

Check out MSFN for guides on how to do a lot of stuff, including slipstreaming service packs, adding hotfixes to the CD (I update this every month or so, so when I install a machine it doesn't need to download *any* updates). Everything nLite does you can do manually, and with the added benefit of 1) knowing what's going on, and 2) not screwing everything up.

You can slipstream the fixes into your install CD, too (along with registry settings, drivers, applications, etc.)

See http://unattended.msfn.org/unattended.xp/.

Try this: http://win2k3.msfn.org/

http://www.ubuntuforums.org/archive/index.php/t-83 499.html

I'm really shocked I haven't seen anyone mention Bold Fortune's guide, nLite, or anything like that.

http://www.bold-fortune.com/forums/
http://www.msfn.org/board/index.php?s=51e07579a39b 89452dcfefedd94d476b&showforum=89
http://www.microwinx.com/

When you really dig deep and lock, you can not only disable, but remove a LARGE chunk of Windows. But as for what you can remove, it depends on what your computing needs are. When I make custom install CDs, I take the 600 meg Windows XP SP2 install CD and rip it down to about 140 megs before I start adding back in newer drivers, and apps.

Unattended Windows

This has worked very well for me, excepting that I can't get the latest version of F-Prot antivirus to install automatically. I suspect F-Prot has deliberately broken this feature.

Actually no. Win2K3 does not have directx enabled by default - it does not even have graphic acceleration enabled. Check this site for how much work needs to be done to get 2K3 behaving like a workstation. They actually got a lot of things right with 2k3; sadly it was lost in the hype and flimflam of XP/Vista etc.

Don't forget HFSLIP!

It is a windows batch file so everything it does is transparent and it can be considered an open solution. It supports 2k/XP/2003 and RIS.

The batch file calls standard windows programs in order to integrate hotfixes, codecs, drivers, and lots of other neat stuff into a fresh ISO (automatically). Really quite easy, and the support is excellent.

The community is here: http://www.msfn.org/board/index.php?showforum=129
And a full description is here: http://www.msfn.org/board/index.php?showtopic=5765 9
(Yeah, this post is mostly from the last Ask Slashdot.)

Don't forget HFSLIP!

It is a windows batch file so everything it does is transparent and it can be considered an open solution. It supports 2k/XP/2003 and RIS.

The batch file calls standard windows programs in order to integrate hotfixes, codecs, drivers, and lots of other neat stuff into a fresh ISO (automatically). Really quite easy, and the support is excellent.

The community is here: http://www.msfn.org/board/index.php?showforum=129
And a full description is here: http://www.msfn.org/board/index.php?showtopic=5765 9
(Yeah, this post is mostly from the last Ask Slashdot.)

Don't forget HFSLIP!

It is a windows batch file so everything it does is transparent and it can be considered an open solution. It supports 2k/XP/2003 and RIS.

The batch file calls standard windows programs in order to integrate hotfixes, codecs, drivers, and lots of other neat stuff into a fresh ISO (automatically). Really quite easy, and the support is excellent.

The community is here: http://www.msfn.org/board/index.php?showforum=129
And a full description is here: http://www.msfn.org/board/index.php?showtopic=5765 9
(Yeah, this post is mostly from the last Ask Slashdot.)

I concur with the parent as far as building unattended installs goes:
a few resources (some of which were mentioned earlier):
MSFN.org
nlite
BartPE
Technet XP Deployment ref
Disclaimer: Scan anything you download thoroughly for viruses. The worst thing you could do is inject a vulnerability in your image framework.

If you are in the position to need to reload your systems for any reason remotely I would suggest using a PXE deployment solution of some kind. Ghost/Altiris both provide good PXE and post-install config utilities. We use altiris and deploy our images through PXE. This allows for imaging in place after the fact, something that we try do semi-anually.

Every major vendor provides UNDI-Driver capable on-board nics now-a-days, so the headache of PXE (nic specific) boot images is pretty much a thing of the past (unless you were one of the saps who bought the Gateway E-4300s.)

There's something about booting to your nic, loading an image on a station in 8 minutes and monitoring the unattended install from a remote TS console miles away from the station you're reloading.

Check out http://www.msfn.org/, the "home" of nLite and many other projects. Personally I use nLite, WPI (Windows Post Installer), BTS Driverpacks, and AutoIT3. I have done both Image/Ghost style for multiple PCs and scripted installations, images are too hard to update on a regular basis, I much prefer scripted installs.

HEX

You can integrate most anything into a Windows installer with The Unattended Windows Tutorial.

Windows Server 2003 doesn't even have this listed on the update page. It also runs quite well as a desktop OS, with a few tweaks.

Go here and read up... you can make a totally slipstreamed/added installers with batch files http://unattended.msfn.org/unattended.xp/

Ok some tools I use to make my life easier (all free):

• nlite (creates unattended installs, needs dotnet) slipstreams automatically service packs and hotfixes and allows other unattended options (more then MS tools). w2k and higher only. http://www.nliteos.com/
• autopatcher contains all the hotfixes, tweaks and third party extras like dotnet 1,2, flash, shockwave, java. http://www.autopatcher.com/ **
• driverpacks contains all the winxp drivers in existence (I think) http://driverpacks.net/Projects/DriverPacks/
• RVM packs, contains hotfixes and some extras. And is compatible with nlite. http://www.ryanvm.net/msfn/ **

Basic usage:

• Drop the contents of your winxp install CD onto your HD. Download the latest service pack.
• Start and Point nlite to both.
• Choose any option that you like but don't create an iso.
• It will automatically integrate the service pack.
• About integrating hotfixes see RVM packs, which is compatible with nlite. http://www.ryanvm.net/msfn/ (also more info about appz integration)
• Again options, choose what fits you. (Talking about nlite)
• Save
• Now follow the driverpacks site instructions to add the drivers to your install CD/DVD.
• About integrating extra applications see: http://unattended.msfn.org/unattended.xp/page/list /switch/ for general info look at its home site: http://unattended.msfn.org/unattended.xp/ and google for specific appz.
• After first boot run autopatcher latest version. (if needed, RVM packs if done well, don't need this step)
• Run your personal little script.
• Now you have a working winxp installation with all tools and most actual updates.
• Deploy!

Ok some tools I use to make my life easier (all free):

• nlite (creates unattended installs, needs dotnet) slipstreams automatically service packs and hotfixes and allows other unattended options (more then MS tools). w2k and higher only. http://www.nliteos.com/
• autopatcher contains all the hotfixes, tweaks and third party extras like dotnet 1,2, flash, shockwave, java. http://www.autopatcher.com/ **
• driverpacks contains all the winxp drivers in existence (I think) http://driverpacks.net/Projects/DriverPacks/
• RVM packs, contains hotfixes and some extras. And is compatible with nlite. http://www.ryanvm.net/msfn/ **

Basic usage:

• Drop the contents of your winxp install CD onto your HD. Download the latest service pack.
• Start and Point nlite to both.
• Choose any option that you like but don't create an iso.
• It will automatically integrate the service pack.
• About integrating hotfixes see RVM packs, which is compatible with nlite. http://www.ryanvm.net/msfn/ (also more info about appz integration)
• Again options, choose what fits you. (Talking about nlite)
• Save
• Now follow the driverpacks site instructions to add the drivers to your install CD/DVD.
• About integrating extra applications see: http://unattended.msfn.org/unattended.xp/page/list /switch/ for general info look at its home site: http://unattended.msfn.org/unattended.xp/ and google for specific appz.
• After first boot run autopatcher latest version. (if needed, RVM packs if done well, don't need this step)
• Run your personal little script.
• Now you have a working winxp installation with all tools and most actual updates.
• Deploy!

You can make a bartpe dvd with all the drivers installed to work on most hardware.
There is a DVD floating around on BT sites that have an updated winxp with all patches/drivers and some needed applications. But I recommend making one yourself for security reasons. (rootkit/etc)

Driver packs and Driverpacks.net
Ryan's windows xp updates
nlite to help modify a windows install.
Bart PE - bootable dvd/cd for windows install.

You can make a bartpe dvd with all the drivers installed to work on most hardware.
There is a DVD floating around on BT sites that have an updated winxp with all patches/drivers and some needed applications. But I recommend making one yourself for security reasons. (rootkit/etc)

Driver packs and Driverpacks.net
Ryan's windows xp updates
nlite to help modify a windows install.
Bart PE - bootable dvd/cd for windows install.

You can learn how to everything from here:
http://www.msfn.org/board/

Here:
http://unattended.msfn.org/unattended.xp/view/web/ 1/

And here:
http://www.driverpacks.net/Projects/DriverPacks/

Applications, Drivers, Updates - all slipstreamed.

You can learn how to everything from here:
http://www.msfn.org/board/

Here:
http://unattended.msfn.org/unattended.xp/view/web/ 1/

And here:
http://www.driverpacks.net/Projects/DriverPacks/

Applications, Drivers, Updates - all slipstreamed.

With your mix of hardware, slamming an image won't cut it for you. You'll have to created an unattended Windows install.

Here's a pretty good guide on the subject.

A bona fide installation disc for Microsoft Windows XP, Service Pack 2, Home or Professional (No multi-disc, upgrade or Media Center versions.)

http://unattended.msfn.org/unattended.xp/ plus a convenient list of patches from http://www.kuku.co.il/windows_xp_sp2_patches.htm , the data from your XP install CD and http://www.nliteos.com should get you a long way on the road to slipstreamed glory.

I've been working on this for a while, it's harder than it should be but it's certainly possible.

The place that helped the most was MSFN Unattended, the documentation there takes you through this kind of stuff step-by-step. They also have forums and driver packs that will help you install to almost any system you can imagine without needing extra driver disks, the BTS DriverPack is the greatest driver collection I've ever seen.

To make your life easier, nLite will automate a bunch of the steps you'll want to use, plus it can strip out a bunch of stuff that you don't want in your install anyway.

I've been working on this for a while, it's harder than it should be but it's certainly possible.

The place that helped the most was MSFN Unattended, the documentation there takes you through this kind of stuff step-by-step. They also have forums and driver packs that will help you install to almost any system you can imagine without needing extra driver disks, the BTS DriverPack is the greatest driver collection I've ever seen.

To make your life easier, nLite will automate a bunch of the steps you'll want to use, plus it can strip out a bunch of stuff that you don't want in your install anyway.

I've been working on this for a while, it's harder than it should be but it's certainly possible.

The place that helped the most was MSFN Unattended, the documentation there takes you through this kind of stuff step-by-step. They also have forums and driver packs that will help you install to almost any system you can imagine without needing extra driver disks, the BTS DriverPack is the greatest driver collection I've ever seen.

To make your life easier, nLite will automate a bunch of the steps you'll want to use, plus it can strip out a bunch of stuff that you don't want in your install anyway.

HFSLIP is highly recommended. It is a windows batch file so everything it does is transparent and it can be considered an open solution. It supports 2k/XP/2003.

The batch file calls standard windows programs in order to integrate hotfixes, codecs, drivers, and lots of other neat stuff into a fresh ISO (automatically). Really quite easy, and the support is excellent.

The community is here: http://www.msfn.org/board/index.php?s=828e7ef495f9 325af8454bbbb194f79f&showforum=129

And a full description is here: http://www.msfn.org/board/index.php?showtopic=5765 9

HFSLIP is highly recommended. It is a windows batch file so everything it does is transparent and it can be considered an open solution. It supports 2k/XP/2003.

The batch file calls standard windows programs in order to integrate hotfixes, codecs, drivers, and lots of other neat stuff into a fresh ISO (automatically). Really quite easy, and the support is excellent.

The community is here: http://www.msfn.org/board/index.php?s=828e7ef495f9 325af8454bbbb194f79f&showforum=129

And a full description is here: http://www.msfn.org/board/index.php?showtopic=5765 9

As has been pointed out earlier in this story, the best you can do is http://unattended.msfn.org/

Having said that, if you are doing this often enough why do you not have an image? Imaging spares you this work and you also get all of your applications as well. Your more likey to mess something up the more manual rebuilds you do, especially if you have a non trivial configuration. Better yet, with a little work with sysprep you can add drivers for multiple models. Bâshrat the Sneaky's DriverPacks works for most hardware and takes minimal effort. I currently use the same image for about 15 different models of laptops. Having one image for all of my on site hardware makes updates a snap.

SGT Gruhn
BCT1, 101 ABN DIV(AASLT)

While slipstreaming service packs is a common practice, you can also slipstream hotfixes. Hack when I was in IT support we used this great script to automate the process. Some of the other links I still had bookmarked may be of value to people who not only want to slipstream service packs/hotfixes but also build an unattended installation CD. In our case we installed all the apps common to our PC images (except for office) from one CD. We threw the CD in, booted from it and came back 2 1/2 hours later to find a fully installed desktop with all our standard apps. This method is superior to using Ghost or other imaging software when you have a heterogenius enviroment where PC hardware varies drastically from depertment to department or desktop to desktop.

http://www.nu2.nu/bootablecd/
http://www.microsoft.com/technet/prodtechnol/ie/ie ak/default.mspx
http://unattended.msfn.org/unattended.xp/
http://www.appdeploy.com/packages/

This last link related to a commercial software distribution enviroment but but it includes an archive of the known switches accepted by various installers to make them silent. The technique we used was to use the unattended.txt file to add a RunOnce registry entry, to regedit (to marge a secondary gegistry file containing other RunOnce entries) to be executed on the second reboot to silently install our list of apps, where the installer commands used included the switches detailed on the appDeploy website (and many other palces across the web).

There are a relatively small number of installers out there that take a relitively well known set of switches to make the installation silent (accepting all the defaults). These methods saves us thousands of man-hours in PC deployment in the two years they was in use.

--CTH

Have you ever wanted a Windows CD that would install Windows by automatically putting in your name, product key, timezone and regional settings? And have it merged with the latest Service Pack to save time? Followed by silently installing all your favourite applications along with DirectX 9.0c, .Net Framework 1.1 and then all the required hotfixes, updated drivers, registry tweaks, and a readily patched UXTheme.dll without any user interaction whatsoever? Then this guide will show you how you can do just that! Through the course of this guide, you will create a CD that does all the installing for you. The CD will be fully updated with the latest hotfixes, and install all your programs for you.

And I call BS on you. There are a ton of resources available for experienced Windows users to allow an incredibly customised Windows installation, along with integrating SATA/RAID drivers.

As you noted, XP doesn't go out of it's way to offer every single option under the sun within it's installer, and describes every process it's going through, which can be helpful to the average user. And I admit, especially in the case of the floppy drivers, RAID/(some)SATA setups can be irritating if you don't want to have to go customise your installation CD, but let's face it, pick any Linux installer from before 2003 (release date of SP2 for XP, I could've used XP's release date... but I decided to be lenient ;) and you'll find that just as much messing around is needed to get everything working 'out-of-the-box'.

Back to your point, there are a ton of resources around that allow fairly easy creation of a customised XP CD (I define 'easy' as 'I can do it'... I'm far from an expert =P) with integrated drivers, program installations and a more openly explained process of the XP installation. Try these resources:

- Integrated Drivers for XP
- Great at removing unneeded items, setting up automatic installation, and lots of other handy things
- An amazing and comprehensive guide to creating a customised XP installation
- Microsoft's own deployment tool

A lot of trouble?!

Just take your installation CD, slipstream service pack 2, add in the latest hotfixes, and heck, while you're at it, make an answer file for an unattended install.

Sure, if you're intent on going to Windows Update, yeah, it's going to involve lots of rebooting. But you don't have to do it that way, you can just download all the hotfixes directly and install them one at a time, if you aren't looking to create an up-to-date installation CD. I, personally, like the installation CD (or DVD) route. It's handy to be able to pop in the disc and walk away and come back to a crisp, clean, fully patched, up-to-date system with all of the latest drivers installed as well.

A lot of trouble?!

Just take your installation CD, slipstream service pack 2, add in the latest hotfixes, and heck, while you're at it, make an answer file for an unattended install.

Sure, if you're intent on going to Windows Update, yeah, it's going to involve lots of rebooting. But you don't have to do it that way, you can just download all the hotfixes directly and install them one at a time, if you aren't looking to create an up-to-date installation CD. I, personally, like the installation CD (or DVD) route. It's handy to be able to pop in the disc and walk away and come back to a crisp, clean, fully patched, up-to-date system with all of the latest drivers installed as well.

A lot of trouble?!

Just take your installation CD, slipstream service pack 2, add in the latest hotfixes, and heck, while you're at it, make an answer file for an unattended install.

Sure, if you're intent on going to Windows Update, yeah, it's going to involve lots of rebooting. But you don't have to do it that way, you can just download all the hotfixes directly and install them one at a time, if you aren't looking to create an up-to-date installation CD. I, personally, like the installation CD (or DVD) route. It's handy to be able to pop in the disc and walk away and come back to a crisp, clean, fully patched, up-to-date system with all of the latest drivers installed as well.

A lot of trouble?!

Just take your installation CD, slipstream service pack 2, add in the latest hotfixes, and heck, while you're at it, make an answer file for an unattended install.

Sure, if you're intent on going to Windows Update, yeah, it's going to involve lots of rebooting. But you don't have to do it that way, you can just download all the hotfixes directly and install them one at a time, if you aren't looking to create an up-to-date installation CD. I, personally, like the installation CD (or DVD) route. It's handy to be able to pop in the disc and walk away and come back to a crisp, clean, fully patched, up-to-date system with all of the latest drivers installed as well.

Download the hotfixes from another computer and burn them to a CD or copy them to a USB drive. See this thread on the Microsoft Software Forum Network for a list of the hotfixes currently out in the wild:

http://www.msfn.org/board/index.php?showtopic=3188 6

The page also lists the switches to specify to do a silent install, so once you've downloaded them all you can create a batch file to install them all, put the hotfixes and the batch file in a folder on a CD, insert CD, execute, get a snack, come back, your machine is now secure. huzzah!

Tip: If you have super sed ( http://sed.sf.net/grabbag/ssed/sed-3.59.zip ) Then you can make this batch file pretty easily. All of the hotfixes released after service pack 2 support the /q /n and /z switches (except the mailicious software removal tool, which isn't really a "hotfix" per se). So put all the hotfixes in one folder, open a command prompt and then navigate to that folder and then get your i/o redirection groove on:

dir /b *.exe | ssed -e "s,$, /q /n /z," > InstallHotfixSilent.cmd

You are trying to update an existing system, not build a fresh one. Using a cheap hardware firewall (like a linksys router) will keep most evil at bay while you do the update. Better to download the big security rollups and service packs from a current machine, burn to cd or thumbdrive, and install those on your box before you connect to the net.

Check out http://www.msfn.org/board/index.php?showtopic=3188 6 for a nice pointer to all the patches you should snag. Get the major ones and you should be OK to just do an update.

well.. you can't sell windows, as you are not microsoft... but you could sell unnatended installation scripts that bundle the installation with all the software , drivers, settings you want. You could even remove microsoft software like wordpad or media player from those scritps... use http://unattended.msfn.org/ as a start to build your own installation.

Windows is actually fairly easy to customize for deployment itself. Microsoft provides some (undocumented?) tools that the sysadmin can use to 'slipstream' installers, registry keys, and support files onto a custom install CD.
In fact, entire communities have sprung up regarding just this: try Unattended XP for a general overview.

Seriously, check out nLite, and also at the nLite forum, especially this FAQ. This is a free Win2k and XP customisable installer. You can use this to get a seriously stripped down install that should run on your old dogs. Worth checking out other parts of this site if you've got to admin Windows.