Page 1 of Scary Movie doesn`t work on Samsung 709
Hack Help Forum
Scary Movie doesn`t work on Samsung 709
I recently brought myself a Samsung 709 DVD player becuase i thought they were a reasonably good model. When I discoved that i could get Region 1 discs cheaper than Region 2 and quite easily I was determined to get my player to be multiregion. So when i found this site i decided to buy my first region 1 DVD movie which was Scary Movie. So when i recieved it in the post i couldn`t wait to do the hack that i found on this site. So i completed the hack successfully. I put the disc in the tray and guess what it froze on the FBI Warning.
If you can help my please reply to this.
I need some help
RE: Scary Movie doesn`t work on Samsung 709
This is a very well known problem - the solution can be found over at:
http://www.709online.com
RE: Scary Movie doesn`t work on Samsung 709
Specifically, you have to insert the disc, look at the front panel and as soon as the panel display changes from LOAD to 00:00 (but BEFORE the FBI screen appears on your TV), quickly press the TOP MENU button on the remote. This takes you past the FBI screen and on to the main menu.
Given that a number of different players (not just Samsung models) have the same trouble with Scary Movie, this is probably an issue of dodgy disc mastering rather than anything to do with the player.
The 709 is an excellent player, so don`t worry about it - you were just unlucky that your first disc purchase happened to be one of the tiny number of titles that cause problems.
Mike G
Samsung Firmware Page - http://www.709firmware.fsnet.co.uk/
RE: Scary Movie doesn`t work on Samsung 709
Found this out the otehr day a friend of mine has a 709 and his didnt work either so i told him to try the sammy own remote hack not the all 4 one one. It works fine now jsut to let you know
RE: Scary Movie doesn`t work on Samsung 709
So i take it this is the same for the Samsung 511?
RE: Scary Movie doesn`t work on Samsung 709
Hmm. I didn`t think the 511 had a problem with Scary Movie!
If it does, though, then the same workaround should fix it.