Alanoll

um... if I had them, I could attempt. If there was a post about them, I could try, but.....yeah.... Untill I either have the programs or whatnot, not much I can do. @armydoc Wow, someone has wanted to do this for awhile..... BartPE should be do able. I'll about making pictures....and I'll need to experiment for a bit on it....shouldn't take too long.... 4. That is a good tip. Definately space saving on the harddrive, and if you don't use CDIMAGE or a tool like it.

He slipped SP2 into his Unattended source. He added the Pre-Sp2 hotfixes using SVCPACK.INF. Since he added SP2, it was no longer needed. Typically, if it is .in_ that is is a blank file. Shouldn't matter if you delete it, Especially if it's 0kb in size. He had to rereplace a modified UXTHEME.DLL to the version of SP2 that he was using so that he could use nonmicrosoft themes. You will need to do the same. the SP1 uxtheme.dll file will not work with SP2. The only themes you can apply in XP without replacing uxtheme.dll are the ones provided by default with XP (Luna and Classic). the IRxxx.a are most likely the Indeo Codecs. They aren't in Sp2 but the entries in TXTSETUP.SIF are still there. You can either safely disregard them, or modify TXTSETUP.SIF and remove the offending lines. As for nLite, http://nuhi.msfnhosting.com/

If there is anything you want added or changed on the Multiboot DVD guide...let me know... I'll be doing some updating of it hopefully this weekend. I got permission from Flyakite earlier, so let me kno.... If it's Linux related, then if you prepare the step by step like the other sections, send it to me along with any pictures and whatnot and I'll see about adding it.

I vote for closing of this thread. It's served its purpose, and now there is a whole forum for people to discuss in.

have you tried a simple /? on the extracted archive (that's what the initial download is BTW

why in the world would you want the pos player? I'm not sure on the config though, perhaps a check into the Divx forums may yield some results? But I tried /S on my Pro download and the play was installed.

the others work because they have a valid boot sector. once youmodify them, they won't anymore depending on how you modified it. Others, it's just the version the disk uses. Some are picky. I have 6.10.6100, but I've never actually done the boot sector thing. Mine just worked.lol.

it looks like all your paths are wrong. is you XML file the same except for teh <items> tag? File not found is not XPlode error, but rather user error. Fix the paths.

then don't. Just open up a command prompt in your current installation, type the path to the file with the switch.

quite a few times.... I believe Zoster developed a script that would rebuild the original setup executable so the password isn't needed anymore, and still does what the original installer did.

it's a pitty people just don't try the common ones... have you tried /S not /s but /S. It's a NSIS installer.

sounds to me like the people with the "Owner" accounts, are using XP Home edition. I'm not sure how to rename it, but it's in one of the system files during install. systemdll or something. Ask gosh or find his post. at one point he renamed Administrator to Admin from the beginning of install.

they're the old Installshield setupscript files I believe. Usually they're compiled so I don't think you can do anything with them. the old setups I thought used -s with either the .iss file or -s by themselves. I haven't encountered any of those installed in a long time.

if you start setup through a normal CD, not through PE, but from CD, are the drivers even loaded at that point for the sound card? I woudn't think so as they're "detected" later on after DetachedProgram is executed. I could be wrong?

sticky where? I could easily make it a sticky in the nLite forum, but I beleive nuhi might have that power now. If you wanted a sticky in the Unattended forum, won't happen. Neither XPCREATE nor XPlode/XPInstall got that treatment before beign banished. @nuhi now for the real reason for moving you. I was getting jealous that you answering faster then me, so you got moved to the back corner so no one would see you. jk. Good job on getting your own forum, and webpage. I believe this isn't nearly as bloated as the old XPCREATE or XPINSTALL threads yet. lol. My browser says you're only on page 22. Tisk tisk, just a few more and you might make it to the "Improved" XPCREATE thread. Not the old XPCREATE thread but the Improved one. lol. You even made it over to Neow1n.

actually you have XP SETUP copying the files over. #Sourcedrive# = The drive XP SETUP is installing from. So you folders should be %XPCD%\install That is what's copying it all over. So if that were the case, then your XML paths are wrong. They should have %systemdrive% not %sourcedrive%If it were then it would work, however you'll still need the XPLODE files in $1 for it to run.

first you're missing the <items> tag in your xml just before the very first <item> second.... What do you mean? You want them deleted after XPlode does it's thing?

I still think even after the edit John0877 still doesn't make much sense. All I got was that he has bad grammar and can't copy something over a network. He didn't say what was removed besides IE or post any log or INI file as supplement.

This is NOT the same as the digital signature provided by Microsoft for drivers etc. The signature for WHQL certified drivers is generally provided in a seperate .CAT file. ModifyPE is simply modifying the internally stored checksum for the file to match that of the original (unmodified) file. This is done because the windows install routine refuses to copy files whose checksums do not match the pre-defined values (presumably to prevent someone from adding a virus etc to a windows install CD). I don't know the dirty details of how ModifyPE does its job, but apparently it is possible to fool the installer into thinking that a modified file is in fact the official one from MS so that it will get copied. Again, this is simply for copying the file from the Windows CD during the install and has nothing to do with driver signing or digital signatures for other files (e.g. hotfixes). In most cases, you Windows setup will note an error or warning in one of the setup logs when it notices a modified file. Regards, Matt not entirely accurate. The errors arise because after modifying a file, the checksum is never updated. So during install, windows checks the file after copying to insure the it is valid, by checking the checksum and making sure the file is good, like using a MD5 hash to verify a file was download correctly. ModifyPE just recalculates the checksum so that windows then can verify the file is not corrupt. It doesn't just arise from files that are original to the disk. I've added for example modified renamed kernels and had Windows setup copy them for me (i added them to txtsetup.sif) and I got that same error. After recalcing the checksum, the copy was fine. There are files you CAN NOT modify because they are digitally signed. layout.inf i believe is one of them.

alrighty then..... step by step, because you're just TOTALLY misunderstanding... read this: http://unattended.msfn.org/xp/gettingstarted.htm then this: http://unattended.msfn.org/xp/winnt_sif.htm then this: http://unattended.msfn.org/xp/batch_commands.htm DO NOT GO FURTHER WITH APPLICATIONS AND DRIVERS. READ THAT, COME BACK AND TELL WHAT YOU AHVE LEARNED. and don't say that you've read them, it's pretty obvious you glanced at them, but didn't read. I should point out, $OEM$,$1, and $$ are not FILES, they are FOLDERS you create.

hehe I've jsut tried installing Windows 98 on my main system (wanna play some old school games) and it doesn't like my hardware. Thankfully Microsoft included a good program to add drivers directly to the install in Windows 98, that's the next project.

you should be able to use variables in shortcuts, unless maybe you're making them through 7zip. A normal shortcut, supports variables.

you need a FAT or FAT32 partition to install to. Alot of people make the mistake that VMWare formats it for you. It doesn't. You must format it using fdisk, or partition magic or the like. Treat the virtual system as a real one. You have to do EVERYTHING you do to a real system to the virtual one. That includes formating the "harddrive".

you made the image of the bootdisk wrong. That's pretty much it. Somewhere along the way, it get screwed up. Have you looked at my post about getting it working? The really long one? As for the updating of the guide, flyakite hasn't really be around much anymore. Haven't seen him in a long time. @Armydoc I came to that same conclusion. It's the ramdrive and formating of C that screws everything up. Once your format C, all the letters change, and OEMSETUP.EXE doesn't change with it. SETUP.EXE works fine though. So my final recommendation is to avoid OEMSETUP.EXE and format using FDISK (you can script it I believe, or there is a version you can) and then continue with setup.

hate to dissappoint you..... all you really needed to do was create a EMPTY text file with those names....and setup doesn't care. That's all those files are anyways. lol. I'm serious, open them up, they're blank 0kb files.