QUOTE(dlevens @ Dec 9 2005, 09:48 PM)
...The link above DW Firefox plugin is the one that comes with the ubcd and does not work. On first load you get a blank screen, so you close it and load and again and sometimes it works... I cannot see any need or reason to add the 6 extensions that were added in that build, all they do is screw things up by adding those. Its always the bloat that ruins a good thing. We need small, fast, and solid for a rescue cd, not the frills and bloat. MHO of course.
Dennis
A couple points of clarification:
The Firefox plugin that comes with UBCD4Win is
NOT my plugin but a modified version... my "pure" version as posted in the above link and elsewhere on this board (
HERE) works perfectly for hundreds/thousands of users.
As well, if you had read post #18 in my Firefox plugin thread, you'd have seen that my plugin is also 100% completely customizable - that is, install the plugin in the usual fashion, build and burn your ISO, boot to your PE disc, and run Firefox. Customize it to your personal liking. Examine your PE disc with an Explorer-clone app, and you should see a folder: x:\Programs\FirefoxPE\Firefox.SFX.Maker. Inside that folder on your disc is
Make.Firefox_SFX.cmd. When you run this file it will MAKE a new
FirefoxPE_SFX.exe and place it in the root of your RAMDrive (B:\) to do with as you wish (most people would want to save it to their hard drive in the FF plugin folder for future use).
The customized "Firefox maker" assumes you have WinRAR on your PE build - see
SET WINRAR=X:\Programs\WinRAR\WinRAR.exe. Of course, change the drive letter/path to where your version of WinRAR resides (including your hard drive). My Opera plugin is customizable in the same fashion. That's the beauty of plugins as utilized by PE Builder - if you don't like the way someone has set up their version of plugin "x" you can easily modify it to your personal preference.
WinRAR questions and answers you may have can be found
HERE.
One more slight correction:
@webmedic
None of my plugins run from the root of the RAMDrive - they all run from their own independent folders - b:\Opera or b:\Firefox for example. The customization routine also uses the browser settings as found in your PE build that is actually running in the RAMDrive, and not settings as found on your hard drive. I would be hard-pressed to imagine that most folks would want the same browser settings as found on their hard drive to be running in PE.
DW
