inconnu1405241515

Honestly I don't know, but usually I tend to think just anything is possible in troubleshooting. If the symptom was only reproduced in normal mode of Windows operation, such has to be doubted too. Missing or corrupt system file can be a problem; this type of accident was fairly common (resulting in random unstableness, not necessarily a floppy drive error) in the Windows 9x age, simply because the system crashed a lot more often than in Windows 2000/XP. As you have tried with safe mode and also booting from diskette, that possibility would be crossed out. You may want to try some CD bootable type of Linux to triple check that the software/OS isn't the cause.

You can open a case for having killed your pet by putting it into a washing machine in trying to clean it; or having damaged your multi hundred thousand dollars suit by using your hair dryer to dry it.The bottom line of the story is that, in many regions of the world, one has the right to file a suit against anything but he is not guaranteed to win over the case.

It appears to me that you have already checked everything you should do.You changed the hardware part; the drive and the cable to the ones that you know should work and they didn't.You tried the operation in normal Windows mode of safe mode and booting (to some basic DOS, as I imagine) without success.The only thing remaining I can think of is, which was a case for me in the past, the physical placement - installation of the drive:when placed in the chasis, the drive might be under abnormal physical pressure, from the top or from the side, as an example, in a way that the head cannot align and/or move correctly to read the diskette. The cause in this case could be like the chasis has been damaged or bent somehow. In some cases the bend can be so small that you won't easily notice by looking at it.If you have tried working with the replaced drive connected to the PC but bare, i.e. not screwed into the chasis, this isn't your problem.In that case, I guess you will have to conclude to the motherboard's floppy I/F being faulty.

Talented indeed are those people who makes up these jokes; they are so good at entertaining others with stories that does not even have to be true.

I hope you have already raised a complaint against the store that has done the maintenence, repair or upgrade work and recovered from that situation, because that's certainly not a problem you should encounter when you have paid for a genuine copy.

A popular example could be like hosting a web server at home. Another example can be to build a file server.Those will mean part of your home network is going to be exposed to the internet in a wider way than not having any server, so be sure to take necessary precautions in terms of security if you do choose to do so.

Good grief, this is funny.Heard of many Microsoft humours in the past, but this one is for sure the most difficult one (at least for me) to reproduce and tell it to another person live.

I guess Marilyn Monroe's dying message with her phone handset in her hands was that sooner or later mankind is to be born with cell phones.Here in my country, over 95% of high school students (typically ages 16-18), and 60%+ of junior high's (ages 13-15) are cell phone owners. Cell phone operators are starting extremely heavy campaigns to lock in low grade elementary school kids (ages 7 to 9) and aged people over 60-65, since these are the bands with least posession rates. (One third [1/3] of the latter half of elementary school kids at ages 10-12 already have theri own.)Me? Well, I guess I belong to some generation completely forgotton by those phone operators --- like it or not, you're going to be obligated to carry one 100% on, all the time. Wish the airpline companies will do away with their in-flight phones and internet services.... they used to be the only place you are peace in quiet.

Heat can cause erroneous behaviour of electronics. You may be right with your intuition about the heat radiator --- was it very hot? Graphic cards are pretty vulnerable to heat, as you know. It may have been prevented to operate correctly, thus sometimes stopping at bluescreen and not further booting, or displaying in crazy colors. Other cause could be like loose connection/insertion of the video card into the PCI/AGP slot. It is also possible that it has been corrected when you have changed the graphic card to another one and changed it back.Otherwise, a worst case scenario is like the motherboard is about to fail.Scan (with your eyeballs, i mean) over the motherboard and see if there isn't any condensor starting to blow out browny electrolytic solution liquid.

There may be multiple points in your problem: 1) Are you using a so-called dynamic DNS service? Is your domain name "yourwebserver.com"? 2) When you say you want to access your web server with FQDN, do you mean you are trying to access the server like "http://www.yourwebserver.com/;? If yes, does your DDNS service support wildcard first of all? What do you mean by "real ip"? Are you trying to access the web server from Computer A, which is inside your LAN? What do you see when you try to access your web server from Computer A? Isn't it the web setup screen. Many routers, including Buffalo's do not allow you to access a LAN server from another LAN client using global IP.

Thank you for bringing this thread up....Reminds me of my good old days, visting this place.

You may find some clue from this thread: Need Help On Remote Access...

What is the virtue of publishing this report, from Microsoft's view?It would have been much more interesting to analyze that point than to be blinded by the fact that, in some benchmarks, Windows scores less. Read the whole document, as the original poster suggests, and think over.

By design and nature of the repeater product, you will suffer from speed down by roughly half.

Hello, I do not see why a Power User account should be prevented from connecting to the network --- just experimented with my XP Pro wireless mobile PC, creating a Power User account and it has no problem. It's true a Power User account cannot change network settings, but once you make a successful connection configuration with an Administrator account, the Power User account should simply inherit it. Maybe we need a couple of troubleshooting, to narrow down the possible cause. Using this PC, can you possibly try the followings maybe? 1. connect to LAN with a LAN cable, and see if problem exists with the Power User account. 2. move the PC closer to the wireless router, and see if the problem still reproduces. 3. change the USB wireless adaptor to any other wireless adaptor (preferably not a USB one), and see if that changes anything. And two questions: 1. Is the Power User virtually "losing" connection that is once established, without any reboots and/or PC power off/on? Or is it that a Power User cannot connect to the LAN first of all, after start up? 2. Have you assigned a static IP to the PC, or is it configured to obtain it from the DHCP? I am in little doubt if your problem is maybe related to the USB wireless adaptor + Windows XP problem: When you restart your Windows XP-based computer, you cannot connect to your wireless network