Laptop output to tv question. Signal issue.

aliasojo

Just bought a kit that is supposed to allow me to view my laptop stuff on the tv.

It's not.

I'm getting a message on the tv which says 'Unsupported signal. Adjust your pc output'.

I've had a look but can't find very much to adjust. Laptop is an old Dell Inspiron 1300 and tv is a Sony KDL40D3000.

Is the laptop just too old/got poor graphics and it can't output the signal the tv is looking for? (VGA cable btw, both ends.)

NiVZ

Hello,

If it's VGA at both ends it should definitely be possible to get it working.

As Paul_R says, try a different screen resolution and try switching your laptop to 'external monitor' as you would if you connected it to a projector (usually by pressing FN key + F5)

Also, on your TV, make sure you are selecting the PC or VGA source. My TV has a DVI port (flat screen monitor connection) and if I pick the HD source on the TV instead of PC source I get the same message.

NiVZ

aliasojo

Thank you. It's working now. I had fiddled around with the resolution but didn't know what it should be so was very much just making stabs in the dark. Obviously I didn't hit on the right one.

Appreciate your replies. :beer:

aliasojo

More help please? Although I had got the video part sorted out with your help, I had no sound (I'd bought the wrong cable at the time). I've since got the correct cable but still have no sound. What am I doing wrong now?

Cable goes from headphone socket on laptop, to 'pc' section on tv (this has vga and one single 3.5mm input). I set the laptop sound to 'headphones' but still nothing. When the cable is plugged in, I get no sound from the laptop either btw, no matter what it's set to.

CHR15

Does it work with headphones plugged in??

If so, the issue is at the TV end, wade through menus on the telly.

aliasojo

Turned out it was a codec problem. Cd's played ok but DVD's had no audio. No idea how or why this happened because I used to be able to watch DVD via Windows Media Player so I don't know what changed.

I had jumped to the assumption that the cable or some setting somewhere was the problem when it fact it was neither of those things.

Anyway, sorted now.