prathapml

Where exactly in the OEM folders is it? My Shell section of winnt.sif is as below, and works fine: [Shell] CustomDefaultThemeFile="%systemroot%\Resources\Themes\Slate.theme" DefaultStartPanelOff=No DefaultThemesOff=NoSee if you are having any unnecessary spaces or any illegal character in line50.

Considering that all nVidia cards based on a particular chip are pretty much the same, and that nvidia makes unified drivers which aren't as buggy as ATi's, the solution is simple: Stick with nVidia's drivers - they aren't "generic" or in any way lesser than what has come with your OEM (eVGA) card. If anything, they are better - nVidia 's own drivers can do better for configuring your second monitor. There's no way I can know what is happening with eVGA's customised drivers and CPL, but I do know that abandoning them and using nVidia's driver set is the better option in your case. I suppose that was your question - if I've missed out on reading any other question you may have asked there, do ask it. Hoping this helps.....

sleepnmojo (above) seems to have gotten it working. I normally install it either through cmdlines, or the autorun - so I can't comment on the certainty of the install. I suppose doing what he has described (in the first page) should get you what you want.

Well, even today (right now) I did a manual slip-stream and it works fine. Must be a problem elsewhere. You could try changing the brand of the CD-media on which you write your installs. Also, open up "I386\txtsetup.sif", and check if the SetupSourcePath is set to "\".

you're welcome. I've been closely following the development of the shrinker since the beginning, and it works well for me (LOL, took me some experimenting before I learnt how it works). Anyways, I figured now's a good time as any to help those coming to this topic.@Moderators Maybe this thread belongs in Application Switches forum? (despite the fact that it is related to Unattended Windows?)

Well, you can put it anywhere you want to - but the appropriate directory should be mentioned in the winnt.sif. I put the drivers within a sub-folder under "Windows" because that reduces the clutter at the root of the C:\ drive. Accordingly, I've changed the OemPnpDriversPath entry.

A short starter, for how to get the nvidia drivers working through this method: 1. Extract all the files of the v61.76 drivers into a folder called "nVidia". 2. Now put that folder in this path on your uA CD - "$OEM$\$$\" 3. So now, you should have a "$OEM$\$$\nVidia" folder with lots of files (no folders) within, including atleast one file with a .INF extension. 4. Confirm that the below is present in your winnt.sif: [Unattended] OemPnPDriversPath=windows\nVidia (if you have more drivers to add, do so using the ";" separator). 5. Also check that winnt.sif is in your I386 folder. 6. Now make the CD (according to instructions from the MSFN guide), and boot-up. 7. Complete the setup, and if you have any graphics card based on an nVidia chipset, the newer 61.76 drivers would have been installed. Hoping this helps drewdogg, and all of you who have been having issues installing this version of the nVidia driver, on XPSP2.

The nVidia drivers are to be used in the "OemPnpDriversPath" method - just like most other drivers - there's nothing special about nVidia drivers install that needs to be mentioned here. If something is unclear, please visit the official MSFN guide here: http://unattended.msfn.org/ - its all explained here, including the details you want to know.

Well, there's a command-line utility available, that will mount your vmdk. This one is for windows (there's another for linux) : http://www.vmware.com/download/diskmount.html. BTW, having corrupted partitions in VMware is a non-issue, if you are not using the physical disk itself - VMware makes virtual HDs and partitions, all contained within a file on your host OS' file-system. So that's not a bother.

Oh yes, I can recognise a former "Bombay walla" when I see one.... And, do test out those settings in winnt.sif (for remote assistance), before concluding testing - maybe it also needs additional settings from Windows.Firewall. Well, in any case, I'm happy to have helped people.

@Cee-Kay That's exactly the sort of dis-couragement I was afraid would get rubbed-off.... You can see that there was plenty of response to your solution. Do keep contributing - just because one person (not exactly good-naturedly) was not appreciative of you doesn't mean you should stop trying to help where you can. The rest of us are all in favour of new wind blowing across us stale old-timers. In fact, you can see that even the one who was critical of your method was initially happy to try it. Please do not move away from the scene. Some ideas work, and some don't - we just have to accept that and keep digging for solutions.

You can search, and there's bits-and-pieces of info all over the place, but there's no one place where you get to see details about it.... Well, I'll see what I can do to help - I've been thinking of writing a how-to for cmdlines.txt usage since a long time (with a beginner's view-point, and tips, and so on). But probably I'll get to that in a day or two, so please bear with it. @all Hey MSFNers, if there's already a HOW-TO for cmdlines existing, do tell me - so that I don't need to spend time on an unnecessary topic. Also, how many of you would be interested in having one, if there isn't already?

No! sleepnmojo above, has given the link to the thread that has instructions for this.

I can confirm that this works - and a small tip for ya people.... Since this is going to be only used on WinXP (from its autorun, or from its unattended setup calls), you can delete InstMsi.exe and InstMsiW.exe, and re-claim about 4 MB of space on the CD. To me, that is the main reason why I'd prefer this extracted (2nd) method, over the first method (which simply uses the downloaded file).

yes, I was thinking so too, so I used the solution here: disable o2k3 CEIP Since we normally use a MST (transform) to install office silently, the solution described there is the most sure-shot way of accomplishing what you want. I did not refresh this page, so what do I get? The solution already posted above, LOL. He was quicker.

Right! You have mentioned an important thing I over-looked - okay here's a plan for eliminating that negative feature: If the password is correct, the CMD loads the necessary environment (or startnet.cmd or whatever) using plain "start" commands (not "start /wait", as that will have the impact likuidkewl pointed out). The next command to get executed after the "start .\myenvGUI.exe" will be EXIT, that's all. So your custom CMD is present only for the purpose of password, and does not encroach on any resource.

Make a new section in winnt.sif called [PCHealth], and then use the values below. your wish is granted.

- If a previous version of SAV is running, the SAV9 setup will automatically manage the uninstall and upgrade. If NAV or some other antivirus is running, I believe you can use the "/uninstall" switch on the original installer package. Also, please note that running more than one Anti-Virus at a time will result in lot of problems. But then, normally an unattended install means that you have pre-decided what are the things going into a setup of a raw machine (so there's nothing existing before this), so that shouldn't be a source of worry..... - Hmmm..... This is a good idea actually, but needs more work than is worth putting in, to make it happen. It will install in its own language - if you have a spanish version of SAV9 on the setup, it will simply install spanish language version of SAV9, that's all - no auto-detection of language - so that's a disappointment for you. - You can pre-configure live-update features using the LU-Admin app : look here - SAV settings can be pre-configured when making a distributable setup EXE. Look on the CD for further help about this. Hoping this helps.....

The easiest way has been told by peachy above - that's the one I've all along been doing too! BTW, please enclose any code from your configuration/INI/REG files within the [code ] tags (the way peachy has above). That contributes to being easy on the eyes, and elicits a quicker response (because it doesn't require all THAT much of reading to understand what the post is all about).

When you have got the setup ending up with a 7.x MB install, you KNOW that it was not successful. What has happened actually, is that just the root of your CD got copied over, and the installer files are still where they were. Here's a few things to check when you have that problem: 1. Have you properly made an admin-install point. 2. Was your source-CD scratched or damaged in any way. 3. What is the language of the MS-Office you are trying to shrink, and is it supported by Office Shrinker. 4. Are you running the shrinker itself properly (un-install Office, and then run the shrinker). If you want any more trouble-shooting suggestions, please have a good read of this thread - all those problems have been discussed and solved. Hoping this helps....

Please just use OEMpnpDriversPath itself, for nVidia forceware drivers - everything (and the nVidia Control Panel) installs properly that way. I've said many times, that the 61.77 (being non-WHQL) does not get installed by windows setup automatically. The solution is to stick with the WHQL-certified v61.76 drivers - get them from here - http://www.nvidia.com/object/winxp_2k_61.76.

Hah! You know what? I've all along been trying to do the opposite of this. (Make the images in "My Pictures" not show up as options for Wallpapers). It hasn't happened on any of the machines I manage, if it did, I could've done with a fair bit of reverse-engineering..... Don't forget me when the solution to this is found - I'd like to know HOW THE HELL I can replicate what happened involuntarily on your PC.

Well, now that you mention it....... 350 watts is too under-powered for a modern system, especially with all those power-guzzling components that you already have. Add a DVD-writer, a high-end graphics card, a USB 2.0 scanner (which _could_ draw power from your PC, instead of a power socket), and you'd see what I mean. It wouldn't be sufficient power at all. Today, 400 W is standard. And I think that is sufficient - if you have the $$$, get a higher rated PSU than 400W (maybe 550W ?). Just so you know, my current PSU (Codegen, 400W) cost $16 - so its pretty cheap actually. And another PSU brand you could consider is Antec (they demand a price-premium, though). You MoBo listed above is actually pretty good, I just meant to say "go for a better MoBo, if its affordable" (instead of your currently listed i865-based MoBo, go for an i875). But yes, the Abit you already have listed isn't bad. Hoping this helps......

Well, your screenshot (attached above) is pretty self-explanatory. Now, what you also need to tell is what information it asks, after showing you that box.

I haven't heard of any way to do it, but your question set me thinking..... You could have a batch-file that runs as the first-thing upon loading the winPE environment, which asks for an input. Now, this input must match a pre-defined text that only you know. (maybe you could use IF ELSE statements, or something) So, if the right input text (or 'password' in other words) is entered, it will run a different section of the batch-file which carries on with the loading. If not, the batch file will simply keep looping to the same "Password Prompt". Also, since the next step in the WinPE loading process is controlled by a different section (:LOAD), anyone who closes the command window will have to see no further progress - script it such that he will simply sit back and see a re-boot. This is just a suggestion, there will be others around, I'm sure, who'll be able to take this and refine it to a usable form. Do post back and tell us how you do it.