OK so to take up less desk space I bought an inland Video Switch to share my monitor with my Mac and PC. It worked fine untill today. I booted up the PC and turned on the monitor but after the starting Windows XP screen it goes blank. If I press buttons on the monitor I get a No Signal sign flickering. I booted up the Mac and switched over the video and no problem on that end. I switched back to the PC and moved the mouse arround and hit the spacebar and no video. I checked all the conections and they're all fine and like I said I get a couple seconds of video when booting then after the Windows XP logo...nothing. Is this another stupid Windows thing like computers not starting up if you don't have a floppy drive? Any sugestions or ways to bypass this. Thanks much.
Anonymous
User login
Please support the defense of Ukraine.
Direct or via Unclutter App
Active forum topics
Recent content
Navigation
No Ads.
No Trackers.
No Social Media.
All Content Locally Hosted.
Built on Free Software.
We have complied with zero government requests for information.
OK, so it would seem that the videoswitch isn't my problem. I pluged the PC into another monitor and I get the same problem. I can boot into Safe Mode and everything seems fine but when booting normally no video after Windows XP start-up screen. I guess I'll take this one to a Windows related fourm...
I've had that happen on a 15" monitor that was a few years old. Sometimes it's because the resolution/refresh rate is too high.
My way around it was to use a newer/larger monitor (17"). Then I could set the resolution to something the smaller monitor could handle.
Used both a 17" ViewSonic CRT and a 17" ViewSonic LCD lower resolution/refresh is no affect. I'm only glad I got my Mac up and running so I can still do things. I'll just have to wait and see what other sugestions come in untill I can get it to work again.
Is the driver for windows corrupt? That could be one possibility
I check the version of the nVidia driver I had 6.1.7.7 and then went to nVidias site and sure enough they had an update and installing that did the trick. I'm not sure if the driver was bad or just a bit out of date but thanks for the sugestion.