Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by MastaVR6

  1. I would suggest upgrading to MDT2012 and re-evaluate your deployment. Use a sysprepped image (include all Core NB/SB HDC drivers) uploaded with ImageX into a WIM file. Build a WinPE 3.1 image and include your XP.WIM as an added file in the resulting WinPE 3.1, burned to a DVD. this link covers most of what you need: brianleejackson.com/tag/sysprep
  2. When performing Sysprep captures, removing the system from the domain is important as the SID is recreated when the system is added to the domain. Preventing a duplicate SID is as simple as renaming PC's as they are deployed, and added to the domain.
  3. I'm also slave to the missing icons in the admintools folder, what gives? -Answer : The SDK is required for viewing the security via a GUI. See this link http://msdn2.microsoft.com/en-us/library/2bc0cxhc.aspx
  4. I didn't use the same switches for the patches as the 7.0 exe, the 7.05 version is a cleaner install.
  5. The first two - probably a BIOS flash is the only option to induce a change in the MB device detection as it is. Otherwise it is likely individual chips/connectors are the culprit. BIOS updates for the next two, while also resetting to default settings. The 'chassis intrusion' message indicates a jumper may be improperly missing or installed on the MB connector. RAM + VGA (PCI or APG?) if integrated VGA exists, check for 1st initialzed device - PCI/AGP, check for IRQ assignment- many ATI (IIRC, older) cards don't need an IRQ. try a PCI video card, your (video-connector) slot may be bad, or not support the AGP 1x/2x/4x/8x card your installing. Resetting a BIOS to defaults may require you to poke into the nooks and crannies of the BIOS to check for settings. ESD issues can cause a setting to 'stick' in a BIOS, yank the battery and power then operate the power switch- (power led) should light up briefly as it burns any residual charge. Check for blown/leaking capacitors!!
  6. I would agree with the posted AMD users and go with an Opteron 165/170 setup, you'll end up using more of your existing parts, and proud you don't have shared FSB (bandwidth) holding your system back. cheers!
  7. edit the winnt.sif of unattend.txt in the i386 file to determine the settings used by the Dell CD. I've delt with reloads on Dell's before, but was not able to do much testing.
  8. /integrate and scripted install via runonceex.cmd, and guistart.cmd.
  9. kb890859 integration causes an error 14 on unattended CD boot. Tested integration on an SP2 slipstreamed CD with and without kb890859 integrated to confirm. Anyone have ay ideas? (my CD is complete except for this patch.)
  10. Make sure you remove any i386\mydriver.zz_ files when replacing them with i386\mydriver.zzz files. There is aconflict in an .inf that is attempting to install something. - otherwise - Try removing your network setup entries from the winnt.sif and test the install.
  11. I'm working on a driver only install for corp PC's (more of a challenge vs. a full install). Most of the setup files can be dropped, I do edit the inf to eliminate alternate languages and other files (It's easier to do with the Intel network drivers). I don't do this for performance reasons, as some of the functionality is lost from CPL and certainly from any of tuning tools and nvidia driver services that get installed. WHQL is (by far) saner to import than the non-WHQL drivers.
  12. never mattered in any of the images I built, NT/2000/XP; the internelfile time stamps stay in the files.
  13. I don't beleive it can done unless you can rewrite the default vga driver to accomodate your needs and shoehorn them into your setup. syssetup.inf is signed by M$ and sets the default vga display setting used in that stage of setup. If someone nknows how this can worked around, I'd gladly pass it on to the masses.
  14. Has anyone tested replacing the older update.exe (within older HF's) with the newer versions that support the /integrate switch?
  15. Cool error message. Recreate your XP build from the source data files. I've had to backtrack more times than I care to remember building NT/2000/XP images. Files out of sync are harder to resolve issues with, you just get useless error messages, in varying severity levels.
  16. Figured it out. I guess thats why I get the the little $$$. CD /D <folderpath> FOR %X IN (kb*) DO %X /x:.\%~nX FOR %X IN (q*) DO %X /x:.\%~nX \ bl0 me.
  17. The following should help... for # 10, set DWORD to 0000 set SVCKEY=HKLM\SYSTEM\CurrentControlSet\Services SET CUCVKEY=HKCU\Software\Microsoft\Windows\CurrentVersion rem Disable Beep reg add HKLM\SYSTEM\CurrentControlSet\Services\Beep /v Start /t REG_DWORD /d 04 /f reg add HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced /v IntelliMenus /t REG_DWORD /d 0000 /f rem Disable Send Report on system crash reg add HKLM\SYSTEM\CurrentControlSet\Control\CrashControl /v SendAlert /t REG_DWORD /d 0000 /f echo Disables Error Reporting, but notifies when errors occur reg add HKLM\Software\Microsoft\PCHealth\ErrorReporting /v DoReport /t REG_DWORD /d 0000 /f
  18. Not feasible to remove it, cumulative patches for IE seem to restore it. the following reg.exe commands can inhibit the icons though...for new profiles I believe. rem kill Outlook Express 6 icon creation reg delete "HKLM\Software\Microsoft\Active Setup\Installed Components\{44BBA840-CC51-11CF-AAFA-00AA00B6015C}" /v "StubPath" /f
  19. I can get this script to try and expand the files the same folder, but it errors out reporting the folder (file) exists CD /D D:\scvpack.XP\07202004 D:\scvpack.XP\07202004>FOR %X IN (kb*.exe) DO "%~nX.exe /x:%X" results in: D:\scvpack.XP\07202004>"KB842773.exe /x:KB842773.exe" The directory name is invalid. how can I get the ' /x:KB842773.exe' output to be '/x:KB842773', creating the desired folder structure? me = BTW this is placed here in unattended Win due to the embedding of these expanded files into the unattend CD. TIA -
  20. See The KB 828930 - it details how most current (Q819696, Kb822603, Kb823182, Kb823559, Kb824105, Kb825119, Kb840374, Q329115, Kb818043) files that use 'update.exe' to execute can use the /integrate switch. There is a newer update tool 'xpsp1hfm.exe' for dual mode updates. KB 828930 - includes link to dual mode updates support.microsoft.com/default.aspx?kbid=328848 Old update page on Technet- microsoft.com/technet/archive/security/tools/tools/hfdeploy.mspx
  21. lose the MS version (on the CD) of winnt.sif and unattend.txt from your i386 folder. Search for my posts on this subject, I have a nearly complete winnt.sif file posted up. There are minor differences between the XP and 2000 versions of winnt.sif.
  22. Some drivers for 2000 (and less so for 2003) are different. It is preferable to run windows update and include the WHQL drivers in your builds. I'm in the process of building my company desktops in 2000 and XP versions to be as identical as possible in look and feel for our (l)users. Mind you I originally started the 'look and feel' with NT4, and need to carry this through to our XP desktops. I do this to minimze user training.
  23. reg.exe - from the resource kit. I use with great success in batch files run from cmdlines.txt, runonceex.cmd, etc.
  24. I ran into a similar issue installing Altiris clients on our network. Apparently this problem stems from bad installer code, that installs an .EXE to : "C:\program files\myapp\app.exe" Sadly, the installer is moronic/anal and reads this as "C:\program", renaming the original .EXE to program.exe (ading the .exe extention) and instlling it to C:\. Unfortunately, the uninstallers created by the setup aren't very reliable in removing this atrocity from your system- especially if you realize your problem and run the offending installers using SFN instead of LFN. There are way too many "C:\program" entries in the registry to root out the most vile versions of this issue. A dummy program that does absolutely nothing is a good workaround.
  25. You have a file mismatch problem- usually the files ntdll.dll amd smss.exe don't match in i386\ and i386\system32\ on you iso structure. This one is a PITA to figure out because the error isn't in your setup files themselves. I am very hard headed and would not let this get the better of me.

  • Create New...