Damn Windoze Update!!!
-
Just to add to the inscrutable here, I've got one machine that will not load Windows. I can't find anything wrong with it, but every time I install Windows it boots to a garbled screen and reports the Registry as corrupted. Yet I can install and run Linux on it without any trouble at all, even though the Linux installer reports that it doesn't have enough RAM to complete the installation! The gremlins are in the neighborhood...
I have a computer that FreeBSD doesn't support multiple processors on. However, with Windows it works just fine. :( Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
-
Well, after 5 reboots it seems to be working again. Honestly how often does it actually give you problems. This is the second time Windows Update has misbehaved. About once a month I get some strange behavior. When I first installed XP it would never boot the first time. I had to boot once, it would fail, then I'd reboot from safe mode and it would be fine. That seemed to fix itself automagically after about 3 months. Last month I was getting BSODs every other day saying that some memory couldn't be accessed, it was dumping physical memory and the system would crash. Mind you it would do this when nothing was running and when nobody was around. That too seems to have automagically fixed itself. To balance the scales I once crashed a Linux system and it never booted again because it took out the hard drive with it. The only time I crashed linux it was my own fault. I was hacking away at the kernel like an idiot and screwed up everything. I dont blame the OS for that. Anyways, all's well in compuville now so I'm happy. Josh Knox that-guy.net
Um, ever consider your hardware might be bad or you are using some crappy hardware with bad drivers? My brother use to bitch all the time about NT always f'ing up and BSOD on him. When I asked him what hardware he was using, he mentioned he had some $19 tape drive that used the floppy. After I had him uninstall that garbage, NT never BSOD on him again. Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
-
Um, ever consider your hardware might be bad or you are using some crappy hardware with bad drivers? My brother use to bitch all the time about NT always f'ing up and BSOD on him. When I asked him what hardware he was using, he mentioned he had some $19 tape drive that used the floppy. After I had him uninstall that garbage, NT never BSOD on him again. Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
Um, ever consider your hardware might be bad or you are using some crappy hardware with bad drivers? Yup, I had considered that but, while my system isn't the latest and greatest, I wouldn't call any of my hardware crappy, and all the drivers are up to date. Seems to be better now though... Josh Knox that-guy.net
-
Thanks to the latest windows update, WindowsXP now refuses to boot. After prompting me to select a user(which it never asked me to do before. I'm the only user) the computer reboots itself. Windows refuses to load. Nice F'n Update!!! :mad: :mad: :mad: Once again, Linux saves the day. Without it I'd have a useless system, since Windows regularly pulls shit like this on me. Power to the Penguins!!! ARRRRRGGGGGHHHH!!!! Josh Knox that-guy.net
After the last update, Windows Messager will not run for me at all. Crashes immediately when it is run. :(( 'course, i've got the box crammed full of cheap, flakey hardware, so i'm kinda used to it now. :) --------
This is what we've waited for This is it boys, this is War!
--Shog9 --
-
Thanks to the latest windows update, WindowsXP now refuses to boot. After prompting me to select a user(which it never asked me to do before. I'm the only user) the computer reboots itself. Windows refuses to load. Nice F'n Update!!! :mad: :mad: :mad: Once again, Linux saves the day. Without it I'd have a useless system, since Windows regularly pulls shit like this on me. Power to the Penguins!!! ARRRRRGGGGGHHHH!!!! Josh Knox that-guy.net
Everyone knows I'm not a huge fan of MS.. but when you stoop to name calling, you mark yourself as a child. In technical terms, "Windoze" flips the bozo bit :')
-
Everyone knows I'm not a huge fan of MS.. but when you stoop to name calling, you mark yourself as a child. In technical terms, "Windoze" flips the bozo bit :')
Jim A. Johnson wrote: but when you stoop to name calling, you mark yourself as a child. So, from your statement am I to assume that you are a child? ;P Jim A. Johnson wrote: Everyone knows I'm not a huge fan of MS Yet you jump to righteously defend them? Hmmm, a closet Windows lover... :laugh: Josh Knox that-guy.net
-
Thanks to the latest windows update, WindowsXP now refuses to boot. After prompting me to select a user(which it never asked me to do before. I'm the only user) the computer reboots itself. Windows refuses to load. Nice F'n Update!!! :mad: :mad: :mad: Once again, Linux saves the day. Without it I'd have a useless system, since Windows regularly pulls shit like this on me. Power to the Penguins!!! ARRRRRGGGGGHHHH!!!! Josh Knox that-guy.net
I guess I got lucky. Finally decided to bite the bullet and install XP on one of my boxes. Froze up the machine about half a dozen times during the initial stages of the installation. Took the CD put it back in the box and tossed it in the closet. Just don't have the time to deal with yet more buggy MS software. Hell, I barely have the time to deal with my own bugs :) Cheers, Tom Archer Author - Inside C#, Visual C++.NET Bible
-
I guess I got lucky. Finally decided to bite the bullet and install XP on one of my boxes. Froze up the machine about half a dozen times during the initial stages of the installation. Took the CD put it back in the box and tossed it in the closet. Just don't have the time to deal with yet more buggy MS software. Hell, I barely have the time to deal with my own bugs :) Cheers, Tom Archer Author - Inside C#, Visual C++.NET Bible
interestingly enough I had the same problem when installing XP. It stopped half way through the upgrade process several times. By this time I was cursing but gave it one more try and it actually installed - much to my relief. Michael :-)
-
Thanks to the latest windows update, WindowsXP now refuses to boot. After prompting me to select a user(which it never asked me to do before. I'm the only user) the computer reboots itself. Windows refuses to load. Nice F'n Update!!! :mad: :mad: :mad: Once again, Linux saves the day. Without it I'd have a useless system, since Windows regularly pulls shit like this on me. Power to the Penguins!!! ARRRRRGGGGGHHHH!!!! Josh Knox that-guy.net
Yes, that friggin windows update seems to have gone crazy lately. At home, W2k, it doesnt work at all, just keeps popping up everytime but there is nothing new to update. At work, XP, it pops up as it should, but when i click 'start download', nothing happens. It been like this for some time now.
-
Thanks to the latest windows update, WindowsXP now refuses to boot. After prompting me to select a user(which it never asked me to do before. I'm the only user) the computer reboots itself. Windows refuses to load. Nice F'n Update!!! :mad: :mad: :mad: Once again, Linux saves the day. Without it I'd have a useless system, since Windows regularly pulls shit like this on me. Power to the Penguins!!! ARRRRRGGGGGHHHH!!!! Josh Knox that-guy.net
Just curious as to what type of stytem are you using. If you were having install problems it doesn't suprise me that you may continue to get unexpected behavior. I have heard that there are some problems with AMD processors and/or chipsets for AMD that cause XP to "misbehave". I have a AMD w/ VIA chipset mobo that I can't even get XP to install on, but my P4 Supermicro board installs just find. In the 8 years that I have been using NT based Windows (3.51) I have only seen about 10 BSOD, a few were caused by me (disconnecting the SCSI chain on a non-active board) and various video card BSOD. This is with having 4 PCs at work and about 7 at home all running NT/2000/XP. The only system that I have the most problem getting XP/2000 to run on is the AMD/VIA/SOHO mobo combo. The other systems are Supermicro or Compaq Prolients systems and almost never have problems with them, but I also make sure I buy ECC memory too. Terry
-
Just to add to the inscrutable here, I've got one machine that will not load Windows. I can't find anything wrong with it, but every time I install Windows it boots to a garbled screen and reports the Registry as corrupted. Yet I can install and run Linux on it without any trouble at all, even though the Linux installer reports that it doesn't have enough RAM to complete the installation! The gremlins are in the neighborhood...
I suspect memory. On a windows 98 machine I had 128 megs PC100 memory. I tried to add 2 256 megs PC133 memory. It said it was PC100 compatible. Anyways I ran into that message. There is a knowlege base article saying Windows 98 maxs out at 512. So I took out the 128. Still same problem. So I figured I pushing the limits. So I took out one of the 256's and added back the 128. Same problem. Someone told me you can't mix PC100 and PC133. So I took out the 128. The problem showed up maybe 1 out of 10 bootups. So I went back to my origional 128. X| I have heard people here talking about building their own systems. I only tried to add some memory and ended up with a nightmare. No thanks! That's not for me, too many variables. I love my prebuilt, just go in the store and pick it out Compaq. :) Cathy Life's uncertain, have dessert first!
-
I suspect memory. On a windows 98 machine I had 128 megs PC100 memory. I tried to add 2 256 megs PC133 memory. It said it was PC100 compatible. Anyways I ran into that message. There is a knowlege base article saying Windows 98 maxs out at 512. So I took out the 128. Still same problem. So I figured I pushing the limits. So I took out one of the 256's and added back the 128. Same problem. Someone told me you can't mix PC100 and PC133. So I took out the 128. The problem showed up maybe 1 out of 10 bootups. So I went back to my origional 128. X| I have heard people here talking about building their own systems. I only tried to add some memory and ended up with a nightmare. No thanks! That's not for me, too many variables. I love my prebuilt, just go in the store and pick it out Compaq. :) Cathy Life's uncertain, have dessert first!
Cathy wrote: I have heard people here talking about building their own systems. I always build my own systems. That way I know what's in them. You appear to have an older BIOS which doesn't know how to test the memory correctly. In that situation, you have to boot to setup, then tell it how much RAM you have. If what the BIOS reports disagrees with what the OS finds, there's going to be a conflict. You can mix PC100 with PC133 chips; you know from your industry that they're the same chips, just tested to a different standard. Check with your MB manufacturer to see if there's a BIOS update available.
-
Cathy wrote: I have heard people here talking about building their own systems. I always build my own systems. That way I know what's in them. You appear to have an older BIOS which doesn't know how to test the memory correctly. In that situation, you have to boot to setup, then tell it how much RAM you have. If what the BIOS reports disagrees with what the OS finds, there's going to be a conflict. You can mix PC100 with PC133 chips; you know from your industry that they're the same chips, just tested to a different standard. Check with your MB manufacturer to see if there's a BIOS update available.
Roger Wright wrote: You appear to have an older BIOS which doesn't know how to test the memory correctly The bios found it. Windows found it. It just kept giving that registry corrupted message. There is a knowledge base article about it. It means a problem with memory. Cathy Life's uncertain, have dessert first!
-
Roger Wright wrote: You appear to have an older BIOS which doesn't know how to test the memory correctly The bios found it. Windows found it. It just kept giving that registry corrupted message. There is a knowledge base article about it. It means a problem with memory. Cathy Life's uncertain, have dessert first!
I missed the bit about being a Compaq. Sorry. They do things their own way, and are very picky about RAM. Microns are that way, too, as are HPs. For future reference, though, I'd like to know the KB article number!
-
I missed the bit about being a Compaq. Sorry. They do things their own way, and are very picky about RAM. Microns are that way, too, as are HPs. For future reference, though, I'd like to know the KB article number!
Roger Wright wrote: For future reference, though, I'd like to know the KB article number! Q186909 Q253912 One of the guys at my work tried this and had nothing but trouble. So I didn't go there. Roger Wright wrote: I missed the bit about being a Compaq. The new problem free one is a Compaq. The old one was built by some computer store. You know the kind where you go in and tell them what kind of system you want and they build one for you. It was 500 mhz Pentium III. My company didn't have any money to update our systems. My work computer was a 200 mhz Pentium I. So I had basically donated my computer to work. They did a lot for me too. Anyways I really wanted to buy a new home computer because the only one I had at home was my son's 233 Pentium I. I had just bought a new digital camera and wanted to play with the photo editing software but it couldn't handle it. Anyways so I was trying to justify this little expenditure when one of the tech support guys said our software wasn't running correctly on WinXP. So I thought well if I went out and bought my new home computer I could test it out on that. Well it was an emergency right? ;) ;) Anyways I didn't have the patience to wait for them to build me a machine. So I went to Comp USA and grabbed one off the shelf. I know, I know my brother is fussing at me telling me they use the cheapest parts they can find. He told me not to run any games that use the graphics accelerator card or it will melt some parts. So I left the new machine at work for two days while we debugged it. I was afraid that if I left it there for longer it I would never get to take it home. It turns out there is a difference in the ends of lines in binary files in WinXP. I don't really know. It wasn't my code. It was my boss'. Cathy Life's uncertain, have dessert first!