ri-rilot

I have been having this same problem on several different winXP boxes. To replicate I do the following. Reboot machine. Bring up the My Computer window Type a URL in to the adress bar and hit enter When this is done the entire screen goes grey and an untitled folder bar appears in the task bar. Alt-F4ing this kills the grey screen and everything will function normally until the next re-boot. If you don't use a standard explorer window to go to a web page and instead just fire up IE directly then all is fine. This only happens ONCE, the first time you go to a page after a re-boot. Any ideas?

Just tried that. Unfortunately it didn't work. All spyware removed but still the grey screen haunts my reboots. Thx anyway.

Can't seem to get this one to work under XP. I have installed the latest updates (1.7 which gives Win2k compatability). When the game launches all seems fine until you try to start a game at which point it bombs out to the desktop. I see DK2 is listed as an XP compatible game in the database but I can't seem to get any joy with it.

Ahhh found the problem. I switched the direct sound acceleration down 1 notch and it works fine now. Thx for all the suggestions.

Tried logging on as administrator to run the game but no joy, same problem, just bombs to the desktop with no error or anything.

I have a very wierd problem with XP that I can't seem to find any info on. Sometimes when directing explorer to a web page my entire desktop will go grey and a folder task will appear in the task bar with no title. Clicking on the folder causes the ENTIRE screen to go grey (even the task bar). Alt-F4ing kills the grey screen. This never happens at clean install but manifests itself after a few weeks or operations and mostly first time you launch IE from cold boot. Any ideas?

Same deal here. All the same problems you described had been plagueing me since Win2k. Switched to a Turtle Beach SantaCruz and no more crackle. It's all down to the SBLive being a bus hog. I don't think it fully complies with the PCI 2.1 specification.

I think it is all a matter of luck with AMD/VIA. I know some fellas that have no probs at all yet they are running out of date drivers, cards all over the place, some pieces of old hardware etc. etc. Yet on the flip side I know others with years and years of technical experience who cannot get their AMD/VIA system stable at all even with all the latest drivers and BIOS updates. I think some combinations of hardware work and others don't. However, It may be a case of how the term "Unstable system" is defined. Some people may say that as long as the system doesn't crash during their daily 2hr game of CS then that is stable. Others (who work with servers for a living usually) consider that only when a system can be stress tested for 1 month continuously without the slightest problem should it be deemed stable. I sit somewhere in the middle. I never turn my system off. I expect it to always work no matter waht I do. I expect the odd crash but I also expect that crash to be to do with dodgy software not something like THREAD_STUCK_IN_DEVICE_DRIVER etc. That seems to plague VIA/AMD users. At the end of the day it is all subjective. What is one mans scrap is another mans Rolls Royce. However, seeing the number of VIA/AMD users on these boards and others complaining of this problem and that I feel that there MUST be some truth in it all. Just my $0.02

Just got shot of my VIA/Athlon combo because I was sick and tired of BSODs and other problems with stability. I saw instability problems when running Linux and Solaris on the same hardware too.... by the way, when I say instability I mean not being able to keep the machine up without a reboot or crash for more than 1 week. Switched to Intel chip and Intel mobo and guess what? No instability whatsoever. No crashes, no rubbish. I will never buy another VIA based board or AMD based chip until they sort out the problems once and for all.

I am having a problem with Carmageddon TDR2000. When ever I try to set a display mode other than 640x480 or 800x600 the game fails to load and bombs out with the error "FAILED: finddisplaymode" The game plays fine in 640x480 and 800x600 in both 16 and 32bit modes. All other d3d and openGL games that I have play fine in whatever display mode I choose. Sys specs: Athlon 1000 1.5GB RAM Abit KT7A GeForce2 Ultra (23.11) Turtle Beach SantaCruz Iiyama 19"

No problems with RF here. Runs fine on XP and 2k and hasn't crashed once. Sys specs: Athlon 1GHz @ 1.4GHz 1.5GB RAM Nvidia GeForce2 Ultra (23.11) Abit KT7A TB SantaCruz

Got em, tried em, loved em. They are superb. Just like the ones for 9x and the stereo effect is excellent.

Hi Guys. Odd one this. When I run some old DOS apps such as Duke 3D or Stargunner the app refuses to accept any keyboard inputs. Eg, when running the Duke 3D installer it says press enter to install esc to exit. Neither works as no inputs from the keyboard are recognised. Any ideas?

I re-installed XP yesterday because I screwed it up with some old ASPI drivers. Since the re-install DOS apps have worked fine. I guess it was some crappy input software like you said. Thanks for the help.

Nope, PS2 keyboard (MS Natural) PS2 mouse (Logitech Mouseman+)

Have you tried the Logitech XP moseware?

I think you already answered you own question. It's definately got a problem if it doesn't work in DOS. Burners are probably the eaisiest things to get working providing you don't do anything silly like set two devices on the same bus both to master.

Has anyone managed to get this to work under Win2k/XP? Saitek were no help at all saying that they won't be qualifying any non usb devices under Windows 2000 or XP.

Beginning to agree with you I have an X36 HOTAS setup as well and Saitek won't release drivers for that either. Wish I'd cought the Microsoft wheel now. Unfortunately I can't return it as it is 2 years old.

Fianlly. Top stuff, shame I just went a bought a M$ mouse though. Think I will install becuase I do prefer the iFeel shape and buttons even if the oFeel stuff doesn't work in XP

Yup. Mouseware doesn't work properly on WinXP, Especially with the iFeel mouseman. Logitech say that they will evaluate weather to release drivers for XP after it is released based upon the amount of people who request it. This is why I have just bought a Microsoft mouse. Works great under XP

Definately get a bigger hard drive. 6GB just can't cut it. For a new graphics card I would suggest a GeForce2 MX400. You can pick them up for about $95 pretty much anywhere.

O.K. that works better. It now detects as a 3 button mouse and I can program the wheel button. However, I still can't program the thumb button. Any more ideas?

When you say "manulally selecting 900b99en drivers" Can you take me through the EXACT steps you took to get it to work. Did you install Mouseware then unpack the installer and substitute drivers?

I'm using USB because the iFEEL Mouseman doesn't support PS2. I tried all of the driver substitution listed above but had no joy. The Moseware control panel fails to recognise the Mouseman and detects it as an M series no matter what drivers I install.