how to make usb write protected

The main cause of viruses these days are USB flash drives. Viruses are now capabale enough to copy itself to whatever flash drive is attached into the infected computer’s USB drive. You can write protecyour USB drive by using this small portable tool.

USB WriteProtector is a portable freewarethat lets you lock your flash drives for write protection so that viruses or other unwanted things don’t get copied to your flash drive themselves.

After you enable write protection, you will not be able to write or delete any files from your flash drive and your data remains safe from being misused by viruses.

Compatibility

This 186 KB is compatible with Windows XP and Vista, and supports nice languages: English, Hungarian, Italy, Dutch, Polish, Portuguese, Russian, Chinese and Spanish.

http://www.gaijin.at/dlusbwp.php

converting FAT to NTFS file systems

Converting to NTFS

Although there are certainly third–party utilities that allow you to convert from FAT16 or FAT32 to NTFS (and may be cuter about it), you really don't need any special tool to perform the conversion—the necessary program is included on your hard disk as part of the Windows XP installation. To use this utility to convert your D drive, for example:

1. Close all open applications. This process may require a reboot, so be prepared.

2. Click Start, click Run, and then type cmd, and press Enter.

3. In the command windows, type:

convert D: /FS:NTFS

4. Press Enter.

That's it. If there are open files on the volume being converted, you'll have to reboot your system for the process to complete. And if this is a large drive that contains lots of files, the process could take a while to complete. I don't recommend that you try to do anything else while the conversion is occurring

FAT and NTFS file systems

To NTFS or not to NTFS—that is the question. But unlike the deeper questions of life, this one isn't really all that hard to answer. For most users running Windows XP, NTFS is the obvious choice. It's more powerful and offers security advantages not found in the other file systems. But let's go over the differences among the files systems so we're all clear about the choice. There are essentially three different file systems available in Windows XP: FAT16, short for File Allocation Table, FAT32, and NTFS, short for NT File System.

FAT16
The FAT16 file system was introduced way back with MS–DOS in 1981, and it's showing its age. It was designed originally to handle files on a floppy drive, and has had minor modifications over the years so it can handle hard disks, and even file names longer than the original limitation of 8.3 characters, but it's still the lowest common denominator. The biggest advantage of FAT16 is that it is compatible across a wide variety of operating systems, including Windows 95/98/Me, OS/2, Linux, and some versions of UNIX. The biggest problem of FAT16 is that it has a fixed maximum number of clusters per partition, so as hard disks get bigger and bigger, the size of each cluster has to get larger. In a 2–GB partition, each cluster is 32 kilobytes, meaning that even the smallest file on the partition will take up 32 KB of space. FAT16 also doesn't support compression, encryption, or advanced security using access control lists.


FAT32
The FAT32 file system, originally introduced in Windows 95 Service Pack 2, is really just an extension of the original FAT16 file system that provides for a much larger number of clusters per partition. As such, it greatly improves the overall disk utilization when compared to a FAT16 file system. However, FAT32 shares all of the other limitations of FAT16, and adds an important additional limitation—many operating systems that can recognize FAT16 will not work with FAT32—most notably Windows NT, but also Linux and UNIX as well. Now this isn't a problem if you're running FAT32 on a Windows XP computer and sharing your drive out to other computers on your network—they don't need to know (and generally don't really care) what your underlying file system is.
The Advantages of NTFS
The NTFS file system, introduced with first version of Windows NT, is a completely different file system from FAT. It provides for greatly increased security, file–by–file compression, quotas, and even encryption. It is the default file system for new installations of Windows XP, and if you're doing an upgrade from a previous version of Windows, you'll be asked if you want to convert your existing file systems to NTFS. Don't worry. If you've already upgraded to Windows XP and didn't do the conversion then, it's not a problem. You can convert FAT16 or FAT32 volumes to NTFS at any point. Just remember that you can't easily go back to FAT or FAT32 (without reformatting the drive or partition), not that I think you'll want to.

The NTFS file system is generally not compatible with other operating systems installed on the same computer, nor is it available when you've booted a computer from a floppy disk. For this reason, many system administrators, myself included, used to recommend that users format at least a small partition at the beginning of their main hard disk as FAT. This partition provided a place to store emergency recovery tools or special drivers needed for reinstallation, and was a mechanism for digging yourself out of the hole you'd just dug into. But with the enhanced recovery abilities built into Windows XP (more on that in a future column), I don't think it's necessary or desirable to create that initial FAT partition.

When to Use FAT or FAT32
If you're running more than one operating system on a single computer (see my earlier column Multibooting Made Easy), you will definitely need to format some of your volumes as FAT. Any programs or data that need to be accessed by more than one operating system on that computer should be stored on a FAT16 or possibly FAT32 volume. But keep in mind that you have no security for data on a FAT16 or FAT32 volume—any one with access to the computer can read, change, or even delete any file that is stored on a FAT16 or FAT32 partition. In many cases, this is even possible over a network. So do not store sensitive files on drives or partitions formatted with FAT file systems.

what is 16 bit MS DOS Subsystem

The 16 bit subsystem is what allows some older MS-DOS software to run in today's Windows NT and XP. It sets up a simulated MS-DOS environment, and many old applications can run fairly well. (This not to be confused with the Command Shell, which is a true 32 bit Windows application.)

But in this case it looks like some old 16 bit MS-DOS application is attempting to start when you log in. In fact, it's possible that the 16 bit debugging program debug.exe is being started.

If you had just installed some new software, I might suspect that as the cause. Especially if it was a new install of some old software package. However my assumption is that this isn't the case.

command.com and command.exe

you probably know, MS-DOS was the predecessor to Windows. It was character mode only, and you ran programs by typing their name at the command prompt. MS-DOS was created when 16 bit processors were becoming popular, and its widespread adoption is credited with kick starting the rise in popularity of the personal computer.

Then two things happened: Windows, and 32 bit processors. Fast forward to today, and MS-DOS has pretty much disappeared from the landscape - Windows, and its rich graphical interface, is everywhere. The same is true for the 16bit processor. Most all contemporary machines are built on various flavors of 32bit processors.

What does all that have to do with COMMAND.COM and CMD.EXE? It's quite simple really: CMD.EXE is a command line processor for 32bit Windows. Much like MS-DOS before it, it provides a character-mode only user interface into which you can type commands to run programs. CMD.EXE is a 32 bit program that is fully a part of Windows - in fact it's what gets run when you select Command Prompt on the Windows Accessories menu.

COMMAND.COM, on the other hand, exists only for compatibility and 16bit programs. It exists solely for those programs which have not been updated since the days of MS-DOS. It's designed to run 16bit applications, and operates just like the old MS-DOS did.

On the surface, they're very similar. Even though CMD.EXE was a complete re-write, it's based on the same concepts and similar syntax. But the differences become quickly apparent. Let's used your "CD" example from above.

In CMD.EXE, you can change to the "Program files" directory by doing this:

cd "\Program Files"
Note the quotes around the directory name. Try doing that in COMMAND.COM and you'll get this:

cd "\Program Files"
Parameter format not correct - "\program
The problem is COMMAND.COM doesn't know about long file names (filenames longer than 8.3) or filenames that have spaces in them, and it doesn't have a way to quote the name. So if you still need to, how do you CD to that directory in COMMAND.COM? Well, first you need to find out the alternate, 8.3 name of that directory ... its short name:

dir /x

Directory of C:\

08/21/2005 09:50 AM PROGRA~1 Program Files
(I've removed some of the lines of output for brevity.) The "/X" parameter to DIR tells it to include the "shortname" in the output. In this case that's "PROGRA~1", a machine generated alternative name for "PROGRAM FILES". Now we can CD to that in COMMAND.COM:

cd progra~1
dir

Volume in drive C is
Volume Serial Number is B026-62CA

Directory of C:\PROGRA~1

08/21/2005 09:50 AM .
08/21/2005 09:50 AM ..
03/24/2005 04:42 PM Adobe
...etc...
The bottom line is actually quite simple: use CMD.EXE unless you know you need COMMAND.COM for compatibility with some older 16bit program. And even then, if you try and run a 16 bit program in CMD.EXE, it will typically run it within COMMAND.COM for you anyway, so you still may not need to know or care.

And in case you're wondering, yes ... something similar is coming down the road as 64 bit processors begin to arrive. The 64bit version of Windows does, I believe, include another command processor, one for native 64bit command-line programs.

when does errors occur when USB2.0 devices installing in XP SP2

1. USB Mouse will rarely work after rebooting when SP2 is installed.
Unplug it & plug it back in. Unplug it & plug it back in again. (Repeat this procedure (x) number of times while at the same time applying random mouse clicks/deskslams until mouse works.

2. good operating Printer/Scanner combo (Dell) will not work when hooked up after SP2 is installed. Neither reinstalling drivers from CD, nor Downloading updated drivers or firmware from manufacturer, nor replacing cables,


"A USB device that is connected to a USB 2.0 hub is not detected in Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, or Windows Server 2003 x64 versions"

CAUSE: Microsoft Windows XP SP2 USB 2.0 driver causes an Enhanced Host Controller Interface (EHCI) specification violation.


MY OPINION (warning, I'm not a professional, but it worked)

SOLUTION: Since installing SP2 caused the problem, then revert necessary files back to the SP1 (working) version.

HOW:
After rebooting, the new hardware wizard will say it found new hardware. Normally, if you allowed it to automatically find the right files, it would take forever to search without finding the right files, and hardware will not be added. Instead, when new hardware wizard asks whether you want it to automatically search for files, don't let it. Do it manually.

Choose the device from the list then click 'have disk'. Browse to the folder on your C:\ where all drivers are stored (not sure if this folder is the same or exists on PCS other than Dell but my folder is c:\I386). First, The wizard finds the necessary USB Controllers (i.e., "USB Composite Device,” "USB Printing Support") but when continuing, it warns you that the files have not passed some logo test thing from MS . . . continue installing anyway.

IMPORTANT: Each device will have at least ONE missing file that it cannot find (i.e., usbccgp.sys, usbprint.sys). Do a search of your C:\ for this file name, and look at the detailed results for a folder having SP1 in the path. Point your Wizard to this folder for the requested file and VOILA! SUCCESS!

Once the USB controllers install a new (duplicate) device should show up (also with errors) in device manager. Follow the same steps to install drivers for these new devices and delete the original duplicate device from the list

CD-R drive or CD-RW drive is not recognized as a recordable device

CD-R drive or CD-RW drive is not recognized as a recordable device





Windows registry editing

Step 1: Back up the registry

Step 2: Edit the drive type value of the volume folder

Step 3: Verify that Windows recognizes the drive as a recordable device



When you try to burn data to a CD-R or a CD-RW, you do not have the option to send data to the CD drive.

When you view the properties of the CD-R drive or the CD-RW drive, you notice that the Recording tab is not displayed in the CD Drive (drive_letter:) Properties dialog box, where drive_letter is the letter of the CD-R drive or CD-RW drive.

Note To view the CD Drive (drive_letter:) Properties dialog box, click Start, click My Computer, right-click the CD drive that you want, and then click Properties.

Additionally, you may receive the following error message:
There is no disc in the drive. Please insert a writable CD into drive.
Back to the top

DUE TO :
This can occur when your computer incorrectly detects the drive as a non-recordable device.

Edit the Windows registry
To resolve this problem, try to edit the Windows registry so that the drive is identified as a recordable device.Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.
Note If the drive is not listed on the Windows Hardware Compatibility List , the drive may not work with your computer’s built-in CD-copying functionality, regardless of the registry setting.
The HCL is a list of computer hardware that is compatible with a particular operating system. To see whether your drive is included on the Windows HCL, visit the following Microsoft Web site:
http://www.microsoft.com/whdc/hcl/default.mspx (http://www.microsoft.com/whdc/hcl/default.mspx)
Step 1: Back up the registry
To back up the registry so that you can restore it if you have problems later, follow these steps:a. Click Start, and then click Run.
b. In the Open box, type regedit, and then click OK.
c. Click to open the following folder:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CD Burning\Drives
d. On the File menu, click Export.
e. In the File name box, type backup of drives key, note the location where you are saving the file, and then click Save.

Note If you have problems later, you can restore this registry subkey by double-clicking the backup of drives key.reg file that you saved.

Step 2: Edit the drive type value of the volume folder
To edit the drive type so that Windows recognizes the drive as recordable, follow these steps:a. In the navigation pane of the Registry Editor window, click the Volume{GUID} folder under Drives, where GUID is a 32-character identifier.

Note If your computer has more than one CD drive, an additional Volume{GUID} folder is listed for each drive.
b. In the right side of the Registry Editor window, double-click Drive Type.
c. In the Value data box, type 1 if the drive is a CD-R drive or 2 if it is a CD-RW drive.
d. Click OK, and then close Registry Editor.

Step 3: Verify that Windows recognizes the drive as a recordable device
To see whether Windows recognizes the drive as a recordable device now, follow these steps:a. Click Start, and then click My Computer.
b. Under Devices with Removable Storage, right-click the CD-R drive or CD-RW drive, and then click Properties.
c. If the Recording tab is displayed, Windows recognizes the drive as a recordable device.
d. Click Cancel.
If Windows recognizes the drive as a recordable device, you should be able to burn data to a CD now. If you still have problems, follow the steps in the "Troubleshooting" section.
Back to the top

Troubleshooting
If your computer has more than one CD or DVD drive and the Recording tab is not displayed in the Properties dialog box (see step 3 in the "Edit the Windows registry" section), a drive may be configured incorrectly as "recordable" in the Windows registry. To resolve this problem, try changing the drive type of the drive you previously identified as a 1 or 2 to a type 3. Then change the drive type of the other drive to a 1 or 2. To try this, follow these steps:1. Follow step 2 in the "Edit the Windows registry" section to edit the Drive Type value of the Volume{GUID} folder whose value that you previously changed.
2. In the Value data box, type 3, and then click OK.

The drive type value of 3 indicates that the drive is a standard CD-ROM and is not a recordable drive.
3. In the navigation pane of the Registry Editor window, click the next Volume{GUID} folder.
4. Follow step 2 in the "Edit the Windows registry" section to change the Value data entry to 1 or 2, depending on the drive type.
5. Follow step 3 in the "Edit the Windows registry" section to confirm that the Recording tab is displayed in the Properties dialog box of the CD drive.
If the Recording tab is now displayed in the Properties dialog box, you should be able to burn data to a CD. If you still have problems, see the "Next steps" section.




This procedure may not work in all cases. This is only a workaround in a situation where the CD-R drive or CD-RW drive is capable of functioning in Windows XP and for some reason has been misidentified. If the drive is not on the Hardware Compatibility List (HCL), the drive may not work with the built-in CD copying functionality, regardless of this registry setting.
Back to the top