Alanoll

Indeedy it is. You're using a SP1 or earlier kernel on a SP2 OS. See the problem with that? Youhave to recreate the boot logo. http://unattended.msfn.org/advanced/cosmetics/bootscreen.htm

I believe the reason it wrapped, was because the string was too long

WFP is replacing it. Go into DLLCACHE and rename ntoskrnl.exe to ntoskrnl.ex_ The replace the one in system32. A box will probally come up asking to you to insert your Windows CD, just click cancel.Restart and it should work. Or, open up boot.ini in C:\ At the end of the bootup lin (the one with /fastdetect on it) add /kernel=mykrnl.exe Rename your bootscreen to mykrnl.exe and put it in system32. Be sure the kernel is the proper version.

out of curiousity, how did you find the heisig-it site? Also, XPInstall is a VERY VERY OLD version of XPlode.

@wherzdaluv Careful Careful with that link i removed... also... http://flyakite.msfnhosting.com

Does the variable stay set even after the batch script is exited? I'm sure it doesn't after the parent exits, but does this keep it alive even in the parent? and again....this was onsite as well. Just not a prompt telling the user the disc wasn't inserted.

the float point calculations should increase in size as well.... As the registers are doubled, allowing for a much larger value to be stored. (why there's also an increase in RAM, the system can address a larger value)

http://www.msfn.org/board/index.php?showto...ndpost&p=270687

http://unattended.msfn.org/global/compress.htm#expand

I should point out -lWinXP_SP1 makes the CDLABEL "WinXP_SP1", and has nothing to do with the directory it gets the files form.

do you receive an error? did you try actually putting those lines IN THEIR PROPER SECTIONS in the txtsetup.sif file? As in, searching for the already present section and adding the lines?

http://unattended.msfn.org/global/timeline.htm And despite the precise lapses of time, what's the difference?

The whole point of the GinaDLL key is to change the classic logon screen. Even in SP1 that was it's function. Even in SP1 is ALSO disabled the Welcome screen (logonui.exe).

the installation of both the PRO and FULL versions result in the EXACT same files on the system. The only difference is the installer, and that difference is a single page where you enter your serial during isntall time. That be the ONLY difference.

Windows is in a VERY crippled state at DetachPrograms, so I don't suggest installs ANYTHING there.

awwww....curses....commercial only?? well crud...

maybe consider adding %CDROM% support. All that you'd need in the GUI is a checkbox, and then when writing the script just write the FOR loop just after the TITLE line. FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\CD.txt SET CDROM=%%i: Besides that i just have one correction for you.. regedit /s %systemdrive%\install\msnreg.reg REGEDIT would be the program to execute, with /s %systemdrive% install msnreg.reg in the Paremeters field.

http://www.msfn.org/board/index.php?showto...ndpost&p=269823 http://www.msfn.org/board/index.php?showto...ndpost&p=270687 Read those. Now on to the problem... please also attach your WINNT.SIF and a screenshot of your directory structure, and if possible a screenshot of the error.

/? when calling the SP file should give you the options.

Guess this weekend I can see about proving you wrong Probally want, but I might be bored I don't believe I have OEMPreInstall=YES set in my WINNT.SIF but I'm not sure... (get my PM about makeie.zip? )

The obvious difference is switches. And how they're packed/what installs them. Type 1: Typically for Core Component fixes, related directly to Windows. Type 2: Typically Component Updates, like IE, OE, WMP The following aren't really covered as there are only one or two for each Type 3: MDAC Updates. These look like Type 2, but aren't. The installer used is dahotfix.exe and requires different switches. Type 4: This one emerged with an XML update i believe. It's similar to Type 3, just a different installer file. Type 5 (as I call em): The newer version of Type 1. These are the ones that have the /quiet and /integrate type switches. These are just like Type 1, but an updated installer.

no it can't be integrated. It can however be installed as part of your normal routine, via GUIRunOnce or RunOnceEX. Just read the guide ( http://unattended.msfn.org ) to get stuff working.

from the hotfix exe itself Search, and you'll find a thread on this VERY topic, infact I believe TWO THREADS in the last week.

I'd like all three back...

let's not forget the new "Search Topic" function at the bottom of the thread...