Subscribe to Windows IT Pro
February 01, 1997 12:00 AM

Reader to Reader - February 1997

Windows IT Pro
InstantDoc ID #3547
Rating: (0)
Downloads
syslist.zip

[Editor's Note: Share your NT discoveries, comments, problems, and solutions and reach out to other Windows NT Magazine readers (including Microsoft). Email your contributions (under 400 words) to Karen Forster at karen@winntmag.com. Please include your phone number. We will edit submissions for style, grammar, and length. If we print your letter, you'll receive $100.]

In "Tricks and Traps" on page 183 of your October issue, a reader asked about a problem with a 3Com card. I encountered the same problem, but the solution was in the BIOS.

Here's how I fixed it. In an Award BIOS, go to PCI and Onboard I/O Setup. Disable pnp bios auto config, first IRQ 9, second IRQ 11, third IRQ 10, fourth IRQ 12. This solution fixed the problem of no soft reset and let me keep the bus mastering.


Automated Clean-Up
Recently, I have added more than 1400 users to my network. This number is not a lot for a large network, but most of these accounts are mobile: The users don't sit at the same workstation all the time. Under Windows NT Workstation 4.0, I store the roaming user profiles on the server as a file and several directories that migrate down to the local workstation when the user logs on. The user profiles contain from 1.2MB to 4MB of data. When you're dealing with multiple users, over time, this data can affect space on the drives. Also, the systems suffer from memory leaks that only a reboot can cure.

Because I have been plagued by such problems, I created a simple Perl script (available for download at http://www.winntmag.com) to locate systems (which I list in a text file called syslist.txt), reboot them, delete profiles from the local directory, and clean up the temp directory. To use this script, you need Perl 5.0 for Windows NT, shutdown.exe from the Microsoft Windows NT Resource Kit for NT 3.51, cacls.exe to set file rights, and full understanding of the AT command.

Follow these steps when setting up this utility:

1. Install Perl 5.0 for NT.

2. Create a directory, adminlog, for the log file off the root drive of the managing system.

3. Create a command file if you want to use the AT command scheduler to automate the script. Make sure you put this file in the \winnt\system32 directory. (AT has a hard time finding things anywhere else.) The contents of the command file are as follows:

cd\

echo * cleaning system

clean.pl

4. Create a syslist.txt file with the machine names of systems you want to clean up. Make sure the last name has an additional space because Perl's CHOP command deletes the last character from the line. Also, place this file into the root. Example:

pc130-01

nickstuff

webrunner

jackie

5. Place the contents of the script in a file called clean.pl.

6. Use Explorer, View, Options, File Types to associate .PL extensions with perl.exe.

7. Enter the following command at a command prompt:

AT 02:00am /every:m,t,w,th,f,s,su clean

This command will run the clean.bat or clean.cmd every night at 2:00 am. Every morning, you will find a log file labeled with the day of the year and the year; for example, 343_96.log. I hope this script helps you as much as it has helped me.

Related Content:

ARTICLE TOOLS

Comments
  • Kevin Belanger
    13 years ago
    Aug 12, 1999

    Having just read February’s Reader to Reader, I wanted to write about the products that two readers mentioned. I had the same troubles as Nate Eckstine with a Creative 8x CD-ROM kit. After failing to make the drive work while it was attached to the Sound Blaster card it came with, I attached it to the IDE controller (because it is an ATAPI drive). Sure enough, it works like a charm.
    I agree that Iomega NT support is not what it should be. In the Windows NT Magazine online forums (http://www.winntmag.com), I’ve read of problems of trying to use Zip drives with NT and I discovered—at least with version 1.2 of the Iomega NT software—you are better off expanding these files in a temporary directory and then installing the Zip drive drivers instead of all the Zip software.
    My workaround (for the Parallel Zip) involves adding the Zip drive as what it is, a new SCSI Adapter. In NT 3.51, run Windows NT Setup, choose Add/Remove SCSI Adapters from the Options menu, and click Add. After NT warns you about the perils of adding SCSI Adapters, click OK and then Other (Requires a disk from a hardware manufacturer). Guide Setup to the temporary directory where you expanded the Zip files. It can then find the oemsetup.inf file. Let NT install the drivers.
    After you reboot, the Zip drive will appear in File Manager as just another drive (albeit a removable one). With NT 4.0, the initial path to installing the SCSI adapter is different, but the steps are the same: In Control Panel, choose the SCSI Adapters applet, and click the Drivers tab, then choose Add. After NT compiles a drivers list, click Have Disk and follow the same as steps for NT 3.51.

    --Kevin Belanger

  • Darrell Prichard
    13 years ago
    Aug 12, 1999

    I read Garren Shannon’s February Reader to Reader tip, “Automated Clean-Up,” about cleaning up locally cached user profiles. To minimize local disk space usage of locally cached domain user profiles, you can create the Registry entry,



    HKEY_LOCAL_MACHINE\\SOFTWAREMicrosoft\\Windows NTCurrentVersion\\Winlogon

    DeleteRoamingCache REG_DWORD

    Range: 0 or 1

    Default: 0



    and log off. The cached profile will be deleted when the user logs off. If this entry’s value is 1, locally cached profiles are deleted from that machine when users with domain profiles log off.
    Unlike Garren’s solution, this approach doesn’t provide any logging functionality. However, for many users, this single entry will work, and it reduces the security risk of copying a local profile to a client machine.

    --Darrell Prichard

    Microsoft Premier Support

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.