prathapml

@netquik Whatever the name of the hot-fix, you need to just replace it with the number. Like for example, info about the update you mention, should be available at this address: http://support.microsoft.com/?id=885894Just set your browser to keep auto-refreshing that page, until the time something gets posted there by the MS documenters.

yeah, but if you just simply want to extract the EXE, using default options specified in the file's "comments" field, there are standard switches. SFX executables created with WinRAR: /S SFXes created with 7-zip: -y /q /r:nYou can even add the location to which you want the 7-zip compressed files to be extracted to: -y /q /r:n -o"%ProgramFiles%\whateverfolder"

Then its good that they did not. Just FYI, MSI installers have been used by MS since late 1999 (office 2000). MSFN forum was started 2 years after that! So this forum did not come up in response to silent installations - that and MSI has been around for longer. There's been a lot more than silent installations alone, in this forum.

Mostly it can accept it, I suppose... But the best way to know, is to try it yourself - try sending the switches to the MSI as you said. You can directly try it within windows itself, no need to _necessarily_ do it only during unattended.

Using command prompt, browse to the folder of the ghost install, and run this command: setup.exe /AThat will create an administrative install point (AIP, it might be called server image). There onwards, you can use the .MSI file in the folder (which you will now select while making the AIP) with the switch that you previously used: /QB REBOOT=REALLYSUPPRESS

Simon's first post has the entire tutorial.

Yes, I do the same things that you said in your guide (first-post of this thread) - and my shortcuts in start-menu says "Enterprise Edition". Works fine!

There's no need to create the folders on D: drive. Setup will look after all that, so no worry on that count. And no, we don't ignore the comment lines, header or section names.... So, the line 12 turns out to be the commonprogramfiles line. (just open winnt.sif in notepad, enable status bar from view menu, and it shows there the line number) And what's making it error out? The extra quote in the value. (I think) (I mean, there is 2 of the "quote" symbol at the point that I have highlighted in red).Hoping this solves the erroring out. Do post back on how it goes. But there's no need for specifying it (or is there need for it? do correct me if this is wrong). I'd think since your "ProgramFiles" folder has already been specified as "D:\Program Files", your CommonProgramFilesDir *WILL* be "D:\Program Files\Common Files" even if you don't specify it in winnt.sif.

Even there, slip-streaming is the better option.If your XP CD was 550 MB before any service packs (I mean windows alone), after SP2 it will be about 570 MB. That is all the difference - and this small difference saves you loads of head-aches! And even after the CD has become 570 MB, you can reduce the size - following the link given by MHz (to the guide), you can reduce it to be just 390 MB! (and that too, without losing anything that will be missed by you!)

Please have a read of what the current 6.6 package includes. Those packages (actually, an updated version of both NVE and NMP) are already "integrated". Simon's first post already includes the info on how to install those as well. He says the nero as well as NVE and NMP can all be installed from this package itself, you only need the switches. @SiMoNsAyS Haha..... Its very difficult to use your nick while referring to you. How do I say that you said something? SiMoNsAyS says?

Yes, its always better to slip-stream the latest SP into the windows install. It saves on time. Also, it saves some head-ache. Some major modifications are made to the system when you install SP2 - which might make some apps stop working, or work differently. If you already have SP2 merged, you won't have those worries. Many worms will not affect you either - since SP2 has a better firewall. And anyway, if not today, you need to upgrade to SP2 tomorrow. So why not do it today itself (I mean, merging into CD as the guide says) if you don't have any problematic apps (any apps which give problems after SP2).

Did you try mounting that (previously D: ) partition back from disk manager? Or, did you try seeing it with a partitioning tool (partition magic/acronis) ? Because its possible that somehow the partition's id got changed. It can be as simple as "NTFS" became "NTFS hidden" or more complicated - just change it back to the normal.

Hello Zilevoli! Welcome to MSFN forum.

@twilli48 yes, that is all you need to put even in your runonceEX method of using it. Of course, remember to increment the sub-branch. For example: REG ADD %KEY%\025 /VE /D "whatever" /f REG ADD %KEY%\025 /V 1 /D "your command to install dwMX2004" /f REG ADD %KEY%\025 /V 2 /D "taskkill /F /IM iexplore.exe" /fTo be specific, the integer that comes after "/V" in the command should be higher than previous one (just reminding, that's all).

@Astalavista yes, I'm not alanoll, but thought I could chip-in.... Simon has already said what to do with the deleting of the demo key. First, you have to get Nero 6.6 from this link. Then, you need to modify the installer file (its a comment to the RAR SFX): ;The comment below contains SFX script commands Setup=setup.exe /SN=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX /WRITE_SN /SILENT /NO_UI /NOREBOOT /NOLICENSE /NOCANCEL TempMode Silent=1 Overwrite=1 Title=Nero 6.6.0.0 Ahead Software AGThis is (I think) the best way to go about it. THAT IS ALL that is needed, and if it is done properly its fine. Works for me, atleast. Now, as for what you DID ask: Let's assume you already have a different key, or a demo/blocked key or whatever - basically you want to have it removed, before installing v6.6, right? Okay, I did a bit of exploring, trying to simulate what you would have on your machine.... and landed up looking at this: [HKEY_LOCAL_MACHINE\SOFTWARE\Ahead\Nero - Burning Rom\Info] "Serial6"=- "Serial6_2"=- "Serial6_3"=-Run this registry code prior to starting nero install - it will ensure that all possible old keys get wiped out, and only your new key gets in. Optionally, if the installer you are currently using IS doing strange things, this should fix it instead: [HKEY_LOCAL_MACHINE\SOFTWARE\Ahead\Nero - Burning Rom\Info] "Serial6"="your key......" "Serial6_2"=- "Serial6_3"=-Run this code AFTER nero finished installing. This will basically re-affirm what your main key is. If you had modified your Nero 6.6 installer as simon said (with the "/SN=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX /WRITE_SN" switches) - that would have established your valid key as the main key, and you only need to delete the additional keys (according to the .REG code above) which are the villain of the piece. @Alanoll yep, he did call you actually.... Anything to add to this post? And I also have this interesting find: [HKEY_CURRENT_USER\Software\Ahead\Nero - Burning Rom\Info] "HaveReadSNFromFile"=dword:00000000I found this while exploring. Any ways to manipulate it? Could it possibly be of use here?

My vote goes to - Diskeeper Pro 8.0. And that is the one used by MS as well (in a cut-down manner, of course) since win2k onwards. The best part is that it simply updates/replaces windows' own defrag tool - since it is actually a cut-down version of itself.

Well, its not supposed to be used like that actually - please select only the tweaks that you want - from the description. Exactly! That proves it - the tweaks contain everything - many of it may not be needed by you.;----- Remove Shortcut Arrow [HKEY_CLASSES_ROOT\lnkfile] "IsShortCut"="" [HKEY_CLASSES_ROOT\piffile] "IsShortCut"="" [HKEY_CLASSES_ROOT\InternetShortcut] "IsShortCut"="" ; Display drive letters [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer] "ShowDriveLettersFirst"=dword:00000004I believe the above will be what you need - to reverse the link icon, and drive letters.

Why don't people read that the rules say "no multi-posting"....

Right. You need to keep that file in the firefox-installed folder - where you installed it. Then all new profiles being created will get it. Eg: C:\Program Files\Mozilla Firefox\defaults\pref\

Yet another round of modifications - mainly corrections as suggested by everybody. Most importantly, the issue where the registry editor right-click option made "My Computer" turn into "� � � � � � � � � � � � r" has been rectified. Atleast now, its (hopefully) bug-free for the most part. Also, some of the tweaks for which some of you wanted warnings in the description - this request has been done. And better sorting in the file too. Then a few additions to the tweaks. All suggestions/additions to this point have been added. Re-download to enjoy the new file. Hope ya like it!

Well, that's true pesko, but ceez is referring to a different thing.... @ceez That is the notification that comes up when any compressed file is being scanned by NAV 2004/2005. So just go into the options and disable "Scan inside compressed files" - from the "auto-protect settings".

Does look that way. And then this is a known issue. The work-around is to use some other ISO-mounting utility (like Nero's ImageDrive or something), and capture that drive into VirtualPC.

If you use the first option - (setting autoactivate=yes in winnt.sif) - that will do the activation online, but by itself without you needing to do anything. That will work only if you have already activated previously once on that PC, with a valid key. The second option, happens completely offline and easy.

Yes, you can run a .CMD thru runonce. You can't directly run it, though - since it has to be processed the command-interpreter. So this is (an example of) what you need: CMD.exe /C "%systemdrive%\install\whatever-filename.CMD And as for .BAT and .CMD - both are actually the same. But I'd say its better to name all your batch-files as .CMD. That's because, that way you'll ensure that the win2k/XP scripts that you're making won't accidentally be run on win98/95.

Its not illegal as such - 'coz its not going against any law. The constitution is not telling you to stay away from modifying windows files. But what it *IS* - is against the terms of the MS-EULA - which you (supposedly) agreed to, when you opened the box/package that contained the Windows CD. As for those sites with modified logonui's and patched what-not.... MS isn't bothering about those, simply because it poses no threat to them. In fact, its in their interest, that you stay excited about their OSes, and innovate new ways to drag other people into getting locked into their platform. For example, the moment there's any file-modification out, regarding breaking activation or something - you can be sure MS will try to get that info/file taken out. So what's the final verdict? Your modified files should be of the harmless type - that's quite okay to have hosted on the web, in the sense that MS won't bother about it, and nor will you be doing anything illegal. PHEW!!! (yes, yes.... don't tell me - I know its too lengthy )