Alanoll

Closed as their is now a post for teh tutorial. No need for a poll on whether people want one created, if you've created one

@BenjaminKalytta This project seems to be REALLY taking shape...very nice work.... I shall start tinkering with it, after I'm done with Winamp, which is after I finish the current incarnation of my DVD, which is when my computer is done defragging. Good luck on those exams... As for an answer to your question.... When some programs install, they enter entries that are ONLY there untill the computer is restarted, but are loaded when the desktop loads. If the computer never gets to that point, the software that entered the entries may never get completely installed. The next thing someone is going to ahve you do, is try to implement a plugin's part of the program, so people can design their own, and the plugin adds a page.....say....for selecting VisualStyle or something....Regtweaks maybe.....but just watch SOMEONE is going to ask for it. EDIT: I removed the attachment to xper's post, so people don't download that first and then complain it doesn't work how the new one does. Some people are stupid, trust me

simpsons maybe?

in the INF format, you have a couple of options.... one is using the SourceDisk entries in an INF, do a search, I never got it working but some have.... find a creative way of using the %1% variable so that %1% is the root path to your files on your CD.

i don't think so... however as per the agreement when joining, you were supposed to have read the rules.... and any subrules that are on a perforum basis.

that will fix it.....

boy.....maybe we need to add this to a sticky in BOLD large font.... you're missing the ident files WIN51 WIN51IP (or IC if it's home) WIN51IP.SP1

you don't need to install something to get it to boot. All that it's doing is modifying the MBR on the drive. You can do that on your own, or you can have a program do it for you. It's not necessarily installing. Configuring maybe, but not installing. Again, it's probally just our interpretation of Installing. But PE is still not meant to be a basis for an embedded system, or to be a full OS in any case.

Bart's PE isn't really PE though. It's Bart's very good attempt at recreating it, without infringing on copyrights and whatnot. PE is not meant to be a basis for embedded systems. There is a reason why there is a XP Embedded..... PE is only supposed to be acquired when licensed with Windows XP Home or Professional from an OEM distributor. PE = Preinstallation Environment and is supposed to be used as such. Any other use, is a modification by the user. It's not meant to be a full blown OS. Never was. And no, BartPE is NOT installed on the harddrive. It isn't installed. It is run just like it would be from CD, no difference besides the medium. Taken from Microsoft's page

now all we need is some good ol' fashion family guy scenes and this thread will be golden.....

[XPlode] HKLM,%RunOnceEx%,"Title",0,"RunOnce Window" HKLM,%RunOnceEx%,"Flags",0x00010001,"0x00000030" HKLM,%RunOnceEx%\install01,,,"Starting XPlode" HKLM,%RunOnceEx%\install01,"1",,"%1%\XPlode.exe /log:#SYSTEMDRIVE#\XPLODE.LOG /xml:#XPlode#\XPlodeRun.xml" This is what I do. and works fine.

if OEMPreInstall is set to NO, then there is no file copy from the $OEM$ directory. You'll have to manually copy them over yourself. So perhaps the SFX is your only recourse to get them over, as i don't believe the network is active when the presetup.cmd file would run or detachprogram.....

you could always try %CD% and see what it gives you. (Current Directory variable) you always just call the rundll32 commands from cmdlines.txt itself, and negate the whole issue of paths.... what value are you trying to get for %1%? I use %1% in mine to get the directory the INF was executed from, and it works fine. I have the INF in \Unattend in the root of my CD and %1% points to \Unattend.

oh, you can have you cake and eat it....with a bit of work that is.... It's possible, but you have to work around alot of stuff. And improvise in a way that may not seem to work but does. how is your $OEM$ copied over in both situations? By your unattend.bat prior to starting? As if your use OEMPreInstall is negates the upgrade. Or is that the problem? $OEM$ is copied over ONLY when doing a clean install and not an upgrade?

whenever you're using user and pass in the arguments of <execute> you need the full path to the program even regedit. so %systemroot%\system32\regedit.exe i believe, or just %systemroot$\regedit.exe <execute display='Nero Burning Rom 6.3.1.6' command='execute' program='%systemdrive%\Install\nero\nero6316.exe' arguments='/silent /noreboot' program='%systemdrive%\Install\nero\nerofr.exe'< this ligne is invalid program='regedit' arguments='/S %systemdrive%\Install\nero\nero.reg' /> You can't have multiple progam per <execute> tag. Each needs it's own tag.

welll... WINNT.SIF is the on CD version, and UNATTEND.TXT is every other way. They're the EXACT same file.... alrighty.... here's what you can do..... go here: http://www.msfn.org/board/index.php?showtopic=12566 However, i don't know if it's possible from an Network install. If your's is indeed a network install.... Go down on that same page, to a post by RyanVM (it's in the last couple pages) and create a SFX archive. It'd be a pain to update, but it will work for your need. Combine the two methods, so presetup.cmd calls the SFX, and then point the file that generates the paths to the directory teh SFX is extracted to. To do this correctly, you may need to add your SFX to txtsetup.sif and dosnet.inf so that Windows setup will copy it over for you, so no OEMPreInstall, and then it still works. If you have a messaging client, i could probally help you through it on there, in realtime, instead of guessing at what you're trying to do

yeah.... I haven't had time of late to up date it..... I"ll try doing it over the next few days. Shouldn't take all that long, as when i did a snapshot to see what changes the new ones made, the registry entries stayed mostly the same. It's mainly the files that changes.....

yes, if you click cancel. But windows setup does it a different way. I've had hardware myself that windows didn't recognize and it NEVER bugged me about it till i remove it and put it back in. Maybe it depends on the hardware, as my printer always used to come up as well..... It could be hardware dependend. WINNT.SIF is used whenever you use it. How do you start the install? If by winnt.exe or winn32.exe there is a argument for specifying the answer file, and you would tell it to use the file. How does you $OEM$ get copied over without WINNT.SIF? Prior to install or what? (I'm just curious) Just thinking through..... you have yet another option...... There is a post in the Drivers forum called "SOLVED: DRIVERS FROM CD". THe methodology might be somewhat what you want, if you want to avoid using the WINNT.SIF file. THe poster created a copy programs. One is a SETUP.EXE file that then runs the batch file presetup.cmd which in turn calls another program to enumerate a directory that would be where your drivers here. (I can't explain it very well, if you look at the post, it might make more sense) I use this method as I install the drivers from CD, but the programs themselves you could use for your drivers without WINNT.SIF

the $OEM$ directory is copied over during TXTSETUP, not when the graphics come up. DetachProgram is in the WINNT.SIF file. Do a search in your ref.chm file (in the deploy tools) and you'll find it. It's under [setupParams] as for your first point, this is true whenever windows finds new hardware it hasn't seen before. It will only see hardware it hasn't seen before if you sysprep (i think, not sure) or if you physically move the drive you installed windows on to another computer. Otherwise, it has seen the hardware before, and knows it doesn't have the driver, so it has no reason to look for it again. Hence, user interaction. I think the detached program might be more along the lines of what you're looking for.

it would have to be a hdd that you move to a different machine.....if you don't, it looks for the devices during actual setup, and if they aren't found, it doesn't look for them again, untill you tell it to. So it'd have to be like a sysprep'd image or something. (not my area, sorry) a better place if it's a computer basis, would be to import the key at DetachedProgram or whatever (it runs are T-39 ) that way it's imported before the initial system scan, and windows finds teh drivers the first time.

changed

uhh.. what was the question again? @pilou1988 make sure there aren't syntax errors (open in IE) or that you have saved it as UNICODE and not UTF-8 @shintoisme what did you want?

sure.... I"m sure someone will find it useful Now if only I had a copy of XP Embedded to test it with.....oh well

%SOURCEPATH% I believe would be %CDROM%\I386, and %SOURCEDRIVE% would be %CDROM% DO keep in mind, it's not limited to %CDROM%. If you have a multiboot DVD, %SOURCEPATH% could very well be something like %CDROM%\SETUP\WXPVOL_EN\I386

I haven't seen that before. Perhaps you're copying over a CPL file that's not really a control panel applet..... or a regtweak.... Is all you do an Unattended install, or do you customize it as well?