Recommended Posts

Shifty, I don't know the technical term for that window that opens when the batch file runs (ECHO?) but can you tell me how I can have AutoPatcher run on my Unattended WinXP w/AutoPatcher Installation CD without that batch file window open? Can I just edit out all the ECHO lines in the CUST_INSTL.cmd file? I don't know much about this stuff, but I'd sure like to learn. :shifty:

Below is what I am using because my Unattended installs APXP from the CD without copying the files to the HDD.

@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

Thanks for any help you can give.

Edited by ITinerant

hmmmm. Well that did what I wanted as far as the command window (if that's what it's called) but now, instead of installing autopatcher on a light blue background, Windows starts with the Taskbar and Start Menu open and the Windows Tour bubble nagging me while AutoPatcher is running. Maybe that /wait was there for a reason? If you know any way to run AutoPatcher on that light blue background without the "Command Window", could you please let me know how? Thanks for all your help.

i think i have a method in mind...but i'm not completely sure...

in CUST_INSTL.cmd, remove the line that says

start %CDROM%\$OEM$\autopatch\autopatcher.exe /noeula /unattend

then, in winnt.sif add this line (under "%systemdrive%\CUST_INSTL.cmd" in the [GuiRunOnce] section:

"%CDROM%\$OEM$\autopatch\autopatcher.exe" /noeula /unattend

so now you will have two lines under [GuiRunOnce]

parts i'm not sure about:

whether or not it will run a second item under guirunonce

whether the command line switches need to be in or out of the quotes.

i'm pretty sure the method described will work.

try

"%CDROM%\$OEM$\autopatch\autopatcher.exe /noeula /unattend"

if that doesn't work, delete the "%systemdrive%\CUST_INSTL.cmd" line, and delete the CUST_INSTL.cmd file from the $OEM$\$1 directory. that will leave you with only one line under guirunonce...that being the one to start autopatcher which is the only one you would need because you are running it from cd

so you don't need the cleanup procedure put in place by the cmd file.

I used:

"%CDROM%\$OEM$\autopatch\autopatcher.exe /noeula /unattend"

under guirunonce in the winnt.sif and deleted the "%systemdrive%\CUST_INSTL.cmd" line, and deleted the CUST_INSTL.cmd file from the $OEM$\$1 directory.

YES! :woot: cpugeniusmv, you is definately DA MAN! :woot:

See edited Quote above for what I did.

Now My Unattended Windows XP w/AutoPatcher Installation CD is Kewl! :cool:

Thanks verrrrry much!

Im pretty much getting the hang of creating unattended inatall cds, using the SLIPXP util that you guys have created, but am wondering if the install process could be done from a folder on a secondary hard drive? Just to speed up the install, and remove the size restriction on CDs?

I know it isnt as straight forward as copying the unattended cd to a drive, then running the winnt.exe (with switches - as yet unknown), or is it? Im trying to get as much info as I can, before I start tinkering!!!

Any help would be appreciated :D

Im pretty much getting the hang of creating unattended inatall cds, using the SLIPXP util that you guys have created, but am wondering if the install process could be done from a folder on a secondary hard drive? Just to speed up the install, and remove the size restriction on CDs?

I know it isnt as straight forward as copying the unattended cd to a drive, then running the winnt.exe (with switches - as yet unknown), or is it? Im trying to get as much info as I can, before I start tinkering!!!

Any help would be appreciated :D

well there's two things to worry about that i've not have experience with:

accessing NTFS from a Boot Disk (not an issue if you have fat32 partitions)

Starting the XP installation process from the boot disk.

Hello,

I ran the the new FULL AP for January with tthe current release SLIPXP 1.0.

Everytink went smoothly ! (Y) :beer:

Before burning the Slipstreamed CD, I was curious to know how much space I saved.

:o I din't save space, I FILLED THE MAX SPACE.

explanation:

My Original WinXP CD I386 folder = 485 MB

The content of my XPCD folder is 728MB (\I386=463MB - \$OEM\$1\Autopatch=262MB) see attached image

Infact, the Autopatch(=262MB) folder is the exact copy of the "Custom Slipstream\AutoPatcher XP" (AutoPatcherXP_Jan.exe after extraction)

My question is:

1) Does the XPCD folder is really slipstreamed?:unsure:

2) If so, How can I know that? :s

3) May I delete \$OEM\$1\Autopatch (262MB)

Tnx for yr help

coucou

Hi again,

I think I found my problem.

After analyzing closely the batch files.

XP_SLIPSTEAM_BUILDER.bat

ECHO [GuiRunOnce]>> XPCD\i386\winnt.sif

ECHO "%%systemdrive%%\CUST_INSTL.cmd">> XPCD\i386\winnt.sif

As everythink went OK and winnt.sif was was created, have a look what's gine inside CUST_INSTL.cmd

CUST_INSTL.cmd

All the commands are refer to \Documents and Settings\All Users\Start Menu\Programs\Startup\ path

As I'm using a french Windows version, the path is \Documents and Settings\All Users\Menu D?marrer\Programmes\D?marrageb>

I have no much time to test this right now, I'll test it on next sundy and let you know.

Nice WE

coucou

ok, I manually removed MSNmessenger.exe Messenger.exe and MESSENGERPLUS so I could fit everything on the CD.. since I wasn't installing these anyway... this shouldnt be an issue.

But now when I try to boot from CD I get an error stating that line 21 of i386/winnt.sif is invalid and setup cannot continue. Line 21 is:

AutoLogonCount=2 REM - do not change this!!

So I don't understand what the problem is. Any ideas?

Dave

You need to edit out the remark in the sif file. It was written by mistake. If you want to make a completely new disc, you can also edit the batch file to move the REM up or down a line and then run the batch file again.

Sorry it should read:

AutoLogonCount=2

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Along with that and very unfortunate for Linux, the AI boom/tariffs/global supply chain instability really destroyed any chances of it getting a decent chunk of market share. By all accounts, if a Steam Deck was still available for $399 (with tons of alternatives releasing at $500-$800 - instead of $1500+ now) and the Steam Machine was out there for $499, I think a lot of people WOULD have been willing to try SteamOS and switch away from Windows. But yeah, with the crazy jacked up prices now, people have to make safe bets with their money.
    • Neowin hasn't been covering the Ladybird browser but it has been posted about on a lot of tech and Linux/open source sites. I have been following the effort myself for almost a year now. Cloudflare and Proton are among their sponsors. You can read the why here--> https://ladybird.org/#about
    • That's really the user's problem, not the developers. It's not like the Windows 10 EOL was a surprise. Once a product goes out of support, you have to understand YOU are owning the risk of running it - the rest of the world will move on, maybe you'll be OK, maybe you'll be OK for a while, maybe you'll have an issue.... But you can't expect devs to write or certify software for dead operating systems.
    • Not mentioned in this blog post is that Linux has now dropped for 2 months in a row. At a hight of 5.33% in March, then 4.52% in April and now 3.99% in May. I suspect the end of Windows 10 got a bunch of people to try Linux, fueled by all the Microsoft hate, and rabid social media push of that....and now they are going back to Windows 11 because of the normal Linux issues. The vast majority of PC gamers want to use their computers to game and not trouble shoot why a game wont work, or half work.
  • Recent Achievements

    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      489
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      84
    4. 4
      FloatingFatMan
      65
    5. 5
      Michael Scrip
      62
  • Tell a friend

    Love Neowin? Tell a friend!