|"I'm in Madrid Spain...."|
Where are you from originally ?
There are zero gum trees outdoors in Canada as far as I know.
"memory 3327 MB CPU intel dual core 2.66GHz."
Those are certainly not performance limiting, even if you are using onboard video.
If you have 4gb of ram installed, you will probably be better off if you can install 3gb instead.
All versions of XP except XP Pro 64 bit are 32 bit operating systems.
The 4gb virtual memory address limit for 32 bit operating systems.
An example of 3gb working better than 4gb in a 32 bit operating system.
See Response 6:
A better explanation I've seen.
If you have a 32 bit operating system and you have installed 4gb in the mboard, the amount of that ram available to Windows and the user is
4gb minus the amount of ram your devices require or have.
- minus the amount of ram shared with onboard video if you're using that
- and/or - minus the amount of ram your dedicated video card installed in a slot has.
If you have more than one video card installed in a slot,it would be minus the ram for all of them.
(and = Some mboard main chipsets have Hybrid video capability. If you have a PCI-E X16 video card installed in a mboard slot that is supported by that feature, it's often the default for both the onboard video and the video on the card to work at the same time, unless you change default bios Setup settings. In that case it would be minus the ram for both of them.)
- minus the amount of ram your sound adapter has, if that applies - e.g. sound cards installed in a mboard slot often have ram
- minus the amount of ram any other devices have,other than hard drives and optical drives,if that applies.
What percentage of the partition Windows is booting from (the drive letter of the one the Windows folder was installed on) is free space ?
"I have three HDs, C 500GB, D 80GB and an external backup K Iomega 2TB"
"This maybe useless information but I rembered after the last serious virus attack a reinstall was needed, and curiously
It installed windows on the D disk. I didn't twig that this was so because all was working normally, albeit the 80GB is older and slower.
Eventually I installed XP again , this time on the C disk ."
I NEVER install Windows from scratch unless I can't figure out how to get rid of the malware (most malware these days is NOT a virus).
It's usually very short sighted, or even DUMB, to install Windows from scratch if you don't need to - it takes less than an hour to run Setup, but that's only the FIRST step.It may take the equivalent in hours to DAYS to get your Windows installation and the personal data and programs you want to use back on the computer. Many people lose ALL their personal data that was on the partition Windows was on, unless they have copied the personal data on it they do not want to lose to elsewhere BEFORE they ran Setup. (If the hard drive itself is okay, you can do that even if Windows will not work normally, e.g. by booting the computer from a Linux CD.)
I always try to get rid of the malware FIRST, without doing that - if I don't know how toget rid of the particular malware , the info about and/or the specific program or programs I need that can do it is almost always easily found on the web.
However, the average person may not know enough or want to put in the time it might take to do that (or they're just impatient). They often spend MORE time getting their Windows installation back to where they want it to be.
All drive letters that are assigned in Windows, or in any operating system, are for logical drives, but the term logical is usually ommited when referring to them.
You can't treat the logical drive letter a physical drive has been assigned the same way as one for a partion on a drive unless the physical drive has only one partition.
The drive letters assigned to drive partitions (or any drive assigned C-Z) are not "written in stone".
You can change any drive letter that was assigned in Disk Management to any free (available) drive letter that's available, EXCEPT that you can't change the drive letter of the partition Windows isbooting from.
XP doesn't necessary assign C to the partition Windows was installed on.
XP's (and 2000's) Setup assigns the drive letter for the partition Windows itself is installed on according to whether or not Setup detects that one or more drive letters have already been assigned by 2000 and up to one or more drive partitions of (a) hard drive(s) Setupdetects when Setupis run.
If Setup detects no other partitions that have already been assigned drive letters,it uses C for the partition Windows is installed on.
If Setup DOES detect other drive partitions that have already been assigned drive letters,it uses the first free (available) drive letter alphabetically, NOT C, for the partition Windows is installed on.
If there ARE other drive partitions on hard drives that have already been assigned drive letters,BEFORE running Setup,if you disconnect all hard drives but the one you want to install Windows on, or if you use what is generically called a "partition manipulation" program to HIDE all other partitions on the same drive if it has more than one partition on it,then Setup will assign C to the partition Windows is installed on.
E.g. If you have two or more hard drives, and if it least one other hard drive has a partition Setup would detect as having already been assigned one or more drive letters, if the drive you want to install Windows on has only one partition,if you disconnect all other hard drives,then Setup will assign C to the partition Windows is installed on.
Also,the drive letter Setup assigns to the partition Windows is installed on can depend on how the drive is connected to the mboard, or it's jumper setting if it's IDE, or on what other devices are detected by Setup.
I recently installed XP Pro from scratch on a hard drive that was the only hard drive connected when Setup was run. It was connected to the Primary IDE header, jumpered Slave, there was another drive on the same data cable, an optical (CD-RW) drive jumpered Master. The desktop case has a memory card reader that connects via one USB cable to a header on the mboard - four drive letters were assigned to it previously in Windows - one for each type or group of card types it could read.
When Setup was finished....
C, D, E, and F were assigned to the card reader.
G was assigned to the CD-RW drive.
H was assigned to the hard drive partition Windows was installed on.
I could have used Disk Management to change all those drive letter assignments EXCEPT the H for the hard drive partition Windows was installed on. (If a logical drive is using a drive letter you want to use for something else, you can change it's drive letter to any other free drive letter to free up that drive letter.)
I changed the drive jumper settings so the hard drive was Master,the CD-RW Slave, and unplugged the USB cable to the memory card reader,then I booted from the CD, deleted the existing data on the hard drive partition Windows had been installed in, and ran Setup again.
When Setup was finished....
C was assigned to the hard drive partition Windows was installed on.
D was assigned to the CD-RW drive
When I plugged in the USB cable to the card reader, it was assigned E, F, G, and H.
( I probably could have left the card reader plugged in while running Setup -the result would probably have been....
When Setup was finished....
C was assigned to the hard drive partition Windows was installed on.
D, E, F,and G was assigned to the card reader.
H was assigned to the CD-RW drive.
The drive letters for external drives, optical drives, and flash drives are normally assigned last, if they're all connected at the same time asthe hard drive(s). Windows retains whatever drive letter drive was assigned unless it has been unplugged and then Windxowswas booted without it being connected.)
"At switch on, windows loads the bios then stops for a couple of seconds to ask do I want to use the C or D xp. If I don't touch any key, the program script selects the C disk XP..
I was curious then and I have tried chosing the D xp installation. But it gives a message, missing XP files. Meaning that when I got XP reinstalled on the C disk and removed the XP windows on the D disk what remains were left .
Meaning of this? Using explorer, the D disk contains no XP files."
If XP's Setup detects an existing 2000 or up Windows installation on a hard drive partition, and if you DO NOT choose that partition to install Windows on from scratch (delete it's data or delete it's partition and make a new one),the the multiboot feature has been enabled after Setup has run and you have a choice of two or more Windows installations to boot from when you boot the computer.
Only one partition on all the hard drives connected to the computer can be made "Active" (bootable) at any one time - the 2000 and up multiboot menu allows you to choose which one. If you don't press any keys to select a Windows installation within xx (15 ?) seconds,the Windows installation last made, the top one, loads first by default.
If all the other Windows installations were working fine before you ran Setup,than you can choose any of them and it will work.
Removing the files you can see in Windows on an existing Windows installation does not remove the data that makes Setup detect it as bootable - you have to use Setup to delete the data on that partition before you actually run Setup itself.
If one or more selections of the multiboot menu do not work, you can
edit Boot.ini and delete the one that doesn't work.
If that results in there being only one Windows installation listed in Boot.ini, then you will not see the multiboot menu when you boot the computer anymore.
In your case...
Control Panel - System - Advanced - Startup and Recovery - Edit - you MUST maximize the window - delete the entire line(s) below the first line below [operating systems].
(The first line below [operating systems] is for the first operating choice when you boot)
Another thing that drastically affect Window's speed.
Whenever you load Windows from a regular Windows CD (or DVD) from scratch, after Setup is finished you must load the drivers for the mboard, particularly the main chipset drivers, in order for Windows to have the proper drivers for and information about your mboard hardware, including it's AGP or PCI-E, ACPI, USB 2.0 if it has it, and hard drive controller support. If you have a generic system and have the CD that came with the mboard, all the necessary drivers are on it. If you load drivers from the web, brand name system builders and mboard makers often DO NOT have the main chipset drivers listed in the downloads for your model - in that case you must go to the maker of the main chipset's web site, get the drivers, and load them.
If the main chipset drivers have NOT been installed, at the very least...
- the Windows support for your USB 2.0 controllers will probably NOT be loaded
- your hard and optical drives will probably NOT be running in Windows as fast as they are capable of.
By the way..... the XP CDs have no built in SATA controller drivers.
They cannot recognize SATA drives by default (unless you load the needed drivers - see below a bit) unless the SATA controller mode in the bios Setup has been set to an IDE compatible mode of some sort.
In my experience, the bios of new and fairly recent mboards often have that SATA controller mode set to an IDE compatible mode of some sort by default, so that you don't have to fuss with having to load SATA controller drivers from a floppy disk in a conventional floppy drive after pressing F6 at the beginning of Setup.
If you want SATA drives to be able to achieve it's faster than the max 133mb/sec IDE max burst data transfer speed, the SATA controller drivers your mboard needs must be loaded in Windows,and .the bios must have the SATA controllers in SATA or AHCI mode.
If your bios still has the SATA controllers in an IDE compatble mode , the difference in perceived speed of the 80gb vs.the 500gb one if it's SATA is
- the 80gb drive, if its IDE, it may have a max burst speed of 100mb/sec, not 133mb/sec
- if both drives are SATA, both have a max burst speed in IDE compatible mode of 133mb/sec, but the 500gb drive has a larger onboard ram cache
When the bios has the drives in SATA or AHCI mode, the 80gb drive may have a 150mbyte/sec max burst speed , the 500gb drive 300mbyte/sec .
NOTE that new desktop SATA drives may have a tiny jumper installed on them that limits them to the 150mbyte/sec max burst speed. You must remove that jumper in order for the drive to have a 300gbyte/sec max burst speed in SATA or AHCI mode.
E.g. I have bought 3 new desktop Seagate 500gb SATA drives in the last two years or so and they all had that jumper installed.