CompuServe Thread

PC screen color HELP!

6 messages in this thread
#84167From: Eugene CottleJan 7, 1993 8:04 PM
I am having trouble with the colors on my PC screen with my bridgeboard. The PCColor software refuses to remember the color settings I give it. I have figured out this much. When I change my color preferences, and save the settings, it writes the settings to sys:pc/system/sidecarsettings.table. I can see by checking the date on the file that it is getting saved. However, some PC software packages reset the colors (DOSSHELL for example). When the colors reset, the PCColor software ignores the values I saved, and returns to the original, 'factory set' colors. Also, when I first start PCColor, it ignores my saved settings, and gives me the 'factory' colors. Nothing I do will bring my colors back. Also, when I am trying to set the color preferences, sometimes the color requestor behaves eradically. If I set one color, then set another one, sometimes when I go back to the first one the gadgets will have moved. Can anyone shed some light on this for me? – E Cottle
#84707From: Marion J DelandJan 11, 1993 1:01 PM
Eugene, Which versions of Workbench and JANUS ar you using? WB 2.04 and Janus 2.0 (or earlier) don't get along. You need Janus 2.1. Though if you can use PCPrefs at all, that's probably not the problem. Marion CROSSINGS Newsletter for the Bridgeboard, etc.
#84784From: Eugene CottleJan 12, 1993 6:57 AM
Marion, Thanks for the reply. I was beginning to wonder if I had thoroughly stumped everyone. I am using WB 3.? (39.29) and Janus ?.? On PC bootup it tells me I have Janus handler V36.85 and Janus library v36.83. I hope it is the most recent version, since it was in an A2386 I bought just before Christmas. As I said, the software appears to have some 'factory set' colors stored somewhere, which it reads instead of reading what I saved. Any other suggestions you have would be greatly appreciated. Thanks. – E Cottle
#84958From: Marion J DelandJan 13, 1993 8:52 PM
Eugene… WB 3.?–Does that mean you're running a 4000? Lucky you! There may be some idiosyncracies with a 386 BB in an A4000, I haven't heard enough feedback to know yet. But the PCPrefs problem I mentioned wouldn't apply. Try removing the SIDECARSETTINGS.TABLE and then re-saving your Bridgeboard menu settings to create a new one. Or did you do that already? Sorry, I don't really have much to suggest. Marion CROSSINGS Newsletter for the Bridgeboard, etc.
#85007From: Eugene CottleJan 14, 1993 5:59 AM
Yes, I have a 4000. I won it in the 4000 reasons contest. Lucky is right. I haven't tried removing the file, that's a good suggestion. I will let you know how it works. Commodore has a 'CommodoreExpress' gold service customer support. I don't know if that is unique to the 4000's. Anyway, customers can actually get technical support by phone. I tried asking them the question, and they said that they did not handle the BB's, that I needed to talk to my dealer. I showed my dealer the problem, and he is completely baffled. He is supposed to have called his tech support people yesterday. I am finding that very few people, including Commodore, know much about either the 4000 or the BB. We're breaking new ground here. – E Cottle
#85008From: Eugene CottleJan 14, 1993 6:15 AM
I tried it. No help. I have come up with a new theory, though, since the last message I posted. There are some 'factory set' colors, which the screen reverts to when it cannot find, or cannot access the SIDECARSETTINGS.TABLE file. However, I have discovered that the screen is *not* always reverting to the factory settings. When I save a set of colors, then close the window and reopen it (or select 'restore settings'), it will come up with a completely different set of colors. They are not the factory settings, and they are not the colors I saved. However, they are repeatable. For example, if I save color number 5 as pure red, it will consistently come back as pure yellow. There are other predictable combinations I have noticed. It looks almost like the software is writing the colors to the file in one format, and when it reads the file it expects to find them in another format. That would explain the behavior I am getting. – E Cottle