Jump to content

tguy

Member
  • Posts

    698
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by tguy

  1. You could also use the WININSTALLLE utility from OnDemand software. Go to APPDEPLOY.COM there are a number of freeware application installer/snapshot utilities there you can try. tguy
  2. With the USB hard drive you may need to use disk administrator to create it on your system as a logical drive and then assign it a drive letter. I have seen this before with some USB drives I have worked with.
  3. Try disabling the XP SP2 firewall to see if that helps.
  4. Here are a couple of things you could try: First it sounds like the problems you describe could be network related. So: 1) Update the NIC drivers on your Windows XP PC's to the latest version. Usually available from the manufacturer. 2) Set the link speed of the NIC. - Go to the Properties of Network Neighborhood - Click on the Configure button of the NIC in your PC - Click on the Advanced tab find the Link Speed which by default is usually set to Auto or Autonegotiate. - Modify this setting and hard code the wire speed to match the maximum allowable wire speed for the hub or switch the PC is plugged into. - Save these changes. You should not need to reboot. - NOTE: You may also want to make these changes on your server as well if you have one. Second you can change the Save options in MS Word by selecting: Tools --> Options --> Save tab Try setting Allow Fast Saves and/or Allow background saves You can also try decreasing the amount of time the Autorecover document feature waits to create backup copies. I think the default is ten minutes. you can drop it to between 3 and 5 minutes to see if that helps. Good luck.
  5. tguy

    Unable C:

    You can use the Internet Explorer Administration Kit from MS to lock down I.E. It is available for free download from http://download.microsoft.com. Make sure you get the right version. As always be careful when using lock down and security tools as you may get unexpected results. Use a test computer system to try out any changes before you apply them in production. Hope this helps.
  6. You can also try these resources: http://www.microsoft.com/technet/scriptcenter/default.mspx http://www.15seconds.com There are scripts on these sites to do what you are looking to do.
  7. Make sure that your Administrator account and special FTP account also have file system permissions to the FTP directory on the server or disk where the directory is located. You can check the permissions through Explorer or with the CACLS utility. tguy
  8. I posted a suggestion for you in the Unattended section of this forum. Please try to refrain from cross posting your inquiries as it may be missed by someone who might have the answer you are looking for.
  9. Check the security logs on your domain controller(s) to see if there is any indication of the attempt to log on. This is assuming that you have auditing configured. If not, turn on auditing in your local security policy and then have the user try to log in. See if there are any errors that appear in the logs. Hope this helps. tguy
  10. Here is how I do it. I created a custom Win2K CD with SP4 slipstreamed into to the source files. Using the $OEM$ method discussed at http://unattended.msfn.org I incorporated IE6 SP1. I launch the setup out of my cmdlines.txt file with the following syntax: "C:\WINAPPS\IE6\IE6SETUP.EXE /Q /R:N" /Q installs quietly /R:N suppresses the reboot This completes before Windows loads the GUI for the first time and has not given me any problems. Hope this helps. tguy
  11. You could try running diskpart.exe with a script to create and format the D:\ from your cmdlines.txt or [GuiRunOnce] section. Then create a folder called D under the $OEM$ folder, ie: $OEM$\D Copy your programs to that drive and then run the scripts to install them from there. tguy
  12. Check out this URL: http://unattended.msfn.org/xp/winnt_sif.htm tguy
  13. I do not see those files in my source file directory either. You should check your [sourceFiles] section of the TXTSETUP.SIF, if the files are listed there, comment out or remove the references to them. tguy
  14. First off, these settings look to be Terminal Server related. I would suggest you check the Microsoft Technet Scripting site, specifically the Script Repository, there are a number of Terminal Server and User configuration scripts located there. Good luck. tguy
  15. I found the NonDriverSigningPolicy 'switch' here in the Forums, worked for me, good luck.... tguy
  16. Try adding these two lines to the [unattended] section of your WINNT.SIF file: Repartition=Yes ExtendOEMPartition=0 tguy
  17. Try running the setup program with a /? or -? to see if it gives you any options.
  18. tguy

    TweakUI

    I have seen this problem before too. Increasing the font size on the Appearance tab of your Display properties, applying the changes, and then reverting to the old setting and applying the changes fixed the problem for me.
  19. This practice is really NOT recommended. SQL Server services are often tied to local accounts like the local Administrator account for startup. In addition, there are entries in the registry related to the server name created during setup. You can rename the server, change the account name for the services accounts and try and edit the registry but if you do, SQL server may become extremely unstable. I would suggest you back up the SQL databases, move them off the server to another drive or to tape, rebuild the server with the new name, install SQL Server and then try restoring the databases back to it. You could also detach the databases, move them to another SQL server and attach them there. This is all dependent upon whether the application using the database(s) will tolerate these steps. tguy
  20. There are a couple of options you can try: 1) Purchase a copy of ERD Commander 2003 from Winternals software it is meant to aid in the recovery of damaged, corrupted, or failed Windows systems. 2) Create a Bart's boot cd, locate and download the Windows Ultimate Boot CD add-in's (there should be a link on Bart's site to it) Add the Windows Ultimate Boot CD plug-in's to your Bart's boot cd and it will include Registry editing and repair utilities you can use to accomplish your task. tguy
  21. You could also do the same thing on a stand alone server that is not part of a domain. Open the Local Security Policy from the Administrator's Tools menu Open or expand Local Policies Open or expand User Rights Assignment Locate the setting for Deny log on locally Add the user(s) or group(s) you want and save. Good luck. tguy
  22. You could also look into PSEXEC.EXE from systernals.com. It should do the trick for you and can be run from a batch file. tguy
  23. You can download all the patches to a central directory, ie: c:\temp. I normally rename them to a shorter name as listed below for the sake of simplicity. Next, you can download qchain.exe from Microsoft's website. Copy or move it to the same directory as the patches. Create a batch file using the below listed syntax and then burn off to CD. When complete all you will need to do is to put the cd in the cd-rom drive and run the batch file you created. Example: @echo off setlocal set PATHTOFIXES=.\ %PATHTOFIXES%\KB823182.EXE /Z /M %PATHTOFIXES%\KB823559.EXE /Z /M %PATHTOFIXES%\KB824105.EXE /Z /M %PATHTOFIXES%\KB825119.EXE /Z /M %PATHTOFIXES%\KB826232.EXE /Z /M %PATHTOFIXES%\KB828035.EXE /Z /M %PATHTOFIXES%\KB830352.EXE /Z /M %PATHTOFIXES%\KB837001.EXE /Z /M %PATHTOFIXES%\KB839643.EXE /Z /M %PATHTOFIXES%\KB839645.EXE /Z /M %PATHTOFIXES%\KB840315.EXE /Z /M %PATHTOFIXES%\KB841872.EXE /Z /M %PATHTOFIXES%\KB841873.EXE /Z /M %PATHTOFIXES%\KB842526.EXE /Z /M %PATHTOFIXES%\KB824146.EXE /Z /M %PATHTOFIXES%\KB828028.EXE /Z /M %PATHTOFIXES%\KB828741.EXE /Z /M %PATHTOFIXES%\KB828749.EXE /Z /M %PATHTOFIXES%\KB835732.EXE /Z /M %PATHTOFIXES%\QCHAIN.EXE ECHO "Installation Complete" EXIT Note: This list does includes most all of the patches released after service pack 4 was released but it is NOT a complete listing. I created this update CD in August of 2004. Any patches released since then are not included if that helps any. Good luck.... tguy
  24. Here is what you need to do: A) Identify the appropriate driver files for the controller you are working with ie: Compaq Smart Array 5i (as will be discussed in this example) B) The driver files can typically be obtained from the manufacturer’s website. Once obtained, expand/copy the files to a temporary directory, ie: C:\Temp. C) Most driver file sets will consist of at least three files. For instance with the Smart Array 5i controller the files are: a. CPQCISSM.CAT b. CPQCISSM.INF c. CPQCISSM.SYS D) Copy the .SYS driver file into the root of the i386 directory where your source files are located. E) Next, in the i386 directory, locate a file called TXTSETUP.SIF and open with Notepad or another text editor. F) You will need to add the following entries for your driver to each of the four sections shown below: a. [sourceDisksFiles] cpqcissm.sys = 1,,,,,,6_,4,1,,,1,4 (Note: the first 4 listed indicates the file is to be copied to the ..\SYSTEM32\DRIVERS directory at the destination location) To identify the exact parameters to list after the = sign, first check a Windows Server 2003 CD to see if driver support for your controller is listed. Then copy the parameters from the TXTSETUP.SIF file on the Server 2003 CD to the TXTSETUP.SIF file for Windows 2000. If the driver is not listed, find a similar driver and mirror those parameters. b. [HardwareIdsDatabase] PCI\VEN_0E11&DEV_B060 = "cpqcissm" PCI\VEN_0E11&DEV_B178&SUBSYS_40820E11 = "cpqcissm" PCI\VEN_0E11&DEV_B178&SUBSYS_40830E11 = "cpqcissm" PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11 = "cpqcissm" NOTE: Again, if available mirror settings from TXTSETUP.SIF file on Server 2003 CD c. [sCSI.load] cpqcissm = cpqcissm.sys,4 NOTE: Again, if available mirror settings from TXTSETUP.SIF file on Server 2003 CD d. [sCSI] cpqcissm = "Compaq Smart Array 53xx-series Controller" NOTE: Again, if available mirror settings from TXTSETUP.SIF file on Server 2003 CD Hope this helps. tguy
  25. I got the settings for the HardwareID Database from the OEMSETUP.INF file that came with the drivers.
×
×
  • Create New...