Jump to content
Compatible Support Forums

Hit

Members
  • Content count

    37
  • Joined

  • Last visited

    Never

Community Reputation

0 Neutral

About Hit

  • Rank
    newbie
  1. Hit

    AIM memory Leak

    Anyone else gets this? AIM 4.7 I still think doesn't work in XP RC1, so I use AIM 4.3, and I've had this leak forever. Basically, after every IM, about 300K more RAM is used. It never goes down, and I'll find that process using 200 megs in no time.
  2. Hit

    The search dog gotta go

    I think his point is that even if you wanted to use the dog, he doesn't make anything easier and takes up space, thus making searching even MORE of a pain. In light of that, I'd say either fix it up so there's room for him or just ..em...put him to sleep and be done with it =]
  3. Hit

    Cant Install AIM on XP 2475

    AIM 4.7 will NOT work in 2474+. Ironically enough, this is probably because AOL tried to make AIM more XP aware, and it broke under 2474. In beta 2, AIM 4.7 had the new XP look. Anyway, you have to use 4.3. In order to get it to install, you have to save the executable to disk, and run it from there. It took me a few tries, but eventually it installs. If it hangs, stop it IMMEDIATELY. Also, check the dir you chose to install to. You may find a 500+MB file sitting there.
  4. Hit

    Any trouble with 2474 ? Like no games running ?!

    I, for the life of me, still haven't gotten NeoRageX to work on any XP build. Has anyone managed otherwise?
  5. Hit

    *Sigh*

    Unlike passing fads, like..say..."All your base", spreading crap about and flaming Microsoft seems to never get old.
  6. Hit

    Windows Beta 2 Review with tons of screenies

    Billy Gates eh? Hmm. Sometimes I wish Bill Gates really would post in here. Then we could give him a piece of our mind on this whole activation business. Not that he'd listen, but...
  7. Thankfully, you can disable the damn dog. Now, if only MS would add the "disable ineffective piracy protection that merely pisses legitimate users off" feature. =P
  8. Hit

    Interesting Install Tid Bit

    ahh..the 'ol deltree /y. Great way to screw up your system, but I would still argue "rm -rf /" on a UNIX box would still hose your system more. Then again, there are more ways to destroy a UNIX system than list directories, so it's not like that's a good thing =]
  9. Hit

    Rats

    That's IT I installed Win2k again to see if I could try upgrading from there, and even it now is starting to ***** about the card. This POS has GOT to go. Oh well, who needs DVD playback anyway? it's all overrated, I tell ya. (The card I'm replacing is a DVD decoding card.) I'll be damn sure the next computer I buy/build will have so many damn PCI slots it won't be funny. OF course, then PCI will become obsolete....ahh. You gotta love PCs.
  10. Hit

    Rats

    ThC - it's not that I'm too cheap to buy a PCI NIC, it's that it won't fit. Period. There are no more PCI slots left...in fact, I think there is only one ISA slot left -- like that's going to do any good. 4&20 (hehe...THC and 4:20...amusing) - I think I'll give that a shot.
  11. Hit

    Rats

    It's a Linksys 16 Ethernet LAN card. Yes, it's ISA. Under Win2k (and build 2296), it would've used the "NE2000 Compatible" driver. When I go to add hardware manually (that is, not asking windows to try to detect the card, which it can't), I get like 3 manufacturers, each with a max of 4 cards each. I have no idea why this is.
  12. Hit

    Rats

    hmm. Just tried 2454. For some reason, my NIC still won't work. Just checking, does anyone get a better list of NIC hardware than me? When I go to list the hardware drivers, I get like just a few cards.
  13. Hit

    Upgrading W2K to XP2446

    I suspect the main reason that doesn't work is because one of your Win2k drivers doesn't work so well in the new XP environment. I remember upgrading from 2K to 2296 worked fine, but after that, it's BSOD hell if I tried it with any later builds. Usually, BSODs mean driver problems. However, when the RC's come out, MS will probably work towards virtually every Win2k driver working in XP as it did in 2K.
  14. Hit

    My ideas for XP

    Yeah, is it me, or JDulmage being more of a jerk than usual? Pull the stick out of your a$$ buddy, it's an OS. No one's insulted your mother or anything. Too bad I can't say the same for you.
  15. Now that you gotten the usual flame response from the most popular guy here ::cough::, perhaps you would like a more helpful opinion. As for as going from 98 to XP goes, this is a big deal. XP certainly has more stabability than 9x/ME does, and, supposedly, will have speed comparable to it assuming you have a decent about of ram (128+). XP will also support hardware that 2K did not in the past. How much more is open to question, but I would take a guess that MS is going for as much 9x compatability as possible. Justifying a move from Windows 2K is tougher. If all your programs work to your satisfaction in 2K, the upgrade to XP may not be worth the money. Also, if stabability is a concern, even the final release of WinXP will probably not be as solid as 2K is now, until it goes through the usual set of service packs. If you're a business that is using active directory, you might have to go to XP, as MS has said that a huge bug discovered 12 months ago in active directory will only be fixed by upgrading to XP. Also, if you have a decent sized network, you know what a pain it is to upgrade all those machines to a new MS OS (or any OS for that matter). Double that if you have domain servers and the like. So that has to be weighed into consideration as well. As for activation, in its current form, it's easily bypassed. If you prefer, buy one copy, and just apply a crack/whatever to the rest of the copies you want to install on your network. Right now, all you have to do is change an easy-to-find registry key. Note I wouldn't try this if you're a legitimate business...from what I've seen, MS will find you. That's my take on the subject.
×