All Things Microsoft > Microsoft Software
close the broken window in XP.
rtgwbmsr:
quote:Originally posted by Zombie9920:
I build my own systems(I choose my own configuration), I do all of the tweaking to my system, etc. Simply put, Windows does not give out any problems *if* you know what you are doing with your comp.
--- End quote ---
Me too. I build my own computers, and yet I still get BSOD's no matter how much tweaking I do. Even failsafe tweaking gets me nowhere.
quote:Originally posted by Zombie9920:
Other causes of system instability are having poorly coded apps installed on your OS(god knows there are alot of poorly written apps for Win32).
--- End quote ---
Yes there are! Some of which are: Internet Explorer, Office (Any Version), The whole OS, Windows Media Player (Something is seriously wrong with this app. It crashes sooo many damn times) MSN Messenger which is a simple messinger app that eats up 15 MB RAM. Mac OS 8.6 doesn't even use that much...
quote:Originally posted by Zombie9920:
you messed with the heart of your OS(like the registry in Windows) and screwed something up, you are using un-certified drivers, etc.
--- End quote ---
WHQL did NOTHING at all to help with drivers. In fact, it actually slows the frequency of driver revisions. As for the registry, it needs to clean itself up. About 25% of it is hexidecimal garbage space-wasting, which helps lead to crashes.
quote:Originally posted by Zombie9920:
Most of the time it isn't the OS'es fault that the user doesn't know what he/she is doing.
--- End quote ---
Well if Windows crashes that often, and it is user error, then idiots must FLOCK to Windows.
And anyone with MS Paint, Fireworks, Photoshop ETC could have faked an uptime counter like that. [This may really be pushing it, but ALL of the numbers in the uptime count are elsewhere on the bar. He could have easily copied and pasted the #s there.]
[ August 07, 2002: Message edited by: Dustin ]
Zombie9920:
quote:Originally posted by Dustin:
Well if Windows crashes that often, and it is user error, then idiots must FLOCK to Windows.
And anyone with MS Paint, Fireworks, Photoshop ETC could have faked an uptime counter like that. [This may really be pushing it, but ALL of the numbers in the uptime count are elsewhere on the bar. He could have easily copied and pasted the #s there.]
[ August 07, 2002: Message edited by: Dustin ]
--- End quote ---
Yeah thats what I did. *sarcasm mode on* You know since I'm a Macintosh lovin' photoshop geek and all *sarcasm mode off*.
Now to be serious. Windows XP, WMP, Office XP, etc. really aren't unstable. I just think you ol boys with Windows problems have cheap no-name brand motherboards or something. If you buy quality stuff(not Via or AMD stuff) then you will have a stable system. The thing is, the most of you have either older systems or AMD Athlon/Duron(furnace) systems. My good 'ol P4 Northwood on I850E chipset motherboard(Asus P4T533 to be exact)is fast, stable and doesn't have heat issue(overheating causes crashes you know). ;P
[ August 07, 2002: Message edited by: Zombie9920 ]
lazygamer:
Interesting ideas Zombie. Your certaintly alot more credible then XP loo-sah ever was. The problem with "stable" is that stable is in proportion to the operating system. Besides stability, what about software speed, hardware power harnessing, bloatedness, compatibility etc.
Then there's "stable". Stable as in "alot more stable then the average windows user's computer" or stable as in "much closer to Linux stability"?
Also, should an OS need to be really picky about it's hardware just to run fine? Should the user have to step on eggshells and know hordes of technical stuff just to get the OS to work the way it's susposed to?
smokey:
quote:Originally posted by Zombie9920:
Yeah thats what I did. *sarcasm mode on* You know since I'm a Macintosh lovin' photoshop geek and all *sarcasm mode off*.
Now to be serious. Windows XP, WMP, Office XP, etc. really aren't unstable. I just think you ol boys with Windows problems have cheap no-name brand motherboards or something. If you buy quality stuff(not Via or AMD stuff) then you will have a stable system. The thing is, the most of you have either older systems or AMD Athlon/Duron(furnace) systems. My good 'ol P4 Northwood on I850E chipset motherboard(Asus P4T533 to be exact)is fast, stable and doesn't have heat issue(overheating causes crashes you know). ;P
[ August 07, 2002: Message edited by: Zombie9920 ]
--- End quote ---
erm I have an AMD Duron and my uptimes on XP are just as good.
Calum:
quote:Originally posted by Zombie9920:
I build my own systems(I choose my own configuration), I do all of the tweaking to my system, etc. Simply put, Windows does not give out any problems *if* you know what you are doing with your comp. With a simple memory timing value change in the BIOS I could turn my stable ass system into an unstable mule. There are alot of aspects that can make a system unstable...most of the time it is from faulty hardware or improper BIOS configurations though. Other causes of system instability are having poorly coded apps installed on your OS(god knows there are alot of poorly written apps for Win32), you messed with the heart of your OS(like the registry in Windows) and screwed something up, you are using un-certified drivers, etc. Most of the time it isn't the OS'es fault that the user doesn't know what he/she is doing.
--- End quote ---
the words 'workman', 'tools' and 'poor' spring involuntarily to mind...
and re the checksum on svchost, why not a garbage file to the same size?
Navigation
[0] Message Index
[*] Previous page
Go to full version