AutoPatcher XP SlipStream Custom Guide

[ITinerant]

also, i've come up with a method to make AP run from the CD rather than be copied to the hard drive during setup.

if you guys would like, i can post information on how to do that as well :)

Yes please. I knew someone would come up with this. You just renewed my intrest in this project. :shifty:

[cpugeniusmv]

How to make your Autopatcher XP slipstreamed disk run from CD rather than from HDD

1. Follow Shifty's guide up to (but not through obviously) the burning part...that way i don't have to rewrite most of the things he's said, only change what i need to :)

2. Navigate to XPCD\$OEM$\$1 and move the AutoPatch folder to XPCD\$OEM$ (this stops setup from copying the files to the harddrive.

3. back in XPCD\$OEM$\$1, open up CUST_INSTL.cmd with notepad, and replace the contents with this:

@ECHO OFF
SET VERSION=1.0

rem - creating cleanup batch file for next boot.
rem - written by cpugeniusmv

ECHO @ECHO OFF > "%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Startup\cleanup.bat"
ECHO TITLE -=CLEANING UP AUTOPATCHERXP FILES=->> "%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Startup\cleanup.bat"
ECHO ECHO SETUP IS NOW REMOVING TEMPORARY FILES USED TO INSTALL AUTOPATCHERXP...>> "%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Startup\cleanup.bat"
ECHO DEL /Q "%systemdrive%\CUST_INSTL.cmd">> "%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Startup\cleanup.bat"
ECHO DEL /Q "%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Startup\cleanup.bat">> "%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Startup\cleanup.bat"

REM - INSTALL AUTOPATCHER XP UN-ATTENDED...
REM - WRITTEN BY SHIFTY
TITLE -=UN-ATTENDED AUTOPATCHER INSTALLER VERSION %VERSION%=-
ECHO.
ECHO -=UN-ATTENDED AUTOPATCHER INSTALLER VERSION %VERSION%=-
ECHO.
ECHO THIS BATCH FILE IS DESIGNED TO SILENTLY INSTALL AUTOPATCHER
ECHO ON YOUR SYSTEM. THIS PROCESS CAN TAKE ANYWHERE FROM 10 TO 120
ECHO MINUTES. 
ECHO.
ECHO INSTALLING AUTOPATCHER...
start /wait %CDROM%\$OEM$\autopatch\autopatcher.exe /noeula /unattend
ECHO.
ECHO AUTOPATCHER WAS INSTALLED!
ECHO.
ECHO.
EXIT

that tells the GUIRUNONCE command to look on the CDROM for AutoPatcher.

4. Now go to XPCD\$OEM$ and create a text file called cmdlines.txt. This file instructs setup to run some commands during the actual setup process...useful for setting up user accounts, or in this case...declaring environment variables!! (not everyone's cdrom is D: you know :) )

open cmdlines.txt and here are what its contents should be changed to:

[COMMANDS]
"setcdvars.cmd"

save, close.

5. In the same directory, create a file called setcdvars.cmd and open it with notepad. here's the contents:

@echo off
cd\
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /f /v CDROM /d %cd%
REG ADD "HKLM\SYSTEM\ControlSet001\Control\Session Manager\Environment" /f /v CDROM /d %cd%
REG ADD "HKLM\SYSTEM\ControlSet002\Control\Session Manager\Environment" /f /v CDROM /d %cd%

that sets an environment variable called CDROM for later use ;)

that's it!

NOTE: This exact method has not been tested, but is about to be (as soon as i hit submit ;) ) But i just finished an install that was very similar, and this should work.

[cpugeniusmv]

just ran my test, and it seems i made a typo in my winnt.sif...

that's what i get for not leaving it at the default :s

there should be no problems for you guys, just make sure your winnt.sif reads CUST_INSTL.cmd under GUIRUNONCE

i left of the L in mine :)

[ITinerant]

just ran my test, and it seems i made a typo in my winnt.sif...

that's what i get for not leaving it at the default :s

there should be no problems for you guys, just make sure your winnt.sif reads CUST_INSTL.cmd under GUIRUNONCE

i left of the L in mine :)

I'm not sure what you meant by that... but I didn't have any problems what so ever. You guys are remarkable! Thanks for making a great thing;(AutoPatcher XP) even better. Congratulations! and Merry Christmas.

[cpugeniusmv]

I'm not sure what you meant by that... but I didn't have any problems what so ever. You guys are remarkable! Thanks for making a great thing;(AutoPatcher XP) even better. Congratulations! and Merry Christmas.

i made a typo when i was doing it, but not in the guide! :)

glad it works :D :D

[tr4ck]

I would like to know if its possible to use this guide along with autopatcher? http://gosh.msfnhosting.com/reduce.htm. If so, should I use that guide before or after running the batch file? That guide just copies over all the files needed for installing xp.. but autopatcher probably makes some files to run during the installation so I'm not sure if they would be copied over or not.. any ideas?

Thanks.

[coucou]

Hello,

I want to congratulate Shifty and the beta tester team.

Also, many thanks for simplifying our life and give this "ready to eat" slipstream.

Here, I'm reporting the installation progress with the message I got. There are some questions I have, hope you can help.

1) Because I'm using WinXP SP1 french version, I've downloaded xpsp1a_fr_x86.exe and corrected the batch file

2) First message: Autopatcher report Current Update: Q831240 - Updta efor the HighMAT suuport in the Windows XP CD Writing here the Message display translation : Another version is already installed. It is not possible to continue this installationversion. To configure or supress the existing version, use the add/suppress of panel configuration (see enclosed images)

3) Second message display Microsoft .NET Framework??????? (see enclosed images)

What's .NET framework used for??

4) Third message display : NDP1.1-KB824629-X86.exe , here the traslation: The corrective update could not be installed by the Windows Installer Service because the program is missing or the update is for a different program. Check that the program exist on your computer and the corrective update is correct. (see enclosed images)

4) When the Autpatcher ended, I got 2 NIS (Norton Internet Security) security alert "Microsoft Inetrnet Information Server is attempting to listen for connections from other computres ":

c:\windows\system32\inetsrv \inetinfo.exe

c:\windows\system32\vms1.exe

My questions are :

During an installation from the slipstream CD just created, does the system ask me to set the country,region, language, Product ID, Login, Pass, ComputerName, NetworkGroup...

I noticed that the XPCD folder

a) not contain \Valuadd, \Support, \Win9xmigr, \Win9xupg, \Winntupg directories as my original WinXP CD

b) the xpcd\\i386\lang directory is missing comparing the original WinXP CD

c) all xpcd\$oem$\$1\$\autopatch directories are empty

d) the xpcd folder contain bootimg.bin and bootcat.bin (as my original WinXP CD). When I burn the CD, do I use those files or I have to use the Guide\Boot image\boot.bin file for the Slipstream CD boot

Kind regards

coucou

[Shifty]

coucou, i dont know about the first error, perhaps SP1 already installed the update and its not needed from the autoupdater.

the second problem you have can be fixed w/ this AutoPatcherXP (.net ?????????? error msg fix)

the third problem might be associated w/ you might want to check w/ flishfun on that one, he and the devs created APXP.

the fourth issue can be resolved my disableing firewall and antivirus software!! i trust the APXP team not to put in viruses or malisious vb scripts ;)

as for you suggestion:

a) those were deleted to save space... about 70+MB!!

b) that too was deleted to save space, but you can delete that line from the batch file so it wont delete it (you can put "rem" before the line to comment it out too) also you can delete all the unneeded languages manually to save space, or just leave it alone. its up to you.

c)your xpcd\$oem$\$1\$\autopatch directory will be empty before the batch file copies AP to that directory.

d)use the boot file i sent you. i do not know if the .bin files you specified are boot files. so just use the one i gave you.

i hope that helps!!

and thanks for the super compliment!!

thans cpugeniusmv for answering posts in my absence!!

Edited December 24, 2003 by Shifty

[Shifty]

tr4ck,

I would like to know if its possible to use this guide along with autopatcher? http://gosh.msfnhosting.com/reduce.htm. If so, should I use that guide before or after running the batch file? That guide just copies over all the files needed for installing xp.. but autopatcher probably makes some files to run during the installation so I'm not sure if they would be copied over or not.. any ideas?

I have studied the the reduced XP install guide for the last week or more...

I tried to incorporate some of that into this one, like the removal of upgrade folders, valueadd, etc

to save much needed space.

I do recommend testing w/ my batch file method and the reduced method, but at your own risk.

The key thing about that guide is the removal of drivers. if you know what you are doing its easy

and a huge time saver, but the average joe on this site doesnt know much about how drivers work

it would be a HUGE problem if someone deleted out their chipset drivers and couldnt get anything to work!!

If you can figure out how to slim down the install w/ some more stuff from that site, by all means let me know!!

i do have plans to make a V2.0 later next month w/ the roll out of the new APXP. the next version will include

a 2nd un-attended install CD for drivers, apps and such. should be fun to make and a definately a logical

uppgrade to V1.0

[tr4ck]

Not sure if you've seen this guide.. but you might wanna think about including some of these in autopatcher.. http://jdeboeck.msfnhosting.com/.

[Shifty]

I have messed w/ that one for the last week and tried getting it into my batch, but the problem

is is that i could forsee tons of people having problems w/ that.

i have personally tried it and failed the first time but the 2nd and 3rd time it worked w/ NO problems.

I will have to tweak it out and write my batch file and guide to do it all...

but most importantly i would need permission from whoever wrote that guide, batch files, etc.

to put that in my program and i need to full support what i give out.

hows this... after new years when we arent to busy you, me and my other right hand man can get together

and work on a "uber" project to do everything: the APXP/SP1 slipstream, 2nd CD un-attended install for drivers and apps, and finally the reduced XP install!!

im sure we can do that all for a release for next month!!

[Shifty]

grrr...

just noticed in the guide i wrote in the Batch.html file about the batch file (duh!)

at the end where i talk about components, i said to use "NO" and "YES", i meant to put "ON" and "OFF", my bad!!

i did reupdate the guide to correct. its up for download now!!

[coucou]

Wooow! Very quick reply. Tnx.

First error: I do installed WinXP SP1 on june 2003 on my hard disk. The WinXP SP1 CD prepared in june too.

second error: I got the patch

third error: in fact, I had no .NET Framework installed, I'm installinf it right now.

When I 'll use the slipstream CD just created, does the system ask me to set the country,region, language, Product ID, Login, Pass, ComputerName, NetworkGroup... You didn't reply for that

d)use the boot file i sent you. i do not know if the .bin files you specified are boot files. so just use the one i gave you. Because I burned (prepared) my original bootable WinXP CD by Roxio which create bootimg.bin and bootcat.bin. Does yr boot.bin be supported by Roxio??? I have not Nero.

Regards

coucou

[cpugeniusmv]

When you use the CD created in the CD-builder, you were prompted for a few of those things...but they can be further customized in the winnt.sif file in the i386 directory.

i'm not familiar with roxio's products anymore (ever since i started using nero) but it should support the boot.bin included, if it doesn't...shame on it :)

Important note: AutoPatcher XP is currently only available in english, and only includes the english patches...i believe that instructions for downloading/replacing them with french versions are included in AutoPatcher XP.

[ITinerant]

Okay, here is the deal... This works IF AND ONLY IF you have disabled the creation of the old DOS 8.3 file names when using the NTFS file system, which I would suggest anyway since you will see a very slight increase in speed. I have a .reg file that can turn off this "feature" for you plus a few others that have to do with NTFS that will all combine to speed things up if anyone is interested.

I would very much like this .reg or if anyone else has info how to disable the DOS 8.3 file names I would appreciate it. I really only see these when running some scans (Norton, etc...) so I don't know if this is really an issue or not, but I would like to find out. Thanks

[Shifty]

ITinerant,

Here is how to do it...

go to "Run" and enter: regedit

the search for a striing called: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem

then look for: NtfsDisable8dot3NameCreation

change the value from 0 to 1 and then save

you "might" have to reboot to have the new value take effect.

Here is the link that I used to figure this out, plus other easy NT tweaks

Disable Dos 8.3 Naming, plus more

[ITinerant]

ITinerant,

Here is how to do it...

go to "Run" and enter: regedit

the search for a striing called:  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem

then look for: NtfsDisable8dot3NameCreation

change the value from 0 to 1 and then save

you "might" have to reboot to have the new value take effect.

http://www.pureperformance.com/images/disable83names.gif

Here is the link that I used to figure this out, plus other easy NT tweaks

Disable Dos 8.3 Naming, plus more

Kewl! Thanks Shifty. :shifty:

BTW I hate to mention this cuz you guys put so much work in this project already, but here goes...

Do you have any plans in revamping the CD Maker tool and the "Guide" to make the changes that allow AutoPatcher to run from the CD rather than be copied to the HDD first? I already have mine working thanks to cpugeniusmv's instructions, but I think it would be worthwhile to make it the Default rather than an adaptation. I know this sounds like some sort of complaint, but it's really not. Thanks to you guys I now have an unattended installation CD that is entirely up to date and even better with the "extras". Merry Christmas :yes:

Edited December 25, 2003 by ITinerant

[Shifty]

the thought of having APXP run from the CD became a topic of debate during the entire process.

i feel that having it run from the harddrive was much faster and more logical.

In a couple of experiments, i copied APXP to a CD and installed it off the CD w/ every update being installed.

it took over 40 minutes w/ a 32X CD ROM drive. Off the Harddrive however was a much different story.

it only took about 20 minutes. so by installing off the harddrive it takes half the time!!

also great reason to have it on the harddrive is when the upgrade for APXP comes out!! that way you dont have to

copy it off the CD to get the update to work.

as far as the CD Maker tool is concerned, i immediately said no to it because once the ISO is made you need

a third party app like Ultra ISO to edit the ISO. I like having the files where i can see them and manipulate them

w/o the hastle of using a 3rd party app. i see it as being very redundant and inefficient. also to save space, you

can compress the XPCD folder alot better than an ISO file!!

Next months release will be awesome. soon, i will hopefully be able to work with the APXP dev team on some stuff

to make it even more better as well as for this project at the same time.

This release was "SlipXP"

next month will be "SlimXP" (not a Eminem reference!!)

and "Batch, Biatch!!" will be a 2nd CD un-attended install for drivers and apps!!

all are working titles!!

[cpugeniusmv]

the thought of having APXP run from the CD became a topic of debate during the entire process.

i feel that having it run from the harddrive was much faster and more logical.

In a couple of experiments, i copied APXP to a CD and installed it off the CD w/ every update being installed.

it took over 40 minutes w/ a 32X CD ROM drive. Off the Harddrive however was a much different story.

it only took about 20 minutes. so by installing off the harddrive it takes half the time!!

i disagree with that.

in my case, installing from a CD and installing from the hard drive took approximately the same time (if one was faster, it was the CD)

in the HDD case, the files used are on the destination drive as well...reading and writing to the same drive slows the entire process down.

in the CD case, it reads from one drive and writes the other...that's a plus. but the CD drive is slower than the HDD.

the fastest install solution is to have AP on a separate hard drive than your Windows installation, and install it from there.

but of course, that would be difficult to code in a generic automatic install...considering everyone's system is a little different :)

[ITinerant]

the thought of having APXP run from the CD became a topic of debate during the entire process.

i feel that having it run from the harddrive was much faster and more logical.

In a couple of experiments, i copied APXP to a CD and installed it off the CD w/ every update being installed.

it took over 40 minutes w/ a 32X CD ROM drive. Off the Harddrive however was a much different story.

it only took about 20 minutes. so by installing off the harddrive it takes half the time!!

also great reason to have it on the harddrive is when the upgrade for APXP comes out!! that way you dont have to

copy it off the CD to get the update to work.

as far as the CD Maker tool is concerned, i immediately said no to it because once the ISO is made you need

a third party app like Ultra ISO to edit the ISO. I like having the files where i can see them and manipulate them

w/o the hastle of using a 3rd party app. i see it as being very redundant and inefficient. also to save space, you

can compress the XPCD folder alot better than an ISO file!!

Next months release will be awesome. soon, i will hopefully be able to work with the APXP dev team on some stuff

to make it even more better as well as for this project at the same time.

This release was "SlipXP"

next month will be "SlimXP" (not a Eminem reference!!)

and "Batch, Biatch!!" will be a 2nd CD un-attended install for drivers and apps!!

all are working titles!!

All good points and certainly understandable. I guess it's just a preference of mine not to have unnecessary installation files on my hard drive. In fact I'm a little obsessed with as clean a system as possible. :rolleyes:

I guess I was a little confused when I said "CD Maker Tool". I did play with the original "Tool" briefly and I guess I just "assumed" this was the same. I now see my mistake. :whistle:

I too keep a XPCD folder as well as a xpboot.bin on a disc that I can copy to a HDD and edit the winnt.sif as well as change the Autopatcher and burn w/Nero according to my future needs. This will be very helpful indeed. :p

Thanks very much for all your hard work. I am looking forward to your future projects as well. They sound very interesting.

Merry Christmas :D

[OptiPlex]

ITinerant,

Here is how to do it...

go to "Run" and enter: regedit

the search for a striing called: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem

then look for: NtfsDisable8dot3NameCreation

change the value from 0 to 1 and then save

you "might" have to reboot to have the new value take effect.

http://www.pureperformance.com/images/disable83names.gif

Here is the link that I used to figure this out, plus other easy NT tweaks

Disable Dos 8.3 Naming, plus more

I like to use 8.3 filenames when browsing around in the Command Prompt; will making that reghack affect my ability to do that?

For example, I might want to browse around my userprofile folder in the Command Prompt. I might type in something like

DIR C:\DOCUME~1\BleepedOut

If I make that reghack would I get an error if I typed in the above command afterwards?

[Shifty]

I did forget that i did install APXP from my D: which a 40GB 7200rpm drive, thats why my times were a lot faster!!

I am totally open to suggestions for the next project.

This one was mostly a generic install w/ minimum frills.

I am open to suggestions for the next release!!!

[cpugeniusmv]

i think i've come up with a way to automatically delete the SP1 files after it's slipstreamed...

i'll let you know when i've got it for sure.

[coucou]

Hello,

First of all Tnx to all slipstream team and wish to all Neowin community a warm Happy 2004

1) I'm trying to customize the Lang version, may you have the list of the programs to be changed.

a)In other hand, do only the .axp files which contain "_ENU" are concerned with the language version?

b) if so, I have just to find those file with any scanner text tool. Do "_FRE" is the ending for french language?

c) Can I recover the the programs from my c:_windows folder as "$NtUninstallQ811114$" if so, how??

2) As I downloaded the M$ french program in example Messenger. The file I got is "setup.exe". Can I change the "Messenger.msi" inside the Progfiles autopatcher folder? (Note .exe by .msi)

3) I have a special driver for my monitor Philips 15" 150S3. which called "Ph_LCD15.icm" How can I integrate it inside autopatcher???

Again Many tnx for all help

coucou

[akaladis Veteran]

1a. yes, only them... for english its _ENU... for greek its _ELL etc...

1b. dunno whats the extension for frech... but if its FRE, then yes it would be _FRE... thus replace _ENU with _FRE

1c. those folders are backups of the files replaced by the hotifixes you install... they are recovered when you uninstall a hotfix from the Add/Remove Programs thingy

2. some of the file we have included are kinda more than just downloaded packages... Some are extracted contents of a file (i.e that Messenger.msi might have been a file of setup.exe), but in order to save space and configure them to run silently, we had to extract it from the original package...

3. that is not a driver... its a color profile! i dunno how you can associate a device with a profile without using the normal procedure

/Raptor