Jump to content

IT_Ranger

Member
  • Posts

    11
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by IT_Ranger

  1. Rancor - Are you perhaps removing the directory that the .cmd file is launched from? I had the same thing and finally figured it out. I was trying to clean up the install by removing my install directory.
  2. I'm sorry if this is the wrong place, I'm posting here since the W2K3 section mentions the similarities to XP. Thanks to many of the tips posted here, I have my unattened XP disk working great. Now I need to do the same for W2K3 Server Standard. The source CD is from MSDN as is the Product Key. Installing using the CD and Product Key works fine. When I try an unattended install, Setup thinks that the install is an Upgrade and wants a Windows 3.51, NT 4.0 or W2K server disk in the cd to verify that the upgrade qualifies. I ran setupmgr to create a new winnt.sif and made sure there were no winnt.si_ files anywhere. Any thoughts. Thanks Here is my winnt.sif: ;SetupMgrTag [Unattended] Unattendmode=FullUnattended OemPreinstall=Yes TargetPath=\WINDOWS Filesystem=LeaveAlone NoWaitAfterGUIMode=1 DriverSigningPolicy=Ignore Repartition=No OemSkipEula=Yes OemPnPDriversPath="DRIVERS\AUD;DRIVERS\MDM;DRIVERS\NET1;DRIVERS\NET2;" UnattendSwitch = Yes AutoActivate = No [Data] UnattendedInstall="Yes" MSDosInitiated="0" AutoPartition=1 [GuiUnattended] AdminPassword="admpass" EncryptedAdminPassword=No OEMSkipRegional=1 AutoLogon=Yes AutoLogonCount=1 OemSkipWelcome=1 TimeZone="035" [RegionalSettings] LanguageGroup=1 Language=00000409 [UserData] FullName= OrgName= ComputerName=ITSetup ProductKey=[** MSDN Key **] [Branding] BrandIEUsingUnattended = Yes [URL] Home_Page=http:// [Networking] InstallDefaultComponents=Yes [Identification] JoinWorkgroup=WORKGROUP [Display] BitsPerPel=16 Xresolution=1024 YResolution=768 Vrefresh=70 [LicenseFilePrintData] AutoMode=PerSeat [Shell] DefaultStartPanelOff = Yes DefaultThemesOff = Yes [GuiRunOnce] Command0=%systemdrive%\install\main_run.cmd
  3. Only difference I see is that Marztabator's working fix ends in 2 double quotes "" and 996's is missing those. See if thats it.
  4. My version of UltraIso is 6.5. I will definently be more aware of it now. Thanks AaronXP.
  5. Seek an ye shall find... I think I found what I was looking for regarding the troubles with UltraIso. AaronXP said: I tested this out by opening one of my iso build images and deleteing all the files. Did a save and had an empty iso that was 400 MB. Did a save as and it shrunk to 64 kb. So the fix for the bloat should be to save as. As far as referencing incorrect files, I havent seen that yet.
  6. Ack - I just bought UltraIso. Seems to work fine. What might be the trouble?
  7. sorry for the hijack...still trying to make sense of all the various methods and permutations. I've been looking at, 6 - here. It seems that in various posts this method is covered. Other posts are creating folders and replacing older versions, copying cat files, making cab files, etc. Does the srvpack.inf method work with out all the file replacement? thanks ITR
  8. Is the CDIMAGE.EXE that you use the one that requires cygwin?
  9. Late to the show as always.... Here's how I install winzip. copy the contents of a working install and put them in a folder: $OEM$\$1\Program Files\WinZip This gets copied over with the other folders\files in $OEM$ Then I run this from apps.cmd start /wait %systemdrive%\Progra~1\winzip\winzip32.exe /noqp /autoinstall DEL "%ALLUSERSPROFILE%\Desktop\WinZip.lnk"" Works for me
×
×
  • Create New...