close the broken window in XP.

[WaWAR_FA]

ok kids straight form my twisted mind is a small fix for windoze XP.

start > control panel > Adminstrative tools > Computer management > Expand services and applications > click services > sort page by log on as > go to the bottom and look for 3 entries from Network service. Open WMI Performance Adapter > Click Logon tab > where is states logon as this service, delete all the fields and replace with garbage data.  switch to local system account to double lock and then click disable to triple lock you just shut the broken window!
WARNING: for 30 days after closing the account access it can still be accessed via normal account name and pass (the crap you deleted).

Next go to Indexing service in the Computer management window. Expand Indexing service, Expand System, click on Directories.  Delete all directories listed. Exit the menus and goto Windows Task manager (Ctrl-Alt-Del) gop to Processes and sort by Image Name. Look for SVCHOST.EXE, there should be 4 copies running at the same time. Close each of them until only one keeps returning. DONOT turn your computer off for any reason for the next 30 days!!

After 30 days remove the last SVCHOST.EXE process.

All windows holes are now closed.

YOU SHUT YOUR COMPUTER DOWN, YOU HAVE TO DO THIS ALL OVER AGAIN!

[pkd_lives]

Okay...Maybe I missed the point, after all I don't use XP, but come on - windows up for 30 days, when, where, prove to me just once you can do it......See ya can't ya lyin'  

[Zombie9920]

quote:Originally posted by pkd:
Okay...Maybe I missed the point, after all I don't use XP, but come on - windows up for 30 days, when, where, prove to me just once you can do it......See ya can't ya lyin'          

Link to image...

You can clearly see my current uptime(the pic was actually taken yesterday evening, my uptime is about a day higher now) in that pic (and I use the PC for alot of stuff like work, photo and video editing, playing games, etc.). If you know how to configure your system it will not crash, simple as that. My uptime would be alot higher but I had to reboot to update mobo chipset drivers. ;P

[ August 05, 2002: Message edited by: Zombie9920 ]

[ August 07, 2002: Message edited by: Calum ]

[WaWAR_FA]

you must have never used your computer then zombie

[Zombie9920]

quote:Originally posted by WaWAR_BOB:
you must have never used your computer then zombie

Bullshit, I use the piss out of the comp. Like I said, if you know how to configure your system properly..Windows NT/2K/XP will not crash on you.

[sporkme]

call me when you cross the year mark.  DONT UPGRADE THAT FUCKER!

of course, my FREE operating system............  I AM NOT GETTING INTO IT

[AlexMax]

You must be one of the flukes.  There are one or two systems out of every thousand from my experiences that run Windows perfectly and flawlessly.  Someone must have really gotten your system tweaked to be JUST SO....which isn't a bad thing, Linux users do stuff like that all the time, you're just paying $200 more for XP and you got lucky with your system configuration.

I would go into how Linux can be tweaked to be stable on almost any system, (which I have NEVER been able to do with ANY version of Windows), but nah...a certain 12 year old might start biting at my ankles and frankly I'm too tired right now to b**ch at him.

[Zombie9920]

quote:Originally posted by AlexMax:
You must be one of the flukes.  There are one or two systems out of every thousand from my experiences that run Windows perfectly and flawlessly.  Someone must have really gotten your system tweaked to be JUST SO....which isn't a bad thing, Linux users do stuff like that all the time, you're just paying $200 more for XP and you got lucky with your system configuration.

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.

[ August 05, 2002: Message edited by: Zombie9920 ]

[lazygamer]

You know how you delete that SVCHOST.exe right? Would it fool XP if you deleted it, created a blank text file and then renamed the text file SVCHOST.exe, then make that file "read only"?

Did Big Bill ever imagine that scenario? Theoretically that might make it possible to permanantly keep your computer free of that file...

[beltorak0]

it probably runs a checksum on it, or if it fails to run, simply restores it.  which would make me wonder: why the hell is it necessary if it is created from the os anyway?

As for the fluke; i hear that win 2k/me/xp are much more stable if they aren't upgrades; which is to say that they need to be clean installs.  As in off the oem shelf.

anyway, -t.

[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.

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).

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.

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.

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 ]

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 ]

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.

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?