83 replies to this topic

[pedrole15]

Thanks, that's the part i still got.
What i don't get is, what would have to be changed and to what.
The way i see it, one can put the [ProgrmFiles] folder anywhere one likes already, without problem just adopt the %ProgramFiles% variable and you're good to go.
But this was somehow ment to work differently.

btw. Anyone using that 'run from CD' feature at all, in his builds?

I've add the code for run from CD in your Opera.script
For working with BootSDI it need :

1- BootSDI.script must not hide the file "BOOT.CATALOG" when making the ISO
In the last line of section [CreateRAMIso] you have :

".....-b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog#$s-duplicates-once -o #$q%IsoDir%\%....."

delete this "-hide boot.catalog"

2- In Explorer.script extract the file "SHC.AU3" and add this two line at the end of the file

$CDDriveLetter=StringLeft($PsyhCD,2) 

RegWrite("HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment","CDDrive","REG_EXPAND_SZ",$CDDriveLetter)

What do you think about that ?

[MedEvil]

A brand new version 004 is available for download.

http://www.boot-land...mp;showfile=231

Fixes include:
- now also sound is working with flash (naughtyPE version already had this) (*1)
- found (and fixed! ) a bug in the protokoll associations (Now also internet addresses without a .html or .htm work.)



*1 - Requires a PE with audio capabilities!

[TheHive]

Is the flash plugin the latest. I think it says v7. And on some flash files it only seems to be able to play the sound. Other then that. Other things tested are working.

[MedEvil]

No it's still the older, way smaller one. Havn't run into troubles with it yet.
Can you give me a link to a site, that doesn't work?

[Lancelot]

Thanks for good work,

I have 2 findings with cd-opera.script

1st:
using #$pProgramFiles#$p with reg add cause sth like this (picture is for bulkrename, same with cdopera)
http://img261.images...708/asdfgw5.png

Founded Fix:
registry addings should be made with %PE_Programs% not #$pProgramFiles#$p


2nd:
i couldnt make association with .url

[MedEvil]

I have 2 findings with cd-opera.script

1st:
using #$pProgramFiles#$p with reg add cause sth like this (picture is for bulkrename, same with cdopera)
http://img261.images...708/asdfgw5.png

Founded Fix:
registry addings should be made with %PE_Programs% not #$pProgramFiles#$p

No they shouldn't!
Let's say you want/need to put your PE on a HDD where already an XP is installed.
You will now need to change the name of the PE Programs folder.
The way i coded it, there is only 1 setting to change. The way you want it, dozends!

If for some reason it's not working anymore properly, somebody 'fixed' something that wasn't broken.

2nd:
i couldnt make association with .url

Do you mean the script option isn't working or really, you can't associate url with opera?

[Lancelot]

1st:
still dont solve x64 compatibility issue,
I have to make the fix i wrote so now i can have
"%systemdrive%\Program Files\CD-Opera\Opera.exe" "%1"
if i dont do the fix it will be
"%systemdrive%\Program Files (x86)\CD-Opera\Opera.exe" "%1"
and it wont work

or my english is bad to explain what is going on.
Maybe an option due to needs ?

2nd:
yes i mean i can't associate url with opera. I use winbuilder 075 beta 4 (official download release), maybe problem is there, maybe not.

there exist Hkey_classes_root\Opera.url key
But Under
Hkey_classes_root\.url\

it writes
InternetShorcut

due to script, it should write
Opera.url
but it dont

[dera]

Hi MedEvil

I just suppose the problem maybe that Lancelot speak about the script dwonloaded fom LiveXP server,
nevertheless using the CD-Opera.script Version=4 Date=2008-02-08 downloaded from the link above from Post #52
in my build the .url association works fine

[Lancelot]

Problem persist with
CD_Opera_v004_2008_02_08.rar

Maybe better to explain with pictures (picture taken from livexp running under vmware)
http://img523.images...08020801fd4.png
http://img523.images...08020802bb9.png
http://img513.images...08020803ag6.png

[MedEvil]

the CD-Opera.script Version=4 Date=2008-02-08 downloaded from the link above from Post #52
in my build the .url association works fine

Thanks dera, for verifying this!

[Lancelot]

MedEvil
I use x64 os, dera use x86, it is normal dera dont have the issue i wrote.
look post 151 and 152, 153, 154, 155 , 159, 161. Only CD-Opera.script left without a solution for second issue (and i dont know the reason yet), and no fix for 1st issue.

[MedEvil]

1st:
still dont solve x64 compatibility issue,
I have to make the fix i wrote so now i can have
"%systemdrive%\Program Files\CD-Opera\Opera.exe" "%1"
if i dont do the fix it will be
"%systemdrive%\Program Files (x86)\CD-Opera\Opera.exe" "%1"
and it wont work

This problem seems to be related to the fact that you use the 64Bit version instead of 32Bit one.
For some reason, that i do not understand, your environment variable is set to contain 'Program Files (x86)' instead of 'Program Files'.
Maybe it's a 64 bit thing.
Do you have two Programs folders in your PE? One 'Program Files' and one 'Program Files (x86)'?

2nd:
yes i mean i can't associate url with opera. I use winbuilder 075 beta 4 (official download release), maybe problem is there, maybe not.

there exist Hkey_classes_root\Opera.url key
But Under
Hkey_classes_root\.url\

it writes
InternetShorcut

due to script, it should write
Opera.url
but it dont

Since the other associations work, there's nothing wrong with the Winbuilder version you use.
The two most likely sources of your problem are:
- Another script, which runs after CD-Opera overwrites those settings.
- - You can check the registry hive in %Target% if the value is written correctly.
- Some scripts register dll upon start of PE. Those love to overwrite file associations!!!
- - There's usually not much to do about this kind of problem, but:
- - - fix the problem script to preregister the dll
- - - do not use that script
- - - create a reg file with operas file associations and put it on the desktop of PE and
- - - double click it, after the boot process has ended.

The last fix can be automated with some trial and errror by applying it automaticly via the runonceex key after the problem dll was registered.

[MedEvil]

@Lancelot
Did some reading about 64bit Windows and they do change the contents of the %ProgramFiles% variable according to the detected executable.
So the proper solution would be, to store all 32bit applications in ProgramFiles(x86) folder.
But hardcoding the path works too, though it basicly just stops a feature from working.

[Lancelot]

Medevil

Do you have two Programs folders in your PE? One 'Program Files' and one 'Program Files (x86)'?

NO

- Another script, which runs after CD-Opera overwrites those settings.

NO opera is the only script i use for browsing, BUT

- Some scripts register dll upon start of PE. Those love to overwrite file associations!!!

probably this register dll is from base script (maybe hojope maybe another) which tries to register .url for IE, but as there is no IE. I dont know which dll/ how/where it is for now.

Changing the contents of the %ProgramFiles% variable according to the detected executable is a very good thing for x64 users (at least i can confirm MS did right with that), also it overcomes most compatibility problems without an issue.


Problem is cdopera.script get %ProgramFiles% from existing operating system, not building pe system.
What if someone using x86 system made his own %ProgramFiles% to C:\laylaylom , or D:\Programs
than in pe, associations made by cd-opera.scipt still wont work.
Issue is not directly about x64, only with x64 as you wrote 32bit applications read %ProgramFiles% as C:\Program Files (x86)

So the proper solution would be, to store all 32bit applications in ProgramFiles(x86) folder.
But hardcoding the path works too, though it basicly just stops a feature from working.

the solution you offer has no good logic 1) as livexp is a 32bit environment we dont need that, 2) this issue happens now only with cd-opera.script




I guess this issue will remain till the day another three x64 users that use cd-opera.script (who loves opera like me) with livexp and report here ( will take a loooong while i guess ). No problem for me, I learned enough to make small personal fixes, for 1st issue i will change the script as i wrote, for 2nd issue till i find the dll that registers i will put a .cmd file to startup to register .url -> opera.url (or sth like that). I reported for a general fix to be made so other x64 users than me dont face this problem anymore.

So as a conclusion, no need to write about this anymore ;)
And thanks for cd-opera.script, i love opera

[MedEvil]

probably this register dll is from base script (maybe hojope maybe another) which tries to register .url for IE, but as there is no IE. I dont know which dll/ how/where it is for now.

All users of that project should have this problem, since this is not a 32/64bit issue!
Best check with Galapo.

Problem is cdopera.script get %ProgramFiles% from existing operating system, not building pe system.
What if someone using x86 system made his own %ProgramFiles% to C:\laylaylom , or D:\Programs
than in pe, associations made by cd-opera.scipt still wont work.
Issue is not directly about x64, only with x64 as you wrote 32bit applications read %ProgramFiles% as C:\Program Files (x86)

No, %ProgramFiles% is taken from PE and never ever!!! from the building system!
If you would for instance build from a 32bit source on a 64bit XP, you would not get that problem.
The other way around it would be there again!

The only 'problem' with my script is, that i didn't thought of 64bit XP. Basicly the script would need a switch, to adjust a few settings according to the detected source.

this issue happens now only with cd-opera.script

If that's really true, that's sad. As it means that the majority/all of script developers have abandoned the rules for how to write proper scripts, psc and i have suggested early 2007, in order to make our projects less static.
Hail the static path!

I guess this issue will remain till the day another three x64 users that use cd-opera.script (who loves opera like me) with livexp and report here ( will take a loooong while i guess ).

I don't do much work on scripts at the moment, but if i should update/fix the script again, i promise to think of you.

[Lancelot]

MedEvil:

just to avoid misunderstanding (or probably i misunderstood):

If you would for instance build from a 32bit source on a 64bit XP, you would not get that problem.

i use 2k3x64 as OS (for personal use very same with XPx64)
i use XP32bitSP2 as source for winbuilder (livexp)

for others, as i have verrrrrrry low info about things compared with galapo, peter, and highly probably you and others, no need to comment .

[MedEvil]

i use 2k3x64 as OS (for personal use very same with XPx64)
i use XP32bitSP2 as source for winbuilder (livexp)

Ok, now things get interesting. With a 32bit XP as source you shouldn't get 'ProgramFiles(x86)'!

Start Your PE go to the command promt and type SET.
Go down the list and tell me what stands after ProgramFiles=




PS: I misunderstood, thought you wanted to build from a 64Bit source.

[Lancelot]

Medevil

it is X:\Program Files
here is a picture for you:
http://img530.images...18/snap1kz8.png

[MedEvil]

OK, so there's no problem with the fundamentals.
Then i guess the problem also does not show up in the shortcuts to CD-Opera, but only in the registry entries, right?

[Lancelot]

it writes

%ProgramFiles%\CD-Opera\Opera.exe

in .lnk file, so no problem there.

this happens only in registry write in script.

please reread post 154 on other topic

[MedEvil]

it writes

%ProgramFiles%\CD-Opera\Opera.exe

in .lnk file, so no problem there.

this happens only in registry write in script.

Ok, this is no problem of winbuilder or the fundamentals or the opera script. The problem comes from using Windows internal Registry commands.
For some reason, Windows thinks again it knows better what you wanna do and corrects your 'mistake'. (Winbuilder is a 32Bit App so %Programfiles% should be %Programfiles(x86)%)

When Winbuilder will introduce the new rawregistry editing the problem will perrish. (hopefully )

[Lancelot]

i have doubts about that, from my experience of utilites tryin to be compatible to x64

Anyway, as my intention is to support livexp, i did my job. I found an issue, i sometimes find a solution, i reported all info to script writer. And that is all.
After all, i will write a fix to cd-opera and all will gone to history for me.

[Galapo]

I did a little bit of checking.

In my local build, .url association was fine. When it came to what's available off the LiveXP server, .url association didn't work at booted PE. However, in the registry hive, the association to Opera was set correctly. So something was overwriting it at boot.

What I've been able to determine from this is that if on the Explorer script if 'Use DLL init at build time rather than at boot time' is not selected then .url association is overwritten at boot. So some dll registration at boot is problematic.

Regards,
Galapo.

[MedEvil]

i have doubts about that, from my experience of utilites tryin to be compatible to x64

You should contact Nuno. I'm sure he would love to test his RawRegistryEditor on your machine.
It's after all ment for circumventing any kind of restriction on Windows systems.

[Lancelot]

MedEvil,

For me, Problems are there to be solved, when available solution is there. Instead of waiting next release of winbuilder here is the solution i made, i hope you like.

I made required fix for x64 os users, which are optional (look right bottom of interface), so for both the reasons you wrote and for users who use winbuilder under osx64 it is available.

you can find changes i made by searching lancelot in the script.
Also look the end of [Interface]


I addition to x64 compatiblity, i made changes on interface for classic theme users so now it looks nicer (i call them cosmetic fix).
Here are 2 cosmetic fixes i made (which are verrrrrrrry minor):
1) I changed
Skin_FileBox=,1,13,203,292,197,28,file
to
Skin_FileBox=,1,13,203,288,197,28,file
2) I changed
ChooseSkin_WebLabel="Choose other Skin:",1,10,74,301,113,18,http://my.opera.com/community/customize/skins/
to
ChooseSkin_WebLabel="Choose other Skin:",1,10,74,298,113,18,http://my.opera.com/community/customize/skins/


I hope you like the addings i made and put it on cd-opera.script next version.
Here is the script
http://lancelot.winb...ncelot_Adds.rar