Start your own community news site
Home  |  FAQ  |  About  |  Contact  |  View Source   
 
SEARCH:
 
BROWSE:
    My Hood
Edit My Info
View Events
Read Tutorials
Training Modules
View Presentations
Download Tools
Scan News
Get Jobs
Message Forums
School Forums
Member Directory
   
CONTRIBUTE:
    Sign me up!
Post an Event
Submit Tutorials
Upload Tools
Link News
Post Jobs
   
   
Home >  Messages >  Windows XP >  Xp is truely a MS product
Add to MyHood

Author
Subject:  Xp is truely a MS product  

Subscribe to this thread

wayne  skeens
skeensw@purdue.edu
11/2/2001 4:32:50 PM Not rated

I finally had my first big crash. :D
I was closing a file info window on a wimamp playlist, and as soon as I hit the X, it died. And it was dead as a doornail. CTRL - ALT - DEL did nothing, neither did ALT - TAB, or ESC, CTRL - C, or any other way to get out of a program. I let it sit for a few minutes, but it wasnt able to pull out of it.
I was getting worried that MS had made too stable of an OS. It took 5 minutes on reboot for it to stop grinding on the hard drive (K6-3 360 229 ram). Now I just need to blue screen it.
I have had a few explorer crashes in the last few weeks. I was getting worried that this might be as good as my install of 2K that went 82 days w/o a reboot.
This is comming from the man who blue screned NT4 setup. :p

Wayne


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Steven  Moon
svm5@hotmail.com
11/2/2001 8:40:57 PM Not rated

Makes me want to go out and buy XP. :)



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Robert  Wlodarczyk
Robert.Wlodarczyk@stonybrook.edu
11/2/2001 9:33:00 PM Not rated

Hmm... you sure it wasn't a WinAmp problem when it's installed under XP? I've been running Windows XP since the early beta stage of beta 2, and never once have I seen it blue screen. Personally, most problems or blue screens in Windows are caused by either bad third party applications or simply bad drivers. That's been my experience.


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Adam  Azarchs
admeralthrawn@hotmail.com
11/3/2001 2:07:42 AM Not rated

A few 3rd-party programs do wierd things in XP, but XP is supposed to insulate the rest of the system, so even if one program does something stupid and screws up it shouldn't crash the whole system.
I find this quite odd, since I havn't had anything crash since I got XP a week or so ago, except one of my own programs I was working, but that was why I was working on it. And it didn't really crash the whole system.



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Robert  Wlodarczyk
Robert.Wlodarczyk@stonybrook.edu
11/3/2001 11:13:19 AM Not rated

Did you try running WinAMP in compatibility mode (say for W2K or NT 4)?


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Chris  Mitchell
cmmtchll@msn.com
11/3/2001 3:49:28 PM Not rated

I've never seen a blue screen in WinXP, altough I did get a dead hang. I was goofing around with video drivers at the time. Oh well, nothing can be perfect, but it can work well. I've been using WinXP since January (slightly past beta1) and I have had few problems. Nobody should ever expect a crash free system, and if you do have fun finding one!

:)



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

wayne  skeens
skeensw@purdue.edu
11/3/2001 4:12:25 PM Not rated

It did it once in the middle of editing about 100 diffrent ID3v2 tags on mp3's. It is not in any compatiability mode. Im not gonna change the compatiability mode to see if it will blue screen sometime.


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Robert  Wlodarczyk
Robert.Wlodarczyk@stonybrook.edu
11/3/2001 4:22:40 PM Not rated

Ok. So to me now it seems clear that this is a WinAMP running on Windows XP problem... hopefully WinAMP will fix that soon. Otherwise, just use the Windows Media Player.



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

wayne  skeens
skeensw@purdue.edu
11/3/2001 4:34:55 PM Not rated

Hmmm.... It froze up again right after that.
TIP dont use the X to close a winamp tag editor window.
I am gonna try win 98 compatiability mode


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Adam  Azarchs
admeralthrawn@hotmail.com
11/3/2001 9:49:07 PM Not rated

It's a winamp bug, not an MS bug, obviously.
Wasn't it great back in the days before Winamp was bought by AOHell? Now there isn't even an ideological reason to use winamp over WMP.



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

William  Reading
billatq@hotmail.com
11/4/2001 2:39:40 PM Not rated

The first week I had XP, I managed to blue screen it 32 different times...so I finally started looking into the logs to see what was crashing it, and determined that an old version of Advanced Call center was the problem. After I uninstalled it...I was still getting problems, but just randomely. After wiping the partition and reinstalling, I finally got it to work properly and have only had one BSOD since then, which was due to some bad drivers that wouldn't uninstall. However..system restore had made a restore point one hour before, so I just used that and my system has been up since then.

As for winamp...I haven't had any problems running it at all, and I prefer it because of its relatively small memory footprint and cpu-initialization. I don't use WMP for music because it just uses up too many resources for my feeble Celeron 333, which actually does run windows xp smoothly.


Last Edited: 11/4/2001 2:41 PM EST [Top]  [Bottom]  [Listen]  [Edit]  [Reply

Adam  Azarchs
admeralthrawn@hotmail.com
11/4/2001 5:51:56 PM Not rated

I prefer winamp because I havn't figured out how to get rid of the stupid visualization windows in WMP, and I like windowshade mode.
You seem to have had some wierd problems, Will. I havn't heard anyone else with problems like that.



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Yifung  Lin
yiflin@hotmail.com
11/6/2001 4:10:53 AM Not rated

no winamp problems for me either. i have an athlon xp and win xp hasn't crashed yet. it's been over a month now, and i never turn my computer off.


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

John  Gallardo
non_interleaved@hotmail.com
11/8/2001 7:18:49 PM Not rated

>>but XP is supposed to insulate the rest of the system

try executing this c program

int main(void)
{
printf("\t\t\b\b\b");
printf("hello");
fflush(stdout);
return(0);
}



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Jon  Krempach
jdk@purdue.edu
11/15/2001 10:37:26 PM Not rated

In the past I would have periodic blue screens caused by nVidia's older drivers, but since they've released the most recent Detonators, that particular issue hasn't hit again. I don't know that I've had any problems since then with the OS.

I've been running winamp from the beginning haven't had any problems with it. Early versions of Winamp 3.0 are floating around if you want to try that...


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Dementrious  Slayer
barker0@purdue.edu
11/16/2001 1:42:53 PM Not rated

I have not had a BOD once since installing XP. I was worried because my laptop is old and I didn't know what kind of drivers would be used.



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

J  J
jones_jj@iwon.com
11/24/2001 3:27:46 AM Not rated

you don't get many true system crashes in a linux system :)


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Don  Lee
don@id-zone.com
11/24/2001 3:37:42 AM Not rated

It is sooooooo true. Linux never crashes, BUT in XWindows, you do get crashes once a while, where you have to kill the process. LOL. I have had BOD when I install XP and run it for the first week. Then I figure that the cooling system of the machine is not high enough. (i.e. RAM is hot) So I decided to install another fan into it. I'm not quite sure if that's the reason of Blue Screen. But now, I don't get BOD for the longest time I ever had. (1 month) In contrary, when I was using W2K, I do get BOD every other week. :(



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Robert  Wlodarczyk
Robert.Wlodarczyk@stonybrook.edu
11/24/2001 9:41:09 AM Not rated

Linux never crashes?!?!? Well, a few weeks ago I was helping one of my friends who run Monte Carlo siumulations under Linux. We were trying to figure out how to install a printer in Linux... and low and behold, it froze on us. I started laughing my head off! It was in XWindows, but we couldn't even type or move the mouse... so, the only alternative was to reset the machine.


[Top]  [Bottom]  [Listen]  [Edit]  [Reply

Kremb  Bula
hornrl@hotmail.com
11/29/2001 5:45:23 PM Not rated

out of the blue, pardon the pun, my XP box started going blue on boot.

no new hardware or software.

all I get now is

blue screen: unable to mount boot device after amdagp driver install.

in safe mode that is about 20 drivers in.

as I said, out of the blue. really wierd.

pretty choked, at least with 98 it was chunky all the time, but rarely total lockout of your system



[Top]  [Bottom]  [Listen]  [Edit]  [Reply

| | Last

Subscribe to this thread

Copyright © 2001 DevHood® All Rights Reserved