gosh

teufel: You can make an image of any floppy disk and boot from it using the cd menu (diskemu.cmd). The easiest way to do this is with winimage. With winimage you click on a menu and read the contents of the floppy. Then you click on File > save as > make sure you select .ima. I'll try to write a guide on how to do this. -gosh

search google, i've never not found cdimage.exe from google. -gosh

My Guide skips the first step of file copy in Gui mode (there's no dosnet.inf on the cd). You still have to do text mode. -gosh

Is anyone interested in me making an inf to install all the critical hotfixes? I could make an inf that you could use in txtsetup.sif using http://www.MSFN.org/board/index.php?showtopic=10873 ? -gosh

i saw the same thing on my cd, i think that's a microsoft bug since like you say there is not unattend file being used. -gosh

cmdlines does run from cd -gosh

nooo... Just follow my guide. LS will be called install. BT will be called BOOT. You want to place BOOT under Install. The i386 folder will be under LS folder. -gosh

If you're asking if you can transplant the reduced i386 folder with another i386 folder, then yes you can. -gosh

I don't do pdf's, but im gonna write some guides tomorrow. -gosh

Do it the easy way. Just copy and paste from hivedef.inf Just edit the string to what you want it to be. Microsoft uses [strings] for localisation. -gosh

/noreboot tells setup to close when it's done, and not to reboot the pc. I've never heard of the /noreboot command to open the my documents folder. You can skip the /noreboot command if you want, just make sure you don't let setup restart the pc. -gosh

I've never tried to move the documents and settings or program files directory. Does anyone know if you can move either of those folders to a network share? In other words move program files to \\gosh2\d$\program files -gosh

Thanks. When i said my method has a speed improvement, i got the idea when i built a pc. I had 2 identical computers side, with exactly same hardware. One computer used my cd, the othr computer used a retail xp cd. Both computers started the install at the same time. By the time text mode was done on the retail computer, the other pc using my cd was already done installing. It could be that computer was built wrong, i don't know. -gosh

Since it's slow tonite i'll talk about one of the things i'm working on. It's always been a goal of mine to make a customized homepage for my unattended setup. My latest attempt to make a custom homepage is here It's very basic, all it does it let you search sites. It does exactly the same thing as importing my iesearch registry keys from install.inf. This homepage also educates the user that they can perform custom searches from the address bar. For example, after looking at the homepage you can see that you can search google by typing 'google term' in the address bar. The background color matched the theme i was using at the time. To get the rgb code, i simply looked at HKEY_CURRENT_USER\Control Panel\Colors and matched it to the color showed in display properties. The idea is to match the homepage with the default theme. The original idea was to have the favorites explorer bar be on the left, but only on the homepage. I found a way to do this, but the html i found didn't work and i gave up on the idea ;( Does anyone know how to show the favories exporer bar via html? I only want to show it on the homepage, once you type a url i want the favorites bar to go away. If anyone wants to edit mine or show a better homepage i'm all for it. -gosh

I'm actually actively working on a way to completely remove ie in XP. Editing ie.inf is a good start. The problem is ie is installed in several inf's: homepage.inf ieunit.inf iereset.inf ie.inf ie5files.inf - used by msinfo32 So the short answer is i don't believe editing just ie.inf will remove ie. For mstask.inf u just need this: -gosh

you can edit mplayer.inf i believe to remove it. Just look under [infs.always] section of syssetup.inf to see what inf's media player uses. -gosh

You might get an error as setup tries registering files. Look in syssetup.inf under the [olecontrols], the movie maker file is in that list (i don't remember the file name off hand, it's something like mmer...dll), so when syssetup.inf registers files it'll say "hey, i can't find this file". Also in the list is srstr.dll, the system restore file (i believe, i'm not in front of an xp box so i could be wrong). If you are using FullUnattended, any errors will be silently logged to setuperr.log, you won't see them during the install. If you're not using an unattended install, you *might* see the errors. -gosh

I am just giving my advice, like any advice you can take it or ignore it. My advice is don't install recovery console in cmdlines.txt. I wish i could give a better reason, but i can't. If you read between the lines you'll understand what I mean. -gosh

If i could give a more specific reason i would, but im not lieing. Why don't you go make a batch file or something green machine, make yourself useful. -gosh

I wish i could give you a better reason. All i remember from previous research is it didn't work for good reasons. I also know that the reason that article doesn't recommend cmdlines is because cmdlines doesn't work, the article intentionally didn't mention it. -gosh

Using cmdlines to install recovery console won't work. If it did, ms would recommend using it. I've seen cases where recovery console has problems if installed via cmdlines. -gosh

good eye, i thought i was the only one that used that command. -gosh

I'm SuperCool -gosh

Dynamic updates is a new feature of XP. The idea is it will install only CRITICAL updates related to the install of XP. This way before you upgrade, you'll have critical fixes integrated. A good example of this is a data loss situation. Using dynamic updates (du for short), microsoft can integrate a fix for a data loss bug, so people don't lose data on the upgrade. The 3 du's where for presp1, i dont think there's been a du available for post-sp1. using the 3 du's as a guide, you can slipstream the du's. The 3 du's on the microsoft site are for administrators to use on a file share. Du's are complicated though, i wouldn't recommend using it. -gosh

In my post http://www.MSFN.org/board/index.php?showtopic=10246, i showed a comparison of the server2003 and xp hivedef.inf. As you see in the red, server2003 disables all sounds be default. An easy way to disable all windows sounds would be to copy the sound section of the server2003 hivedef.inf, and paste it into the xp hivedef.inf -gosh