Jump to content
Compatible Support Forums

Tom-boy

Members
  • Content count

    113
  • Joined

  • Last visited

    Never

Community Reputation

0 Neutral

About Tom-boy

  • Rank
    member
  1. Tom-boy

    Weird media problem

    Thanks for the link Got the answers from there- busted codecs and, oddly enough, DirectX problem. Fixing was a piece of cake. Appreciate it.
  2. Tom-boy

    Weird media problem

    Basically, when using Media Player 9 or CorePlayer, some of the files play upside down, heh. Would be funny if it wasn't. Any ideas what causes this?
  3. Tom-boy

    Logitech LX700 mouse problem

    Default drivers, eh? Never thought of that, have to give it a try. I don't think in my case it's not the lens or pad being dirty since I bought both on Friday 23rd but of course that doesn't mean anything, so I cleaned them anyway to no avail. My guess also would be that there's something funky with Setpoint and Mouseware, giving even more reason to drive Win2kPro's drivers. What keyboard are you using with MX1000? Mine being so new I could still return them back to the store and switch to something better, if it goes to that.
  4. Tom-boy

    Logitech LX700 mouse problem

    Yes, it's a cordless system with a base station and all. The problem is not that it lags really, since I can configure the mouse very nicely but that the cursor suddenly starts to live a life of it's own, bouncing around. You can get it back in control by left-clicking but that isn't always an option, of course. So I was more like wondering if someone with same model has a some specific tip regarding configuration (what on/off)or something similar. One thing I've noticed is that my cooling seems to pick up speed now a lot earlier. Are these cordless systems really such a powerhogs? This could possibly explain also my problems.
  5. Tom-boy

    Logitech LX700 mouse problem

    Namely, the cursor moves rather erratically. With games this is just unacceptable since the cursor often suddenly jumps who knows where and especially fine, small movements tend to do this. I upgraded Setpoint, cleaned the lens and asked from Logitech but they gave me solutions I've already done. Did I just buy a dodgy product or is there some simple tricks, settings or such to solve this? I know this rather vague quesation and description but I'm out ideas here.
  6. Tom-boy

    Mediafile problems - big time

    Well, I just finished with a complete reinstall of the system and files and I'm glad to say everything runs just fine again. The most likely culprit is the 81.94 Detonators. Even though I switched back to 77.72 and used the tool Sampson recommended, something was probably still left behind or then some files became corrupted due to 81.94 because the problems remained. After the clean install I first installed 77.72 again- worked fine and then switched to 81.95, with same media players+ codecs. Still working fine if not better So stay steer clear of 81.94! to Relic: As you can see from above, you'd se safe with 77.72 and 81.95. I've MSI GF 6600GT 128MB AGP and been very happy with it. Can't run everything on max, cause my processor is a bit weak but as far as the card is concerned, there're no complaints here. Of course, it'd be nice if it had more oomph with it but so far it'll have to do. FEAR ran great in 1024x768x32 AAx2, minus soft shadows, no fps issues whatsoever. COD2 was another story, in one level had to drop AA off and turn rez to 640x480 just to pass it. 81.95 has a compatibility fix for this, though I haven't tried it yet. So yes, 6600GT is a nice card and I'm sure you'll do fine with it
  7. Tom-boy

    Mediafile problems - big time

    OK, I uninstalled (again) and cleaned regisrty of all QT related. Sma results, except that once a movie started to play with 85% of processing power being used, very choppy playback too. Since I really can't make heads or tails what codecs are needed (they definitely should be up-to date). I guess the only thing left to do is to have a complete reinstall,goddammit. Cheers for help though, appreciate it. Got some new ideas too in case something like this happens again. Tom-boy
  8. Tom-boy

    Mediafile problems - big time

    No dice Ran it twice, also did the same thing to sound card drivers and nada. Even the Sound Blaster flash screen failed to play. But what I did notice, is that when attempting to play some files, my virus scanner icon switches on and off (F-Secure 5.41). This is rather odd, since last night I updated the definitions and ran the scanner without finding anything. It must be something inside the media codecs that is seriously conflicting with Windows or then I've actually been bombed by a virus. However, since I uninstalled/reinstalled all the players and codecs, and using CCleaner to get rid off the keys, I can't for the love of god figure out what it is.
  9. Tom-boy

    Mediafile problems - big time

    OK, let's try that. I've GeForce 6600GT 128MB so the drivers should work properly. I also did have A-V turned off. Cross your fingers
  10. Tom-boy

    Mediafile problems - big time

    Wonder what happened to all my media files and players: Running Win2k Pro+SP4+ all updates Until now, everything has been running fine, then a series of problems occured on a string. - At first, movies in Silent Hunter 3 seized to play; Ubisoft intro screen, option menu background movie etc. No biggie, sometimes this happens and solution is to delete Movies folder but nevertheless... - I install Brothers in Arms: Earned in Blood which installed Media Player 9 codecs without an option to passing it (already having them and working fine). - Also, I installed Detonator 81.94 because of it's compatibility fix to Call of Duty 2. Now the problems start. None of the avi's, mpeg's etc won't work, the players (Irfanview latest, MP 9, Quicktime 4, DiVX Player)completely stall when attempting to play the files and can't even ctrl+alt+del back to desktop but have to hardboot instead. BiA:EiB & CoD2 in-game movies work, as well as MP3's. Tried rolling back to Detonator 77.xx, ran a virus scan, defragged, ran a system clean up (CCleaner)and nothing works. Now, when trying to burn the media onto CD's, even the selection menu of Nero stalls when clicking a media file to be added to the quey. It can't be that all the movies are corrupt all of a sudden and reinstalling the players dont' work either. Hopefully someone has an idea to what is going on, since I rather not do a complete overhaul at the moment and since I don't know what gives, there's no guarantee the problems wouldn't reoccur anyway.
  11. Tom-boy

    FlashGet : a serious spyware threat?

    Hi and thx for tips for alternatives. I tried DownloadPlus but couldn't get it to work with Firefox, so instead got LeechGet2004, which seems to be a nice manager also. On the basis of the link ScinteX posted, it too is supposed to be free of spyware-hint, hint. But I keep those other two in mind as well and give 'em a shot, just to compare which is the best.
  12. Tom-boy

    FlashGet : a serious spyware threat?

    OK, thanks- it's good as gone Download Plus, eh? I'll go and have a look at it
  13. I just downloaded and ran M$ AntiSpyware and it gave a rather big load of potential threats, affected registry keys and files concerning FlashGet 1.3. Neither Spybot nor Adaware regarded it as a threat. So, should I be worried? Is it really as malicious as AntiSpyware claims or is this just some sort M$ threat tactics in the works? I do realise that FlashGet is ad-supported program and therefore collects data but since I use it only on legitimate and 'innocent' sites it doesn't really matter that much. Annoying it is nevertheless, no doubt.
  14. Tom-boy

    Oh no. Floppy disk(40) error.

    Bloody success!!! Thanks guys, especially jmmijo Actually, your advice to try the drive on another machine gave the solution- it wasn't the drive but the cable. I took it with me to my mates and sure enough, the drive worked fine with his cable but not with mine. It must've been damaged at some point when tinkering inside doing this or that. Just went and bought a new cable and everything is fine now.Sweet 8) Heh, funny thing happened when we were testing the drive. Just in case, I brought the modem driver floppy with me (for which I needed the floppy drive) to see if we could turn it into bootable CD. After many hairraising attempts, when the drivers tried to install themselves into my mates box, we managed to burn the CD. Only after that, an idea occured to us:'You know, there's this new thing called internet. Maybe we could've tried from there'. First hit in the Google took us to the manufacturer's page lol. Live and learn, people Cheers and thx, guys. [Edited by Tom-boy on 2004-12-28 12:43:04]
  15. Tom-boy

    Oh no. Floppy disk(40) error.

    Thanks guys for your help but, unfortunately, still no luck. What I've done so far is this: - detached A-drives cables, booted and set BIOS to Floppy:none and not booting with it(obiously) Boot order was set to hard drive as first and D-drive as second, third none. saved and went to Windows and the shut the box. -attached A-drive cables, booted and in BIOS set floppy to correct 1.33/3.5, stll non-booting option for it. saved, got the error message but went to Windows anyway and closed it. - switched the data cable around, booted and got the error message again. installed the drives from Windows again,closed it and rebooted. stll the same.closed the Windows again. -switched the cable around once more,booted and set A-drive to boot as third in order but still get the message. I'm out of ideas. Does anything above strike as obvious mistake to you? The A-drive is brand new, so it can't be that it's simply broken. All I can think of is that the data cable is busted or I actually managed to switch between A- and C-drive cables. The A-drive cable sort of stands alone on the mobo, whereas the one for the C-dive in next to RAM-memory bank, right? Also, As far as I remember, the red ribbon on data cable goes to pin#1 and that usually is closes to the drive motor, in the middle. It's odd that even if the ribbon is 'on the side' of the drive, nothing happens. There's probably just some small detail I've forgotten that causes the hick-up. But which one
×