VistaPE beta 011

in the History of changes of VistaPE beta 011, i read:
8. now folder with programs not linked to "Y:", be careful and use API for shortcuts

my question is now:
how can i make a registry entry, that contains a path to an application on the boot media?
so what is the replacement for %LinkDir% in this code:

...

...

[Variables]

%ProgramTitle%=SumatraPDF

%ProgramEXE%=SumatraPDF.exe

%ProgramFolder%=SumatraPDF

%LinkDir%=Y:\%ProgramFolder%



[process]

Echo,Processing %ProgramTitle%...

Add_Shortcut,StartMenu,Office

Unpack,Files,SumatraPDF.7z

RegHiveLoad,Tmp_Software,%HIVE_HKU%

RegWrite,"HKLM",0x1,"Tmp_Software\Classes\.pdf","","SumatraPDF"

RegWrite,"HKLM",0x1,"Tmp_Software\Classes\.pdf","Content Type","application/pdf"

RegWrite,"HKLM",0x2,"Tmp_Software\Classes\SumatraPDF\DefaultIcon","","%LinkDir%\SumatraPDF.exe,0"

RegWrite,"HKLM",0x1,"Tmp_Software\Classes\SumatraPDF\shell","","open"

RegWrite,"HKLM",0x1,"Tmp_Software\Classes\SumatraPDF\shell\open\command","","%LinkDir%\SumatraPDF.exe #$q%1#$q"

RegHiveUnLoad,"Tmp_Software"

...

...

any help would be appreciated
fuwi

Use this code to associate SumatraPDF.exe with pdf files:

[Variables]%ProgramTitle%=SumatraPDF%ProgramEXE%=SumatraPDF.exe%ProgramFolder%=SumatraPDF[process]Add_ShortcutAssociate_file,pdfUnpack,Files,SumatraPDF.7z

Look here for more details:http://www.boot-land.net/forums/index.php?showtopic=2707


%LinkDir% is no longer required.

fuwi

You can try use "%PE_Programs%\%ProgramFolder%"

Thanks Nuno Brito & NightMan

i tried the solution of Nuno Brito (Associate_file,pdf in [Process], all RegWrite's removed)
it doesn't work for me, in the registry, the path in pdffile\shell\open\command ist now "!CD\Programs\SumatraPDF\SumatraPDF.exe" "%1"
(!CD instead the actual CD-driveletter)

@NightMan
do you mean: %LinkDir%=%PE_Programs%\%ProgramFolder%
and leaving the RegWrite's unchanged?

Thanks, fuwi

hm ... it's very interesting... use "RunFromRam,True" and all will be work, no way right now make true link to program in registry if you place program to cd ... i try fix it soon

Thanks NightMan

fuwi

I am a little unhappy that the beta downloaded through Winbuilder over-wrote my working Release 10 directory.

In Virtual PC 2007:

1. I can't boot with Grub4DOS as teh boot manager. No matter which Grub4DOS skin I choose, I get white text on a black background and, when it tries to boot:

Booting 'VistaPE'



chainloader /bootmgr



error 17: FIle not found\



press any key to continue ...

When I press a key, it goes back to the menu.

2. I can boot using IsoLinux boot manager, but not without intervention. If I wait for the timer on the intial screen to count down to zero, it just starts aggain. I have to press <Enter> to get it to boot.

I downloaded a fresh copy of beta 11 into a new directory with the same results.

I can confirm that, at least with PDF extension (I still didn't try it with other extensions), the "associate_file,pdf" function doesn't work...

I had already noticed this behaviour with another PDF Reader and with SumatraPDF 0.7 the situation doesn't change (please, see the screenshot).

In order to work "PDF file association" I had used some registry entries in my old SumatraPDF 0.7 script that I've added also in my updated script for use with VistaPE 010, and it works fine.

About "LinkDir" issue I'm sure that it should be solved soon, meanwhile I think that two workarounds exist (about this specific case):

1. To change "RunFromRam,True" with "RunFromRam,False" and to change "X:\Program Files\" with "Your CD-ROM Drive Letter:\Programs\" in two lines (this is a ugly workaround useful only for both personal and aimed use, but it works).

RegHiveLoad,Tmp_software,%RegSoftware%

RegWrite,"HKLM",0x1,"Tmp_software\Classes\.pdf","","SumatraPDF"

RegWrite,"HKLM",0x1,"Tmp_software\Classes\.pdf","Content Type","application/pdf"

RegWrite,"HKLM",0x1,"Tmp_software\Classes\SumatraPDF\DefaultIcon","","X:\Program Files\SumatraPDF\SumatraPDF.exe,0"

RegWrite,"HKLM",0x1,"Tmp_software\Classes\SumatraPDF\shell","","open"

RegWrite,"HKLM",0x1,"Tmp_software\Classes\SumatraPDF\shell\open\command","","""X:\Program Files\SumatraPDF\SumatraPDF.exe"" ""%1"""

RegHiveUnLoad,"Tmp_software"

2. To add neither "associate_file,pdf" function nor registry entry lines and to use at program start-up the option "Make SumatraPDF default application for PDF files?".

1. I can't boot with Grub4DOS as teh boot manager. No matter which Grub4DOS skin I choose, I get white text on a black background and, when it tries to boot:

Booting 'VistaPE'



chainloader /bootmgr



error 17: FIle not found\



press any key to continue ...

When I press a key, it goes back to the menu.

Most probably there is a problem in the menu.lst.

When you go back to the menu, press [b]c[/c] to enter grub4dos command mode, then type:

find --set-root /bootmgr

and press [ENTER]
then type

chainloader /bootmgr

and press [ENTER]
then type

boot

and press [ENTER]

if it does not work, it may be a problem with the way the boot media is detected, then try the following:

find (

and press [TAB]
grub4dos will give you autocompletion options, such as

(fd0) (cd) (hd0) (hd1)

complete the line with the media from which you are booting, like:

find (hd0,

or

find (f

and press [TAB]
grub4dos will give you autocompletion options, such as

(hd0,0) (hd0,1)

or

(fd0)

continue typing and put a forward slash "/" like:

find (hd0,0)/

or

find (fd0)/

and press [TAB]
grub4dos will list files on that device, see if you can find the bootmgr file, if yes (say on (hd0,1) issue these commands:

root (hd0,1) [ENTER]

chainloader /bootmgr [ENTER]

boot [ENTER]

if it does not work, try using:

rootnoverify (hd0,1) [ENTER]

chainloader /bootmgr [ENTER]

boot [ENTER]

(you can also use the [TAB] autocompletion on other commands, i.e. chainloader /b[TAB] will list all files beginning with "b", pay attention to CaSe oF fIlEnAmE, bootmgr is not the same as BOOTMGR or as Bootmgr)

Once you have found the correct command sequence just edit accordingly menu.lst (the last "boot" statement is ONLY needed when grub4dos is used in Command mode)

jaclaz

i tried the solution of Nuno Brito (Associate_file,pdf in [Process], all RegWrite's removed)
it doesn't work for me, in the registry, the path in pdffile\shell\open\command ist now "!CD\Programs\SumatraPDF\SumatraPDF.exe" "%1"
(!CD instead the actual CD-driveletter)

@NightMan
do you mean: %LinkDir%=%PE_Programs%\%ProgramFolder%
and leaving the RegWrite's unchanged?

This association error should be reported to NightMan or PedroLe15 to be properly solved.

Using static paths is not a good solution since it will only be a temporary workaround leaving this issue unsolved for the next time someone needs to associate a file.

Will try to find time some to debug the reason why it happens.

This association error should be reported to NightMan or PedroLe15 to be properly solved.

Using static paths is not a good solution since it will only be a temporary workaround leaving this issue unsolved for the next time someone needs to associate a file.

Will try to find time some to debug the reason why it happens.

Hi nuno
Galapo have found an error in Api Associate , see here

In Api.script replace in section [do_associate_action_open]
%my_file_type_label% by #1file


Pedro

i tried the solution of Nuno Brito (Associate_file,pdf in [Process], all RegWrite's removed)
it doesn't work for me, in the registry, the path in pdffile\shell\open\command ist now "!CD\Programs\SumatraPDF\SumatraPDF.exe" "%1"
(!CD instead the actual CD-driveletter)

Hi all
In previous version of Api.script for VistaPE I use:
%PE_Programs%=y: and it was working
Now NightMan use:
%PE_Programs%=!CD\Programs

For making Associate work we must know what is the drive letter of !CD
If it is always Y: why using !CD , if not how to find it ?


Pedro

ALL

Hm... i really not like mount folder with programs as drive y:, it was made for very old version of VistaPE, when we have only BS Explorer and all shortcuts was amked directly from scripts, without API and other automation... now all is working more better, but for registry we need add full path to program, we must know cd drive letter (every time different) or add global environment variable (inside VistaPE), i try use "set" and "setenv" commands, try add variable directly to registry, but VistaPE can not see it, can anyone help with it? Also i can return drive Y: back, or parse registry files at boot time (from vpeldr.exe)... not registry API works well only if place program to boot.wim .... any ideas?

I have a (crazy) idea.

You can't change all dynamic paths on the registry because you require harcoded settings inside the reg hives to make them valid.

But what happens if you create a small program to scan all registry keys and change all references from !CD to whatever drive that points to the correct location while the boot disk is starting up? (Y: on this example)


It would allow to use a static value (whenever absolutely necessary) and still keep the boot disk dynamic and flexible to be used in other configurations.

Scanning all registry keys and replacing any !CD values is a fairly quick process when using an efficient coding.


What do you think?

Hi NightMan
Is it possible to run a little au3 at boot time before parsing shortcut ?
This au3 scan all cd drive to find the file Vistape.cd and write the letter of cd in registry
So
In Script.project we add %LinkDrive%=#$pCDDRIVE#$p (Default value)
In section [RunFrom_Ram] we add If,#1,Equal,True,Set,"%LinkDrive%","#$pSystemDrive#$p\Program#$sFiles"
And in Associate we change %PE_Programs% by %LinkDrive%


Pedro

But what happens if you create a small program to scan all registry keys and change all references from !CD to whatever drive that points to the correct location while the boot disk is starting up? (Y: on this example)


It would allow to use a static value (whenever absolutely necessary) and still keep the boot disk dynamic and flexible to be used in other configurations.

Hi Nuno,

This sounds like the (temporary until I have a better idea) solution I came up with to a couple of registry entries that required hard-coded paths for UltraISO and IZArc. ExpEnvVar expands variables passed to it from a text file generated during build when the variables are unknown. Here's a couple of lines from IZArc:

reg_add,0x2,"%reg%\Microsoft\Windows\CurrentVersion\App Paths\IZArc","","%PE_Programs%\%ProgramFolder%\IZArc.exe"

TXTAddLine,"%Target_prog%\ExpEnvVar\ExpEnvVar.txt","HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\IZArc#$c","Append"

The first line is the one written to registry. The second is the one written to the text file which ExpEnvVar will read and then expand the registry entries listed upon boot. So since %PE_Programs% in LiveXP is '%SystemDrive%\Program Files', this is expanded to 'x:\Program Files' with ExpEnvVar upon boot.

Of course, this is a bit rough, and I'd be happy is someone could write something better than what I've done.

Here's the AutoIt code anyway:
ExpEnvVar.au3

#NoTrayIcon

Opt("ExpandEnvStrings", 1)

$file = FileOpen(@ScriptDir & '\ExpEnvVar.txt', 0)

If $file = -1 Then Exit

While 1

	$line = FileReadLine($file)

	If @error = -1 Then ExitLoop

	If $line <> &#34;&#34; Then

		$array = StringSplit&#40;$line, &#34;,&#34;&#41;

		$reg_var = RegRead&#40;$array&#91;1&#93;,$array&#91;2&#93;&#41;

		RegWrite&#40;$array&#91;1&#93;,$array&#91;2&#93;,&#34;REG_SZ&#34;,$reg_var&#41;

	EndIf

Wend

FileClose&#40;$file&#41;

Regards,
Galapo.

So it is possible - nice to read your solution!

Nuno Brito
Your "crazi" idea is not bad, i already think about it, but it will be not fast (theoretically)... but it's really interesting

pedrole15
Sorry, but your method is not work, VistaPE ("set" command) can not see new values and i not know why


Galapo
Interesting ...may be it's will be better idea

Thanks

ALL

I plan make new config file for vpeldr.exe (VistaPE Loader), one file will be at "x:\windows\system32" folder and one at root folder at any device, config file will be contain main settings, shortcuts (before making link, vpeldr will be check for file existing), autorun, registry setting, file association setting, shell setting (for PE Shell Swapper)... (default) program folder will not be mounted as drive Y:, but all settings can contain variable with path to programs... boot.wim will be contain core files and possible change many setting without rebuilding it, true hotswap for program media will be support too...

new vistape.cfg example:

[main]

screen=800x600&#59;screen resolution

wpeinit=normal&#59;or normal

mountprogram=yes&#59;mount program folder as drive Y:

drivers=drivers&#59;filder with drivers

defaultshell=Total Commander&#59;default shell for PE Shell Swapper



[shortcut]

Category|Program Title|Path|Parameters





[autorun]

x:\windows\system32\cmd.exe /c echo test :)

normal|Program Title|x:\windows\system32\cmd.exe /c echo test :)

hide|Program Title|x:\windows\system32\cmd.exe /c echo test :)

wait|Program Title|x:\windows\system32\cmd.exe /c echo test :)

waithide|Program Title|x:\windows\system32\cmd.exe /c echo test :)

wait+hide|Program Title|x:\windows\system32\cmd.exe /c echo test :)

nowait|Program Title|x:\windows\system32\cmd.exe /c echo test :)

nowaithide|Program Title|x:\windows\system32\cmd.exe /c echo test :)

nowait+hide|Program Title|x:\windows\system32\cmd.exe /c echo test :)

hide+wait|Program Title|x:\windows\system32\cmd.exe /c echo test :)

hidewait|Program Title|x:\windows\system32\cmd.exe /c echo test :)

hidenowait|Program Title|x:\windows\system32\cmd.exe /c echo test :)

hide+nowait|Program Title|x:\windows\system32\cmd.exe /c echo test :)



normal|Program Title|x:\windows\system32\cmd.cmd /c echo test :)

normal|Program Title|x:\windows\system32\cmd.bat /c echo test :)



[registry]

"HKLM",0x1,"Tmp_software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes","System,0","System,204"





[association]

pdf,x:\windows\system32\cmd.exe



[shells]

Program Title|x:\windows\system32\cmd.exe

Hi NightMan
Until you find a better way
For making association work compile this au3 file to UpdateAssoReg.exe
Encode it in "Standard-3-Config.script" in Build folder
and add just after

#autorun

TXTAddLine,"%TargetDir%\windows\system32\winpeshl.ini","autorun.cmd","Append"

this line

TXTAddLine,"%TargetDir%\windows\system32\winpeshl.ini","UpdateAssoReg.exe","Append"

@pedrole15

good workarround!
but your code works only for VistaPE on bootable CD's, and not on bootable USB-Sticks.

so if you change in your code:

$CDRoms=DriveGetDrive("CDROM")

$PsyhCD=""

If NOT @error Then

	For $i = 1 to $CDRoms[0]

		if(FileExists($CDRoms[$i] & "\vistape.cd"))then $PsyhCD=$CDRoms[$i]

	Next

EndIf



If&#40;$PsyhCD <> &#34;&#34;&#41; then 

$CDDriveLetter=StringLeft&#40;$PsyhCD,2&#41;;

with this, then it works also on USB-Sticks (my $BootDriveLetter is your $CDDriveLetter)

$Drives = DriveGetDrive("ALL")

For $i = 1 to $Drives[0]

	$Drives[$i] = StringUpper($Drives[$i])

	$DriveType = DriveGetType($Drives[$i])

	If DriveGetType($Drives[$i]) = "Removable" or DriveGetType($Drives[$i]) = "CDROM" Then

		If DriveStatus&#40;$Drives&#91;$i&#93;&#41; <> &#34;NOTREADY&#34; Then

			If FileExists&#40;$Drives&#91;$i&#93; & &#34;\VISTAPE.CD&#34;&#41; Then

				$BootDriveLetter = $Drives&#91;$i&#93;

				ExitLoop

			EndIf

		EndIf

	EndIf

Next

BTW:
i use booty's USBStick.script for making bootable VistaPE USB-Sticks. Works very well.

creating an environment variable 'CDDrive' doesn't make sense, because you have to reboot the system to have access to this variable!

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

@NightMan
i think, your vpeldr.exe also search just for CD-drives and not for other removable drives.
On booting from USB-Stick i get the message from vpeldr.exe 'Searching disk with programs...not found. Trying start "wpeinit.exe" and searching again...'

regards,
fuwi

NightMan - looking on the config file you propose have only one suggestion - whenever possible avoid references to X:\ inside the new config file - using a variable value would make wonders when placing VistaPE on hard disk.

Nuno Brito
It's only example for file format, all already working, i need make more test and will upload it very soon Now we have to config files, on in x:\windows\system32 for default setting and program in boot.wim, and one (or more) at cd (dvd, usb, hdd), we can change basic setting without rebuilding boot.wim, registry ad file association work very good, all program can be detected automaticaly... next is drivers, i plan move it from boot.wim to disk (not SATA drivers)... and i think about interactive mode for vpeldr for changing setting during boot process

Ok, nice to hear that you're on top of these things!