How to Burn PSX Disk to Play on a Plastation 1 in 2018.


For a long time I always wanted to mod my psx to play burned CD’s , however I didn’t know how to mod playstation1’s and I was afraid to break mine. Recently on the recycled electronics section in the basement of my building someone threw a playstation 1 with a strange adapter connected to the serial port on the Playstion 1.


After googling the name of the device I realized this was an action replay adapter which would be used to load backup psx games or imports. I turned the machine and it booted into a Chinese language menu. I went to google and learned how to use the adapter, basically you put an original psx disk and turn on the psx with the action replay and boot up the machine. then the disk will spin but stop and then you switch it for your burned disk.

So I found a link on the internet with all all the psx games available for download and I burned my CD. I the files came in a zip folder with files that contained a cue and bin files inside . The majority of tutorials said to use IMGburn to burn the cd.


I burned the image at 10x and then took it out of my CD burner and then I went to my psx and turned it on. I removed the real psx disk I had on it after it stopped spinning and put this new disk. I crossed my fingers and nothing happened. The disk just spinned and spinned and then stopped . I tried 3 times and no luck :( .

I guess maybe I burned the disk at a high speed since many blogs said to burn at slow sleeps. I tried burning at 2x , 4x, 1x and no luck :( only once I was able to get a menu to boot from a Tekken game I burned but it will fail to load the game.


I spent a whole night up reading why this process was not working when it occurred to me that I had another psx which I had my original psx so I put the adapter on it and booted the real game and then switched for the backup cd I had created and I was able to get further.

it was 4am in the morning and I was able to get the games loaded but the sound was stuttering and music out of sync. I went to bed knowing that was getting close to solving this issue.

The next day I searched online and many people complained about this same issue. It was hard to find information because this information is outdated since no one is burning psx games anymore and most articles are from 8 to 9 years ago.

What I found was that you must use high quality disks to burn your CD’s and burn at 8x on most recent CD burners from the past 4 years. I went to Best Buy and bought these CD’s verbatim is the best brand you can buy and also the cd’s look cool since they look like 45 records. Who remembers those right.


I went home that night and downloaded crash bandicoot 3 put it on the burner and burned the cd and waited. Once the CD ejected I took it out. booted the psx with the a real psx disk and then did the swap
and guess what. :)


The first thing I heard was Sony computer entertainment presents and then I saw the intro for crash bandicoot and a big smile appeared in my face. I was able to play a few stages and all of them worked fine.

The new day I setup a script to download all the games from the site that I found and download them to a 2 terabyte disk I have and I burned other games and all of them worked.

So what was wrong with the psx that I found ? Well two things were the problem with that machine. One is that the lens on that machine was already worn out eventually the psx lasers start losing sensitivity and need to be replaced. you can change the potentiometer and try to make them work which I did but still had errors. However, I knew I took care of my original playstion and its lens was fine.

Second the quality of the disks I was using was important so if you are burning psx games in 2018 you have to make sure you have a machine with a good lens and use verbatim or better quality disks :)
and use imgburn at 8x speed.

Thanks for reading :)


Kubernetes vs AWS ECS after my own experience using them.

kubernetes vs ecs

At my job we went ahead and decided to move some of our applications to Docker container. We had to decide on a technology that would run our containers on production . 99% of our stuff runs in AWS so the choice by the team was to use ECS. Part of it is that ECS is a managed service from AWS, there is great documentation and it gave us freedom of managing the cluster.

here are the pros and cons of using ECS after a year of running it in production.

Managed by AWS but there are some gotchas
Documentation is clear
it is fairly easy to run containers on it.
Streaming logs into cloud watch is very easy.

The console is awful
tooling is a bit of a pain. We managed it by using cloud formation templates.
ECS agent needs to be upgraded all the time . The ecs agent is the container that communicates to the AWS ECS control plane and launches containers or stops them but AWS is always pushing updates that you need to work out the details on how to do the updates of the agent.
Cron scheduled tasks are awful to manage no visibility since everything runs via cloud watch events.

you still have to do some support of the instances and provision them and though you use cloud formation templates for that you still have to manage disk space, sizing and monitoring of the ec2 instance.

Which then made me look into AWS FARGATE which basically allows us to launch containers in ECS without having to manage the ec2 instances everything is transparent to us. Which is great so our job is only to manage container deployments. It also allows containers to connect to services inside our vpc without us having to launch instances inside our vpc. They manage all that magic internally at AWS and the security.

But why did I look into Kubernetes.

Kubernets is everywhere and it is taking everything that gets into its path. I used to work at a company where they had been using kubernetes in CoreOS the whole thing was a mess. We provisioned the instances with ansible and then deploy kubernetes on it. I think the problem at the time was the way that things got launched and it was hard for engineers to understand how it all worked. It was all in place already before I joined the company and everyday we had problems.

A lot of the problems with Kuberentes is mostly misunderstanding how it works, and how to set it up and how to launch applications. I recently build a cluster to test stuff and use it as a playground. Configuring the cluster manually and not using Kops was much better for me to understand how everything works and how to debug it if it breaks.

Even when I configured everything by hand it didn’t take long. I was eating a cereal bowl and watching youtube videos when I started the project in about and hour and a half I had Kubernetes deploy and Kubernetes UI. I knew how to provision nodes, make deployments, look at logs, describe services and expose services via a load balancer in less than 2 hours. Which is great as an exercise.

here is a piece of technology that a lot people are using and I was able to get up and running in less than 2 hours. The next day I deployed a guestbook application by applying some deployment and service yams files and it all worked. Then I build a container of an app I was working and was able to deploy it to my cluster pretty easily. I know this is just a proof of concept but I feel confident of launching and supporting an environment running kubernetes in production. Maybe at one point I will pitch this to the team at work.

The reason why is that the documentation for Kubernetes is very concise and clear. The stuff just works and once you understand the principles behind of how kubernetes works then you can basically get up and running. maybe we can start with staging environments and then move into production.

Also there is a TON more of tooling for Kubernetes than there is for ECS.

Amazon will come up with EKS soon , there is no doubt that Kubernetes is the big gorilla room. Kubernetes is fun and pretty cool technology.

I am looking forward to my journey into production kubernetes.