• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

XPpro is a joke

B

BraeBrae

Member
Hello All,

I'm testing the waters for my gaming platform. I have been and still am using Windows 98 First edition with no problems. I am running two other boxes, one running Windows 2000 Server and Mandrake Linux 8.1. I used a spare disk that had a bare Win98FE install and upgraded to the XPpro. All seemed to go well until the third time I tried to power down and the machine locked up. Oh well, about what I expected from the MicroShaft Corporation.

I thence proceeded to wipe the disk of its existing partitions and install XPpro cleanly. I got to the point that I have installed the updates and only one suite of applications (Office 2K). I tried to view a media file on a networked box and it seemed to stall, everything was unresponsive, and then wham! The box rebooted. So much for the Windows Media Player--new feature, maybe?

The accounts I've setup do correspond to accounts on the W2K server, which are also accessed from the Win98FE client and the MD81 node. Is there maybe a known issue of data throughput/file authentication-submission in XP (any variety) and W2KS that could have led to this event? Upon reboot XPpro wished to send a couple of reports--KMA, MicroShaft!--but I declined.

I'm really curious how M$ could take a somewhat stable system, alter a GUI, and then make the end product this unstable. XP is NOT a new OS--that classification is left for ground-up works of art. Well, M$ has my money already.
 
I've had it for a month or so and it has not once froze or blue screened on me. Every other M$ OS I put on my system has at least froze or gave me a blue screen, but this one hasn't yet. Every thing seems to be running fine and smoother then all the others.

I do agree with you though, it is quite like 2K with some GUI. But there is still quite a few other changes as well.
 


<< I've had it for a month or so and it has not once froze or blue screened on me. Every other M$ OS I put on my system has at least froze or gave me a blue screen, but this one hasn't yet. Every thing seems to be running fine and smoother then all the others.

I do agree with you though, it is quite like 2K with some GUI. But there is still quite a few other changes as well. >>



i would have to say the same.. i got rid of my ME system 2 days ago.. I built a p4 1.7 system with xp pro.. OMG never seen anything more stable .. this os ownz!!
 
Sounds to me like you are bit high on the horse, blaming problems that may be your fault on the OS.
 
Win XP Pro has been rock solid for me also. I even had the beta's RC1 and RC2 and not once did they ever crash on me. I upgraded my home machine for Win98SE to XP Pro Corporate and it is great. Love everything about it except gotta figure out where everything is. But, it's a new interface basically. I work in Technology and have tested the beta's pretty extensively with no lockups.
 
I tried to view a media file on a networked box and it seemed to stall, everything was unresponsive, and then wham! The box rebooted. So much for the Windows Media Player--new feature, maybe?[/i] >>


The most likely explanation is that the machine encountered a blue screen and you had auto reboot set.

Find an event with source SaveDump in the system event log. Get the STOP code and bugcheck parameters and do a web search on some or all of those numbers.

Recent history has demonstrated that the VAST majority of blue screens are caused by third party, not MS, drivers.
 
check for a new driver for your NIC card. If it bsod's while doing network stuff then that would probably be the culprit
 


<< The accounts I've setup do correspond to accounts on the W2K server, which are also accessed from the Win98FE client and the MD81 node. Is there maybe a known issue of data throughput/file authentication-submission in XP (any variety) and W2KS that could have led to this event? Upon reboot XPpro wished to send a couple of reports--KMA, MicroShaft!--but I declined. >>


Holy sh!t, I'm glad someone else has the same problem I had. The problem is that most people here have a basic setup using XP Pro. If it is a stand alone machine with simple internet access everything is fine. My problem came in when logging into my domain and accessing shared files on the domain server. The weird thing was that the internet through put was great (to get to the internet the client has to go through the domain server). However, browsing shared files was like watching grass grow. I tried different NICs and different switches all with the same result (and these NICs I used worked perfect with 2000 and 98SE). Once I did finally connect to a share, the through put was like <56Kbps on a full duplex 100Mbps network. :| I tried everything in the book but to no avail. I REALLY liked XP Pro, but if I can't browse my network it is useless to me. Hopefully this will get taken care of in the first service pack. :|

Hey BraeBrae, if you get this one figured out, PLEASE PM me with the solution because I gave up and went back to 2000.

P.S. My system did not reboot though, it just too forever to log in and took 5-10mins to access a share. :|
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top