83 replies to this topic

[pscEx]

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.

This statement honours you.
I'm thinking similar with some concerns:

A fast particular solution (I sometimes call it q&d -quick and dirty) works well, but is not the best behaviour in all cases.

If everybody in this forum offers particular working solutions, maybe that we soon have (script depending) a bunch of different solutions for the same issue.

In my opinion it is better that:

• You work on a general solution of the x64 issue
  (of course you can use Opera as test object)
• You suggest the general solution here
  Maybe that needs a change of core functions like buildModel or whatelse:
  No problem!

Continue to do your excellent work!

Peter

[Lancelot]

Peter:

I have same concerns too, that is why i prepare addings without touching concerns.
I write in a way that when a general solution found, it can be easly deleted from script, but i dont think delete will be needed as it is not an adding only for x64, it adds an option to cd-opera.script which, one who use x86 would also like to use this options as he/she needs..

If everybody in this forum offers particular working solutions, maybe that we soon have (script depending) a bunch of different solutions for the same issue.

the solution i made is not particular, but it is special for medevil needs with lack of feature in winbuilder. So medevil use as he/she likes, x64 users use by enableing options, other x86 users may enable or disable as it wont have a direct effect on them.

You work on a general solution of the x64 issue

i find a general solution, which writes at post #55 , but MedEvil want to use as it is becouse MedEvil likes the existing configuration 'cause of its flexibility to transfer cd-opera to other platforms.


Explaning more detailed, The solution i added is, which is not particular and used by all other scripts, changing #$pProgramFiles#$p to %PE_Programs% when x64 fix checkboxes are selected on gui.

When using x86 as OS;
if you disable x64 fixes, you have
%ProgramFiles%
in registry
(as medevil wants)
And if you enable x64 fixes, you have
%SystemDrive%\Program Files
in registry

When using x64 as OS;
if you disable x64 fixes, you have
%ProgramFiles(x86)%
in registry
(if medevil transfer script to x64 system he/she would like this too as it still suits medevil needs and make medevil required flexibility,
but if medevil transfer script settings to x86 using x64 as OS (as it is the case on creating PE) medevil wont and i dont want this)
And if you disable x64 fixes, you have
%SystemDrive%\Program Files
in registry

So in both cases using %PE_Programs% results with %SystemDrive%\Program Files on Pe registry without causing a problem.

The real fix will be made by winbuilder i guess, as the problem is using #$pProgramFiles#$p in .reg operations under OSx64 converts these reg addings to %Programfiles(x86)% at registry of PE. (read posts/ look pictures after post #55)

When this fix or additional feature added to winbuilder, my fixes may or maynotbe used, as fixes are not specific to x64, it only makes you choose what you want to see on winbuilder registry. (%ProgramFiles% or %SystemDrive%\Program Files)

I put name as "x64 fix" on gui to take attention of any other x64 user, but it is not x64 specific and real gui name may be "use %PE_Programs% in registry" but this name wont take attention of any other x64 user . And there wasnt enough space on gui to write "use %PE_Programs% in registry" and to create a text box "x64 users use this settings". Also i didnt want to alter script much as medevil is the write of script.

Btw, cd-opera.script is the only script left that needs this. But i agree with medevil that it is not cd-opera.script fault.

I hope these explanations are enough Peter, if not read posts after post #55, and look at the link at post #55. I hope solution is quick and clean for you

You suggest the general solution here
Maybe that needs a change of core functions like buildModel or whatelse:

My Suggestion Till a feature added to use #$pProgramFiles#$p on registry operation of winbuilder under x64OS to x86OS(livexp), addings i made to cd-opera.sciprt i found looks nice and clean to me.

To overcome my bad english and communication problem, i try to write as detail as i can, i hope i suceed this time

[Lancelot]

Peter,

how can i find exiting OS architecture (amd64, x86, IA64) with script ?

[pscEx]

Peter,

how can i find exiting OS architecture (amd64, x86, IA64) with script ?

I'm not sure to understand you correctly:

I think you want to make a script which checks the hardware of your PC and as a result it tells you some of
(amd64, x86, IA64)

Currently I do not know. But let me see tomorrow. If there is a way, I'm rather sure to find, propably with a small new app.

Peter

BTW: Your ideas:

[Lancelot]

Peter,

not really hardware, but OS
when i write a .cmd file with similar need, i write this:

if "%PROCESSOR_ARCHITECTURE%" == "IA64" goto IA64
if "%PROCESSOR_ARCHITECTURE%" == "AMD64" goto AMD64
if "%PROCESSOR_ARCHITECTURE%" == "X86" goto X86

i try to write a script:
FileCreateBlank,%baseDir%\Temp\1.cmd
TXTAddLine,%baseDir%\Temp\1.cmd,"ECHO#$s#$pPROCESSOR_ARCHITECTURE#$p>2.txt",APPEND
ShellExecute,open,%baseDir%\Temp\1.cmd

but it returned with x86 (2.txt file is in %basedir%) , but i wanted it return with AMD64 as i use x64OS. 32bit cmd used (as it should be) and echo gave x86. (so i learned this method of writing script dont solve what i am looking for)

determining the OS used (IA64, AMD64 ,X86) would be nice when you get somefiles from system (like acronis script) or make some script behave differently on running OS (like cd-opera.script), at the moment when 32bit application call files from os, os give it the 32bit files, which is a nice automatic feature of x64os of MS which solves many problems automatically.

example:
when i write cmd in script
C:\WINDOWS\SysWOW64\cmd.exe
runs (it is 32bit)
when i write cmd on my run box (start->run->cmd)
C:\WINDOWS\system32\cmd.exe
runs (it is 64bit)

when i start C:\WINDOWS\SysWOW64\cmd.exe and write ECHO %PROCESSOR_ARCHITECTURE% , it shows x86.

anyway, i put checkbox on cd-opera.script, so no problem for now.

But it would be nice if we have an option in winbuilder to learn running OS Architecture.

[Galapo]

how can i find exiting OS architecture (amd64, x86, IA64) with script ?

[Process]

_Calculate,"@ProcessorArch",architecture

_Calculate,"StringInStr('%architecture%'#$c'64')",architecture_result

If,%architecture_result%,Equal,0,Message,"System is 32-bit",Information

If,%architecture_result%,Bigger,0,Message,"System is 64-bit",Information

Regards,
Galapo.

[Lancelot]

Galapo,

ahhhhh i forgot this , this was one of the first thing i learned but gone from my mind with reproducing habits of cmd, sorry, thanks a lot for reminding.

I wont put this on my modified cd-opera.script because of the same concerns with peter, and it would be better if MedEvil decide to use it or not as it is MedEvil's script. I hope thunn use it ( look here ) as it is more essential there to use.

[Lancelot]

Hi MedEvil,

Since you are back, here is an update. (I wasn't expecting you around so i didnt wrote here before)
After having java script available and working (thanks to dera, check post 17 18 19 http://www.boot-land...?showtopic=6144 ) I found out that cd-opera script is not good with java, (post 18), later fixed (+minor cosmetics) and uploaded to LiveXP server.

You may also consider to add contact info to your future versions
Contact=http://www.boot-land.net/forums/index.php?showtopic=1081

Welcome back

[MedEvil]

Well as i told you, i would not get completely lost, but i needed some time off and i'm not back in the sense, that i will be around as much as i used to.

Can't recall at the moment what i threw out of CD-Opera, but i did as much as i could, i think.