Alanoll

From what I see for directory structures on the disc, there really isn't a pattern....I attached the DIR output to this post so you can see. But be aware, I did a hex compare of both of the SETUPLDR.BIN files I posted, and they're exactly the same for 32bit and 64bit. Now I don't remember there being AMD64 support in the original SETUPLDR.BIN file... root.txt

the folder is ST3R , my bad. http://www.msfn.org/staff/Alanoll/SETUPLDR64.BIN Here's the SETUPLDR.BIN file from a 64bit edition.

Here's what i do know about those files, versus the standard ones that come from a slipstreamed SP1 source... the SETUPLDR.BIN file is DRASTICALLY different. I'm not entirely sure if it's the old one or not, all I did was a HEX compare of the one linked and one taken from the Win2k3SP1 distro. the SETUPLDR.BIN is taken from a WORKING AIO DVD with multiple copies of Windows 2003 SP1 32bit AND 64bit working correctly. Heck, the folder used in the linked SETUPLDR.BIN is EN3R i believe.

http://www.msfn.org/staff/Alanoll/SETUPLDR.BIN http://www.msfn.org/staff/Alanoll/ST3R.DAT For those still interested. Those are two files taken from a complete AIO with Win2k3SP1 32bit and 64bit. These are specifically from the 32bit os

Alright, I was avoiding having to do this... Copy Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] UIHost="%systemroot%\system32\dragon.exe" Into NOTEPAD, and save it as REGTWEAK.REG Notice it's a REG and NOT a TXT file. Save it in your $OEM$ folder. Open up CMDLINES.TXT and add this line on the next line after the one calling your RunOnceEX.cmd file "regedit /s regtweak.reg" Save CMDLINES.TXT and recreate your ISO

This thread will definately bring out how many people live their lives on P2P networks, becaue they'll come here and whine about it.

can't do that. The bootsector (atleast BOOT.IMG) just contains the code to lauch the setup sector. To initiate a batch file, you'll need the command line interpreter as well. Make an image of a Win98 boot disk, and use that image as the bootsector instead of BOOT.IMG. It'll then boot into the "disk" and reach a dos prompt. That being said, you should be able to figure out how call you BAT file.

I honestly have no pity for you, if you can't recognize it's based off a InstallShield installer. That being said.. http://unattended.msfn.org/intermediate/ap...stallshield.htm

Please don't post the NFO again...

That would be the primary reason I personally deleted your posts.

http://support.microsoft.com/kb/155197/EN-US/ Now stop the bickering, and leave eachother alone.

talk to the people at Invision. We're using their software. Or you could always just copy paste into a Word Processor and then copy it back after spell checking.

ALLUSERS=2 will return an error if the user doesn't have Admin Rights. I honestly don't know how it'll work Tomorrow I'll try and add in a script or something to check for a certain value if =0 really doesn't work.

The Shortcut issue should be fixed now. If you don't want the shortcuts created for All Users, use the ALLUSERS=0 switch, otherwise it will default to All Users IF you have the appropriate access rights.

Javascript needs to be enabled. There's a menu, with drop menus and such on the site. That's where the links are.

yall with the shortcut create problem.... Open up a CMD prompt window, and type SET. Then attach what's displayed to your post in a TXT file.

It should, yes.

actually, I'd lean more to having it be a subforum within the Unattended Windows forum. But I do agree it'd be pretty sweet to have one.

@Dynaletik It didn't do it with the previous installer? If need be I can send you a link to one of the prior versions for checking. As far as I'm aware, the only shortcuts being created, are done so by the Windows Installer API using the system variables %AllUsersProfile% and %UsersProfile%. @Macho I'll check it out. It could jsut be how you're using it. If you're using a switch that is superceded by another (using XINTEX=0 while using XFULL=1) then the superceding switch takes precedence (XFULL in the example).

there

The MSI is pretty much done. I'm testing it now to ensure it works...though I have to go through and remove some files, since I left some Milkdrop files and a couple others in there that aren't in the 5.1 distro.

to be fair he did use the smiley :-\

Something along the lines of.... I take it? And actually, I'll probably get to it tomorrow before i continue writing code. I had to capture the install again, since there are technically new components that need to be added (which also means more switches)

you made the MSI either wrong, or something in the system isn't keeping a setting and it must reinitialize it. You could have also made it, so that the shortcuts you create for Winamp aren't normal shortcuts but Advertised shortcuts which would then need to call the MSI to find where the files are located.

i plan to start work on it when i get out of class (which is where i am now ) I would have had it done over the weekend, but other things got in the way. I should have the system setup to start (assuming i remembered to bring InstallShield X with me to school) when i get back. This is also gonna be cutting into my time to work on the Unattended site, but oh well. EDIT: One worry down, the system already has InstallShield 10.5 installed, so that's good to go. Just need to capture the settings created by the new Winamp installer (and probably add a couple components)