72 replies to this topic

[JonF]

- Why did you hardcode driveletter X:?

I don't remember. Perhaps Reg_Add using %SystemRoot% would work.

No, it doesn't work . It looks as if the loader would have to create the entries at boot time to avoid the hardcoding. I'll think about it for a bit.

[JonF]

Updated, with no hardcoded X:\... entreis.

I considered moving all RegAddBoot entries into the loader, but that requires setting up communication between the script and loader (telling it which entreis to add), so I didn't do that.

[MedEvil]

Which environment variables does the loader require to work?
Maybe one is missing in NaughtyPE.

[JonF]

%SystemRoot%. Got a suggestion for another?

[MedEvil]

%Appdata% ?

[JonF]

%Appdata% ?

Sorry, no. %Appdata% doesn't tell me anything about where the subdirectories of system32 are, at least in LiveXP. Look at the script: the hardcoded X's are in paths to X:\i386\system32\Macromed\Flash, or X:\Windows\system32\Macromed\Flash, or whatever the equivalent is in NaughyPE.

Got a %Windir%?

[MedEvil]

%Appdata% specifies the folder in which, on a normal XP, all the application hold their ini and other files.
Firefox puts his profile there.

But maybe a misunderstanding. ?
- Which environment variables does the loader require to work?
+ %SystemRoot%. Got a suggestion for another? (Which is required to work.)
- %Appdata% ?
+ %Appdata% doesn't tell me anything about where the subdirectories of system32 are

[JonF]

%Appdata% specifies the folder in which, on a normal XP, all the application hold their ini and other files.
Firefox puts his profile there.

Yes., I know. But when we are talking about hardcoded X:, we are not talking about Firefox. We are talking about Adobe Flash Player plugin. Adobe Flash Player plugin puts its files in %SystemRoot%\System32\macromed\.

The loader uses HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\AppData to decide where to put Firefox's profile.

In order for Flash Player plugin to work, some program has to enter the path to its directory in three places in the registry. Originally the script did that, using hardcoded X:\... . Now the loader does it using %SystemRoot%, and if %SystemRoot% does not exist Flash Player plugin will not work. The loader could use %WinDir%, if that exists. Or maybe there's a registry key that it could use.

I do not have NaughtyPE and, frankly, I am not particularly interested in it and I do not have the time to try it out and explore it. But I am willing to expend some reasonable effort to make the Flash Player plugin work in NaughtyPE.

In VistaPE a program can easily determine that the 32 bit system files are in X:\Windows\system32. In LiveXP a program can easily determine that the 32 bit system files are in X:\i386\system32. If there's no way for a program to reasonably easily locate the directory containing the 32 bit system files, then the loader isn't going to make the Flash Player plugin work. Where are the 32 bis system files in NaughtyPE?

(Perhaps the Flash Player plugin would work if its files were moved somewhere else that's easily located, but my guess is there might be problems and I'm not very interested in finding out.)

[MedEvil]

Somehow this whole conversation has run straight into the next wall.
We seem to always talk about different things.

If the flashplayer makes trouble or not, i can't even say, since FF crashes at start and i thought we wanted to fix that first. ?

Where are the 32 bis system files in NaughtyPE?

In AnyDriveletter\AnyFoldername\System32 or %systemroot%\System32 for short.

I do not have NaughtyPE and, frankly, I am not particularly interested in it

Your loss.

[JonF]

If the flashplayer makes trouble or not, i can't even say, since FF crashes at start and i thought we wanted to fix that first. ?

It would have helped to have mentioned at some point that FF crashes. Then I could have addressed that issue. You did say "it wouldn't work" and asked several questions, including why did I use X:. I thought there was an issue with X:.

Is the profile created when you try it? Does the registry entry I listed above exist?

[MedEvil]

The named registry entry exists and hardcoded X: would be a problem.
For the check about the profile directory, you'll have to wait till tomorrow.

[JonF]

If possible, try it without Java.

[MedEvil]

The first two stages of the loader seem to work. The profile is created.
But when FF is started it crashes, with crash dialog , but the loader just won't exit.
How do i disable Java in FF.script?

[JonF]

But when FF is started it crashes, with crash dialog , but the loader just won't exit.

What does the crash dialog say?

How do i disable Java in FF.script?

Sorry, there is no Java. I meant Flash. Uncheck Flash on the setup page in WinBUilder.

[MedEvil]

No Idea what the reason is, the dialog doesn't tell.


btw. without Java, ehhm Flash.

[JonF]

Yeah, that's no help at all. I guess I will have to find the time to run NaughtyPE.

[MedEvil]

Send me a note, if you wanna do this, cause you'll need some updated files or your script would not have the chance of a snowball in hell.

[JonF]

Updated.

[jsgage]

very nice script JonF mighty big thanks . one small request can you add the "no script" plugin to next release so firefox is that
little bit more safe

[ktemplar]

What does the crash dialog say?

I've got the same problem. After the launcher tries to start firefox, it crashes. The dialog exactly print:

Add-ons: {987311C6-B504-4aa2-90BF-60CC49808D42}:2.1,{a7c6cf7f-112c-4500-a7ea-39801a327e5f}:1.0.5,firebug@software.joehewitt.com:1.4.2,{CAFEEFAC-0016-0000-0007-ABCDEFFEDCBA}:6.0.07,{CAFEEFAC-0016-0000-0012-ABCDEFFEDCBA}:6.0.12,{CAFEEFAC-0016-0000-0013-ABCDEFFEDCBA}:6.0.13,{CAFEEFAC-0016-0000-0015-ABCDEFFEDCBA}:6.0.15,foxmarks@kei.com:3.3.1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:3.5.2

BuildID: 20090824101458

CrashTime: 1260282419

InstallTime: 1252859883

ProductName: Firefox

StartupTime: 1260282417

Theme: classic/1.0

Throttleable: 1

URL: 

Vendor: Mozilla

Version: 3.5.3



This report also contains technical information about the state of the application when it crashed

I build a VistaPE with Winbuilder 078 SP3. I know with older Versions of Winbuilder the firefox script works fine.

[JonF]

Hm. Thanks, but that doesn't help much.

[esgaroth]

When adding this script to win7rescuepe I get an error message when running firefox. "Failed copying profile files to /Mozilla/Firefox"
Firefox runs afterwords.
Also the make firefox default isnt working in win7rescuepe.

[JonF]

When adding this script to win7rescuepe I get an error message when running firefox. "Failed copying profile files to /Mozilla/Firefox"
Firefox runs afterwords.
Also the make firefox default isnt working in win7rescuepe.

Humph. I don't have a working build here. Can you check if HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\AppData exists and has valid data and is on a writable drive? How about the APPDATA environment variable?

The make-default thing is tricky, I don't even know how it works or doesn't work myself.