C2k Help
Non-C2k Issues => Legacy Networks => Topic started by: Bill Bixby on June 22, 2006, 10:50:18 AM
-
I'm starting to have a bit of bother with our 2.4 network, which is on its last legs. Whenever you log on to some of the stations the display is corrupted - screen is mostly black, some icons are visible but they're huge. These are screens that have previously worked fine on these PC's and then they suddenly go like this. None of the pupils are set up to save their desktop settings and I haven't had this problem until this year. Swapping the monitor works but then I've been able to use the supposedly faulty monitor on another 2.4 workstation with an identical setup. It's bizarre and I haven't investigated it fully as it means lugging monitors about and it's my least favourite thing, next to removing chewing gum from CD drives.
Just wondering if anyone else has had the same problem.
-
Haven't had this problem but I'm wondering if it's a screen resolution problem. Have you tried creating a new desktop, setting it to 640x480 and allocating it to a few test users.
-
Hi, hade that same problem here a while back. Casper is correct. You could also try reducing the color. Some of our older monitors did not like settings above “High Color (16 bit)”, when I tried “True Color (32 bit)” I got the problem you describe.
-
It's not a resolution problem as far as I can see. These machines ran for years with these monitors at 800 by 600, I can't understand why they would go all of a sudden. It's bizarre that I can swap another identical monitor model over and it'll work.
-
I would try creating a new desktop just in case the current one is corrupt.
-
I used to get the same problem when switching from old machines to new machines and back again on the legacy network. Try going to a macine you can log in on ok and change settings down one at a time log off and go to a problem machine. If this doesnt solve it then update your graphics drivers is the only other idea I can think off.
-
Just a quick update in case anyone else comes across this problem. I discovered that it's a problem with our RM workstations with on-board graphics - they just don't like non-RM monitors. I mistakenly thought non-RM monitors I had put on these workstations were working (because they came up with the logon screen), but when you actually logged on the display became corrupt.