Alanoll

how are you transfering them over to your new install? Are they all appearing in Resources\Themes? as in all the files? You can't switch back, because Windows can't find it. themes go in Resources\Themes. But their msstyles file, go in a subfolder inside Resources\Themes named after itself, or whatever it appears on the appearances tab.

so for each system we want this to run on, we have to create the hardware definitions for each computer seperatly? Surely there is a way to make it simpler and just include a bunch of command drivers and whatnot for the systems....

boot.ini is typically in your Systemdrive at the root (C:\) and is a hidden system file. It's not changed in the slipstream process, so you can ignore it. as for boot.bin which is the boot sector, there's a download link at the top of that page..... here is a direct link for ya : http://www.msfn.org/uploads/files/boot.zip

rundll32.exe setupapi,InstallHinfSection DefaultInstall 128 .\RunOnceEx.inf Change .\RunONce.inf to the path to your INF, and change DefaultInstall with the name of the correct section in your INF. You'll have to look for it in your INF file. It's typically the one with all the AddReg, CopyFiles lines

the double slash is because other wise Windows believe's it's a relative path in the registry, not elsewhere. Also....your INF is wrong HKCU,Software\Microsoft\Internet Explorer\Main,"Window_Placement",0x00000001,2c,00,00,00,00,00,00,00,01,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff, 00,00,00,00,00,00,00,00,80,04,00,00,60,03,00,00 Is correct. No " when using binary or dword values (your's is binary) and remove those \'s that regedit adds when exporting. EDIT: There ARE quotes around Window_Placement, if it looks like & #34, the board is messing up. They're quotes.

I point ye to : http://www.msfn.org/board/index.php?showto...ndpost&p=148467 which is in a previous page in this thread. Not yet implemented.

and the point of this was what? It's jsut ramblings to me honestly. The point of all this was what? telling people how to create a new package with InstallRite? There's already stuff on that. Telling people how to make a START.CMD? Already there too. Telling people what you did? Congrats to you for getting it working But serious, what was the point. I found that the most annoying thing, was all your line breaks, in the middle of the sentences no less. You also neglected to use CODE tags, like it says to in the rules, and that I've reiterated in the sticky entitle "Just alittle reminder" Also, why in the world would you want to recreate ALL of your setups using InstallRite when you can use their OWN native installers?

(I should note I didn't test it....) but if you say it works, great, forget what I said But by logically, I mean Command.0=Software\dotnetfx.exe works fine.... but it would seem like Command.0=msiexec.exe /i Software\dotnetfx.msi would work (imaginary file) because I didn't know how WIHU gets the paths. Whether it was the first program that would get the full paths, or it went through and did it for all. Wasn't sure, so that's my logic (most of the time, it's flawed by the way) But but hey, if it works already without the variable, then by all means, forget what I said What happens when you copy WIHU over to the harddrive, then run it, but want to install the programs from CD? Maybe that would cause a problem? Does not including the drive letter have WIHU base the paths off of it's current position?

In lite of that, could you add a %CDROM% variable for within WIHU? My one and only suggestion. As before, people just just leave it as Software\Install.exe but with the MSI, it's being passed as an argument and logically shouldn't work the same way.

try adding a \ to the lines I gave you.

try this.... <copy source='#SOURCEDRIVE#\Applications\apms\Preferences.xml' target='#ProgramFiles#\AutoPlay Media Studio 4.0\Data'/> <copy source='#SOURCEDRIVE#\Applications\apms\settings.ini' target='#ProgramFiles#\AutoPlay Media Studio 4.0\Data'/>

well, I mean if you find where the switches are in the firefox you may be able to enable them, and have a native installer for it. I'll look into the XPI's.

you may have to use MSIEXEC.EXE /I (MSIFILE) to install them. Maybe even %systemroot%\system32\msiexec.exe /I (PATHTOMSI)

i don't have it you could just not open the file in NFODIZ and use NOTEPAD like most other people.

is all you did to the image add the hotfixes? what which ones show up? one other thing, http://www.msfn.org/board/index.php?showtopic=21582

patch OS files? www.cdshell.org is an open source boot loader. www.nu2.nu you may find useful.

I opt for option B myself. Or they just don't know how to properly search, as by default it's within a span of 30 days, and alot of stuff is not within 30 days.

where did Aaron say it doesn't work in SVCPACK.INF? Or is personal expierence? switches work regardless of where they're used, it's the ones with quotes that might need alittle modifying depending on where you got them, as \" doesn't work in a normal batch install.

you'd have to use a boot disk, and then call winnt.exe to start the installation.

Yeah, that could be a good idea. May be this will be added in future. umm....I was kidding by the way. lol. It's great idea, but not in practice. There won't be many people that make the plugins if any.

did you check the log before restarting?

That's really no excuse. Moved to Windows XP Forum thought I already moved it..... along with his "poll" post. Oh well, atleast it's done.

And here I thought I was the one that told 996 what to do.....blast, people never see that The switching of the isntallers works fine, as all the "setup.exe" is is a stub loader for the config.ini to gather it's settings to install with. My guess is that the installer is a custom build, and they didn't bother changing version number, but they did tinker with it a bit. Has anyone tried hexing the installer to find the offset for the switches?

PM sent

not if it's a shortcut. and Windows puts quotes around it in it's own usually. Man, that's gotta stink for Bâshrat the Sneaky. Proven wrong twice. No hard feelings I hope. Cudos on the posting of the shortcut.exe though. I'm sure some will find it usefull, untill it is lost to the pages, and most be reattached again I've never had problems with variables, but why use %systemdrive%\Program Files\Trillian\trillian.exe instead of %ProgramFiles\Trillian\trillian.exe?