Alanoll

That's because it's not a CRITICAL patch. It's only intended if you have a problem with certain programs in the loopback range. I personally am thinking of rehacking the TCPIP.SYS file myself again, and change it to 255. Dunno why 255, but....couldn't hurt. lol.

check your BIOS and make sure you are able to boot to a CDROM (DVD is the same thing). If it still doesn't boot, then my guess would be something messed up in the burn, and without knowing what you did...can't help ya much.

I dunno prathapml ... lol.

Here is the one I've been using since SP2 originally went RTM. It's unlimited connections.....so take your pick.... It's also ready to go as is, just copy it in your I386 folder and your good to go. http://home.comcast.net/~alanollv/TCPIP.SY_

Don't double post. Topics merged.

it may be that Dlink's setup is not an InstallShield but rather Wise or something else.

it should work fine.... I believe they're the exact same file, but I could be wrong.

the uxtheme.dll file is a language dependant file (for the most part). The English version may work on the hebrew, but it may cause unfor seen errors. You have two roads to take..... Use nLite....it should work. It just searches for a set number of bytes. Or Go to RaveRod's site for the HEX things to search for and patch it yourself... Or Go to vorte[x]'s website (www.vreality.net i think) and send him your uxtheme.dll file and he'll patch it and add it to his archive for others as well.

It's not a myth. It's undocumented. There are others as well. The full list is in SYSOC.INF (use expand sysoc.in_ sysoc.inf to view ) and there is a key in the registry that lists them as well. Give me a sec and I'll try and drag it up. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Oc Manager\Subcomponents] That's the key.

the ONLY txt file should be CMDLINES.TXT, atlest that you're concerned with. The others are NEVER even SEEN by setup. ALl that's neccesary is the GUIRunOnce line and the CMD line right below it.

Updated.

well.... you could have also used the official Microsoft reference as well. it's on your XP CD, in SUPPORT\TOOLS\deploy.cab. It's called ref.chm.

No, but there is a program with a GUI that you can copy and paste your Switches and program paths, and it makes the RunOnceEX.cmd file for you. http://www.msfn.org/board/index.php?showtopic=23751&st=0

Completely remove it from the install. Your registry keys do in this order 1. Disables the MESSENGER Service, which allows popup message from across a network, say from an Admin. 2. Unchecks the box in Express so the people on your list don't show up in the "address book' 3. Does exactly what your description says. the msmgs=off , I've found does NOTHING. You actually have to remove the INF. Use nLite, or open up sysoc.inf in your I386 folder, and put a ; infront of the line with the Msmgs INF file listed.

whoa boy...calm down Basically, what they're saying is.... Say you DON'T want to install Windows just yet, maybe you haven't saved everything. But you put the disc in the CDROM anyways (or you just burned and restarted). If you press a key, it will format the computer. True this is what you want when you ACTUALLY want to install Windows again....but say you DIDN'T want to JUST yet. Or AFTER Setup has completed, you press the key again, and then you have to wait for it to finish yet again, because you accidentally pressed a key. In this instance, it's better to use [Data] AutoPartition=0 [Unattended] Repartition=No FileSystem=* As then you will have one last chance before it all gets formatted. Bear in mind, you can use this, AND STILL format your drives through setup (or prior using Partition Magic or what have you) with just a few more key strokes (D , L , ENTER i believe). It's just a safeguard to accidentally pressing a key when you DIDN'T mean to.

EVERYTHING in $Prog will be copied over to %ProgramFiles% , and that's not where to put things that need to be installed. As prathapml, read the guide. That IS the "newbie" guide. Just AVOID ANY MENTION OF RUNONCEEX, and stick with the simple start /wait stuff in a command prompt. You basic files should be , install.cmd and cleanup.cmd. Both of which are in $OEM$\$1\Install. Then add this to your WINNT.SIF file [GUIRUNONCE] "%systemdrive%\install\install.cmd Work from there. Read the guide, and any thing you want installed, enter the lines into install.cmd. don't worry about cleanup.cmd till your done. All it does is basically removes all the setup files from the things you've installed.

@mtimmermann There already is a german translation of the Unattended Guide. Check the first page at the bottom. If you WERE to do a translation, you have TO ASK FOR PERMISSION first, if you look at the Credits & Copyright page, you will see...

yes. because. and you didn't change XUSER to XNAME

did you try moving the /qn AFTER the others? did you try adding msiexec.exe /i prior to the whole thing? The registration thing, try XNAME not XUSER. Wrong switch.

What line/lines are you using to install Winamp and to register it? As in copy paste what you TRIED to get Winamp to register via the MSI. I'm betting it's a simple issue as mistype or not proper syntax

What code are you using to register it?

use a full path for your destination.

it's in txtsetup.sif did you check for any random lines with just = or something? Sometimes it could always be a syntax error just before the line in question..... Or for some reason, you mistakenly copied over a SP1 txtsetup.sif file over your SP2. That could happen.....

@bishooman I changed your title to reflect the new version.

the xpboot.img and loader.bin are NOT the same file. Loader.bin should have come from your CDSHell download archive, and if you used any other file replace it with the original one. the xpboot.img is called FROM your INI file as usually a DAT file. LOADER.BIN is what you specify as your boot sector when creating the ISO. As for moving, WHY DON'T YOU COPY. Usually, you need all the files from the CDShell archive, in the folder boot, for cdshell towork properly.