So, can anyone tell me the difference between FreeVAST and the Independence exploit? Is there any reason I should switch to FreeVAST, other than not needing a trigger disc?
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
So, can anyone tell me the difference between FreeVAST and the Independence exploit? Is there any reason I should switch to FreeVAST, other than not needing a trigger disc?
Honestly I would prefer you read up on BOTH of them and come to your own conclusion.![]()
Independence was great for its time but has been buried under the all out amazingness of FMCB.
Sure, we have gone ahead and done that......just for you! Its been exlained in great detail in many posts/threads....right here in this very forum called freevast. We even made them 'stickies', just so you could find them even easier
If your happy with what you are currently using, i dont have any reasons to give you.
But if your looking for a better way to do some things you cant do with the PS1 Exploit, then i could give you a whole bunch of reasons, depending on what it is your unhappy with in your current exploit.![]()

Some thoughts, why I prefer FMCB over PSX-Indy. and also DEV.-Modes.:
-start from MC without the need of a disc, with no need for a hardwired solution (thus also very portable)
-easy user-handing (be it for elf-launching in whatever case [Auto-, Button-Launch, hacked OSD], or backup-launch [Fastboot, or OSD-Boot])
-probably a complete init (& if bugous, it also probably can be fixed)
-...
Btw.: Just one thing. It seems (some) Mod-Chips do not initialize the Hardware in DEV.-Modes correctly, thus I use the button-launch-feature of FMCB, rather than my Chips (DMS3, cuz CC isn´t working properly and didn´t tried DMS4PRO, yet) DEV.(1)-Mode.
I´m not sure about the xploit (I think, it do not have this problem, but it might be...).
Last edited by TnA; 12-19-2008 at 08:08 AM. Reason: a typo
I know this kinda goes hand and hand with "not needing a trigger disc" but if you don't have to load a disc each time you start the system you don't need to deal with those "Disc Read Error"s and could possibly extend the life of your lens.
Why are you asking anyway? Why not just try it?
If for some odd reason you don't like it, just erase the files it puts on your MC and stick a PSX disc back in there.
I would say the same.
I think this is not a good suggestion, if he do/did a Multi-Install (if so, he must revert it to a normal-install with the FMCB-Installer and then can delete the rest of the files...).If for some odd reason you don't like it, just erase the files it puts on your MC and stick a PSX disc back in there.
First off, FreeVAST as such does not exist.
It is just the name of an old project which never took off before it died.
But from the ashes of that death there rose a new project named "Free McBoot" aka: FMCB
It is FMCB which is the new dominant PS2/PStwo softmod, vastly superior to the independence exploit.
Why do you exempt that vast difference as if it were meaningless ?Is there any reason I should switch to FreeVAST, other than not needing a trigger disc?
In fact that is the most crucial difference of all, which will add years to the lifetime of your console.
Once your CD laser dies (as all of them do eventually) you will no longer be able to boot the old exploit, as there is no longer any way to trigger it then. But an FMCB user can keep booting as if nothing happened, playing games from HDD and running homebrews as before, almost completely unaffected by the fact that the CDVD drive is no longer working.
Another huge advantage, as long as the DVD laser still lives, is that you can use ESR after booting with FMCB. (Some say they can do that after booting with PS1 exploits too, but I have tried it and for me that never works.) ESR allows you to use DVD discs both for backup games and for homebrew discs with emulators and media files etc, almost as on a modded console, except that each ISO must be given a special patch before burning to make it readable on the PS2 (when ESR driver is active).
Best regards: dlanor
Oh!
I've never done a Multi-Install...(never had a reason to), but that is when your installing it on a MC for someone else(or for another PS2 that you have) right?
But I do remember reading something about it putting extra files on a MC that would make it appear as if there was more data on the MC then there really was...but not being able to delete the files?
Well, just make sure to read the tutorials, especially if your using a bigger(older) PS2...
Yepp (to be exact for keeping compatibility to PS2-Versions, which do not search for the same file like yours, which is "osdmain.elf" in many cases).
Not exactly. It patches the FAT-Filesystem to point to the same sectors for all dummy-files (all filenames point to the same file).But I do remember reading something about it putting extra files on a MC that would make it appear as if there was more data on the MC then there really was...but not being able to delete the files?
It patches some dummy-files (thought 1K, or Clustersize) to be at the same sectors as the file, which was installed in first case (osdmain.elf).
You can delete those files manually, but the dummys will remain as unusable space on MC (thus 22KB in total thought...) and there is no way to recover these, except a mc-format. That´s why it is recommented, to revert a multi-install back to normal install, because it unpatches and deletes the dummys.
If you´re talking to the thread-starter,... Yes. The "INJECT"-Part is all you need to know, if you want to keep it small.Well, just make sure to read the tutorials, especially if your using a bigger(older) PS2...
| « Previous Thread | Next Thread » |