Discussion
assword@ftp.yoursite.com) in IE should work. 
rico said:
I would wager its a local issue on your Crapintosh
funny that, just had to solve yet another problem due to the very problematic xp pro. this time was eplorer.exe running at 100% cpu.
my so called "crapintosh" still running strong. guess my pc is due for is bi-annual OS reinstall.
i should get paid for troubleshooting windows problem.
jodypress said:
funny that, just had to solve yet another problem due to the very problematic xp pro. this time was eplorer.exe running at 100% cpu.
my so called "crapintosh" still running strong. guess my pc is due for is bi-annual OS reinstall.
i should get paid for troubleshooting windows problem.
all platforms have a single common bug, their users.
A well installed, un fettled with Install of XP or OsX will be stable forever.
its only once users get theirs hands on them that they cause issues.
I have never EVER had a BSOD on XP, EXCEPT when I made cockups.
a) installed Beta Drivers -- BSOD
b) installed Beta SP2 -- BSOD
I support many G4 and now G5 Xserves, they also are mostly fine, save for their appetite for Memory Sticks, they do like to destory them!
BUT, the users error, does look like a local machine error, as ooposed to a Remote machine error.
that was my point
JamieBeeston said:
A well installed, un fettled with Install of XP or OsX will be stable forever.
its only once users get theirs hands on them that they cause issues.
Absolutley correct.
The only time I ever have problems with my XP machine is when I install something with beta drivers, or when I install something with Microsft certified drivers, or when I try and use two USB items at the same time, or when I leave the machine on for over a week, or when I first switch it on and it decides not to boot up, or when I try and use it for email or surfing the web, or when I try and write a word document, or...
trooper1212 said:
Absolutley correct.
The only time I ever have problems with my XP machine is when I install something with beta drivers, or when I install something with Microsft certified drivers, or when I try and use two USB items at the same time, or when I leave the machine on for over a week, or when I first switch it on and it decides not to boot up, or when I try and use it for email or surfing the web, or when I try and write a word document, or...
Cheeky Monkey
I can only speak from experience, but I do accept the level and quality of Kit I am using if far beyond that of the home user environment.
ECC Ram = No More BSODs
dont overcook your Cpu = no more BSODS
dont try and install lots of 'aftermarketware' applications which replace integral Windows Components with their own versions (software firewalls/bandwidth throttlers etc)
Its all down to what you want to make of it.
BUT, in my first hand experience, I have seen 3 Xserves kill ram, first hand. I cant see how or why, they run very hot granted, but arent running 'overly hot' comparativly, but all the same, 3 so far have needed new ram.
Possibly just a bad batch of ram installed at source.
Anyway
Apples have their places, DB and Design.
PCs have their places Everywhere else!
Just like Linux and Windows have their places
but we are going OT here
Sorry Rico.
You are intimating that some if windows core subsystems are inherently flawed?
As that would be the only way for such issues to come about.
My point wasn't that ECC makes your machine infallible, as already stated, I can still induce a BSOD with ECC, it DOES however substantially reduce the chance of a BSOD.
As that would be the only way for such issues to come about.
My point wasn't that ECC makes your machine infallible, as already stated, I can still induce a BSOD with ECC, it DOES however substantially reduce the chance of a BSOD.
I spent the whole night once talking to a core engineer in the states regarding why one of my servers was blue screening 3 times a week - turns out there was a bug in NTFS.SYS which our usage was exploiting, probably wouldn't have been found during the beta testing as hardware has moved on and now you can push the OS harder.
There are loads of problems that you don't come accross until you start using the servers hard. Recently had 8 servers that failed to come up after the weekly reboot with a BSOD (the fact that that a weekly reboot is a requirement should say something), turns out we had found a hard coded limit to a certain registry key size and we had to rebuild the boxes (you can replicate this by adding about 1000-1500 print queues to a win2k server if you are interested). Luckily our automated server build means we can build and comission a server in about 1.5 hours so not too much down time for the business.
There are loads of problems that you don't come accross until you start using the servers hard. Recently had 8 servers that failed to come up after the weekly reboot with a BSOD (the fact that that a weekly reboot is a requirement should say something), turns out we had found a hard coded limit to a certain registry key size and we had to rebuild the boxes (you can replicate this by adding about 1000-1500 print queues to a win2k server if you are interested). Luckily our automated server build means we can build and comission a server in about 1.5 hours so not too much down time for the business.
m12_nathan said:
A driver being a core part of the OS and the program also being a core part of the OS
Win2k3 looks like It'll be much better from the testing we've been doing.
Cheers
Ya, but EVERY single client managing their own 2k3 box as been hacked so far :|
Script Kiddes running (mostly german) Warez Sitez.
Still, you live and learn
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff