Alanoll

your link doesn't adress his problem of missing shortcuts

looks fine now

The powerdown automatically only works for ATX systems, and even then it should be automatically enabled.

Did you make a post in teh unattended forum about it?

open up a command prompt type in EDIT and press enter. Open up the CMD file, then type in the characters as you need em. Save it. Then test the CMD file.

If you haven't enabled the continue button, then you have not read the EULA. It's that simple. When you actually read the EULA you will see how to enable the continue button.

the location to edit is not known. The particular file has yet to be found and the exact HEX location to edit will then need to be found.

Higher ups I'm assuming is probally a boss of some sort. Dunno why a corporation would want AIM on their computers but that's what I've gathered from his posts. His boss told him he can only use built in tools or such. If that's the case, use VBS. It's a built in component of Windows (unless removed with nLite) and can perform the same tasks as AutoIt.

can't. The reason why setup is able to do so with the Windows files, is because it has a list to copy. The $OEM$ folder files aren't listed anywhere and aren't counted during setup. They're simply copied over as a whole.

use a program called Office Shrink. It's stickied in the Application Switches forum. Careful, this comes awfully close to a warez request....

on my system, it's slightly off as well. IE 6.0 SP2. The google image perhaps raised 10 pixels fromt he bottom of the search box.

I working on it

alright, you're not understanding what we're saying. Windows Setup HAS NO SETUP.EXE that it copies over during installation. So either you reported the WRONG file that has the error, OR it's a problem with one of the files you use in $OEM$ in either case, YOU NEED TO FIND OUT WHICH IT IS

add another CDKEY to my collection

using nLite's file, you can enable/disable it via a registry tweak. nLite just also removes protection on folders so that they aren't recreated even when they're empty. the key is either SFCDisable or SFCSetting for an nLite CD (forgot at the moment) and to turn off, I believe it's 0xFFFFFF9D and to turn on it's 0x00000001

it's a file you added, unless you got the name wrong. and txtsetup.sif is in I386.

so the nLite disabling of SFC isn't working for ya? The sfc_os.dll that slimsky does the same thing as nLite's so it won't work either.

here you go: http://www.msfn.org/board/index.php?act=Search&f=70

try capitalizing it as well.

setup.exe is not reference in txtsetup.sif last I saw... is it one of your setup files in your $OEM$ directory?

did you use nLite?

MSI2XML might work...

I've had those on bad burns or such. I usually just remake the image and retry.

mount it in a virtual CD rom drive (Daemon tools, or Alcohol) then have VirtualPC capture that CDrom

if you link to it's homepage I'll see about making a new one