prathapml

Right. Trying to get around the trial process is not allowed. You can find the link to forum rules in my signature.

Nope, it works with any valid Nero 6 key The emphasis here is on "valid" - with each new version release, pirated keys keep getting blocked out, so people using one of those will be told their key is invalid.

Done the moving of topic. Thanx for the heads-up Astalavista! Now if we could find an official news-source of this, only then it could be posted as software news. I guess it will show up on the official home-page of Executive Software soon, then. And was there any particular reason you originally posted this in Application switches forum? The switches for it will (mostly) still be the same: first "/A" to make an AIP Then "/QB" from the resulting MSI and folder. TADAAA !!!!! silent switches! @oioldman It won't show up v9 on our updates, because: 1. Its not on the official website yet. 2. We are only entitled to get updates to v8 - we will need to buy v9 to get it.

@busb 1. This build of XPSP2 (build 2180) is NOT buggy. It is the final release version of SP2, been perfect all through, for me. 2. Your monitor settings (the [Display] block's values) will be ignored if the correct driver for your video card is not found during windows setup - if windows doesn't have the needed driver within its driver library, you can integrate the driver that you install after windows setup - so that it gets done during setup itself. That way, you save time on installing drivers, and also your monitor resolution, etc. will come up correctly as per what you specified. 2. The regional settings and time-zone do work - try checking up on the position of the [Regional Settings] block in winnt.sif. Some of the threads here had got their problems (of winnt.sif values being ignored) solved when they changed the position of the relevant section. So maybe a try could be given to that? This is the order in which I have mine: ;SetupMgrTag [Data] [Unattended] [GuiUnattended] [UserData] [Display] [TapiLocation] [RegionalSettings] [Branding] [URL] [Identification] [Networking] [Components] [SetupParams] [Shell] [GuiRunOnce]It seems that (for example) having the [Components] block before the Identification block would leave [components] unprocessed.

No setup is affected at all!Those registry keys are related only to Windows Media Player (and even then, SPECIFICALLY to versions 9 and 10). If you start WMP for the first time (v8) on XP original, or XPSP1, it just simply runs - it doesn't throw nonsensical dialogs at you. But you would have noticed with a slip-streamed XPSP2 CD, that when you start WMP9 for the first time, it starts a **** setup (that is very annoying - come on, it was already setup which is why its able to run in the first place). This setup runs whenever you login with a newly created account (or user profile) - its annoying if you're the Sys-Admin for 30 PCs on a network, and each PC has 4 users - and 120 users have to see the WMP9 (which was actually integrated into XP) setup when they run it the first-time. And if you keep re-installing your OS, its even more annoying to see the WMP setup screen every month! While going through these setup screens, you're required to choose which locations, the short-cuts to WMP should be created in (desktop, start menu, quick launch). Also, if you have set WMP (component) to off from winnt.sif, you don't want the shortcuts to WMP to be brought back on, after running wmplayer for the first time. So there you have it - a detailed explanation of why the WMP setup should be managed using those registry keys. You can use them if you want it, don't if you are a fan of WMP.

I was asked about the below, and thought it better to post it in the thread as well, so more people benefit: What's the difference between Nero Enterprise Edition and Ultra Edition? The Ultra is actually the best version for most individual users - Ultra has everything that the other (lower-priced) versions have and more. The enterprise edition of nero has all features of Ultra, plus the following - enterprise edition is better if you have 2 CD-writer drives. Because the enterprise edition will let you write to multiple CD/DVDs at once, and also is compatible with NeroNET (write CDs over the network). The Ultra version does not have these 2 features.

It does work for me - many more of us also have a use for it. Just hope it doesn't get blocked by google!

Well.... this is a site/forum issue - so moving it there. Although, I don't know how many ppl are going to use the AvantGo feature - there has to be significant numbers, to think about doing such a thing.... Also, I had seen that MSFN was accessible fine with a WAP-enabled cell-phone (CDMA-based) - so that is pretty much sufficient, I thought.

huh?Could you expand on that? 'Coz I don't get what you mean. But I did think about it, and sort of understood what you mean... You need to put the .URL or the associated as per the below folders, on your uA CD: For all users (single entry) desktop: $OEM$\$Docs\All Users\Desktop\filename.urlFor entries individually on each newly created user's desktop: $OEM$\$Docs\Default User\Desktop\filename.url To have it in your Network NeighbourHood, I believe you need this: $OEM$\$Docs\Default User\NetHood\filename.extension Hoping this helps...

Yes, pretty much the same... Just the difference would be that you don't need to separate the files needed for nero 6.6, and all that. The same switches, the same zero-byte method.

You can try it if you want.... There never is one "right" method - anything is right, as long as it works! The command given in my previous post worked for me - always been using it that way...

Yes, its just a normal URL, AFAIK. You need to "Create new shortcut" and enter in a location like the below example: ftp://anonymous:password@ftp.microsoft.comThat's the pattern for FTP login thru a browser, and it will open the .URL file using whichever happens to be your browser.

Nope, both the two download links are working fine here. And if you DO get some "file access denied" or something of the sort, alanoll has also posted another link to the MSI in this thread, in a post on previous page.

Yes, this is a known issue. Discussed here - LINK You can use the slip-streaming of .NET 1.1 SP1 into the original installer. That will solve your problem, and also save you space on the DVD. How-To - of course, at the end of it you need to install your language pack. That would give no issues - same way as it is running now.

No, please don't re-post. *topic moved

*moving topic to software hangout

Everybody is valued here. Number of posts does not matter. ANNOUNCEMENT: Yet another change, with all the corrections suggested in the last 2 days. The start-menu and recycle-bin error is fixed. Some more sorting carried out, for ease-of-use. Version number bumped up to v1.6. Updated first-post. Re-download to get it. The bugs reported until now are (hopefully) fixed by now. BTW, its been a long time since some new tweaks were introduced on this thread. Looking forward to them!

XtremeMaC has given me this link: http://msdn.microsoft.com/library/en-us/ht...lpDownloads.asp So finally, for all those of you on this forum, who are making their own tool but did not know how to make their own help-file (.CHM) - here's your chance!

1. There was no need to set that, because that was the default value, anyway.2. I'm already mad at a few MSI-based app installers because they won't accept system-variables for the INSTALLDIR property. Add to that list. In fact, no MSI I've seen supports anything other than absolute paths for that property - which is a bother to specify, when you need portable installs for multiple PCs and differing patterns of usage (for example, if you install to D, then the installdir becomes a head-ache).

@crahak My nLite'd WinXP+ normal office XP. Running fine since 2 months on a Cyrix 233 MHz, 32 MB RAM, 2.5 GB HDD, 512 KB video card. His system definitely beats that.

You need to have your winnt.sif on the media that you use to boot. So you need to have winnt.sif on the floppy. Now, I don't know WHICH floppy needs to have it - probably the first one, or the last one. Just to be sure, put on your winnt.sif on all the 6 floppies. Then it should work unattended.

[quote]so does installshield x pro work on wise installers?[/quote]Best way to know: Try it and see.

@SiMoNsAyS What would be the use of 24 hours? Because, (if I am in his place) and I have made a new msstyles.dll (visual style) or a logonui.exe, or a resource-edited shell32.dll for Mac OSX style (or for whatever reason). I would have to host it on the site, and then go around announcing it - to classmates, friends, and online contacts. So each of these ppl aren't going to download it the minute I tell them. They will write it down somewhere, forget it for a week (or month, or 6 months), and then suddenly remember that "http://www.XYZ.net/macosx/shell32.dll" is needed by them for what they are trying to do. And by then, 24 hours is loooong past. Also, hardly 1 percent of people who have this "visual-improving" passion (those who use other logons, themes, etc.) have the ability to do the needed edits by themselves - the majority of them simply use files readily given to them. Just registering one down-side that I think it could have, that's all.... Having it hosted for just 24 hours is nothing. Yes, it might be not clearly allowed for you to modify files, but look at the thousands of sites that do it! (biggest example: themexp.org, wincustomize) And MS is not a bit bothered - its all the better for them, since you leave behind win98/2k and move to XP to be able to do all those cool new things. Nope, if you aren't doing cracking or something of the OBVIOUSLY illegal sort, you have nothing to fear. You can host for as long as you want.

If the setup.exe is needed, then mostly that should be in that folder (D:\Ghost_AIP) too. If its not there, give it the the setup.exe that it wants! (copy the setup.exe from your original installation folder to the AIP folder). Then try again, do tell how it goes.

Well, it gets to be a stumbling block to use the installer. What if you use this CD on a PC that is not based on the VIA chipset? Either the install fails, or it will show a dialog-box and stall the install - which makes it not unattended anymore. And what happens if the VIA drivers actually get installed on an intel-chipset based system? jeez.... frightening. Of course, its no worry if you're only doing this for one PC - this post is just to caution you about the possible problem that could happen. And people lend out their uA CDs to their friends too (for a minute, don't consider its legality) - so if you give your CD to your friend, he'll end up facing instability, because of VIA drivers on non-VIA hardware. You need to rather extract the 4-in-1 driver file, and use it through the OEMpnpDriversPath method - from winnt.sif.