strel

OEMSCAN_ADDON_MULTIOEM v1.8 is more updated. That's quite useful for your admin tasks and a barrier for most people, but the problem is that anyone with the same manufacturer string (BIOS) can use it as you do, moreover anyone knowing that method can take the CD and adapt it to their hardware.

If they were installed through svcpack.inf you can revert it, otherwise don't think so. Look for the packages in question into ..\yourXPCD\I386\SVCPACK\, and if you find them you can remove them from this folder and remove its entries in svcpack.inf doing this: ..\yourXPCD\I386>expand -r svcpack.in_ ..\yourXPCD\I386>notepad svcpack.inf Remove the entries in question and save. ..\yourXPCD\I386>makecab svcpack.inf ..\yourXPCD\I386>del svcpack.inf

Binding installing to MAC would the most effective way, but I think it is not possible, though not affirm it. I think you best chance would be net install.

Maybe it's because of firefox is not installed (but would be really strange), download page states the .NET assistant addon should be active in firefox for the hotfix install to be effective, and if not, reinstall should be done for the addon uninstall button to appear. I think langpacks has nothing to do with all this.

I've found this, it's similar to your scenerio but make your checkings.

Don't know what's the cause. But I'll try to use diskpart to assure the system detects CD-ROM volume and if this happens to try to assign a letter to that, this way: 1. Run 'cmd 'or open a console 2. Run 'C:\>diskpart' 3. Run 'DISKPART>list volume' , and notice wether diskpart see the CD-ROM or not, and if it has a letter assigned. If it see CD-ROM but don't have letter assigned do: 1. Run 'DISKPART>select volume #' ,with # as you CD-ROM vol number as listed previously. 2. Run 'DISKPART>assign' 3. Run 'DISKPART>list volume' to check.

I don't think so. What iamtheky is saying is that he got similar problems than yours when he was using this diskpart script that assigns z: letter to drive 0 (CD), and system was reasigning the rest of the drive letters because of that. He is only pointing to a possible cause.

2 Trolleri The installations are made through administrative install method which is an officially documented method of preinstalling. The only unofficial thing this script does is pushing some registry tweaks through NETWUFIXES.MST to avoid some of the win/ms update .NET annoyances to make it think it has finished its work (what it actually did, until now, it seems). Nice weather here too. EDIT: I could get KB963707 installed though ms update without problems, i.e. using a 3.5 SP1 SNMsynth installer without KB963707 applied. Are you using maybe 3.5 SP0? As the ms download page clearly states this hotfix should only be installed after 3.5 SP1 has been installed. Actually the SNMsynth script applies KB963707 to the installer if you put it in the work folder, but the resultant installer abort when executed, don't do it. Aftermath: KB963707 should only be applied after 3.5 SP1 installer has finished. In my experience WU install KB963707 without problems over 3.5 SP1 SNMsynth installer. If you're using 3.5 SP1 take care of install order. Report any news about this please.. 2 Igrugeman You should not try to apply KB960737 to the building process. Though it accept it, it breaks 3.5 SP1 installer. See guide. Those lines you posted are not useful.

Your solution was erroneus too, "System" means an OS installed, the only pointer reliable in diskpart output is "Active: Yes". And that's it (ECHO OFF now sorry): actpart.cmd And about static %HDNUM%... if you're using it on a installed OS simply value could be changed manually or user could be asked about what HD to check; and if used during an installing process, again user can be asked, or script could check with diskpart what's the HD of %HOMEDRIVE%, provided that you are probably tryining to modify the boot.ini of the active partition of the BIOS selected bootable HD. I've been investigating what WMIC can get from BIOS and I couldn't find how to get the HD booting order, which maybe could help you.

What about this? I'm supposing Disk 0 but it can be adjusted. See post #13.

I think there's no point in detecting what's the active partition at install time. This is something you should state before making the install and decide if you want multiple boot loaders, one for each partition or only 1 in the first partition. But you seemed to prefer multiple, so you're going to activate each partition upon a install on it, and your problem should be edit boot.ini of the rest of the partitions to be updated to the new layout. So you don't need to detect the active partition, is the one you're installing on, you can obtain it from %HOMEDRIVE% variable.

On your example when you're installing XP on a recently active D:. Is not win creating a new boot loader in D:, as an active partition it is, which will call boot.ini in the same partition? That boot.ini in D: should have listed previously installed XP in C: as bootable. So boot.ini in C: is the one which should be edited for booting XP in D: in case C: become the active partition. Isn't it?

Read again, specially about all RunOnceEx variants, SVCPACK.INF, CMDLINES.TXT methods, and about $OEM$ folders. Always consult timeline section for better understanding.

I use Roufneck's DrvComp. And yes, there's an specific subforum for this and you have the google metasearch bar above. Use it.

And what about applying them on first logon?

The langpack is version 3.5 while the frameworks packet is 3.5 SP1. Download the matching langpack.

You're supposed to put unattended.mst in the same folder than office installer, and to trigger install from the batch file pointing to the folder where office installer will be in this moment, yet in the HD if you put office folder under some $OEM$ subfolder that copies it to HD during setup, yet in the CD if youre using GuiRunOnce from CD method. But as long as .mst is in the office installer folder you don't have to specify full path for .mst but only for the installer. See reference for the install method you're using in the guide.

Follow the link in the post linked in my previous post.

Search, search, search... If you'd have done that you'd have found this.

1. Read the Unattended Guide in the link above. You'll find various methods to do it. 2. There's an application install subforum here. 3. Use the metasearch google bar. 4. Other places to find software prepared for unattended install. - Ryan VM forums (this link is for switchless installer releases subforum) - WinAddons (nlite addons)

Check your nlite output. Open ..\YOURCDFOLDER\I386\WINNT.SIF and look for Timezone setting under the section [GuiUnattended]. I think it should be set to Timezone=190 (India time). Fix it if it doesn't. And don't post this file here, it has private info.

I think this is what you're looking for, and it is in the previous link:

Here it is.

This inf file modifies the registry to open these ports and cmdlines.txt is executed on a limited environment so probably netsh command are not available. Try to import these keys with a reg or regedt32 regfile.reg command that should be available at that time.

I wouldn't bet my head on this. Open that WINNT.SIF and look for something like: [GuiUnattended] ... DetachedProgram="path\oneexefile.exe" Arguments="/switches" ... And you'll find how he did it.