jayroos.com

Set Page Numbering for Multiple Excel Sheets

Jay — Wed, 24 Jun 2009 18:08:16 +0000

For the first time I can recall, I had to setup page numbering in an Excel footer. Initially it was driving me crazy that I would set the footer for one tab, but it wouldn’t apply to the rest. For a brief moment I thought I would have to set the footer on each page and remember to adjust the numbering.

Fortunately, I decided to Ctrl-click each of the sheet tabs I wanted to number enter page setup and set the footer in the normal Microsoft Office way. Sure enough it worked. Shift-click will also work to select a range. No doubt this also works for other Page Setup options.

This may be common knowledge, but I never needed to do it until today.

Daylight Savings Time Update for Windows 2000

Jay — Sat, 03 Feb 2007 23:27:17 +0000

The United States government has changed the start and end dates for Daylight Savings Time as part of the Energy Policy Act of 2005. The theory is energy will be saved by starting earlier and ending later. Of course our computers don’t know that yet. Unless you fix it, your computer’s clock will be off by an hour when you wake up on March 11th.

If you have a computer running Windows XP or later you’ll be fine if you just go get the patch for your OS from Microsoft. If you have Windows 2000 you have to do it the hard way, unless you have Extended Hotfix Support. Windows 2000 is no longer supported by Microsoft, but they do provide a long knowledge base article to tell you how to do it yourself.

Fear no more. I needed to simplify the process so it can be repeated on hundreds of machines. I’ve wrapped it all up in one self-extracting zip file and I’m sharing it with you. DSTUpdate.exe was created with ZipGenius and if you want to check my work feel free to look inside and check it out.

Make the Windows 2000 Registry Repair Utility into a Bootable CD

Jay — Tue, 13 Jan 2004 12:00:00 +0000

In September Microsoft released the Windows 2000 Registry Repair Utility at their downloads site. The utility fills a void in my software toolbox I’ve been trying to fill for some time. There are ways to boot into the recovery console and fix the registry but there’s never been an easy way and they often don’t work. This utility has already saved more than one computer I administer.

The instructions provided with the utility require creating six Windows XP Setup Floppy Disks and then running an installer that copies some files to the sixth disk. To run the program you need to boot from the floppy drive and successively insert each disk until you get to the last one. The program then asks which installation to fix and hopefully fixes it.

I wasn’t satisfied with loading six floppies to get the job done. My toolkit only includes one blank floppy. Everything else I need is kept on CDs. If I need a bootable floppy I have images on a CD that I can load to the floppy as needed. So I set out to figure out how to move the utility to CD.

I tried booting from a DOS floppy and running the program but it does not run in DOS mode. I also tried adding it to a Bart’s PE-Builder CD
but it didn’t want to run there either. My last try was to run it from
the recovery console but I had no such luck. The six disks I had
created were obviously some flavor of recovery console, which can be
booted from CD, so I turned to Google and started searching.

Requirements

To create a Windows 2000 Registry Repair Utility some programs and files are required:

Windows XP or Windows 2000 bootable installation CD
Windows 2000 Registry Repair Utility
Windows XP Setup Floppy Disks
Bart’s Boot Image Extractor
Disk Image file Extractor
CDRTools for Windows

Assumptions

Drive D: is a hard drive
Drive E: is the CD-ROM drive

Directions

Create 3 folders on drive D: named w2krepaircd, w2krepairfiles and temp

Get instructions on using the Windows 2000 Registry Repair utility from Microsoft.

Resources

Windows 2000 Registry Repair Utility
http://www.microsoft.com/downloads/details.aspx?
FamilyID=56d3c201-2c68-4de8-9229-ca494362419c&DisplayLang=en

Windows XP Setup Floppy Disks
http://www.microsoft.com/downloads/details.aspx?
displaylang=en&familyid=55820EDB-5039-4955-BCB7-4FED408EA73F

Barts PE-Builder
http://www.nu2.nu/pebuilder/

Bink.nu – Making a Bootable Windows 2000 CD with Service Pack Integrated
http://old.bink.nu/bootcd/

Windows Network Mag – How do I create a bootable CD-ROM containing ERD Commander/Professional?
http://www.winnetmag.com/Article/ArticleID/14732/14732.html

Bart’s Boot Image Extractor
http://www.nu2.nu/bbie/

Gilles Vollant Software – Extract
http://www.winimage.com/extract.htm

Dual Boot Windows 2000 and Ghost

Jay — Mon, 04 Nov 2002 12:00:00 +0000

For some time now, I’ve been using Norton Ghost to make perfect backups of my computers. The one thing about Ghost that gets old, is you have to boot up to DOS with a floppy disk or CD-ROM in order to make the backup. In addition to requiring a boot floppy, I keep my BIOS set to only boot to the hard drive so I don’t accidently boot up a floppy and risk infecting my computer with a virus.

I decided to figure out how to dual boot Windows 2000 and DOS so I can boot up to DOS on the hard drive and run Ghost without popping in floppy disks and changing BIOS settings to allow the computer to boot to the floppy.

If you don’t follow these steps your system may not be able to boot
up. Make sure you have a Windows 2000 boot CD handy before you start.

I found instructions in Microsoft’s Knowledge Base article Q153762 when creating the dual boot.

Boot your machine from a Windows 98 boot disk or another boot disk with the sys.com utility.
At the DOS prompt type sys c:. This will destroy the Windows 2000 boot sector but we’ll repair it in the next step.
When the system transferred message is displayed, reboot with the Windows 2000 Install CD-ROM or the Windows 2000 Setup Disks.
When prompted press R to repair.
Press R again to use the Emergency Repair Process.
Select M for Manual Repair.
Deselect Inspect startup environment and Verify Windows 2000 system files. Then select Continue
Select L to locate the current Windows 2000 install location.
If the directory displayed press ENTER
to fix the boot sector. The computer will reboot when the repair is
complete. Remove the CD-ROM before the computer boots to it again.
Boot into Windows and use Notepad to edit boot.ini located in C:\.
Add a line at the end of the boot.ini file with something similar to c:\="Boot to Ghost backup" and save the file. If you want to change the amount of time that the boot menu is shown, change the line "timeout=30" to whatever number of seconds you like.

Make sure you copy the files you need to the hard drive such as ghost.exe and mouse.com.

You’ll now be able to choose whether to boot into Windows 2000 or DOS and you won’t need to put in a boot floppy to do it.

You may want to have autoexec.bat automatically run some commands
when you boot up but autoexec will run whether you boot DOS or Windows.
See the example below for a workaround. I haven’t come up with a
similar method for config.sys yet.

Sample Autoexec.bat:

@ECHO OFF

IF “%OS%” == “Windows_NT” GOTO QUIT

PATH=c:\winnt\system32;d:\
D:\mouse.com
D:\

:QUIT

Recovering From a SYSTEMced Error

Jay — Wed, 16 Oct 2002 12:00:00 +0000

Note: This procedure has been superceeded by the availability of the Windows 2000 Registry Repair Utility. Please see my tip on how to make it into a bootable CD and try it before you try this tip.

The Windows 2000 SYSTEMced error occurs when the system can’t load the SYSTEM hive of the registry. The reasons include the SYSTEM hive being damaged, missing or too large to load.

The cause I’ve experienced most often has been the hive being too large to load. The SYSTEM hive has to share 16 MB of memory with several other processes when it is first read so if the hive is 16 MB and the other processes take up 3 MB it just can’t be read. Microsoft has instructions for recovering from a hive that gets too large in knowledge base article Q269075. However, I’ve never been able to recover a system using only the method they specify. Microsoft assumes that the SYSTEM hive is too large because there are a large number of shared resources and their fix is to eliminate the key of the hive with the shares in it.

If the SYSTEM hive isn’t large due to shares then what makes it too
big? As the system reads, writes and deletes data in the registry, it
sometimes leaves gaps. While the size of the actual data may not
increase by much, the system still has to read in the entire file. If
there are 3 MB of data and the registry file has 13 MB of wasted space,
there’s going to be a problem. Normally the wasted space doesn’t get
very large, but occasionally a bad program or runaway process makes a
mess of the registry.

I recently discovered a program called RegCompact
that eliminates the empty wasted space from the registry. Unfortunately
it only works on hives that are currently loaded so if you follow
Microsoft’s instructions and replace the oversized hive with the backup
you won’t be able to compact it.This procedure requires logging into
the recovery console and changing registry hives. If you’ve come this
far chances are your system is already not working right. You could
still make things work so take care.

Follow my instructions to repair a SYSTEMced failure that is not due
to a large number of shares. These steps are very similar to
Microsoft’s but we’ll assume the problem is not with shares.

Use the Windows 2000 CD-ROM or Windows 2000 startup floppies to boot up.
Choose R to enter the repair menu.
Choose C on the repair menu to run the console.
Select the installation of Windows you wish to repair and enter the administrator password.
Type cd system32\config and press enter.
Rename the bad SYSTEM hive and its alternate by typing ren system system.bad then enter and ren system.alt systemalt.bad then enter.
If you have run the Emergency Disk Wizard in the Windows Backup program, type copy C:\WINNT\Repair\Regback\system and press enter. Most if not all of your drivers will already be installed.
If you have not run the Emergency Disk Wizard type copy C:\WINNT\Repair\system and press enter. This is the default system hive and you will likely have to install drivers when you reboot.
Remove any CDs or floppies and type exit and press enter to reboot.
Once Windows boots and you’ve installed any necessary drivers obtain and install a copy of RegCompact
Go to Start -> Run and type regedt32.exe and click OK
Locate the window titled HKEY_LOCAL_MACHINE on Local Machine and click on HKEY_LOCAL_MACHINE.
On the menu go to Registry -> Load Hive…
Navigate to C:\WINNT\system32\config and select system.bad then click Open.
For the key name enter System.bad and click OK
At this point the bad hive will either load or it won’t.
- If it doesn’t load, it’s simply corrupted. You can either use the backup hive you just loaded or start with a fresh install.
- If it does load, continue on with the fix.
Exit the Registry Editor.
Open RegCompact. You should see system.bad in the list of hives. Click Compact. The computer will restart.
After
the system has booted up into windows again, reboot and use the Windows
2000 CD-ROM or Windows 2000 startup floppies to boot up.
Choose R to enter the repair menu.
Choose C on the repair menu to run the console.
Select the installation of Windows you wish to repair and enter the administrator password.
Type cd system32\config and press enter.
Rename the temporary SYSTEM hive and its alternate by typing ren system system.bak then enter and ren system.alt systemalt.bak then enter.
Copy the formerly bad system file to make it the actual system hive by typing copy system.bad system. There is no need to replace the alternate file because Windows will create a new one.
Remove any CDs or floppies and type exit and press enter to reboot.

Your computer should now be running as well as or better than it ran before the SYSTEMced error.

Modified 2003-09-04

Cleaning up after Internet Explorer

Jay — Thu, 28 Mar 2002 12:00:00 +0000

Internet Explorer leaves pieces of information from browsing all over the place and doesn’t clean up after itself when you’re done browsing. Whether your concerned about privacy or just don’t like having all the garbage lying around, this one’s for you.

You use this script at your own risk. I am not a programmer. I just occasionally hack together code that gets the job done. If this script should happen to go wild and hose your computer you’ve been warned.

CleanExplore.vbs

This script replaces launching IE directly. Instead CleanExplore launches IE and watches it. When IE exits the script wakes up and deletes Typed URLs, Cookies, the Cache and History files. It will not remove any index.dat files or any subfolders that are not empty.

Installation:
Copy this file anywhere you like. If IE is not in the standard location change the strIEPath variable below. Replace your IE shortcuts with shortcuts to this script. Rename them to Internet Explorer for transparency and change the icon to the big blue E.

Securing Netbios on Windows 98

Jay — Mon, 12 Mar 2001 12:00:00 +0000

Microsoft is not known for it’s high security practices. As a result most people who run a Microsoft operating system have the security holes already built in. In this tip I’ll show how to add just a little more security to your Windows 98 setup.

If you are using file and printer sharing or any other service that depends on netbios you shouldn’t use this tip. If you are unsure you certainly shouldn’t bother. This procedure also requires registry editing and renaming of system files. Anytime you venture into the registry you risk rendering your system useless. Before following these instructions be sure you have all important files backed up.

To completely disable netbios in Windows 98, first open the Network Control Panel and make sure that File and Printer Sharing is uninstalled. Next go to C:\Windows\System and rename vnetbios.vxd to vnetbios_vxd. Now open regedit and navigate to the Key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETBIOS. Right click on the VNETBIOS key and choose delete. With you must restart to apply the changes. Once you restart if you open a DOS prompt and type netstat -a you shouldn’t see any netbios ports listening (ports 137-139).

Modified 2001-03-12

Securing Netbios on Windows 2000

Jay — Thu, 08 Mar 2001 12:00:00 +0000

Microsoft is not known for it’s quality security practices. As a result most people who run a Microsoft operating system have the security holes already built in. In this tip I’ll show how to add just a little more security to your Windows 2000 setup.

If you are using file and printer sharing or any other service that depends on netbios you shouldn’t use this tip. If you are unsure you certainly shouldn’t bother.

Open the Network Control Panel. Then right click on your Local Area Connection and choose properties. The first step in securing netbios is to uninstall File and Printer Sharing if it is listed. This goes for any operating system and any protocol. If you don’t need a protocol then it’s just another security hole. The next thing to do is disable netbios over TCP. Click on Internet Protocol (TCP/IP) and choose properties. Next choose Advanced… and click the WINS tab. On this page uncheck Enable LMHOSTS lookup and choose Disable NetBIOS over TCP/IP. Click OK and if it asks you “This connection has an empty primary WINS address. Do you want to continue?” click yes. Click OK and OK and then close the control panel. You should reboot. Now any scanner looking for netbios information will turn up empty. One less hole.

Modified 2001-03-08

Creating a Bootable CD-ROM

Jay — Thu, 07 Dec 2000 12:00:00 +0000

The directions for making a bootable were never obvious to me so I never did it. One day I decided I wanted a bootable CD and made several coasters in the process of trying to get it right. Hopefully my directions will help you save a couple bucks on blanks.

The directions that follow were written with Adaptec Easy CD Creator in mind. There are many CD burning packages available and there will be variations in procedure.

When you create a bootable CD, a boot image is created on the CD that the computer uses to boot up. The boot image is created from a floppy and behaves like a floppy. The image is opened in to memory just like a ram drive and uses the drive letter A:. There are a couple things to keep in mind when you are creating a bootable CD. The first thing is the format used on bootable CDs is ISO 9660, which means filenames can only be 8 characters long with a 3-character extension. If any file names are longer than that they will be truncated so they look like filena~1.txt. The second thing to remember is the CD-ROM drive still needs to have drivers loaded in order to use it. Without the CD-ROM drivers, the computer will only read the image information from the CD. The best way to make a bootable CD is to act like you’re still using a floppy disk and CD. Set up a floppy to work with the CD as if it was a non-bootable CD. That means the floppy should be bootable and include the CD-ROM drivers, config.sys and autoexec.bat as well as any other files and drivers necessary to start the computer. Once you get everything set up all you have to do is burn the CD. If you use Easy CD creator it will ask you to insert a bootable floppy. Just add files to the CD and you’re all set. The last thing to keep in mind is the computer must support booting from CD-ROM and the CD-ROM must be set to boot before hard drive otherwise it’ll just ignore the CD and boot to the hard drive instead.

Modified 2000-12-07

Flushing the Windows 2000 DNS Cache

Jay — Wed, 29 Nov 2000 12:00:00 +0000

In Windows 2000 there is a service that keeps DNS information cached on your computer. This is good because the computer doesn’t always have to query the DNS server to locate web sites you’ve already visited. The problem is if you don’t restart your computer often enough and one of the DNS entries changes it doesn’t always get reflected in the DNS cache. A recent example is when a friend of mine changed his hosting service. Other computers showed the web site with no problem but my computer continued to show the old site. I fixed it by restarting but depending on what else is running on the computer it’s not always possible or desirable to restart to update or flush the DNS cache.

There’s no real danger with this tip. The worst thing that could happen is your DNS server may go down immediately after you flush the cache and you won’t be able to access any web sites until it comes back up. Not likely.

This is a simple procedure. Just open a DOS Window and type ipconfig /flushdns at the command prompt. All done.

Modified 2000-12-07