prathapml

@MCT (no offense meant) Brush up on your DOS! It don't work that way.

Hmm.... So we shall look forward to seeing you more around the board, posting then? Great!

No, that would work perfectly the way you want it.The two dots mean "parent folder". So, you work it out and see. ..\Tweaks\RegTweaks.reg --equals-- XPCD\Tweaks\RegTweaks.reg

Thunderbird silent install Use the combination of simply extracting the app's files to the destination, then applying the INF.

Try extracting the nForce drivers EXE, then go to device manager. There, for each flagged device, direct it to find the driver in the folder where you extracted it - basically, tell it where the driver's INF is to be found.

Sometimes you want to just check if your AntiVirus is working. Save the following into a text-file: X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*And rename to eicar.com Norton AntiVirus should immediately detect it - in my case it automatically deleted the file even as it was being saved. More information: http://www.eicar.org/anti_virus_test_file.htm

Hi digrevo, Yes these keys are in my HKCU as well. I don't remember having seen these before! [HKEY_CURRENT_USER\S\P\890190932] "Prompt"=dword:00000000 "MsgPrivacy"=dword:00000001 What is it for?

Ha ha... Welcome again. (though I thought you'd choose any other nick that sounds not like the old one). And.... that post had nothing about why you chose "DL". (or did I miss something)

Hear me! Hear me! In all of this, we have probably over-looked the most important tutorial which could have made the guide a comprehensive one. I think its a major handicap, that msfn's slip-streaming guide is in one place and uA in another. Why not start from scratch? Giving instructions to start from the base SP0 CD, to slip-stream into it, then to go further with the current uA guide. Summary: Take the content of the current Universal Windows Slipstreaming and Bootable CD Guide and put it up as the starting page prior to uA operations.

I agree with what drew said. Limiting posting would be a downer. But this is not a very big problem. I think new members are sent a PM by default, to read the rules and Guide before posting. So a more strict step is not necessary. I think the main problem for newbies, is the huge lot of things they can access in the forum. I mean... they don't have a simple interface, etc. - you can play around with so much in your forum-board interface, that they find it too intimidating to learn to search. And then, changing the default search-period from "30 days" to "any date" is not good too, because most of us want to search only in last week, actually. So if it is "Search in any date" by default, that will totally flood the newbie with results. Again, it gets intimidating to look thru all of that, so they take the easy way out and directly post their repeated questions. No, as of now no action is needed. Just wait until the upgrade to IPB2 is finished. Then, the new member when sent a PM (about the rules and guide and searching and introducing himself) - will see a big-coloured message at the top of the board. So he cannot possibly forget (or not notice) the PM. Patience, I think is needed. The entire frustration will be solved (or helped to a large extent) once the upgrade is done. It will solve itself, don't do anything about it. If any of you feel irritated with repeated questions, the best thing you can do about it, is to *NOT* reply to it. After some days, they'll get round to search. Shouting at someone for not having read old topics only just deviates from the friendly atmosphere here. You either help the person, or don't reply to a question (if it irritates you). That's all.

Right, All programs whose path is defined in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Pathswill run too. And I think you need to change the shell used while logging users in, and reboot to take effect: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "Shell"="ProgMan.exe"

WinCDman is notorious for creating non-working multi-boots! Its better to do it manually. In anycase, WinCDman does not *ACTUALLY* slip-stream IE6SP1 into win2k. It can only just merge windows Service Packs and hot-fixes. And its a good idea to not start thinking of multi-boot until one has everything else working fine.

Great guide GK! So now it is possible to have the entire NAV-thing done totally silent.

Theoretically, it should be possible. Try VNC.

Hi nvbauer, Welcome to MSFN forums! Please make yourself clearer. All those details and background is fine, but give a one-line sentence (summary) at the end, telling *WHAT EXACTLY* you want us to help you to do. Otherwise, you just have a whole lot of uncertain things above, and you'll simply be pointed to this guide - click here.

If the VBS is not working, try Auto-IT.

Well, generalmandible asked for this, but I'm posting this here for the benefit of everybody: A. The forums has lot of posts with people swooning and praising their favourite desktop shell. So a search will show up alternatives. But most of those (except for litestep) are paid utilities. And just a word of opinion - *NEVER* go for DesktopX (stardock) - its a massive memory-eater. B. Now, as for the question of whether its worth using those to replace the explorer shell, the answer is not a straight-forward one. It goes like this: 1) If you don't keep using windows explorer all day to browse through your file-system, then its worth. 2) If you don't browse web-pages using IE (or a derivative like maxthon/Avant), then its worth. 3) If you don't like the way windows looks, then its worth. 4) If you want more control over the interface (example: you don't want employees to access the "Run" dialog) then its worth. But what can make the entire purpose of using these shell-replacements redundant, is some people's tendency to browse thru their file-system (folders/files) all day. Now, what I mean is, by using those shells, you have wanted to throw away explorer.exe - but if you run MyComputer or WindowsExplorer or IE, you are effectively bringing it back and loading it into memory. Therefore making no memory-savings. Instead, if you have a complete alternative plan: 1. Desktop shell like aston/talisman/desktopX/litestep. 2. Browser like opera/firefox (whatever except IE). 3. File manager like PowerDesk/TotalCommander/DirectoryOpus/xplorer2. That is when you see the full effect and power. But then, you notice that the combined memory usage of using 3 utilities in place of 1 explorer.exe takes up more space on memory usage - you can bring down mem-usage by putting in place appropriate policies. Last of all, consider one thing - many of the utils I suggest above are paid utils (if its good enough to replace, its paid ) - so that is a problem too. But still, its needed for some organizations (or PC-beauty enthusiuasts ).

This is cool! SP1 madness begins. This is where Server 2003 SP1 will have a home (sort of): http://www.microsoft.com/technet/prodtechn...ck/default.mspx Go there for accessing any technical details (all info ) regarding it. Changes to functionality in SP1 SP1 Technical product overview SP1 FAQ What hot-fixes are included in the latest RC ? Top 10 Reasons to Install Windows Server 2003 SP1 And security configuration wizard in RC1 looks good!

Slip-streaming IE6SP1 (and updates) into windows 2000 Try that Mugatu.

Slip-streaming IE6SP1 into windows 2000 Yep, the holy grail.

Ha ha... Longhorn is problematic alright. Don't at all expect it to work properly. And yes, I've started to work on mine. All info right on the CD. Check out the XML on the disk - that's the answer file now. They are moving to a totally different paradigm with longhorn. In addition to the above, you can also take what's on the disk after first phase of setup (which is WinPE mode, basically). And whatever you do, don't down-grade longhorn. I've seen some people converting longhorn to use a text-mode setup or to run it after booting from DOS.... don't do such a thing because ultimately that's useless. If what you're doing, is to prepare for longhorn's release and roll-outs - then use it with the new methods (XML). And if you're just trying to have some fun with longhorn, even then its nice to use the new uA features introduced with longhorn. Take a look at the info on the CD, and if you have anymore things to know, I'm here.

Yes, you can - just remember that you won't be able to format it (of course).

Either that, or keep your winnt.sif on a floppy disk. Then its easy to modify the key for each machine (since the floppy is easily writable). z:\i386\winnt32.exe /s:z:\i386 /unattend:A:\winxp.sif /udf:testbox1,winxp.udf /syspart:C /makelocalsource /noreboot

Solution is as simple as could be - Don't re-edit your setupldr.bin! I've been using the same setupldr.bin for WinXP, all the way from the gold (SP0) release, to SP1, to SP2 alphas/betas, and SP2 final - in other words, entire XP series used same setupldr.bin Similar was the case with Win2k - I used same file for SP0, SP3 and SP4 (I was not knowing to slip-stream in the days of SP1/SP2 of win2k). I haven't dl'ed the SP1RC for ws2k4 yet, so I can't say for sure about it. Use the same old setupldr.bin (which worked for you) - it really can't have changed.

What you want, is to modify the WINNTBBU.DLL - there's plenty of info on how to modify its (bitmap and text) resources, on the forum. As for the specific purpose - of moving the "setup status" words lower down - I think you could just make some of them blank, and replace the ones lower down with the text of the ones higher up (if you get what I mean....). But that will really mess up things - I don't know why you want to do this, but an unattended setup screen that I (obviously) don't see/attend-to does not matter how it looks.