prathapml

First of all, check if file-name extensions is not being shown, the exact file name should be: WINNT.SIF Sometimes people have accidentally had their setup file name winnt.sif.TXT - which is obviously unused by setup. I also noticed that you called the file "winnit.sif" which is wrong (name it as mentioned above).

From the look of it, seems like you're either doing this on a 64-bit PC (which may error out), or your XP install source or the service-pack version is 64-bit. That just could be a cause for the problems you are facing. Try eliminating those factors.

Okay, let's settle the issue un-ambiguously. Yes, it is possible to fully automate windows setup, the best way to do that being what ml20 (2nd post in this thread) has said. But keep in mind that it involves ripping out all your existing data on that HD. Otherwise, you can just keep the "AutoPartition=1" value alone (without repartition). It will work in the way that "Bâshrat the Sneaky"s post above states (a small correction here, it will *NOT* re-format any existing partions, *NEVER*). If a windows-compatible FS primary partition exists on the first StorageDevice, setup will install to that partition, otherwise, setup creates a partition that occupies the entire available free partition-space on HDD (it will not interfere with any incompatible FS partitions, like those of linux/BeOS/etc.) Which is again not a very good option, (as anyone who has experienced an over-burdened C: drive, or a Windows.000, or a UserName.ABC folder problem will tell you) for those of us who insist on clean installs. The only true saviour is the WinPE-based method of install (which again has its own quirks and problems). In this, a Win32 pre-installation environment (similar to what you see at T-39 in normal setup) gets initialized/booted-up from CD, and thereafter what you do with it is left to your imagination. You can then do the below: 1. Set it to run a .cmd which will..... 2. run a diskpart script (diskpart is what you see in the text-mode partitioning as well) 3. Which is configured to silently format the first primary partition (in NTFS) on the first IDE HD. 4. mount that partition as C: 5. Create whatever other partitions you want as per the sizes you want! 5. start I386\winnt32.exe with switches (for choosing the unattend.txt of your choice, options of copying cource, etc.) 6. after that, everything else happens in the way we are accustomed to. As would be obvious, it takes a **** lot of time before you can get a setup running off WinPE without major mess-ups. WinPE is geared towards a wholly different audience (not casual/home users), and its functioning makes that as obvious as can be. For more info on the WinPE/bartPE based method of installing windows, search the MSFN forums. Count the small mercies, and blessings in life - and just use the simplest method, which is manually partitioning in text-mode.

There's some humour going on here (in first post by topic starter) - did someone notice the word in emphasis? Well, I concur with his typo, alright! Windows does seem to go out to 'lunch' pretty often

As a matter of fact, I'd like to know if it is possible to manually 'catch' and 'release' such worms intentionally on a system. If so, how?Please see this thread, if you have an answer. From where can I get (and keep for later manual use) such worms, ( and how to 'slip-stream' them onto my CD, ROTFLOL).

@sead0nkey- It's nice that you posted some feedback at the end. It's always nice to know whether the solutions offered, worked or not. Well, so now I know how to get this thing working, after seeing what you did to solve your problem. This episode just proves that the learning experience (for me) never ends. So, is it like this? A: = 00000001 B: = 00000002 C: = 00000004 D: = 00000008 E: = 00000016 F: = 00000032 ........ Z: = 33554432 So, if I want to block access to Z: and C: drives, I would use the below code, is it? [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "NoDrives"=dword:33554436 "NoViewOnDrive"=dword:33554436 @maxXPsoft- Does the code, similar to as posted above for Z:+C: work for you? EDIT: bah, looks like I wasted time calculating the dword values for each drive all the way to Z. The same info was available in pretty clear terms at the site that maxXPsoft has referred to (above).

well, that command *IS* for the installation reboot. I hope you didn't think that your OS installation could possibly reboot without <GASP> windows itself re-booting.

If this is for WinXP/2k, here's a registry tweak to do your bidding: Windows Registry Editor Version 5.00 ; Will apply only to currently logged-on user [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] ; hide F: drive in "My Computer" "NoDrives"=dword:00000007 ;the user cant view the content of the drive and also stop them using - Run, DIR, or Map Network Drive "NoViewOnDrive"=dword:00000007 Save this text (above "CODE" section) in a new text file as "hide-drive.reg" (see that you haven't accidentally saved as hide-drive.reg.txt). Then log-in with the user name of the user who should be restricted access to the drive, and double-click on hide-drive.reg, and when you are asked "Are you sure you want to add this info to the registry?", click Yes. The above registry-code will disable viewing/accessing of the partition mapped to your F: drive from Windows.

LOL...... This incident proves that you have to understand what you are doing. I guess you just blindly copy/pasted all the commands found on the unattended guide. If you see in your main.cmd, you might have a line which starts with shutdown -r -f -t 60 -c "blah-blah blah" If you don't want that re-start, you have to remove this line.

Thanks for the download, got the utility and ran it (not tested it though) - it runs fine. The nice thing about it seems to be that it can even rename a domain user. But then, I don't see any extra features in it than in the NetUser tool. Also, if both were made by the same author, which is newer and which is older? As for who is the author of both the tools: RenUser does not offer any command-line switches, it is a simple and direct tool, and the "/?" switch does not reveal who made it. NetUser offers an extra command-line argument to make the user's password never expire, and running "/?" yields the info that it was made in Dec1997 by Siemens.

Nowadays, IE6/IE-shells are simply too vulnerable and bullet-ridden with security holes. That's because of the deep integration between the OS and the browser. Here's a proof of one such lame exploit: 1. Go to google or any other site, or open a HTML page in IE. 2. Right-click anywhere in the white space and select the option "View Source". 3. The code will be shown/opened in notepad - so far, so good. 4. Now make a folder called "NOTEPAD" on the desktop. 5. Repeat step 1 & 2. 6. You will see that the notepad folder (instead of notepad-the-accessory) opens. 7. Hereafter, it's your guess as to how this bug can be manipulated maliciously (embed an active-X control as folder icon in desktop.ini or autorun a JPG file with system commands, etc.). It is tested to work on IE5/IE6 and on all versions of MS-supported windows versions (Win98/98se/ME/2k/XP/2k3). But I seem to be here preaching to the already converted - last I saw, IE/IE-based browsers had a very low share of votes. The majority of the 'post'ers here have reported using alternative browsers.

I don't understand what you mean to convey with that sentence....OK, so Alanoll's confirmation makes it apparent that there's something *ELSE* wrong somewhere on my CD (user error ). I was afraid that's what it would turn out to be. In any case, I'm gonna put off trying to find out exactly *WHERE* that bug is (since I can simply use a silent SFX for the same function).

I love all this info coming in, do keep at it pals.... You do come up with things which I have over-looked. Some more?

Oh! So such a thing explains my problems...... Here, I refer to OOBE - the first-run experience (which asks to turn on automatic updates, Asks user names, network, activate, register). I had altogether removed OOBE (using nLite). After that, I found that nothing in my $Docs folder was copying over to the HD anymore. This was happening on SP2 RC2. Due to this unexpected 'feature', I then re-slipstreamed and re-built my CD, but I still am not able to get the $Docs folder working. I suspect $Docs functionality has been removed in build2149 to make it process-compatible with win2k. Could Alanoll or someone test out this for me, and tell me if this is true or not? {Just place a "deleteme.txt" file in your CD's "$OEM$\$Docs\All Users\Desktop\" directory, and see if it copies over as it should - if it does not, my suspicion is true}.

Well, getting rid of all your Pre-SP2 hotfixes (after having integrated SP2 into your CD) should free up about 40-50 MB (if you've been keeping yourself updated with all the latest updates), I think. As for the "80 meg" figure, /me thinks it is to our detriment. The current builds (250MB+ in size) of SP2 can be used to update XP Tablet/MCE as well. Maybe the SP2 final will be geared only towards Pro/Home. Also, I'm finding it a little difficult to believe MS's current claims (of SP2 being an ~80 MB download). What they say can only mean 2 things - either they are actually referring to the consumer WU install (not the full, network installer); or these are just wild rumours. The Alanoll of old seems to be back now: The same literary/poetry bent of mind..... The same "have-to-read-his-post-a-second-time-to-understand" language..... [hey, wait a minute, don't my style of posts look that way too?] @Alanoll- I'm not trying to bait you, I hope you understand that I'm just trying to have some good-natured fun (unfairly, at your expense, sorry , but couldn't let go of the chance)

I would like a download link/home-page to renuser.exe please.......

As of now, none. If at all you want to be on top of simply *EVERYTHING*, you could add the .NET framework, but other than that none. After SP2 RC2, there are no required windows updates, nor any component updates (like dX9, WMP9, etc.).

See my post here for the easiest way to do it. You can run that tool before first-login (the way you want to do it) as well.

If you want to set the computername and more things after install, or at T-13 stage (thru cmdlines.txt) read on...... Download and save the change.vbs (attached to this post). Then, put that file to where you want and call the VBS file (start /wait ....) during T-13. Enjoy! change.vbs

I see you didn't even try searching. The page you want was linked to from MSFN's guides section. Go here to find an answer to your question : SysReq If you want *REALLY* technical detailed documentation about the same, go here and download the "Draft version 0.45 of Windows Logo Program System and Device Requirements".

Yes, it counts as default for all users you create (in whichever way). BTW, WIHU might be a bit of an overkill (for a function as simple as renaming the Admin unattended-ly). As for event log, I have no idea - I guess some one who does will trip along to this thread and tell you how to do that.

See and click the link (to BootSkin) I posted in the above post. All info you need is available there.

I've not ever heard of ristndrd.sif! But I would think that its syntax should most likely be identical to unattend.txt (i.e., the normal one, created thru SetupMgr - that's what is used for RIS installs - which is what you are doing, I suppose). This line makes me think that you are just talking about winnt.sif (but renamed, can be pointed to using a switch for winnt32.exe). If so - yes, you can.Just remember that not all the settings described in ref.chm are usable across all types of setups - some parameters are to be used when the install is from a CD, some for a RIS, some for install from DOS-mode, etc. So use the relevant settings for your ristndrd.sif In any case, trying what you have read here won't hurt (on a test machine, to be sure). So see what works and does not in your environment - enjoy!

That could be because you have set a @ECHO OFF line in your batch file (the one to be logged).

I have Opera running crash-less since 2 years here. Currently on Opera 7.53+Zone Alarm 5 Security Suite. Opera doesn't have problems when XP's SP2 pre-release Windows Firewall is active either! The reason for your crashes must be something else other than a firewall - maybe you have a corrupted installation? Try un-installing and re-installing Opera (latest version). Also, see if re-generating your Opera AppData can solve the problem (delete the folder "C:\Documents and Settings\user_Name\Application Data\Opera" in Win2k/XP and "C:\Windows\Profiles\user_Name\Application Data\Opera" or "C:\Windows\Application Data\Opera" in Win95/98/ME).