AllenF

will give that one a go cheers for that Allen

having the oem preinstall at no wont copy the $oem$ folder over nor will it look at it. It HAS to be yes. Move forward a step.. did you write your own WINNT.sif file then use nlite?? If so the nlite one takes priorty. If you just used the Nlite one did you fill out EVERY detail for full unattended?? if you left say the user name blank (or forgot to uncheck the @must have a password@ box then it kicks the options back to the user for input Try using HIDE PAGES instead. From there By just putting an EXE in the $OEM$ folder WONT run it it just copies it to the HDD during install (the blue screen yellow bar prior to your winntbbu.DL_ file kicking) you will need to run the exe files after install ethier BEFORE login use something like WPI or after login using runonce. Good luck with the runonce commands though. the description in the unattended section IS NOT CLEAR for a clearer understanding of the commands take a look at http://msdn.microsoft.com/en-us/library/ms...bedded.10).aspx

the exe i use to make the installer. do i need that on the disk too in the $OEM$folder I keep getting wpi.exe cant be found HELPPPPPPP I read the manual back to front and it doesn`t say I know earlier i was told i only needed the two files runwpi.exe and the cmdlines.txt in the $OEM$ folder i tried that and gt the error

Can you run through the new winnt.sif file I`ve written and tell me if there are any errors that jump out at you Cheers [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" AutomaticUpdates=yes [unattended] UnattendMode=GuiAttended FileSystem=* OemPreinstall=Yes OemSkipEula=Yes OemSkipWelcome=1 TargetPath=\Windows DriverSigningPolicy=Ignore AutoActivate = Yes KeyboardLayout="United Kingdom extended" WaitForReboot="No" OemPnPDriversPath="Windows\System32\Drivers\OemPnP\Accessories;Windows\Syste | m32\Drivers\OemPnP\Chipset;Windows\System32\Drivers\OemPnP\CPU;Windows\Syste | m32\Drivers\OemPnP\Graphics;Windows\System32\Drivers\OemPnP\LAN;Windows\Syst | THIS BIT em32\Drivers\OemPnP\MassStorage;Windows\System32\Drivers\OemPnP\Sound;Window | it should point at $OEM$\$$\system32\drivers s\System32\Drivers\OemPnP\WLAN;" | [GuiUnattended] ProfilesDir="%SYSTEMDRIVE%\Users\" |this is in $OEM$\$$\users OEMSkipRegional=0 TimeZone=85 OemSkipWelcome=1 [Display] BitsPerPel=32 Xresolution=1024 Yresolution=768 AutoConfirm=1 [userData] ProductKey="*****-*****-*****-*****-*****-*****" {key is entered in original file} ComputerName=My pc [TapiLocation] CountryCode=44 [RegionalSettings] Language=00000809 [Networking] InstallDefaultComponents=Yes Home_Page=www.google.com [Components] msmsgs=off msnexplr = Off OEAccess = Off WMAccess = Off Have i got those folder locations right or not???? Cheers Allen

If i just create a blank folder in the root wpi folder called wpiscripts then save the new config script to there will it put all the stuff in it ready to go ( profiles themes etc) or do i have to put those in manually Cheers Allen Also in the runonce section would regedit /S %SOURCE%\RegTweaks.reg regedit /S %SOURCE%\MyTweaks.reg regedit /S %SOURCE%\$OEM$\APPS\"app.exe" or have I gone wrong YET AGAIN If i wanted to force an app to install silently would i use enter MY TWEAKS to the new copy of XP or have i gone wrong again (tried asking in the unattended section to no avail LMAO) Somebody please help before i trash this dammed computer totally cos its doing my head in Cheers Allen

thanks for that but not quite what im after...... You cant use that method if you cant specify the commands. everyone keeps throwing the unattended install site at me.. thanks but if it were up to date it may help. As you know SP3 overwrites stuff like that for SP2 on top of that it doesn`t really give any definitive answers it beats about here and there it touches a subject then leaves it alone. A simple command line that will run an exe file from a drive that it doesnt matter what letter it is.. AFTER the install but before desktop kicks in Surely not that hard ( well I know it isnt because i did it years back but due to a house fire lost everything pertaining to it.. now I`m trying to get back into it and seem to be getting nowhere fast) but I`m not the only one..... response to that post That`s bad news. If you can`t understand THIS by reading again and again, noone can explain it better than the guide. Maybe you read again and then ask detailed questions, cause noone will explain the whole guide to you. ok read a history book then take a maths exam you`re not going to get anywhere fast

I`ve read all the tutorioals until I`m blue in the face I`ve read the unnattended guide over and over.. Now I`m close to just quitting altogether, this runonce thing JUST DOESN`T want to work. Its quite simple really all i want to do is run a few exe files from a non specific cd/dvd. does nobody actually know how to do this and can give me some simplistic answers PLEASE dont post links to other threads as all I get when i click them is the dammed home page AGAIN. search comes up with the same thing and I`m afraid reading over 700 pages for one line of text is not really an option. Please sombody out there MUST have some idea Allen

Here here. Ask a question get a link back to the answer and all you get is redirected to the home page????????? or is it just me

yup thats where ive been reading but still for the life cant see whether its right or not

Sorry for being stupid again If i want to run an .EXE file it install do i Put the exe file in the $OEM$ folder then use %source%\$OEM$\****exe to make windows look at %source%as being ANY drive letter for a cd/dvd or have I misunderstood the command Its hard to remember things after so long away from this sort of thing lol If that line is wrong what would it be to install the EXE file from a drive with ANY letter then direct to the $oem$ folder then look and install the EXE fil if that makes sense Cheers Allen

KK bear with me LOL i`m stupid sometimes In the command line where i put the installer,, Do i delete the "N:\new project" bit and leave the rest to run from the dvd??? I`m assuming so so that it has the correct path correct ???? Thats the way I`m reading it but i may have missed summat here as I gfot a ringing skull ache and manflu to go with my bad back lol Cheers Allen

AHA I get it cheers for that

Am I right in thinking that after i have made the install files and saved them to the WPI install folder in the project directory, all i have to do is copy the WPI folder over parallel to the $OEM$ and I386 folder The CMD lines RunWPI.EXE andRunWPI.inf are all in the $OEM$folder then it will run after windows installs Is that it or have i missed something here surly it cant be this easy can it do I need any other switchs or cmd lines/batch files to run it????

mmm Ok think out loud here and out of the box If i were to use the ORIGINAL shell 32.dll file in the root I386 Then in the $OEM$/system32 folder put the NEW shell32.dll file Am I correct in thinking that windows will install with the original then bang the modded one in from the $OEM$ file Or am i being stupid here. its a modded one to look like win7 the sizes al spot on but the chksums are different (?????) OR is there a way of telling the modded file that its checksum IS not what it thinks but what I tell it to be ( i have a basic understanding that they work on size and data within but thats about it)

nice one dencorso cheers for that ModifyPE also doesnt like my system (64bit windows with 6 gig ram up it Now that I haven`t read anywhere lol) put it on my old (ANCIENT noah wants it back dell lappy LMAO overnight it did it) but it still comes back on boot with a bad checksum tried a different shell 32 and the same thing occurs.. Any ideas i tried searching the forums but it keeps thowing me back to the home page or comes up with nothing Cheers Allen

cheers for that coffee fiend.. any ideas on one that works smoothly (preferably on vista or 7 ) but backtrackable to xp

Sorry please delete the first post

I done EVERYTHING by the letter placed both file and modifype in the same folder Typed in ModifyPE.EXE shell32.dll -c KK should work and throw back no errors etc WRONG comes back with Invalid parameter, type modifype for help LMAO all i get is the list of switches ( -c used) and operatins (not used) ANYONE cos this thing dont seem to work AT ALL i tried 9 different source versions now and they all say the same Please somebody must know Cheers allen

modifyPE doesn`t seem to want to work for me all i get is errors then the BSOD tried it on three different pc`s (three differnt source files all clean install) so i have binned that option question is the checksums should they be different or not. Maybe I`m going up the wrong path here.

p the files in the ISO are the modded ones. and yes the original files (that were deleted and replaced with the modded ones that check out with iso buster as the modded ones) seem to take there place. So i get the ORIGINAL install of xp not the modded version of xp md5`s modded 2CD602ABA8482E457ACAC5298839EDB4 origina l8A5EA6D8B09C9ACF2B57EADCC3F839ED ???? now i`m totally lost lol

Sorry its for a custom bootable cd WFP is modified to be off when i copy the new .dl_`s files to the source folder then Nlite does it stuff and i install on a VM then all the dl_`s that i put in have somehow reverted back to the windows original ones even though they were deleted from the source folder Hope that helps and makes sense

Hi guys I dont know if this is in the right place so if not please feel free to move it.. I have a problem and cant see what I`m doing wrong. I changed the SHELL 32.dll file MSGINA.dll file NTOSKRNL.dll file WINNTBBU.dll file (basically to make xp look like 7 and install as such without having to run windowblinds or something similar) When i throw these into the I386 folder and "replace" the old ones the boot it, it seems to throw everything back to the original xp stuff. How do I make xp keep these modified files? I have used the MAKECAB command and they now see as .DL_ foles the same as the original files. What have i missed here I kanow its something silly but cant for the life of me either find it or see it Cheers Allen