Get your fill of sci-fi, science, and mockery of stupid ideas
http://stardestroyer.dyndns-home.com/
It's not related to MSN Messenger.Howedar wrote:I know. I was saying that if you use it, you can trade for Trillian and kill MSNIM.Dalton wrote:I'm referring to the Network Messenger service in XP that's automatically turned on.Howedar wrote:Trillian is not a window for popups.
Messenger Service != MSN MessengerHowedar wrote:I know. I was saying that if you use it, you can trade for Trillian and kill MSNIM.Dalton wrote:I'm referring to the Network Messenger service in XP that's automatically turned on.Howedar wrote:Trillian is not a window for popups.
Rebooting after I manage to screw up a kernel installation (eg forget to run lilo) or daemon(which then hangs on init, example of screwing up would be piping syslog stuff to psad, and starting syslogd before psad, which is default), since I have to reboot at least 4 times- after installation, after failed boot, after inserting bootdisk, and after repairs made, assumming that it was done right. Normally it would be fine, but the video card takes 5 seconds to start, and the ATA controller takes 10 seconds to start.phongn wrote:Oddly, my RH9 box never had that kind of uptime as RH kept informing me of kernel-level security updates that required a reboot...AdmiralKanos wrote:Someone obviously doesn't install all of the Windows security updates when they come out. You'll never get three-month uptime on Windows if you install all those patches, most of which require a reboot in order to work properly.
Restarts are indeed annoying, though (especially if you have a huge AD box that needs a loooong while to reboot)
Ah...ggs wrote:Poe, the reason ME gets so much crap is that its the last OS based on the win9x kernal and never should have been released (its basicly win98 3rd edition, with some extra 'features')
Yeah, that's one of the biggest problems with Windows ME. It has a memory leak the size of a small nation. Which meant that whenever a program ran, not all the memory it used was returned to the memory pool. So the memory available got lower and lower and lower, until the system ground to a halt.Lord Poe wrote:Ah...ggs wrote:Poe, the reason ME gets so much crap is that its the last OS based on the win9x kernal and never should have been released (its basicly win98 3rd edition, with some extra 'features')
Well, the only problems I've had lately is if I use too many paint programs at once, along with a memory hog like Simpose. Then I get a freeze up if I don't restart.
Did you do an upgrade install or a full reinstall?McNum wrote:I just made the Me to XP Pro upgrade and I'm impressed.
Win XP has crashed once. Only once. During installation, of course. I've even tried overloading XP to see if I could crash it. The worst I could get was that it slowed down and refused to open another program until I closed at least one of the open ones.
My verdict: XP is good. Me can be ok, if you are able to do the few regular adjustments to keep it stable.
I used to have a Win95 & win98se boxes and since I do programming, I was periodically rebboting 4-5 times a day when I did any development work.Lord Poe wrote:Ah...ggs wrote:Poe, the reason ME gets so much crap is that its the last OS based on the win9x kernal and never should have been released (its basicly win98 3rd edition, with some extra 'features')
Well, the only problems I've had lately is if I use too many paint programs at once, along with a memory hog like Simpose. Then I get a freeze up if I don't restart.
For others with this problem, there's a bootdisk creation utility on the win2k CD, and you can download the boot disk creation utility for WinXP from the internet.ggs wrote:(My old Win98se box I reformated & installed win2k on it. That was fun, the BIOS didn support booting from CD...)
There was something like a page-worth of stuff left out of Home that's in Pro.Vendetta wrote:and XP Pro offers absolutely nothing above home for a desktop OS at all)
How well does something like that work? I don't know if I frequently encounter that sort of problem (although I probably have...), but I'm both interested and slightly wary about just installing something like that.GrandMasterTerwynn wrote:Yeah, that's one of the biggest problems with Windows ME. It has a memory leak the size of a small nation. Which meant that whenever a program ran, not all the memory it used was returned to the memory pool. So the memory available got lower and lower and lower, until the system ground to a halt.
And there were only two ways to fix the problem. One was the old three-fingered salute. The other was to pick up some sort of utility to do the garbage collection that Windows should've been doing. An example of that is here.
Click Here for Home vs ProfShinova wrote:There was something like a page-worth of stuff left out of Home that's in Pro.Vendetta wrote:and XP Pro offers absolutely nothing above home for a desktop OS at all)
Read carefully. For a desktop OS, Professional's extra features are just so much wasted disk space.TheFeniX wrote:Click Here for Home vs ProfShinova wrote:There was something like a page-worth of stuff left out of Home that's in Pro.Vendetta wrote:and XP Pro offers absolutely nothing above home for a desktop OS at all)
Vendetta wrote:Read carefully. For a desktop OS, Professional's extra features are just so much wasted disk space.
For a workstation or network terminal, they're useful, for a single user desktop (especially a games/internet PC, like mine), they are utterly irrelevant.
The only difference I would see if I had Professional is that the loading bar would be blue, and I would be £90 poorer.
Is this basically what hyperthreading is?Multi-processor support - Windows XP Pro supports up to two microprocessors, while Home Edition supports only one.
And He was pointing out that the Windows Messenger service and MSN Instant Messenger are completely different things. Removing MSN Messenger will have no effect on shite delivered through Messenger Service, and stopping Messenger Service will in no way affect MSN messenger.Howedar wrote:I know. I was saying that if you use it, you can trade for Trillian and kill MSNIM.Dalton wrote:I'm referring to the Network Messenger service in XP that's automatically turned on.Howedar wrote:Trillian is not a window for popups.
No.Is this basically what hyperthreading is?Multi-processor support - Windows XP Pro supports up to two microprocessors, while Home Edition supports only one.
If it is, then it's one good thing for Pro over Home, if you have P4 or equivalent.
Hey, don't look at me. Information was asked for and I provided.Vendetta wrote:Read carefully. For a desktop OS, Professional's extra features are just so much wasted disk space.TheFeniX wrote:Click Here for Home vs ProfShinova wrote:There was something like a page-worth of stuff left out of Home that's in Pro.
No, this is actually having two physical CPU's in your PC. For a home user, this would only help out on programs that could take advantage. I think Photoshop will use dual CPU's with a patch, but I've never tried it.Shinova wrote:Is this basically what hyperthreading is?Multi-processor support - Windows XP Pro supports up to two microprocessors, while Home Edition supports only one.
If it is, then it's one good thing for Pro over Home, if you have P4 or equivalent.
I do like RDP a lot, though (VNC is much slower). For those who don't have single-user machines, ACLs and Group Policy is a godsend.Vendetta wrote:For a workstation or network terminal, they're useful, for a single user desktop (especially a games/internet PC, like mine), they are utterly irrelevant.
Bah. SMP is nice and smooth - you can continue doing tasks while the other processor is doing intensive stuff. I have a single-CPU box, but have played with dual-CPU desktops.TheFeniX wrote:Although, with some tweaking XP can be used to split up work between the separate CPUs. I'm not entirely sure (I've only installed Dual CPU systems on FIle application servers where it wasn't needed), but I think you could setup one CPU to handle all the background work, and the other to handle actual applications. With how advanced and fast CPU's are getting though, it's probably not even worth the money.
Well, SMP is a method for supporting multiple processors, usually having a shared memory pool. There are other methods, like NUMA (which Opteron and PPC970 use, for example).Vendetta wrote:SMP support is where you use two (or more) seperate CPUs. Hyperthreading is a single processor pretending to act like two (almost, occasionally, ish).
It does. Both versions of Windows XP support HT, as does Linux kernel 2.4.x onwards.phongn wrote: I can't recall if XP Home supports two logical processors (on a single physical one) or not - if SMP support was totally removed than HT won't work, period. It's unlikely, though.
I think the newest SP of Win2k supports hyperthreading.Vendetta wrote:It does. Both versions of Windows XP support HT, as does Linux kernel 2.4.x onwards.
Windows 2000 and .NET server don't and won't.