I've found this hack somewhere on the internet, it works for my R2 player.
1) Turn on the player with no disc in the tray
2) Press the Open/Close button to open the tray
3) Press the info button, the firmware version shows up (mine was 080220.13.B.1080PXKEG)
4) After the version info disappears, close the tray again by pressing the Open/Close button
5) At this point, it will show "no disc" at the top. Press the Info button again, and this will disappear.
6) Now type the code that applies for your region (R2 is 57538). A '2' will briefly show up at the top left corner
7) Now press 9, and 9 will show up in the top left corner
8) Power off the player, and turn it on again. You'll have a multi region player
I've found the following codes at the 1080P7 hack:
R1 - 29334
R2 - 57538
R3 - 56732
R4 - 76884
R5 - 53814
R6 - 24462
Not sure if all are correct, but it worked for R2.
Saturday, 29 January 2011
Thursday, 13 January 2011
Top find - Remotely switch on Remote Desktop Client
How to Remotely Turn On (and off) OS X Screen Sharing
This procedure keeps security in mind. The idea is to turn on screen sharing while you need it, and then turn it off when you’re done. Also, the write-ups of Tim Boland and Chris Brewer were very helpful in figuring this out.
1) SSH into your remote OS X machine with an administrator’s log in and password.
3) Login using a VNC client.
As I mentioned, TightVNC worked for me; for some reason, RealVNC and UltraVNC didn’t. Your password is “mypasswd” (see the -vncpw flag in the above command; you can — and should — change this).
4) When you are done, turn of screen sharing using your SSH session:
This procedure keeps security in mind. The idea is to turn on screen sharing while you need it, and then turn it off when you’re done. Also, the write-ups of Tim Boland and Chris Brewer were very helpful in figuring this out.
1) SSH into your remote OS X machine with an administrator’s log in and password.
2) Enable Remote Desktop (a.k.a. Screen Sharing, a.k.a. VNC) with this command:
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -access -on -clientopts -setvnclegacy -vnclegacy yes -clientopts -setvncpw -vncpw mypasswd -restart -agent -privs -all3) Login using a VNC client.
As I mentioned, TightVNC worked for me; for some reason, RealVNC and UltraVNC didn’t. Your password is “mypasswd” (see the -vncpw flag in the above command; you can — and should — change this).
4) When you are done, turn of screen sharing using your SSH session:
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -deactivate -configure -access -offFriday, 26 November 2010
Finally - embed yoube clips with valid HTML
Anyway, this is how you do it:
< object type="application/x-shockwave-flash" data="[INSERT VIDEO URL FROM EMBED CODE PROVIDED HERE]" width="400" height="326">
< param name="movie" value="[INSERT VIDEO URL FROM EMBED CODE PROVIDED HERE]" />
< param name="FlashVars" value="playerMode=embedded" />
< /object >
That's all there is to putting a video or slideshow from www.youtube.com into your pwn valid html.
Wednesday, 24 November 2010
Forms not submitting from an iframe (IE8, IE7)
So, we had a login system that was written in PHP.
The parent site got moved and so for reasons we can't remember, the site got a new URL. We then ended up putting the login system in an iframe...
... and the login stopped working in IE7 and IE8.
The solution is a simple header line at the top of the page inside the iframe:
What this does is let IE retain the cookie/session information rather than start a new one each for each page.
The parent site got moved and so for reasons we can't remember, the site got a new URL. We then ended up putting the login system in an iframe...
... and the login stopped working in IE7 and IE8.
The solution is a simple header line at the top of the page inside the iframe:
<?PHP
header(‘P3P: CP=”CAO PSA OUR”‘);
?>
What this does is let IE retain the cookie/session information rather than start a new one each for each page.
Thursday, 11 November 2010
Google Does not Use Keywords
Its pretty clear - please check out this link if you are in any doubt about your SEO stratgey:
Google Webmaster Central
Google Webmaster Central
Tuesday, 9 November 2010
Manually Install SSL Certificates
So - you have a domain ready to go, you have paid verisign for their seal of SSL approval.
How and where do the files go?
First off, you need to generate a certificate request, which should give you a .csr request file and also a private.key file (or the ascii text that goes inthese files). The 2 files go to verisign where they generate an SSL certificate key, which is typically emailed back to you.
You will also need to get the appropriate Verisign 'Intermediate CA Bundle' which is normally flagged up in the email you receive when you purchase the certificate.
Now place the 3 files in to a nice, safe bit of your host, something like:
/home/[MY-DOMAIN\/user/cert/public.crt (the one you get from verisign)
/home/[MY-DOMAIN]/user/cert/private.key (the one you generated at the start of the process)
/home/[MY-DOMAIN]/user/cert/intermediate.key (downloaded from the verisign site)
Now you need to edit the host settings for your host (which are normallyin your vhost.conf file) Somewhere in your block, you need to add/edit:
# Begin SSL Config SSLCertificateFile /home//user/cert/public.crt
SSLCertificateKeyFile /home//user/cert/private.key
SSLCACertificateFile /home//user/cert/intermediate.crt
# End SSL config
Now, save the updated vhost.conf file and restart apache:
> service httpd restart (for Centos and linux users)
How and where do the files go?
First off, you need to generate a certificate request, which should give you a .csr request file and also a private.key file (or the ascii text that goes inthese files). The 2 files go to verisign where they generate an SSL certificate key, which is typically emailed back to you.
You will also need to get the appropriate Verisign 'Intermediate CA Bundle' which is normally flagged up in the email you receive when you purchase the certificate.
Now place the 3 files in to a nice, safe bit of your host, something like:
/home/[MY-DOMAIN\/user/cert/public.crt (the one you get from verisign)
/home/[MY-DOMAIN]/user/cert/private.key (the one you generated at the start of the process)
/home/[MY-DOMAIN]/user/cert/intermediate.key (downloaded from the verisign site)
Now you need to edit the host settings for your host (which are normallyin your vhost.conf file) Somewhere in your
# Begin SSL Config SSLCertificateFile /home/
SSLCertificateKeyFile /home/
SSLCACertificateFile /home/
# End SSL config
Now, save the updated vhost.conf file and restart apache:
> service httpd restart (for Centos and linux users)
Monday, 8 November 2010
Javascript based Flickr slideshows
There is only one way to to:
phpflickr.com
However, if you know a little simple XML, then php has everything you really need already built in...
More to follow when its tested.
Subscribe to:
Posts (Atom)