Jump to content

cluberti

Patron
  • Posts

    11,045
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

Posts posted by cluberti

  1. Have you considered extracting the driver to $oem$\$1\Drivers\Audio, then pointing your OemPnPDriversPath to include "drivers\audio" (like so: OemPnPDriversPath = drivers\audio)? Assuming you extract the driver here, and use OemPreinstall = YES, this should install the drivers during the GUI portion of setup without issue.

  2. Part of the problem is that it's not a dahotfix.exe hotfix :). If you extract it, it's an update.exe hotfix.

    So, you can call it by "msxml4sp2-kb887606-x86-enu.exe /passive /norestart", or you can integrate it via "msxml4sp2-kb887606-x86-enu.exe /integrate:<path to xp source>". DAHOTFIX won't work for this hotfix, because it's an update.exe hotfix.

  3. The Mozilla suite of apps run completely on their own, without using any built-in MS OS functions or API's (well, not entirely, but I won't bore you with the file API's and such). That's why those work fine - they aren't using anything in the OS to display menus or HTML, etc.

  4. Powerpoint (any version) does not support the shw format. It does allow you to save in the PowerPoint Show format (pps), but as faras I know, that's it. Perhaps there's a converter or something out there, but I've never seen one.

  5. Just a note - you CAN slipstream and integrate hotfixes into a RIS flat-file source. So if you have an XP SP2 source, when SP3 comes out you can simply slipstream your RIS source and viola, SP3. This doesn't affect RIPrep'ed images, obviously - they stay at whatever SP they were created on.

    And WDS is much more admin-friendly than RIS is, as some of you have already found :).

  6. In your unattend.txt or WINNT.SIF file, the following [Components] section should remove everything you don't need. Do some googling on these if you think you may use some of these, but I use these settings all the time without issue:

    [Components]

    Accessopt = Off

    CertSrv = Off

    CertSrv_Client = Off

    CertSrv_Server = Off

    Chat = Off

    Deskpaper = Off

    Dialer = Off

    Fax = Off

    Fp_extensions = Off

    FP_Vdir_Deploy = Off

    Freecell = Off

    Hearts = Off

    IIS_Common = Off

    IIS_Doc = Off

    IIS_FTP = Off

    IIS_HTMLa = Off

    IIS_Inetmgr = Off

    IIS_NNTP = Off

    IIS_NNTP_Docs = Off

    IIS_Pwmgr = Off

    IIS_SMTP = Off

    IIS_SMTP_Docs = Off

    IIS_WWW = Off

    IIS_WWW_Vdir_Printers = Off

    IIS_WWW_Vdir_TerminalServices = Off

    IISDbg = Off

    Indexsrv_system = Off

    LicenseServer = Off

    Media_utopia = Off

    Minesweeper = Off

    Mousepoint = Off

    Msmsgs = Off

    MSMQ_ADIntegrated = Off

    MSMQ_Core = Off

    MSMQ_HTTPSupport = Off

    MSMQ_LocalStorage = Off

    MSMQ_MQDSService = Off

    MSMQ_RoutingSupport = Off

    MSMQ_TriggersService = Off

    Msnexplr = Off

    Netoc = Off

    Pinball = Off

    Solitaire = Off

    Spider = Off

    WMAccess = Off

    zonegames = Off

  7. Most menu functions in applications are actually called using the MSV*.* files in system32. Run an sfc /scannow or (at worst) a repair installation. What you're seeing isn't a driver issue, it's file corruption (thankfully, they're most likely MS Windows files, so an sfc will fix them).

  8. In the services key, find the service in question that you'd like to remove. Within the service's key, there should be a value (ImagePath) pointing to the application or file that the service loads - either uninstall that application from add/remove programs, or manually remove that application's program files and service key. You may also want to search the registry to make sure any other references to the application are removed, just to be safe.

  9. CoolSights, there is no real way around this in non-interactive mode. The setting in gpedit no longer applies to non-interactive driver installations, and thus you must approve the driver from the console or it won't install. There is no way around it, at least in 2003. If you had an XP machine in a Windows 2000 or mixed-mode 2000/2003 domain, you could still set the driver signing policy to ignore and it would apply to both interactive and non-interactive installations, but 2003 Server no longer allows this, as it is a security risk.

    What drivers are you attempting to install non-interactively? And have you contacted the driver manufacturer to see if they have signed drivers, or have any in the works? If you had signed drivers, your problem would be solved.

  10. Yes, it removes them from the list. Obviously it doesn't remove the program the service references, but they do get removed from the list (and won't start, of course).

    As for the Control Sets, those are the last x good boots that you've had, x being the number of ControlSet00x keys. These are used when you try booting from Last Known Good in the F8 boot menu.

  11. Windows setup will ALWAYS check the floppy drive for a WINNT.SIF file upon starting - remove the WINNT.SIF file from the i386 folder if you have one there, and make sure the PC will boot from CD first. Put the XP CD in the CD drive, and your floppy with your WINNT.SIF in the floppy drive. Press a key to start the Windows setup when prompted, and it will read your WINNT.SIF from the floppy.

×
×
  • Create New...