I recently got a 2tb Samsung HD204UI and I could really use help making a bootable cd or usb thumb drive in order to run the firmware update. I've spent a few hours trying various things and I'm just not getting it at all. The samsung website provides me with a zip file (http://www.samsung.com/global/business/hdd/faqView.do?b...) that contains an .exe file and instructs me to create a bootable cd or usb drive in order to run it. I've tried tinkering with nero/ultrasio/magiciso and I Just can't seem to get it. From all the reading i've done, i'm assuming i have to take the .exe file then somehow make that into a bootable iso file - i've made it into a regular iso file but not bootable - and then create a bootable usb drive with it. But i really can't get past the first step - if that is even the route to go. What do i need to do? What programs do I need? Any help would be appreciated or even a link with pictures of a step by step guide. Thanks in Advance.
not sure this tells me how to go from an .exe file to bootbale iso. i've made a bootable USB pendrive in the past for a ubuntu live install, i got that part. but where do i begin as far as getting that .exe onto the pen is concerned.
Thanks for the feedback. I wasn't sure whether X: was the drive letter of a RAM drive. For example, Seagate's CD based firmware updaters create a RAM drive and then extract the firmware files to this RAM drive. I was wondering whether F4EG.EXE (not FAEG -- sorry) operated the same way.
I notice that Samsung's instructions say to "connect Target HDD to Primary / Master". Instead you say that your drive is connected to port 2. Is this SATA port 2 or IDE port 2?
Have you configured your SATA controller for "compatibility" mode in your BIOS setup? This will make your drive look like a PATA drive, not SATA. Samsung's updater is looking for a PATA drive.
After several attempts of trying this, I was able to re-flash successfully. I made sure:
-All USB flash drives were disconnected
-No other HDDs were connected except the Samsung
-The Samsung drive was plugged into 'SATA1' on the mobo
-The SATA configuration was set to 'Compatible' in the BIOS
This time the FREEDOS boot menu was actually a little different for me while getting to command prompt than what I was given during the unsuccessful attempts. I knew something was up when I didn't get the usual 'X:\FREEDOS' in command prompt either; all that was there was a 'X:\'. I just typed 'F4EG' and hit Enter and watched it successfully do it's thing. Here is a screen shot: