prathapml

But importing for current_user and applying it during component registering will be the more "certain" way. Since the .DEFAULT key is not at all modified by any user you create! You need these keys: HKEY_CURRENT_USER\Control Panel\International\Geo HKEY_CURRENT_USER\Control Panel\International

If you need content on the page and links to start apps from there - and need it to be easily modifiable (and look good visually too), then what you need is: Autoplay Media Studio - easy to build an autorun within minutes.

is the HTML and setup.exe in the same folder? It may not be working, since the working folder of your HTML might be different. And since you've anyway started on this path, let me tell you of some more nice possibilities: 1. Rename the .html to .hta - that makes it a HTML application that runs without a browser-like toolbar, etc. (useful to have a "pro" looking autorun). 2. Setup an autorun.inf in the root of the CD, which will run this HTA file.

In this case, using disk-mount is not a help. Because runonceex.cmd will get run at T-12 (during cmdlines.txt, when it shows "12 minutes remaining"), take a snapshot at that point, and then it should work.

Because RunOnceEX.cmd is a batch-file, you just need to use standard batch-file methods for such purposes.All you need to do, is to either use "REM" or the double-colon. For example, let's say that you want to make it such that the last 2 lines are ignored in runonceex.cmd: REG ADD %KEY%\025 /VE /D "IsoBuster 1.5" /f REG ADD %KEY%\025 /V 1 /D "%systemdrive%\install\IsoBuster1.5.exe /VERYSILENT /SP-" /f REG ADD %KEY%\025 /V 2 /D "taskkill /F /IM isobuster.exe" /f REG ADD %KEY%\030 /VE /D "Kerio Personal Firewall 2.1.5" /f REG ADD %KEY%\030 /V 1 /D "%systemdrive%\install\KPF\Setup.exe -s" /fThen you'd change it to: REG ADD %KEY%\025 /VE /D "IsoBuster 1.5" /f REG ADD %KEY%\025 /V 1 /D "%systemdrive%\install\IsoBuster1.5.exe /VERYSILENT /SP-" /f REG ADD %KEY%\025 /V 2 /D "taskkill /F /IM isobuster.exe" /f REM REG ADD %KEY%\030 /VE /D "Kerio Personal Firewall 2.1.5" /f REM REG ADD %KEY%\030 /V 1 /D "%systemdrive%\install\KPF\Setup.exe -s" /f REM DigeratiPrime, these lines are ignored Hoping this helps....

Well, sometimes the answer is so simple that we don't get it until after we have chosen a HUGE round-about way to do it. Happens to me too! Anyways, here's what you should do: 0. The below is only to simplify things as far as using switches goes - you can use the setup.exe as it is, but I'd rather not use diskeeper's original installer. 1. Run the original installer (according to your VBS, its "\Diskeeper9\setup.exe") with the "/A" switch, at command-line to have it install an Administrative Install Point (AIP). 2. Then get to the folder where the AIP was created - it will normally be larger than the original installer was. 3. Put that folder on your unattended CD or network-share. [optional : If you want it to occupy less space, compress it to RAR and make it an SFX (self-extracting silent archive). My diskeeper 9 archive is only 8.7 MB. ] 4. Now, using your normal scripts, call the .MSI from that folder. If you use RunOnceEX or XPlode or any of the million methods, you might need to modify the example below (below is just a simple command-line/batch-file type of command to silent-install diskeeper to where you want it) %systemdrive%\install\diskeeper9\admin-point.msi INSTALLLOCATION="C:\Program Files\Utilities\Diskeeper" /QB If you want to disable the "check for updates" that diskeeper does, when its started the first time, there's a registry tweak - just search in your registry for it. Yes, most MSI-based installers have this property. They even have a property to specify exactly where the shortcut to the app should be created, in your StartMenu! IMPORTANT notes about installlocation property: 1. You need quotes around the path, *ONLY IF* your path has spaces (otherwise don't use quotes). 2. The **** thing doesn't allow you to specify system variables (for example, you can't use INSTALLLOCATION=%ProgramFiles%\Utilities\Diskeeper). Hoping this helps.....

Well, the first .BAT file, you can run it from GUIrunOnce. The second .BAT will need to be scheduled to be run at next reboot after that. how? you can use RunOnceEX registry keys for doing that. You need to have the commands for making the RunOnceEX registry entries, at the end of the first .BAT file. some info

Please post in correct section next time! *moving to gamer's hangout

Also, if you need to modify the files on your Virtual Machine's hard-disk, you can mount the .VMDK in windows under a drive-letter. VMware DiskMount Utility (for Windows XP, Windows 2000 and Windows Server 2003) Examples Using the VMware Virtual Disk Manager

You need the PsShutdown tool from here: http://www.sysinternals.com/ntw2k/freeware/psshutdown.shtml Check out its switches for its usage.

@nazz It looks like you have an older version of the drivers. The SoundStorm utility does not use INF anymore, plus it has got renamed to NVmixer. Re-download the new version of drivers, and the new NVmixer uses standard InstallShield procedures.

The problem with this, is that if you use this script on a PC that is especially slower than expected, it will not work properly (i.e., if expected dialog-boxes do not show up within 500 milli-seconds). If all you want is to change the folder to be installed to, just use the "INSTALLLOCATION=C:\Program Files\MyApp" property of the MSI installer, at command-line. Example: %systemdrive%\install\diskeeper9\admin-point.msi INSTALLLOCATION="C:\Program Files\Diskeeper" /QB

Does NT4 offer such abilities at all? Anyways, attached is a list - you'd find the required settings in it. TimeLanguageCodes.txt

For me, SP2 has been same as SP1 has always been. Opinion: Don't use XP without it.

XtremeMaC's right! I really don't know what we can add here, that you can't already get thru google! (no offense meant) But still, if you need suggestions, here's one: http://100webspace.com *topic moved

Nope. Its not the same. The purpose in this thread is different. The 66.93 drivers come "CAB"bed up - and by that, I mean, nVidia has "makecab"ed each file. So when you aggregate all your drivers, the total file-size ends up higher due to the over-head of double-compression. The purpose here is to have all files in their pure, extracted form. (and also delete a few useless files along the way).

Of course, you end up having errors. And about the other post, somebody did use the WINNTBBU.DLL from Svr2k3 for WinXP.

Well.... Look around the forums, and you'll find info about it. Its too long a topic to type out! Below is a pointer to what you should look for. In short, Win2k/XP use hardware abstraction layers to operate in protected mode. Now, your objective should be to get it to use a common HAL that's compatible with all MoBo's. So prolly install it on an old PC that uses extremely common and base-line hardware, then image it. Or, just before you ghost it, remove your mobo/proc drivers. There's sites that tell you how to do that.

IRC 5t!11 rul3s. B)

Hi you're uber, and you won't be a noob for long! Welcome to MSFN forums. You sure would have a nice time here.

Add your user account pics at this folder-structure on the CD: $OEM$\$Docs\All Users\Application Data\Microsoft\User Account Pictures

Please read up more about it. XtremeMaC is right, I really don't think such a standard exists.SATA 1x = 150 Mbps SATA 2x = 300 Mbps SATA 3x = does not exist (not yet even formed a committee to create that standard). Nowhere does 3Gb exist! They did want to move to BTX power-supplies, but in all likelihood, compatibility with ATX will still be maintained.

Yes, you can remove IE and still keep DirectX. Best thing is to use nLite to remove IE - you'll find nLite on this forum itself.

I don't think its possible.In all likelihood, the guide's gonna have wholesale changes, and the translators will have to re-work it.

That's nice gape. I'll look forward to it. Just see that all the WinME haters here don't latch on to you!