29 replies to this topic

[Sirquil]

Could someone give the correct syntax for this line:

If,NotExistFile,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt",FileCreateBlank,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt"

[pscEx]

Could someone give the correct syntax for this line:

If,NotExistFile,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt",FileCreateBlank,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt"

The syntax is correct!

If you have troubles, I assume that %Target_prog% is not defined or contains an invalid value when your script runs.
To test, insert a line

Message,%Target_prog%,Information

before this suspicious line.

Peter

[Sirquil]

Peter,

I inserted this line above the suspious line in UltraISO; I asked about correct syntax.

Message,%Target_prog%,Information

All I received was the %Target_prog% in a pop up message. Is this because the variable is undefined?

I am not knowledgeable about what I should see and how to fix it if the variable needs defined.

Bill

[MedEvil]

Hi Bill!

If the message box reads %Target_prog% instead of the value that should be contained in the variable, then the variable is not defined.

[Arvy]

That's strange. VistaPE's script.project file defines %Target_Prog% as %TargetDir%\Programs. So both %TargetDir% and %Target_Prog% should be properly defined unless the UltraISO script is failing to read the project environment. The only other possiblility I can think of would be if your script.project file for VistaPE had been corrupted somehow?

[Sirquil]

Why does the %Target_Dir% not show up when I have inserted the line:

Message,%Target_Dir%,Information

All I get is: %Target_Dir%

Bill

[allanf]

Message,%Target_Dir%,Information

Hi Sirquil,

I'm not sure if that is a typo in your post or from the actual script. It should be

Message,"%TargetDir%",Information
... no underscore. This should definitely resolve to the setting in Winbuilder's Paths Tab

Or the other one... "%Target_prog%" is it?

I prefer to use quotes around path variables.

BTW, thanks for zipping the log. VistaPE's log file seems to be getting way out of hand size-wise. Unfortunately, still too big for me to download with slow connection and not unlimited downloads.

Regards

[Sirquil]

Does this work inside a script?

###############################Script.project ######################
#default setting - all to disk
%Target_Prog%=%TargetDir%\Programs <<< Does this work inside a script? <========

###############################################################


################################UltraISO.script v011########


This is the pop-up error message. FileCreateBlank,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt"


Thanks to the community for the project and for your support!

[allanf]

%Target_Prog%=%TargetDir%\Programs <<< Does this work inside a script?

It should work if it is in the [Variables] Section. EDIT: With or without the percentage signs around Target_Prog?? Note that in that Section, quotation marks around a Path can not be used when defining a variable. (One exception is the %SourceDir% Variable in script.project!?)

In the [Process] or Custom Sections, you need the 'Set' Command. eg
Set,"%Target_Prog%","%TargetDir%\Programs"
followed by (if the variable was previosly defined)
System,RefreshVars

But as Arvy pointed out, ,%Target_Prog% is already defined in VistaPE. Maybe it is losing the definition when RunFromRAM is being selected, because in that case, %Target_Prog% should be re-Set to "%TargetDir%\Program#$sFiles" (... I assume.)

[Arvy]

Does this work inside a script?

It would IF the %TargetDir% variable were defined properly before using it. That is THE critical question. All else is merely a corollary.

Why are variables that are defined in VistaPE's script.project file are not being properly read and handled within the application script that you are trying to use? Until you pin down and resolve that underlying problem NOTHING is likely to work.

[pedrole15]

Could someone give the correct syntax for this line:
If,NotExistFile,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt",FileCreateBlank,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt"

I have made some test and i get the same error when I enable the checkbox RunFromRam
When disable RunFromRam ,the file is well created with no error
so for resolve this problem I sugest :
Make a blank file 'ExpEnvVar.txt' and encode it in the ExpEnvVar Folder in UltraIso.script
Delete or rem this line :
["If,NotExistFile,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt",FileCreateBlank,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt"]
Other problem the file ExpenVar.exe is not run at startup
You must correct the api.script like this:
#######################################################
#shortcuts
#Add_Shortcut,[Type],[Folder],[FullFileName],[Title],[Work Folder],[Parameters],[IconFile( .ico .exe)],[StartMode(1, 2, 3, or 4)]
#Category|Program Title|Path|Icon|Parameters
[AddShortcut]
#category
If,#1,Equal,Desktop,Set,#2,Desktop
If,#1,Equal,QuickLaunch,Set,#2,QuickLaunch
If,#1,Equal,Autorun,Set,#2,Autorun
If,#1,Equal,AutoStart,Set,#2,Autorun
If,#2,Equal,,StrFormat,filename,%Scriptdir%,#2
#pach to program
If,#3,NotEqual,,StrFormat,path,#3,%Shortcut_Folder%
If,#3,NotEqual,,StrFormat,filename,#3,%Shortcut_Exe%
If,#3,Equal,,Set,%Shortcut_Folder%,%PE_Programs%\%ProgramFolder%\
If,#3,Equal,,Set,%Shortcut_Exe%,%ProgramEXE%
If,#3,Equal,,Set,%RR%,True
#program title
If,#4,Equal,,Set,#4,%ProgramTitle%
If,#4,Equal,,Set,%RR%,True
#iconfile
If,#7,Equal,,Set,#7,""
#check run from ram
IniRead,%VistaInfo%,"VistaInfo","ForceAllToRam","%ForceAllToRam%"
If,"%ForceAllToRam%",Equal,"Yes",Set,"%AtRam%","True"
#
If,%RR%,Equal,True,System,Refreshvars
#process
If,%AtRam%,Equal,True,If,#2,NotEqual,Autorun,IniWriteTextLine,"%VPECFG%","shortcut","#2|#4|%Shortcut_Folder%%Shortcut_Exe%|#7|#6"
If,%AtRam%,Equal,False,If,#2,NotEqual,Autorun,IniWriteTextLine,"%VPECFGCD%","shortcut","#2|#4|%Shortcut_Folder%%Shortcut_Exe%|#7|#6"
#autorun
If,%AtRam%,Equal,True,If,#2,Equal,Autorun,IniWriteTextLine,"%VPECFG%","autorun","wait|#4|%Shortcut_Folder%%Shortcut_Exe%#$s#6"
If,%AtRam%,Equal,False,If,#2,Equal,Autorun,IniWriteTextLine,"%VPECFGCD%","autorun","wait|#4|%Shortcut_Folder%%Shortcut_Exe%#$s#6"

#######################################################
Last problem that i can't correct is :
The variable %SystemRoot% is not reconize by VistaPE
I have look in registry and find this variable only for ultraIso/EasyBoot so it's not implemented by Nightman

[Arvy]

Last problem that i can't correct is :
The variable %SystemRoot% is not reconize by VistaPE
I have look in registry and find this variable only for ultraIso/EasyBoot so it's not implemented by Nightman

It really has nothing to do with NightMan, nor with any other WinBuilder project, for that matter. The %SystemRoot% variable is a part of the Windows common environment and is frequently used in the registry by many kinds of applications, including Microsoft's own. In fact, it is generally considered good programming practice to avoid all assumptions about the OS installation path, especially drive letter assignments, wherever possible. Thus the use of variables such as %SystemDrive%, %SystemRoot%, %UserProfile%, etc.

There's nothing unique about VistaPE in that respect. All such registry entries must, however, be of the type REG_EXPAND_SZ in order to be properly utilized by any application. For merging in .reg files, they are shown as hex(02) and in WindBuilder scripts as 0x2 values. For some scripting cases (e.g., Add_Shortcut) the percent signs may need to be expressed as #$p as in #$pSystemRoot#$p.

[pedrole15]

Ok but i find strange because the script is well working in livexp not with VistaPE
In Ultraiso configuration under VistaPE
The Value %SystemRoot%\system32\NOTEPAD.EXE is not find

Perhaps I have not the good VistaPE11 ,i have download from http//:vistape.net/project

[pscEx]

[Perhaps I have not the good VistaPE11 ,i have download from http//:vistape.net/project

(Some kidding:) Maybe a new reason to remind on 'VistaPE for Dummies'

Peter

[Arvy]

Ok but i find strange because the script is well working in livexp not with VistaPE ...

Well, I suppose it's possible that you got a bad VistaPE download, but your source is the same as my own. The only thing that VistaPE or any other preinstallation environment can possibly do is to install each application in accordance with the instructions contained in its script and it appears to have done that in this case based on what you report seeing in the registry.

I know that I had to upgrade some of my applications, including commercially purchased ones, that were designed for earlier versions of Windows and that just don't work properly under Vista. That happens with almost every new OS and this may simply be one of those cases. I haven't tried UltraISO myself, but the script author's download notes do indicate that he only tested it with LiveXP. So, perhaps it's not really so strange after all, although an application not being able to find notepad.exe with that explicit registry pointer to its location certainly is peculiar. Did you try changing that registry entry to just 'NOTEPAD.EXE' without any path at all? Other Windows apps installed under VistaPE are certainly able to find it that way.

[pedrole15]

I have make an other test
It's working same in LiveXP so it's a problem with the script
The isodrive seem not working under liveXP and VistaPE
Same for the default wiever "Notepad" not fixed
@Galapo can you see that

[Galapo]

Hi Pedro,

I'll take a look shortly. But last time I checked the isodrive service and notepad were fine.

Regards,
Galapo.

[Galapo]

I have made some test and i get the same error when I enable the checkbox RunFromRam
When disable RunFromRam ,the file is well created with no error
so for resolve this problem I sugest :
Make a blank file 'ExpEnvVar.txt' and encode it in the ExpEnvVar Folder in UltraIso.script
Delete or rem this line :
["If,NotExistFile,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt",FileCreateBlank,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt"]

Do you have an explanation as to why the file isn't created?

Thanks,
Galapo.

EDIT: it's likely due to the folder not being created. I'll update the script.

[online]

In Ultraiso configuration under VistaPE
The Value %SystemRoot%\system32\NOTEPAD.EXE is not find

Hi, pedrole15!

Try this

RegAddBoot,"HKU",0x1,".DEFAULT\Software\EasyBoot Systems\UltraISO\5.0","DefViewer","%SystemRoot%\System32\notepad.exe"

it's 100% working.

[Galapo]

Is this api command working in LiveXP? If not, I cannot yet adopt this solution.

Regards,
Galapo.

[Sirquil]

pedrole15

I made your suggested changes; have not yet tried to use UltraISO from VistaPE. Registration looks correct. I have
used UltraISO in Vista with no problems. I have Vista Home Prem. (32Bit).

The icon that gets placed for the StartMenu is placed near the bottom of the StartMenu.
Should this icon (ExpEnvVar.exe go into the StartMenu, Startup folder?

Bill

[Galapo]

Should this icon (ExpEnvVar.exe go into the StartMenu, Startup folder?

Yes.

[Sirquil]

From VistaPE running; I used UltraISO to load VistaPE.iso and burn a cd --with no problem.

Created a cd image from my cd drive to an iso file, mounted the image on a virtual
drive; again no problem

All worked as advertized.

Thank you to ALL that have helped to resolve my errors -- truely a World community
here on boot-land.net!

Bill

[pedrole15]

Do you have an explanation as to why the file isn't created?

Thanks,
Galapo.

EDIT: it's likely due to the folder not being created. I'll update the script.

Yes, when you use the api for extract file the folder is make by the api
when you use filecreateblank under vistape in ram the folder is not created but it is in livexp and in vistape not in ram ==>strange
So you encode a blank file or you place the line for extract before the line with filecreatblank

But this is not fixed same under LiveXP and VistaPE

[Arvy]

when you use filecreateblank under vistape in ram the folder is not created ...

If you haven't already done so, you might want to pass that along to NightMan via email so that he can correct it in his ongoing v.12 development.