Jump to content
Compatible Support Forums

DuSTman

Members
  • Content count

    9
  • Joined

  • Last visited

    Never

Community Reputation

0 Neutral

About DuSTman

  • Rank
    stranger
  1. DuSTman

    DVD recognition peculiarity.

    I have a pioneer DVD-104s, and am having a slight problem with getting it to correctly recognise DVDs. I can put a CD in the drive, remove it, then put a DVD in the drive and it will recognise that there has been something inserted in the drive, but recognises it as the cd that was previously there instead of the disc that actually is in there. Anyone else having similar trouble?
  2. DuSTman

    Pauses

    Thanks for the suggestion, but one of the games i was having the problem with was the Thief 2 demo, which i was running entirely off the dard disk, which, if i'm not mistaken eliminates the CD-rom theory.. This generates no events. i would have thought that if it was a hard drive spinup delay i would have been able to hear the noise the drive makes while spinning up..
  3. DuSTman

    Pauses

    I am having some wierd pauses in various games (starlancer, Tachyon: the fringe, thief 2 demo). The game will (at random points) just stop for several seconds. The last frame that was on screen remains there, and the last sound heard repeats several times. This lasts for about 10 seconds before the game resumes. My hardware: AMD k6-3-450MHz, 128MB pc100 SDram. Gigabyte GA-5AX motherboard Guillemot maxigamer phoenix (voodoo banshee) Soundblaster Live!player 1024. Windows 2000 professional Any ideas anyone?
  4. DuSTman

    Pauses?

    I am having some wierd pauses in various games (starlancer, Tachyon: the fringe, thief 2 demo). The game will (at random points) just stop for several seconds. The last frame that was on screen remains there, and the last sound heard repeats several times. This lasts for about 10 seconds before the game resumes. My hardware: AMD k6-3-450MHz, 128MB pc100 SDram. Gigabyte GA-5AX motherboard Guillemot maxigamer phoenix (voodoo banshee) Soundblaster Live!player 1024. Windows 2000 professional Any ideas anyone?
  5. DuSTman

    Too fast. I need help.

    The thing with this is that it means that with windows 2000 the OS must be re-installed when a processor is upgraded, which, AFAIK, never used to be the case in the older operating systems. Just seems like a bad thing to do, only taking a processor speed value that you'll use for timing the one time the OS is installed.. A bit wierd.
  6. DuSTman

    Too fast. I need help.

    God damn. I had deduced that it had something to do with the mobo/cpu. Yeah. That sucker reports as a 266 MHz. I don't think i will bother flashing it, for one because i'd have to install DOS for that and everything. No. If gigabyte wants to do that to me that board is going to find it's way into my microwave. What's a good replacement socky 7 board? DuST
  7. DuSTman

    Too fast. I need help.

    Yeah. It's more that the timing is buggered, It's not that the frame rates too high. Just.. too fast. I tested how much faster by recording a demo in half life, running it oin another OS (the timing in which works properly), and timiing it on windows 2000. Strangely enough, the demo ran damn near exactly twice as fast as it should have done on the 2000 test. wierd
  8. DuSTman

    Too fast. I need help.

    I am having problems with many games running under windows 2000, that most people seem not to have. I common recurring problem is that for some reason, unknown to me, the timing in most games is buggered. Half-life, GLquake1, Unreal and tournament, Homeworld, all running too fast (And by this i mean that everything in the games happens too fast, the timing routines seem screwed up.) I posted about this in the w2000 games newsgroup and one other person was having the same problem. The hardware that is common to both our systems are AMD K6-3s (mine 450MHz, his 400) and a Gigabyte GA-5AX motherboard. My system: AMD K6-3-450 GA-5AX Guillemot maxigamer phoenix(voodoo banshee) SB Live!Player 1024 Anyone got any idea about this? This seems to be quite an esoteric problem, so i was wondering if no-one knows how to solve it that it is a bug in wither the BIOS, or Win2000s timing code. Any ideas? DuSTman
  9. DuSTman

    Help! is my V3 3000 dying?

    Well. I personally think that the card's goose is cooked. At my old school we had a vidoe card fail in near enough exactly the same way you described. It carried on like that, and then one day someone rebooted the computer and the vidoe card just died.
×