From:  rem
|
On: 2007/12/28 09:05:52
|
Hi folks,
Got a problem here. I set up a computer (having some spare parts) for my daughter .
The problem is the IISonic TFT 15" display which doesn't seem to be liked by XP. The screen comes without any firmware or drivers. It is recognized as an ordinary PnP screen. The Graphics Controller is an Intel 82815.
When switching the computer on, I have a 800 x 600 16 colour display, and no way to change that.
When booting the machine without any screen... and then plugging the screen back into place, I can go to 1280 x 1024 24 bits.
WHY???
|
|
|
From: JOK
|
On: 2007/12/28 14:09:14
|
|
http://www.inte...aphics/intel815/sb/CS-009151.htm ?
|
|
|
From: rid
|
On: 2007/12/28 14:58:03
|
Normally, I'd expect you to be able to choose in a list of possible monitor varieties in windows and you should choose "Generic LCD at 1280 X 1024 (if that's what you've got). In most cases, I'd expect the Plug 'n' Pray system would identify the screen correctly. You could try deleting anything monitor-related in Device Mangler and have the system re-detect the monitor (hopefully correctly).
Or get another O/S, like Ubuntu... :)
/RID
|
|
|
From: rem
|
On: 2007/12/29 04:56:42
|
JOK:
the info given in the Intel page is OK, but there is NO firmware, driver, or other display related software for this LCD TFT screen.
rid:
I tried Ubuntu. Ok for me, but the rest of the family does have some problems related to configuration.
I also tried deleting graphics controller and screen stuff, but to no avail.
Thanks both of you for the input.
FFR the only thing working right now, is unplugging the display while booting the computer, then when Windoze makes its standard noise, plugging the screen on.
|
|
|
From: JOK
|
On: 2007/12/29 08:27:46
|
|
u've deleted the device AND the driver for the monitor? and the GC?
|
|
|
From: rem
|
On: 2007/12/29 12:30:14
|
Yes mate, I deleted everything. Windoze didn't care a lot though. It rebooted with a 640 x 480 full colour display; No way however to get beyond that resolution; Immediately afterwards it started redetecting the intel graph cont. etc. and the same s*** began all over again.
|
|
|
From: rem
|
On: 2008/01/04 11:11:56
|
I close this conversation. According to Intel there is no solution. Its the screen's they say. The displaymaker says it's Windows, Microsoft says it's Intel no longer supporting their own chips.
They are all right and wrong I guess. The workaround mentionned earlier does the job for the time being.
Thanks to rid and Jok for their input.
|
|
|
From: rem
|
On: 2008/01/04 11:12:16
|
|
50 points for both of them
|
|
|
From: rem
|
On: 2008/01/04 11:12:28
|
|
This conversation is now closed.
|
|
