Weird video behaviour

[Rob Beattie]

My system consists of an abit is7 mainboard with a P4 3.0GHz cpu and
Ti200 graphics card. It is dual booting WinXp with Win2K and my
monitor is an iiyama prolite 431 tft.
For some time now one of the internal fans has begun to bet noisier.
So I opened the box and had a look around at all of the fans. After
discovering that it was the chipset fan I put everything back
together again and booted the system up. The boot process got as far
as the windows xp is starting screen and the the monitor came up with
a 'no signal' message. It kept doing this when I tried to run winxp
but was fine with win2k. So I loaded xp in safe mode and the problem
went away. It seems to me that maybe there is a driver issue but why
would this be if I just opened the system up? To get it running xp
properly again I had to use the option of using the settings when the
computer last ran succesfully (you get this when you press f8 during
boot).
Does anyone know why this would happen?

 

[johns]

Doesn't sound cause and effect at all. My experience with dual
booting is that sooner or later, you are going to crash the system
in one OS, or the other, and that is going to whack the startup
files, and try to over-ride the bootup with a chkdsk sort of thing.
I suppose that could be something like the W2k video driver is
trying to over-ride the WXP video driver. Maybe safe mode sorted
that out. Still, what a junker. Why would you want to dual boot
essentially the same OSes? I've seen dual 98 - 2k , but that's
because lots of vendors took their sweet time updating 98
drivers for just about everything when 2K first hit the market.
I'm betting by now, you've got a hard drive going bad, and it
is causing those chkdsk over-rides. You'll see this one again.

johns

 

[Michael Hawes]

My system consists of an abit is7 mainboard with a P4 3.0GHz cpu and
Ti200 graphics card. It is dual booting WinXp with Win2K and my
monitor is an iiyama prolite 431 tft.
For some time now one of the internal fans has begun to bet noisier.
So I opened the box and had a look around at all of the fans. After
discovering that it was the chipset fan I put everything back
together again and booted the system up. The boot process got as far
as the windows xp is starting screen and the the monitor came up with
a 'no signal' message. It kept doing this when I tried to run winxp
but was fine with win2k. So I loaded xp in safe mode and the problem
went away. It seems to me that maybe there is a driver issue but why
would this be if I just opened the system up? To get it running xp
properly again I had to use the option of using the settings when the
computer last ran succesfully (you get this when you press f8 during
boot).
Does anyone know why this would happen?

Take your pick, Gremlins/Murphey's Law or just blame Micro$oft, like
everybody else does.
Mike.

 

[dawg]

What is your refresh rate set to in XP?When you booted in Safe mode the
refresh rate is set to 60hz. That is what it should be. If your normal
refresh rate is set too high you could get a no signal error.

 

[JAD]

bump the vid card slightly, making it loose connection while playing with
the fans. Boot, Xp doesn't see the card...you go and check the cable and
move it, the card clicks back back in place poof!!

 

[Rob Beattie]

What is your refresh rate set to in XP?When you booted in Safe mode the
refresh rate is set to 60hz. That is what it should be. If your normal
refresh rate is set too high you could get a no signal error.

Nope, the rate is 60Hz - I have not meddled with this value at all.

 

[Rob Beattie]

Doesn't sound cause and effect at all. My experience with dual
booting is that sooner or later, you are going to crash the system
in one OS, or the other, and that is going to whack the startup
files, and try to over-ride the bootup with a chkdsk sort of thing.
I suppose that could be something like the W2k video driver is
trying to over-ride the WXP video driver. Maybe safe mode sorted
that out. Still, what a junker. Why would you want to dual boot
essentially the same OSes? I've seen dual 98 - 2k , but that's
because lots of vendors took their sweet time updating 98
drivers for just about everything when 2K first hit the market.
I'm betting by now, you've got a hard drive going bad, and it
is causing those chkdsk over-rides. You'll see this one again.

johns

This has only ever happened twice - both times after I had opened up
the case. The first time about 6 months ago the signal returned after
rebooting 3 or 4 times and the last occasinon I had to select the
'computer last ran succesfully' option before the video returned
without having to use the safe mode.
Also the reason I have an XP/2K dual boot is that I have come across
software that runs on one but not the other. As well as this I trial
some installations on 2K before putting it on XP so that I minimise
the number of uninstalls in XP.