PC panel prices to rise in July

"Prices for PC-use panels are estimated to rise in July, according to industry sources. "

Search News

  • Scrolling Image
flat panel

PC panel prices to rise in July

According to industry sources we can expect to pay a little more for PC-use panels in July.

Prices for PC-use panels are estimated to rise US$2-5 in July, according to industry sources. Panel makers are requesting a quote increase of US$3-5 for their 17- and 19-inch monitor panels, the sources said. Demand for standard monitor panels continue to be strong in July and panel makers keep raising prices while LG.Philips LCD recently stopped producing 19-inch standard panels at its 7.5-generation (7.5G) plant while still manufacturing 19-inch widescreen panels at the plant, the sources indicated.

Notebook panel prices are set to increase US$2-3 amid a strong season, the sources added. Notebook makers expect a quote increase for notebook panels in the future, so they are set to procure materials and launch an overbooking scheme, the sources explained. Although the range of average price increase for notebook panels will stay at US$2-3 this month, an unspecific panel maker has offered a US$5 price increase for its notebook panels, the sources said.

I wonder how much the panel price increase will be felt by the consumer.

Discuss in our forum
«Prev 1 Next»

Most Recent Comments

03-07-2007, 12:23:11

One of the x2 systems I got running a very stripped version of XP, works really well, has F@H mostly going on it but sometimes it handles file movements and the odd game.

The system works well, however, out of the blue yesterday I decided to run an old game on it (Close Combat 5), and figured I could leave an F@H core running. I turned off the F@H client running as core_0 and noticed that the processor usage gauge on both taskmanager and the G15 performance display didn`t drop one core down to zero (as it`d usually do), but showed both cores cut down to 50%. i.e. two cores still showing but instead of core_1 still running at max, it showed the workload shared between the 2.

This is the first time I`ve observed this for weeks, so I have no idea of how/what/when this has happened, as with a machine working fine u don`t seem to question much.

But what`s going on there ? I`ve chucked in replacement core.cfg files to see if it was that, but it stayed the same - infact anything I run seems to be shared over 2 cores instead of one, with a fluctuation here and there - and yet 2 cores display on all testing things.

U reckon I re-application of the AMD patching lineup is in need here ?

03-07-2007, 12:37:48

AFAIK that's how it's supposed to work... Tried setting the affinity for the process in taskman?

03-07-2007, 14:32:12

Hey Frag,

Nah man, when I used to run a core, it would only fill up 1 side of the cpu meter and likewize on taskmanager (only 1 core doing the work).

Now I click on something and they both level the same just for 1 instance.

That`s another thing, affinities don`t seem to stick. Run something, assign it - run it again and it`s back to 2 cpus. Used to be able to tell something like winrar just to use core_1 or something.

03-07-2007, 15:21:52

Yeah, sounds strange. Normally the load gets balanced over both cores unless you manually change the affinity of a process to one of the cores. Sounds like you're on the right track with the affinities not sticking, though I don't know what would fix it. As you said, maybe reinstalling the AMD patches? There isn't a performance hit balancing over both cores is there?

03-07-2007, 15:47:42

Performance-wize everything seems kewl.

Think I`ll re-go thru the AMD patch lineup and see what happens. brb

03-07-2007, 16:59:50

Nep, re-went thru the patching process, checked the Throttle thing and it still does the same.

I can set Affinity, whilst the prog is running, and correct things like F@H to use the correct cores. However, closing them down and starting them up and I need to do it again as it`s all forgotten.

Hmm I wonder what`s going on here, my other x2 does as it`s s`posed to.. Run F@H for core_0 and only core_0 is active.


03-07-2007, 17:48:04

I never bother setting affinity to anything. I just let the task manager do its thang

Works fine

03-07-2007, 18:32:02


I can set Affinity, whilst the prog is running, and correct things like F@H to use the correct cores. However, closing them down and starting them up and I need to do it again as it`s all forgotten.

Bah, I misunderstood. I was thinking that setting the affinity had no effect at all for you. ^^ this is what happens on my computer too.

However, if you want your computer to 'remember' the core affinity for a program then I'm sure you have to create a special shortcut or use a program like SetAffinity.

03-07-2007, 18:49:23


I never bother setting affinity to anything. I just let the task manager do its thang

Works fine

Yeah it`s not my normal practice unless I got something that `has` to run, but something`s screwy here, I don`t know what`s going on atm. Just has another rip on CC5, and instead of core_0 filling up (game only uses 1 core), both cores filled to 50% max - wouldn`t go over 50.

Meh, I`ll see what I can come up with. Good thing is the pc is not acting up beyond this..

I`ll look at the nVidia drivers 2morrow, I read a line or 2 about some variants not getting along and so on. Bit sketchy, but was kinda the last thing I "did" to the pc (try out the latest drivers), so I`ll entertain some more reading on that.

Register for the OC3D Newsletter

Subscribing to the OC3D newsletter will keep you up-to-date on the latest technology reviews, competitions and goings-on at Overclock3D. We won't share your email address with ANYONE, and we will only email you with updates on site news, reviews, and competitions and you can unsubscribe easily at any time.

Simply enter your name and email address into the box below and be sure to click on the links in the confirmation emails that will arrive in your e-mail shortly after to complete the registration.

If you run into any problems, just drop us a message on the forums.