Alanoll

http://www.msfn.org/board/index.php?showto...=0entry154767

Not really, just pointing out that there is NOTHING wrong with the MSI, but instead it's user error. As with most things (not just with the topic starter. There are times even I screwed up with my own MSI, but you people didn't know that [while creating it, there were a few oops])

the netfx.cab is .NET 1.0, and is only there as a by product of the slipstream. It's required for Media Center and Tablet PCs andis installed with those. If you wanted, there is a INF file in I386, that starts with netfx, and you can modify that to install .NET for all systems.

Not easily. You can program in to the effect of having it, if you are able to save a file to harddrive without it being erased. Or since you already have a multiboot, the simplest thing to do, would be to have each boot folder point to a different Install folder (I'm assuming you have boot folders). Then that negates any hardcoding, and each Install folder can have it's own CMDLINES.TXT.

I personally like NEC's myself when I look for response times.

It could be either, harddrive error, or a related thing such as driver error. Sometimes the driver gets corrupt for some reason, or you added a SATA/RAID/ATA driver, and forgot to update the file after adding entries to txtsetup.sif

attach a zip or post a link with the file, containing.... txtsetup.sif, setupldr.bin, and pro1.dat I don't need ANY CDSHELL files as it's not related to CDSHELL. I'll go through and check that everything is correct. You are editing the files in your PRO1 folder and not your Install source folder correct?

you need the full paths in the copy command. install\Winzip won't work. Most likely should be %systemdrive%\install\winzip and since you used COPY, you also need to tell the file to copy %systemdrive%\install\winzip\*.*

then you OBVIOUSLY didn't read the thread that the MSI belongs to. What commandline did you call? All you say is that it doesn't work, and trust me, it does. User Error. The MSI can't just be called with winamp.msi /qb. You would KNOW this if you read the thread. BY DEFAULT JUST THE CORE IS INSTALLED. YOU MUST SPECIFY WHAT IS INSTALLED.

user error. You've already said that you're sure you did everything right, so user error.

What's the problem? Is that what you wanted?

but did you search "mcafee" or "virusscan" or "mcafee virusscan" as it would be with THAT?

Is this what you mean? http://www.msfn.org/board/index.php?showto...ndpost&p=154767 indeed. Thanks. But I"m also trying to get 1.1 installed that way, but I highly doubt it will work, as the CAB file is totally different.

@Adiel you REALLY need to use the search button, and post in the proper forum

what you could do instead, is mount the UNC path as a drive letter (Z: for example).

I"m going to merge your two threads, just because it's a double post technically. And they're somewhat related It's all good.

that's usually a problem with your bootsectors (after CDSHELL). Either you have a missing file of SETUPLDR.BIN or you hexed your files in lowercase characters instead of upper, or you missed one entry that you were supposed to hex.

did you modify kernels or system files? or ANY FILE? Tell us what all you did.

yeah doubt so, just looking at the country flag you have, I'd say not. It was updated around 11-12 PM last night (doesn't really matter timezone in your case, as it's not the moring )

it's not the reason. Did you press ENTER or any other key? the error message is NORMAL when running in the script debugger. If you notice the command trying to be execute "boot", do you really want to BOOT the harddrive at that moment? It's most likely a syntax problem or something in your INI file, or you didn't press Enter, OR you didn't press enter SOON ENOUGH. If you are using the INI file (basically) form the website, it's logic is this... It prints "Press the ENter key..." for 5 seconds. If in those 5 seconds you press the Enter the key, the menu loads, if NOT then it will boot 0x80 (the first harddrive). Which is most likely what happened, you didn't press the Enter key within five seconds of CDSHW.EXE loading. I only see it for 2 seconds on my monitor as it changes resolution and takes a bit.

now the REALLY interesting thing, is that the topic refers to POWERDVD where as the post refers to WINDVD. Which is it? PowerDVD can be done via -r as you input it during installtion. WinDVD is harder as it is hashed in the registry and coded into the files.

try this instead.... start "" /wait "%Programfiles%\winzip\winzip32.exe" /noqp /autoinstall

so...did you not like the link I gave you when you asked me in PM? http://www.msfn.org/board/index.php?showto...is++True++Image

actually, MCT has this problem and I think a few in the nLite forum were having it, till I set both straight and told them it was the kernel last week or something.

the startmenu thing, I can understand. I accidentally deleted the component, and when I recreated it, I forgot to add the conditions. Will be fixed momentarily. I'll look into the XINET thing. EDIT:: OH! You're using the INI file aren't you? EDIT:: Hopefully they should be fixed now. Redownload.