> the last one "working with less colours" and "8-bit (256) colours" made
> difference.
Wow that's interesting. What sort of graphic card do you have?
Graham
> the last one "working with less colours" and "8-bit (256) colours" made
> difference.
Wow that's interesting. What sort of graphic card do you have?
Graham
Nothing special, Intel HD Graphics 630, says device manager
Thanks
Darko
OK just to add few words more,
I knew that new monitor was the only difference (and yes, the new resolution
was 2560 x 1444),
so first thing to try was run to basement and take the old one Samsung 22" back
and put resolution back to 1920 x 1200
Removed new hardware AOC monitor under Control Panel Devices and set as Generic
PnP monitor, removed monitor driver as windows asked.
All the same.
Btw. whatever I did I rebooted after to be sure, Jeff, Jeff :-) as SSD reboot is a blink
NOW I was confused and then asked a question
At a moment I have my AOC 32" back
Thanks for all yours opinions
Darko
Oh.. plus I completely removed SB and reinstalled back the fresh one so I am
pretty sure nothing missing there
Darko
>> the last one "working with less colours" and "8-bit (256) colours" made
>> difference.
> Wow that's interesting. What sort of graphic card do you have?
Thanks for the compatibility mode idea, Graham. I swear, this was not even
the last item on my list of possible solutions. And it does not make any
sense to me.
Thanks again!
Friedrich
Hi Friedrich,
Well when Darko said it worked my first thoughts were that it was
something like the Catalyst Control Centre issues that we've had with
the Clarion IDE and disabling CCC.exe and MOM.exe (the monitoring
program) would do the trick.
But maybe what's needed is the latest Intel HD Graphics 630 drivers
Graham
Hi Graham,
> Well when Darko said it worked my first thoughts were that it was
> something like the Catalyst Control Centre issues that we've had with the
> Clarion IDE and disabling CCC.exe and MOM.exe (the monitoring program)
> would do the trick.
>
> But maybe what's needed is the latest Intel HD Graphics 630 drivers
But the weird thing is that he only changed the monitor and not the graphic
card. Hmmm... but I am sure he also increased screen resolution and this
might have caused the graphic card issue (low on memory?).
Friedrich
Hi Darko,
> As Graham pointed me, I tried just everything under compatibility mode,
> the last one "working with less colours" and "8-bit (256) colours" made
> difference.
>
> I did changed monitor to AOC 32" but didn't changed graphic card so I
> wasn't
> think at this direction
IMO, this does not make any sense at all <g>. Why should "8-bit (256)
colours" make a difference in this case? And you did not even change the
graphic card (no new drivers, etc.).
> Now, while I can live with less colours do you suggest to try with 2018
> prerelease anyway?
You can try 2018 because this will be the basis for new SetupBuilder
versions. But the IDE does absolutely nothing with colors etc. so you'll
definitely run into the same problem in the future.
It still does not make any sense to me. You changed the monitor to AOC 32"
and this "locks" a Windows application. Setting compatibility mode to
"8-bit (256) colours" (brings us back to the Windows 95 days) and it's
working again. What a nightmare.
Friedrich
Friedrich,
> IMO, this does not make any sense at all <g>. Why should "8-bit (256)
> colours" make a difference in this case? And you did not even change the
> graphic card (no new drivers, etc.).
Sounds suspiciously like resource problems. Now that he can open the
SB IDE I would shrink it and save it, reset the colors and restart the
IDE to see it works. If it does he's running really low on video
memory.
--
Lee White
RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com
Creative Reporting: http://www.CreativeReporting.com
Product Release & Update Notices
http://twitter.com/DeveloperPLUS
Lee,
> Sounds suspiciously like resource problems. Now that he can open the
> SB IDE I would shrink it and save it, reset the colors and restart the
> IDE to see it works. If it does he's running really low on video
> memory.
Yes, I think you are right. With the new monitor and a higher screen
resolution, video memory (or an outdated driver) might be
the culprit here.
Funny thing is that the SetupBuilder IDE itself is not resource hungry at
all. It still works fine on Windows 2000 <g>.
Friedrich
There are currently 1 users browsing this thread. (0 members and 1 guests)