Hi guys, Need some help with GC iso. I have this iso (1,459,998,720 byte) which is larger than 1,459,978,240. I used fstfix1.5 loonycube to get the size right, but it turned out the output file was way over 2.5 gb. I've tried this command: fstfix.exe filename.iso f and also this command: fstfix.exe filename.iso t f Both gave me a huge output size. From what I've read in the GC forums, the fstfix is used to pad or to put garbage date for undersized iso so it has the right size of 1,459,978,240. My question is: what program should I use to reduce the oversized iso to the right size? Ah another thing, how long does it take for you guys to pad an undersize iso? It took me more than an hour to pad, and I'm running a Athlon 1.7 with 512 mb ram and windows XP. Read in another thread, took them only 2 minutes to pad the iso. Me confused. Thanks in advance for your help. Regards, pinkorochi
dont worry if your using fullsize just burn it anyway. have you tired wipping the garbage bytes? that may reduce it. padding only took 1 minute for me on 512mb RAM. you probably have tons of stuff running in the background if it took that long. when padding just close out eveything and only use the padding program. [bold]also what game is it? i need to know more info before i can help.[/bold]
Hi zombie_x, Thanks for your reply. First of all, I don't use full size DVD-R. I use Verbatim mini DVD-R 1.4 gb, 4x speed. I tried burning the slightly oversized iso (1,459,998,720), it was good, no error reported. Put it in my cube and play the game for 15 mins, and looked OK. Also, I burned the slightly undersized iso (1,459,976,192 bytes), still it was good. No error, and it plays on my cube. My question is that: do I have to get the right size of the iso's in order to play them correctly? I hate the idea of playing Harvest Moon and 2-3 hours later the game freezes and won't let me continue. Do you think it's possible? Whenever I use fstfix for an iso (oversized & undersized) it always gives me a huge output. I've tried many times with different s t f combination. I even tried using the command without those s t f attributes. By the way, the 3 gig padding option is OFF. Still the output is over 2 Gb and it took me over an hour. I didn't open any other program, just running fstfix on my comp. One more thing, when I burn them with Nero, the only option for the write speed is 4x. There's no drop down box wheren I can select the speed. The media I'm using is Verbatim mini DVD-R 1.4 gig which support 4x. I'd like to burn them with 1x speed to reduce the chance of error. Any idea? Thanks!
the iso you have is already fixed so there is no need to do anything to it. Just burn away. how are you burning the iso w/ nero? the best way is to open nero burning rom and from a dropdown box on the top select burn image and select your image. then after that it will give you a screen where you can select write modes(DAO,RAW), write speeds, and the finalize option. hope that helps but if it doesn't i will try to hlp some more.
Make sure you are using v1.5f. Earlier versions of 1.5 would create oversized files and take forever, 1.5f will create the proper size and should just take a couple minutes.
Hi guys, thanks a lot for your replies. Someone told me to leave all fstfix attributes while doing the iso to strip away all the garbage data, and then rerun the small output through fstfix using the f at the end of the command. I tried this method, and it worked for my papermario iso. It gave me a 591 MB iso output, then after rerun it again through fst fix it gave me exactly the right size. Below is the screenshot: http://pg.photos.yahoo.com/ph/pinkorochi/detail?.dir=db1b&.dnm=3bfc.jpg&.src=ph But this method didn't work for my other iso's. I tried harvestmoon (1,459,998,720 bytes), zelda windwaker (1,459,998,720), metal gear solid disc 1 (1,459,671,040 bytes). Notice that they're slightly oversized or undersized). I tried doing what I did to the papermario iso but still it took forever and gave me huge output. I don't understand why the method I used on papermario wouldn't work for other iso's. Here's the screenshot when fstfix would take forever: http://pg.photos.yahoo.com/ph/pinkorochi/detail?.dir=db1b&.dnm=fd43.jpg&.src=ph @xian: I used wiped_gcm_fixer_v1.5-loonycube I got it from modthatcube website if i'm not mistaken. Un-rared the program, then put the fstfix into the same folder as the iso's which is in h: folder. @zombie_x I did the same way you did with the Nero Burning Rom. Click on the Recorder and chose Burn Image. After I chose the iso, the Burn Compilation window appeared, I could see the Writing Method, but it's greyed out. I could choose the writing speed from the drop down box (1x, 2.4x, 4x, max), but when I inserted the blank DVD-R disc, the dropdown will only show 4x speed with no other choice. So I couldn't burn the iso lesser than 4x speed. Kinda weird since I've read people burning their isos at 1x speed. Do you think firmware upgrade should fix it??? By the way my burner is Lite-ON 1673S. By the way how could you know if an undersized or oversized iso is already fixed? I thought fixed iso always has 1,459,978,240 bytes in size. TIA, pinko
I had used wiped_gcm_fixer_v1.5f-loonycube.rar when I had oversized problems with the first 1.5. I can't remember where I got it from though. From the NFO VERSION 1.5Fixed ( Arrrrgg Sorry fogot to replace 1 call of detect APPsize! ) ------------- Ok Guys there is another version for your pleasure ! fstfix.exe v1.5 Wiped GCM Fixer by SlideR/LOONYCUBE! USAGE: fstfix image.gcm [option] [option]... -------------------------------------------------------------- What's New [24/03/2005]: v1.5F (Fixed version 1.5) -My fault Sorry for the Bug! I'm HUMAN
Xian: Turned out I've been using the old version of fstfix1.5. I downloaded the fixed version of fstfix1.5 and everthing is working perfectly now. Many many thanks to you and others who helped me out. One more question though, if I downloaded an iso which already has the right size, do you think it's better to just burn the iso or use fstfix to remove the garbage data and repad the iso? I wonder if this makes any difference. Regards, pinko