Let's demand some fixes from Mico$oft!!!
I have prepared a list of bugs with the Win2K O/S which I will be sending
to MS again and again until I get some action. Please feel free to contribute to the list.
Include your Win98 and Win ME bugs etc. too!
Here's what I've got so far:
------------------------------------------------------------------------------------
The following applies in particular to the Windows 2000 O/S
What was Service Pack 1 for???
All of the same bugs are still here!
I have been able to reproduce all of the following faults in all conditions
of use, including immediately after a fresh install on a newly
partitioned and formatted drive (to eliminate the possibility of a
virus causing any of the problems). These are genuine problems with
the Windows operating system and, considering the price of the
software, among other things, they need to be rectified and the
changes made available as a free service pack to consumers ASAP.
I have observed these same problems, year in, year out, from version
to version, never being dealt with. Surely, I am not the only one
to notice these obvious flaws.
1.
The priority of the processes is all up the whop when carrying out
commands/actions in the GUI. eg. Click on a hyperlink in IE and wait,
sometimes 5 seconds to hear the click sound. You don't know if it got
the message or not so you keep clicking. The sound effect should be
processed first; problems with dialog windows when installing drivers.
These windows often "hang" for periods, without letting the user know
what the system is doing. It is easy to think that the system has
locked up, when in actual fact it has not.
This kind of thing is a common theme in Windows, and is a problem that
should never have been allowed to happen. It's a simple matter of
changing the order of the processes, i.e. update the display BEFORE
updating the system files/registry etc. instead of the other way around.
2.
Removing programs from the Add/Remove Programs window.
When removing a program which does not come with an uninstall exe file,
upon clicking the Add/Remove button, the window locks up until the
process has completed. So, once again, one keeps clicking, thinking
that it didn't get the message and inadvertently deletes other programs
as well because when the window comes back to life, the next program
on the list lines up with the mouse pointer and the clicks which are
stored in the buffer are carried out. Duh! Just a simple message box
to confirm that "Yes I got that and am currently removing the requested
program..." would be obvious, wouldn't it?
3.
When making a dialup connection, one clicks the connect button and the system locks for a moment, to the point where even the mouse pointer
will not move. The modem seems to be the only thing that can actually
stop the mouse in its tracks. This is just a pain in the butt!
4.
After removing a CD-ROM, the shortcut icon in the task bar does not
always change back to the standard icon for a CD-ROM drive, making one think that there is still a CD in the drive. Also when changing CDs,
the icon is often not updated to the icon of the new CD.
5.
Clock display incorrect
This one is still uncertain. It seems to take some time for the clock to
update after the computer has been in screen-saver mode. Even on double clicking the time display to bring up the Date/Time Properties window, the time is still wrong. To date I have not been able to determine when it corrects itself, but it does, eventually.
6.
Opening My Computer when there is a CD-ROM in the drive.
After inserting a CD-ROM and then opening the My Computer folder, the window locks and will not display anything or accept any input (such as an attempt to close it) until it has spun the CD drive up and got the table of contents.
That should be done on a separate thread so that the known contents can be displayed first and the window can be closed if required. This is because often one is going into My Computer to open a hard-drive or floppy drive, but just happens to have a CD in the CD drive not being used. But we still have to go through that "locking up" experience while the system checks the CD drive which is not even being used. I would suggest that checking the CD drive be done on a separate thread and in the case where the user immediately opens another drive, that the CD check operation be canceled. This is also a major problem when saving documents. When clicking on the drop down combo box to select a drive/folder so save to, it will not drop down until the CD drive has been spun up. As if you could save directly to a CD from there!
This is also a problem when there is a floppy present, although not as severe.
7.
Emptying the Recycle Bin.
Why does it take so long to empty the recycle bin?!?! Just one file takes about 3 - 4 seconds!!! The mouse pointer changes to an hour glass and one can't do anything else until it's done. I use VB which is a slow language, but the Kill command will delete a file instantly without hanging up the system, and that is a command that has to go through a chain of I don't know how many interpreters before it gets to the system. So what's up with the Recycle Bin? Come on!!!!! Sort it out!!!!
8.
Opening Network Neighborhood
Once again, a lockup problem. While the system is searching for computers on the network, the Network Neighborhood folder is locked. It can't be minimized or closed or moved or otherwise until the search is finished. This only happens when something has changed on the network of course, but it is still, nevertheless, an unacceptable problem.
Re: Let's demand some fixes from Mico$oft!!!
If Micro$oft offered $100 per person for every new bug reported... we would all be Millionares by now... ;)
