Can't delete Non-DOS partitions with fdisk Microsoft's version of fdisk has problems dealing with file systems such as Linux. You'll need to do one of three things -- 1.) Contact the hard drive manufacturer for a low-level format utility. 2.) Use a commercial program such as Powerquest's Partition Magic that can recognize the partition or 3.) Use the fdisk utility that ships with the Linux distribution -- start the Linux install, choose Fdisk (NOT Disk Druid) as the partition method, and delete all partitions. Go as far as writing the partition table and then abort the Linux install.

Can't get rid of LI or LILO message on boot This is a simple one to fix. Boot to a system floppy containing fdisk.exe and type FDISK /MBR at the command prompt. If the system hangs at "LI", and you wish to dual boot between Linux and a Microsoft OS, please see my Linux support page.

Installation Hangs Sometimes this is a memory management issue. Be sure of 2 things: If upgrading from DOS, be sure that you DISABLE expanded memory support during the upgrade. If you have started the computer using a Windows-98 startup disk, it creates a RAMDRIVE to load all the programs. Make the hard drive bootable, and rerun SETUP AFTER reboot.

Windows Protection Error Win-95 with AMD processor Microsoft itself has confirmed this to be a problem -- the AMD processors running at greater than 333 megahertz exceed the design capacity of Windows-95 OSR2. This causes the error message upon reboot to start Windows-95 for the first time. Microsoft has an update available at its web site, which works, but its method of deployment is faulty. They say to run the update by starting Windows in safe mode and then installing the update. But Windows doesn't start, even in safe mode. The only workaround is to (first back up the Windows\system\iosubsys and Windows\system\vmm32 directories), install the update on a machine that doesn't need it, copy the files it modifies in the Windows\system\iosubsys and Windows\system\vmm32 directories and then transfer these files to a floppy. Then boot the problem machine to a command prompt and manually overwrite these files. Then restart Windows and everything will work fine.

DOS Programs Won't Run Windows-95/98 is designed to support the mouse, CDROM and soundcard with 32-bit drivers. Some DOS programs cannot function that way, so that's why there's an MS-DOS mode. But the MS-DOS mode needs to be set up properly, and memory-optimized. For more information, click on this link. Windows-NT and Windows-2000 both are able to run DOS programs in a virtual DOS machine and in some cases will even run programs that can only run in MSDOS mode under 9x. But neither will run programs which 1.) directly access the hardware (like ones that use a soundcard) 2.) use VESA video modes or 3.)otherwise violate memory usage requirements. In addition, some programs run slower. If any of these situations are true under NT or 2000, the only recourse is to reboot the machine to an OS that has real-mode support which means DOS or 9x and using MSDOS mode if needed.

Devices Don't Work After Win 95/98 Install I'm not kidding about this one -- the rumors that Plug and Play doesn't work right are true! The problem is that sometimes, devices that are already in the computer when Windows is installed aren't properly detected -- Windows just figures that something mysterious is using resources. The workaround is to first try (I'm not kidding!) REMOVING ALL peripheral cards except the video adapter. THEN, reformat and reinstall Windows. AFTER Windows is reinstalled, shut down the computer (properly) and put in one card. Turn on the computer. Windows will usually detect the hardware properly because it sees a change. Allow the install to proceed, using manufacturer's disks (or CDs) as needed. Allow Windows to restart when prompted. Power off and repeat this process for each peripheral card. If this fails to resolve the problem, consult the motherboard manual to determine if a special driver for the motherboard needs to be added (if so there should be an installation diskette or CD-ROM)

Internet Access Doesn't Work (95) By design, Windows-95 installs the NETBEUI and IPX/SPX protocols but not the one needed for Internet (TCP/IP). To fix it, click on Start, Settings, Control Panel. Click the Network icon. Click the Add button. If TCP/IP is not listed, click 'Protocol', then Add. Select Manufacturer 'Microsoft', then select protocol 'TCP/IP'. If IPX/SPX and NETBEUI are not needed for anything else, remove them. If they are needed, do not remove them but instead select TCP/IP or TCP/IP-->Dialup Adapter and click Properties. Click the Advanced tab and be sure the box is checked to set TCP/IP to be the default protocol. Click OK as often as needed to exit, and files will be copied. Restart the computer when prompted.

Remote Access Doesn't Work (NT4) RAS is not installed by default. To make it work properly, it must be installed AND Service Pack 3 or higher (I currently recommend #5) must be reapplied.

Can't Install AGP Video Driver (NT4) Service Pack 3 or higher must be applied before NT will be able to recognize the AGP port.

SCSI Adapter Not Detected (NT4) Consult the manufacturer for installation instructions. Frequently the cure is to reinstall Windows-NT from the 3 boot floppies (if you don't have them you can make them by running "winnt /ox" from the i386 directory of the NT4 CDROM), and inserting a manufacturer's support disk BEFORE allowing NT to detect ANY other adapters, including ATAPI CD ROMs.

Windows (95/98) is still goofy after reinstall If you attempt to install Windows over itself, version conflicts may occur. That's why I always recommend a reformat whenever installing your current version of Windows.

USB or Dial Up Networking Upgrade Issues (Windows-95) USB is supposed to work with later versions of Windows-95, but it doesn't. Also Dial Up Networking Upgrades for games often cause other communications software to not work properly due to DLL file alteration. In either case, upgrade to Windows-98.

NT Setup aborts with a master boot record message Though the error message might suggest otherwise, the real cause is probably a design limitation of Windows-NT: It will not install on

NT Service Pack Deployment Issues If this is the first time you've deployed a particular service pack, it is recommended you back up the files in case you have to uninstall it later. If the installation aborts the service pack either has become corrupted or is not from Microsoft. Service packs may be downloaded from the Microsoft web site. I recommend using the option of downloading the entire service pack for later installation. It will take longer to download but you have the advantage of only downloading it once (you can burn a CDR disk) and you protect yourself from being disconnected from the internet in the middle of an upgrade and finding out too late your download was bad.

Applications Won't Run in Windows 2000 Check the documentation that comes with the Windows-2000 CDROM to find out if your application is one of the 40 or so applications that won't run with Windows-2000 or won't run correctly. CD recording especially is difficult, due to changes in the operating system, and requires the use of the most up-to-date software. Consult Usenet newsgroups if you still have a problem after installing the latest CD recording software. If you can't get it to work with Windows 2000, and don't wish to revert to 95, 98 or NT4, consider also the use of the Linux operating system.

Windows 2000 only sees one drive in a CD changer This only affects ATAPI changers. They are treated by the OS as tape drives. They are given only one drive letter. To access additional drives, you'll need to go to the Control Panel | Administrative Tools | Computer Management | Storage | Removable Storage | Media Pools and find the drive unit to mount the correct device. Unfortunately not all ATAPI changers have the right driver to allow this, in which case you have incompatible hardware and no choice but to use 95 (preferably 8-24-96 or later), 98, or NT4, all of which have no trouble recognizing the changer. Linux will not recognize ATAPI changers either beyond the first drive bay but won't have trouble with SCSI changers.

Networking doesn't work after upgrading to Win-2000 Aside from checking the usual stuff like your cable, the lights on the back of the netcard, workgroup / domain name, and TCPIP properties, also check the documentation that comes with the Windows-2000 CDROM to find out if your network card is one of about 100 that are not supported under Win-2k. If this is the case, your options are