Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


eth0

Member
  • Content Count

    21
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About eth0

Contact Methods

  • Website URL
    http://
  1. It's not wrong, but you lose one of the advantages the WIM format has i.e. specify multiple versions in the same file. You can check the (revised) imagex documentation http://www.microsoft.com/downloads/details...;displaylang=en for the details if you want. I think the hardest part would be getting your script to list the internal catalogue and echo that back into your HTA/textfile/whatever. I dunno, maybe a dynamic array or something "could" solve that.
  2. Also, keep in mind that some software installs don't work properly when you're using UNC paths (e.g. \\server\share ). I usually create a temporary drivemapping for those apps. [edit] If you're using a Windows server + Active Directory , why not do a managed install? AcroReader is pretty easy to deploy by Software Installation GPO.
  3. The Administrators group 'll have a different name if you're using a Spanish XP.
  4. To start off: any file that gets copied over is written to disk in 8.3 format. Which means scripts calling files may break, registry settings with filenames break, etc. I myself use winnt32 + BartPE. First off: Access denied errors are probably caused by not using the proper authentication. WinPE (and BartPE) are running on the SYSTEM account, and that usually does not have permission to connect to a network share. Instead, use net use [driveletter] \\server\installshare /user:validuser {password} If you use a non-formatted disk, there is no filesystem for setup to write files to. I've installed many win2k workstations using a network bootflop based on Bart's network bootdisk (nu2.nu site) with Gdisk and smartdrive added. Gdisk can be scripted. If you use winPE or BartPE: Have a look at Diskpart. This is my diskpart script: diskpart /s dodisk.txt rem after diskpart format the freshly made partition format c: /fs:ntfs /q /y /v:sys dodisk.txt contains diskpart commands: rem select future c:\ drive select disk 0 rem wipe the disk clean clean rem create a single primary partition 8GB create partition primary size=8000 rem set the drive to mount at c:\ assign letter=c active exit HTH
  5. Hedi Klum Setup Screenshot BBU DLL (rename to dll) (text is to be removed, just haven't gotten around to it yet)
  6. I was under the impression that if you add the appropriate registry entries @ stage T-12/13, still in the unattended install, there are no users logged on. That means that any hkcu key is automatically entered in the Default User hive. me, I'm merging multiple regfiles in cmdlines.txt and quicklaunch is active for any user I create; even on a completely finished install on which I add a new user.
  7. I think you might prefer using the extracted sp2 files and use the update.msi in an installation GPO (you're using SUS, so I presume you're running AD anyway).
  8. Why the >> logfile twice? You only need it on the second line.. Heh.. compare your registry entries to the one for alcohol.*mumbles about /VE* Heh. Bet you if you dry-run your .cmd and check your registry key that it 'll say c:\Install\Applications\K-lite Use more quotation marks to wrap the commandline. http://unattended.msfn.org/xp/runonceex.htm <<< highly suggest you read that one once more, especially the summary regarding testing.
  9. I did some hunting earlier in my \inf dir and noticed that SP2 also incorporates many new drivers, including wlan / gbit stuff. Just so you know
  10. Did RunOnceEx complain about "too many setup parameters" ? I noticed that error flashing by very fast in a command prompt. I got around it by using a full install on another PC, then grabbing the files from \windows\Cache\Adobe Reader 6.0.1\ENUBIG : Renamed the MSI to AR6.msi, dropped 'em into \install\apps\adobe dir and used the following: REG ADD %KEY%\000 /VE /D "Acrobat Reader 6.0" /f REG ADD %KEY%\000 /V 1 /D "%systemdrive%\install\apps\adobe\AR6.msi /qn" /f That worked perfectly.
  11. Also, make sure and test that your applications actually work with your setup instructions from runonceex...
  12. Well, it sure does support $oem$ folders, so there must be something else wrong. BTW: fastest way to check if runonceEx is still used is to make a simple script and run it on your freshly installed XPsp2. If you see the proper keys added in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx then it is working, just the parameters you're passing could be wrong. Sort of a RunOnceEx after the fact shall we say?
  13. Use bartPE with the appropriate storage(such as raid drivers) + network drivers loaded. map your installshare: net use [driveletter:] \\server\installshare /user:validuseraccount step 1 Use Diskpart rem select future c:\ drive - disk 0 is the primary IDE master disk select disk 0 rem wipe the disk clean clean rem create a single primary partition, mine is 10GB - alter to your wishes create partition primary size=10000 rem set the drive to mount at c:\ assign letter=c active exit step 2 Then format the new partition format c: /fs:ntfs /y /v:sys Step 3 Then run your unattended. Since bartPE / WinPE is a win32 environment you can now use winnt32 instead of DOS winnt (which would fail anyway) set AnswerFile=.\unat3.txt set SetupFiles=.\i386 .\i386\winnt32 /s:%SetupFiles% /unattend:%AnswerFile% /copysource:lang I run all 3 in unattend.bat like this: diskpart /s dodisk.txt : dodisk.txt contains scripted diskpart actions from Step 1 format c: /fs:ntfs /y /v:sys set AnswerFile=.\unat2.txt set SetupFiles=l:\i386 l:\i386\winnt32 /s:%SetupFiles% /unattend:%AnswerFile% /copysource:lang Your $oem$ folders should be inside i386 if you do a network install. On completion of copy action (t-51 or so) reboot and take out the bootCD. Sit back, have a coffee and relax
  14. Now where did that come from? I'm ashamed almost to say this, but I know people who reinstall every 2 months (I cant think of a good reason to do so otoh), and they've been running XP for 2 years. You do the math
  15. That doesn't sound like a company whose products you'd like to use hmm?
×
×
  • Create New...