Recommended Posts

I'm seeing another problem. It seems that the AP files are being copied to the HDD and installed from there. :cry:

This being the case, I think I would just as soon install from 2 seperate CD's. Oh well...

yeah, that's what it does :-\

I just used the winnt.sif file posted on the previous page, made the suggested mods, plus added autologon with user/pass etc.......

Problem one: I had to choose a partition to install to......would prefer automatic

Problem two: It didn't autologon, went to the checking to see if you are connected to the net screen and wanted to know if I wanted to register. I also had to enter the user name. THEN Autopatcher started up and took off.

Cutting and pasting Winnt.sif I used:

;SetupMgrTag

[Data]

AutoPartition=0

MsDosInitiated="0"

UnattendedInstall="Yes"

[unattended]

UnattendMode=FullUnattended

OemSkipEula=Yes

OemPreinstall=Yes

TargetPath=\WINDOWS

[GuiUnattended]

AdminPassword=*

EncryptedAdminPassword=no

OEMSkipRegional=1

TimeZone=4

OemSkipWelcome=1

[userData]

ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

FullName="DEFAULT"

OrgName=""

ComputerName=DEFAULT

[Display]

BitsPerPel=32

Xresolution=1024

YResolution=768

Vrefresh=85

[identification]

JoinWorkgroup=LAN

[Networking]

InstallDefaultComponents=Yes

[GuiRunOnce]

"%systemdrive%\InstallAP.cmd"

Also in the $OEM$\ directory I have:

saved as autologon.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"DefaultUserName"="Xxxxxxx"

"DefaultPassword"="xxxxxx"

"AutoAdminLogon"="1"

cmdlines.txt: (I'm thinking this where someof the problem is)

[COMMANDS]

"useraccounts.cmd"

useraccounts.cmd:

net user Xxxxxxx xxxxxx /add

net localgroup Administrators Xxxxxxx /add

REGEDIT /S autologon.reg

EXIT

Problem 1:

Change Autopartition from 0 to 1. (In the [Data] Section)

Problem 2:

I don't know if these will fix it, but there's only one way to find out...

Under [unattend] add:

UnattendSwitch="Yes"

WaitForReboot="No"

if those don't fix it, then it must be something with your cmd files...it could be the ASP.net account, make sure AutoPatcher deletes that account...it has been known to screw up autologins...

This is awesome what you guys doing. I can't wait to this is release,, cause i need to reinstall my computer now cause its messed up so it be a good way to test this out. I have a 52x cdrw this is gonna be cool man.

Just go here <a href='http://unattended.<< spam >>/xp/' target='_blank'>Unattended Install of Windows XP</a>

I use this and it rocks. Auto install with no 3rd party program for me.

EDIT: Ok so neowin is banning msfn dot org stuff now? What's up with that? Go to unattended dot msfn dot org to view the guide.

Edited by wd40

Worked like a charm, only trouble I had was the known problem with the dot net install,oh and some media player stuff didnt install, I may not have had version 9 set to install....oh and can someone tell me how to set AP to remove that damned MSN messenger? =P

Worked like a charm, only trouble I had was the known problem with the dot net install,oh and some media player stuff didnt install, I may not have had version 9 set to install....oh and can someone tell me how to set AP to remove that damned MSN messenger? =P

in the attached zip file are two files (three actually, one is a copy of this post)

autopatcherxp.apdb <--this has been updated so that you can remove windows messenger without having to install MSN Messenger.

NETFramework.axp <--fixes the NET error message.

the text file tells you exactly where to put them :)

fixapxp.zip

one thing i did find that many of you might run into is the autopatcher bug!!

do go to the thread about autopatcher bugs and read up there too!!

i had to edit one file to make it install w/o problems.

flish can confirm this too.

AutoPatcher XP Bug Thread

Edited by Shifty
i got an error while running the batch file and i did everything,, it says cannot find autopatcher.exe,,, how can this be,, when i extracted autopatcher to the same folder??? odd...

I got the same error when I ran the batch file. I think it is caused by having turned off the creation of 8.3 file names when using the NTFS file system. To fix the problem I renamed the AutoPatcher XP folder to AutoPatcher_XP, and then I edited the 2 lines in the batch file to reference AutoPatcher_XP instead of autopa~1. I know the first line worked, because the AutoPatcher XP program starts up and lets me edit the options and then do the "save as default", but when I exit the AutoPatcher XP program, the DOS command window says 0 files copied when it is supposed to be slipstreaming the files from AutoPatcher XP into the XPCD folder. I will keep working on it to try and figure out this second part.

Edited by RottGutt
i got an error while running the batch file and i did everything,, it says cannot find autopatcher.exe,,, how can this be,, when i extracted autopatcher to the same folder??  odd...

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. Anyway, on the second line that references autopa~1, I changed it to AutoPatcher_XP, but it is imperitive that you leave a space between it and XPCD. Please see the .jpg of the batch file if you are confused. I hope this helps anyone who is having trouble with this issue.

Good Luck!!

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. Anyway, on the second line that references autopa~1, I changed it to AutoPatcher_XP, but it is imperitive that you leave a space between it and XPCD. Please see the .jpg of the batch file if you are confused. I hope this helps anyone who is having trouble with this issue.

Good Luck!!

yep, you got it :) i was about to post to say what was wrong with the first one, but you beat me :)

I changed the batch file so that it would NOT install certain Windows apps, but they installed anyway. My batch file section regarding this looks like this:

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

ECHO msmsgs=no>> XPCD\i386\winnt.sif

ECHO msnexplr=no>> XPCD\i386\winnt.sif

ECHO freecell=no>> XPCD\i386\winnt.sif

ECHO hearts=no>> XPCD\i386\winnt.sif

ECHO minesweeper=no>> XPCD\i386\winnt.sif

ECHO pinball=no>> XPCD\i386\winnt.sif

ECHO solitaire=no>> XPCD\i386\winnt.sif

ECHO spider=no>> XPCD\i386\winnt.sif

ECHO zonegames=no>> XPCD\i386\winnt.sif

I changed all the instances of "off" to "no". Should I have deleted the arrows after the words too? Where did I go wrong?

In regards to these 2 lines of the batch file:

ECHO OEMSkipRegional=1 >> XPCD\i386\winnt.sif

ECHO TimeZone=85>> XPCD\i386\winnt.sif

I would also like to know how to find out which number corresponds to Time Zone (GMT-05:00) Eastern Time (US & Canada). The default # in the batch file is 85, which corresponds to Greenwich time. Is there a table to follow that lists all the time zones? Also, what does the # 1 in the previous line (OEMSkipRegional) signify? Does this mean it disregards whatever is put in the following line?

Thanks!

Edited by RottGutt

the >> definately needs to be there, that's what adds those lines to the winnt.sif

oemskipregional makes the setup skip the screen where you enter your regional settings, so that needs to be 1...

and timezones....

Index Time Zone Display 
000 Dateline Standard Time (GMT-12:00) International Date Line West 
001 Samoa Standard Time (GMT-11:00) Midway Island, Samoa 
002 Hawaiian Standard Time (GMT-10:00) Hawaii 
003 Alaskan Standard Time (GMT-09:00) Alaska 
004 Pacific Standard Time (GMT-08:00) Pacific Time (US and Canada); Tijuana 
010 Mountain Standard Time (GMT-07:00) Mountain Time (US and Canada) 
013 Mexico Standard Time 2 (GMT-07:00) Chihuahua, La Paz, Mazatlan 
015 U.S. Mountain Standard Time (GMT-07:00) Arizona 
020 Central Standard Time (GMT-06:00) Central Time (US and Canada) 
025 Canada Central Standard Time (GMT-06:00) Saskatchewan 
030 Mexico Standard Time (GMT-06:00) Guadalajara, Mexico City, Monterrey 
033 Central America Standard Time (GMT-06:00) Central America 
035 Eastern Standard Time (GMT-05:00) Eastern Time (US and Canada) 
040 U.S. Eastern Standard Time (GMT-05:00) Indiana (East) 
045 S.A. Pacific Standard Time (GMT-05:00) Bogota, Lima, Quito 
050 Atlantic Standard Time (GMT-04:00) Atlantic Time (Canada) 
055 S.A. Western Standard Time (GMT-04:00) Caracas, La Paz 
056 Pacific S.A. Standard Time (GMT-04:00) Santiago 
060 Newfoundland Standard Time (GMT-03:30) Newfoundland 
065 E. South America Standard Time (GMT-03:00) Brasilia 
070 S.A. Eastern Standard Time (GMT-03:00) Buenos Aires, Georgetown 
073 Greenland Standard Time (GMT-03:00) Greenland 
075 Mid-Atlantic Standard Time (GMT-02:00) Mid-Atlantic 
080 Azores Standard Time (GMT-01:00) Azores 
083 Cape Verde Standard Time (GMT-01:00) Cape Verde Islands 
085 GMT Standard Time (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London 
090 Greenwich Standard Time (GMT) Casablanca, Monrovia 
095 Central Europe Standard Time (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague 
100 Central European Standard Time (GMT+01:00) Sarajevo, Skopje, Warsaw, Zagreb 
105 Romance Standard Time (GMT+01:00) Brussels, Copenhagen, Madrid, Paris 
110 W. Europe Standard Time (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna 
113 W. Central Africa Standard Time (GMT+01:00) West Central Africa 
115 E. Europe Standard Time (GMT+02:00) Bucharest 
120 Egypt Standard Time (GMT+02:00) Cairo 
125 FLE Standard Time (GMT+02:00) Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius 
130 GTB Standard Time (GMT+02:00) Athens, Istanbul, Minsk 
135 Israel Standard Time (GMT+02:00) Jerusalem 
140 South Africa Standard Time (GMT+02:00) Harare, Pretoria 
145 Russian Standard Time (GMT+03:00) Moscow, St. Petersburg, Volgograd 
150 Arab Standard Time (GMT+03:00) Kuwait, Riyadh 
155 E. Africa Standard Time (GMT+03:00) Nairobi 
158 Arabic Standard Time (GMT+03:00) Baghdad 
160 Iran Standard Time (GMT+03:30) Tehran 
165 Arabian Standard Time (GMT+04:00) Abu Dhabi, Muscat 
170 Caucasus Standard Time (GMT+04:00) Baku, Tbilisi, Yerevan 
175 Afghanistan Standard Time (GMT+04:30) Kabul 
180 Ekaterinburg Standard Time (GMT+05:00) Ekaterinburg 
185 West Asia Standard Time (GMT+05:00) Islamabad, Karachi, Tashkent 
190 India Standard Time (GMT+05:30) Chennai, Kolkata, Mumbai, New Delhi 
193 Nepal Standard Time (GMT+05:45) Kathmandu 
195 Central Asia Standard Time (GMT+06:00) Astana, Dhaka 
200 Sri Lanka Standard Time (GMT+06:00) Sri Jayawardenepura 
201 N. Central Asia Standard Time (GMT+06:00) Almaty, Novosibirsk 
203 Myanmar Standard Time (GMT+06:30) Rangoon 
205 S.E. Asia Standard Time (GMT+07:00) Bangkok, Hanoi, Jakarta 
207 North Asia Standard Time (GMT+07:00) Krasnoyarsk 
210 China Standard Time (GMT+08:00) Beijing, Chongqing, Hong Kong SAR, Urumqi 
215 Singapore Standard Time (GMT+08:00) Kuala Lumpur, Singapore 
220 Taipei Standard Time (GMT+08:00) Taipei 
225 W. Australia Standard Time (GMT+08:00) Perth 
227 North Asia East Standard Time (GMT+08:00) Irkutsk, Ulaan Bataar 
230 Korea Standard Time (GMT+09:00) Seoul 
235 Tokyo Standard Time (GMT+09:00) Osaka, Sapporo, Tokyo 
240 Yakutsk Standard Time (GMT+09:00) Yakutsk 
245 A.U.S. Central Standard Time (GMT+09:30) Darwin 
250 Cen. Australia Standard Time (GMT+09:30) Adelaide 
255 A.U.S. Eastern Standard Time (GMT+10:00) Canberra, Melbourne, Sydney 
260 E. Australia Standard Time (GMT+10:00) Brisbane 
265 Tasmania Standard Time (GMT+10:00) Hobart 
270 Vladivostok Standard Time (GMT+10:00) Vladivostok 
275 West Pacific Standard Time (GMT+10:00) Guam, Port Moresby 
280 Central Pacific Standard Time (GMT+11:00) Magadan, Solomon Islands, New Caledonia 
285 Fiji Islands Standard Time (GMT+12:00) Fiji Islands, Kamchatka, Marshall Islands 
290 New Zealand Standard Time (GMT+12:00) Auckland, Wellington 
300 Tonga Standard Time (GMT+13:00) Nuku'alofa

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

    • No registered users viewing this page.
  • Posts

    • Feels like Hitman in Bond skin. But overall a great game! 👍
    • Microsoft released new Defender update for Windows 11, 10, Server ISO installations by Sayan Sen Microsoft releases new Windows Defender update packages very frequently to protect against various newly discovered malware. Once a while every three months or so, the company also pushes out these updates to Windows images (WIM and VHD) and ISOs, that are used to install Windows. Hence with the newest Windows 11 update available via the official MCT tool, you should get these definitions. This update package is necessary as a Windows installation image may contain old, outdated anti-malware definitions and software binaries. Aside from better security, these updates can also provide improved performance benefits in some cases. When a new Windows installation is set up, there may be a temporary security risk due to outdated Microsoft Defender protection in the OS installation images. This happens because the antimalware software included in these images might not be up to date. Thus Microsoft says that these updated definitions essentially help close this protection gap. Microsoft delivered the latest security definitions for Windows images via security intelligence update version 1.445.323.0. The Defender package version is also the same. It applies to Windows 11, Windows 10 ESU, Windows 10 Enterprise LTSC 2021, Win 10 Ent LTSC 2019, Win 10 Ent LTSB 2016, Windows Server 2022, Windows Server 2019, and Windows Server 2016. Microsoft writes: "This package updates the anti-malware client, anti-malware engine, and signature versions in the OS installation images to following versions: Platform version: 4.18.26040.7 Engine version: 1.1.26040.8 Security intelligence version: 1.447.236.0" From Microsoft's security bulletin, we learn that the security intelligence update version 1.447.236.0 was released early last month and adds threat detections for various malware like trojan, backdoor exploits, ransomware, stealers, AutoKMS, and more. For those wondering, the latest intelligence update is version 1.451.297.0 at the time of writing.
    • Hello, Hope all is well. I am in UK.  
  • Recent Achievements

    • Collaborator
      conkir earned a badge
      Collaborator
    • Rising Star
      olavinto went up a rank
      Rising Star
    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
    • Reacting Well
      X-No-file earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      PsYcHoKiLLa
      271
    3. 3
      +Edouard
      75
    4. 4
      Skyfrog
      74
    5. 5
      Steven P.
      71
  • Tell a friend

    Love Neowin? Tell a friend!