something missing with msi.script (Projects\LiveXP\Basic\Shells\Addons), but WHAT????

Here is the test routine:
1) enable msi.script
2) enable fbwf or bootsdi
3) Download
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) from here and add it to livexp cd.
4) in LivexP double click vcredist_x86.exe


ps: (maybe relevant maybe not, in my tests ScriptingCore.script , ScriptingSup.Script, mmc and dipe selected too)

to overcome for specific example, i manually extract vcredist_x86.exe so VCREDI~3.EXE went out. double clicking VCREDI~3.EXE gives same error.
Than i manually extract VCREDI~3.EXE and vcredist.msi+vcredis1.cab came out. double clicking vcredist.msi worked.
ps: also same issue happens with "Microsoft Visual C++ 2008 Redistributable Package (x86)_SP1"


probably in most .exe cases that installs .msi this error occurs, any idea for solution???????


edit: ps: "vcredist_x86.exe /q" works successfully.

Lancelot Personal TODO list:

**TODO: check how livexp works when source is xp64

**TODO: Finalize Batch script, check if bugy fixed described at post 1240 note starting with @Peter (psc) X 2

**TODO: Basic-Shells-Explorer.script ---> "Use DLL init at build time rather than at boot time" is checked
a verification needed ( info from post 1233 )
-Source CD language is different from host OS language
-Source CD architecture is different from host OS architecture
-In Explorer.script the checkbox "Use DLL init at build time rather than at boot time" is checked
than use dll init at build time should be unchecked
ps: post 1235

**TODO: paraglider hwpnp request
post 1201 Paraglider can make a setting for hwpnp with a text on gui saying "Press 'Esc' to close Hwpnp" !?
note: fxscrpt solved the issue on LiveXP-hwpnp and updates made to hwpnp + xpnp aio script,
to reproduce the issue: enable hwpnp , disable xpnp-aio, disable qemu option at hwpnp, disable acpi on qemu
to reproduce the issue: disable hwpnp, enable xpnp-aio, disable acpi on qemu
(hwpnp 15 , xpnp-aio 35)

**TODO: wimpack
having fat option back (reason post 1241 )

**TODO: for create iso and bootsdi script
(System,SAVELOG, not available with wb076, first with wb077b1)
++also pack with .7z
7za ... %target_win%\logfile%myDate%.html ... %target_win%\logfile%myDate%.7z /// filedelete %target_win%\logfile%myDate%.html
ps: an example available at nativeex, dont forget to change %target_win%\logfile%myDate%.html

**TODO: change script.project interface (remember Nuno's advice)

**TODO: change scripts interface
Start Menu Folder (blank for default)
or
Start Menu Folder

**TODO: nic gpu script project (kare)

**TODO: prepare a tutorial to boot LiveXP from C: mentioned here at post 78 and at post 80

**TODO: script.project - Maybe "Clean Temporary Files" if exists automatically

**TODO: dotnet3 script or lodr pack with help from sanbarrow (post 487)

**TODO: app script:
remind and test my request about StartMenu .lnk creation folder (Start Menu Root) post 341

**TODO: "DriverForge for DPS LAN support on LiveXP"
idea first introduced here
put option to start penetwork after adding lan (also sleep10 seconds before starting and no sleep when penetwork starts)

**TODO: BootScreen for LiveXP (changes required with createiso and bootsdi script)
Follow tutorial here and Take and edit Shrin's picture: How to place your own Boot screen in XP setup CD - Shrin
also remember old bartpe plugin picture when editing .


**TODO: Read WinBuilder DBMS Beta Client Packages

**TODO_Personal: Verify special files
Verify files at startup to prevent user, expecially for setupldr.bin and ramdisk.sys for bootsdi and createiso (maybe size or version check for them, 2k3sp1 files are all same bytes) + fbwf with create iso (etc) Example

**TODO: Theme - I dont think it is possible but check this
http://www.boot-land.net/forums/index.php?...ost&p=53737

**TODO: Script project
my wimL idea with optiononal LOD (first written in sanbarrow's topic) Galapo, Thank you for help by post 64I need to figure out to pack with wim by using winbuilder, i love this idea but i will finish later ......
+++With Nuno's idea at post 54, unpacked files maybe kept in %GlobalTemplates%\wimlpack_Files\%scriptfilenamestr%_%scriptfileversion%\ folder

**TODO: Create ISO adding
An option to create a iso which works with ramdisk.sys method (iso in iso) for some purposes.
Reason: Currently with grub4dos we can boot this
It will be better to have also this

**TODO: Create ISO adding
*fbwf not start automatically option. Kare says acronis10ti needs 96mb, which results not working with 128mb ram computer when fbwf enabled (fbwf on boot+%25imdisk).
*a utility (or a set of shorcuts to start fbwf with different options (%10, %20, %30 .... )
*can fbwf be stopped and start

**TODO: Ramdrive
resize ramdrive, i guess increasin is not a problem
for decreasing maybe with an option saying "minimum as possible" which result with 5 mb space. My idea is creating a new ramdrive (ex: K:) with the size of B: + 5mb, than copy files to K:, remake B:, and copy files back to B:, remove K: (+maybe refresh shortcuts)

**TODO: A mini introduction to new users to show:
%target_win% %target_sys% %source_win% %source_sys% %GlobalTemp% %ProjectTemp% %GlobalTemplates%

**TODO: Reorganisation of scripts
kare's idea (sharing him) an extra in apps for essential scripts for optimal needs like:
penetwork, notepad, taskmanager, mmc, regedit, offbyone (for opening html files and minimal internet), addcmd utils, 16bit support and a very small picture viewer, maybe we can register some common picture extensions with FreeFSCapture (not sure)
This is also a good idea to say user "disable all apps script, and enable only apps\essential"

**TODO: Winbuilder script selection idea
when clicked on folder on winbuilder, it disables or enables all scripts. What about a mid option, example: imagine no scripts selected under a folder, clicking first will enable only scripts that have download level lower than 2, this will help a lot for commercial scripts. With 2nd click all scripts selected. If this idea okey than for commercial scripts enableing on 1st click can be availabe when required license exists.

**TODO: Reorganisation of scripts
Read Nuno's post and other posts

**TODO: post #997 dipe bug to kare (reported to kare, will be deleted from my todo list when done

****Suggestions:

****Suggestion: wimpack
-an option to create wims out of BootSDI.img without .vmdk (I need this once during tests with JonF)

****Suggestion: Login Picture for LiveXP
Maybe login picture for LiveXP can be good
but script method dont work because NTOSKRNL.EX but NTOSKRNL.EX recopied by some scripts
so maybe on bootsdi-createiso stages

****Suggestion:
Maybe we need a button on main screen to make a minimum build to satisfy the idea of Peter post 29 , another midway

*********Suggestion - post 688 - 689 - 699
Shortly: Something needed for Vista Symbolic links and junctions to ease the access Vista disks using livexp
XP dont know which one is symbolic link and which on is not, also xp cant use the junction of vista
*->Maybe a command utility to show where folders are junked
*->Maybe an explorer (like A43) that has ability to show Vista Symblick links and junctions
Here are the utilites that i tried:
hardlinkshellext
-Reads Vista JUNCTION successfully
-But NO Vista SYMLINKD folders with chain icon, or dont give info about SYMLINKD folders.
-vcredist_x86.exe for Vs2005 Sp1 required which we dont have a script for this yet
junction-shell-extensions -NO Vista compatible
ntfslinkext -NO Vista compatible
winbolic -NO Vista compatible when used in xp, and no practical usage
ps:
Mini info about 'symbolic link', 'hard link' , 'Directory Junction' from howtogeek

****Suggestion
Java Runtime Environment

****Suggestions/Issue
Wouldn't it better to have sharing->permission option for folders?
http://img518.imageshack.us/img518/3648/1234zi0.png

***Suggestion:
Wouldnt it be nice to see local area connections default seen on right low of screen like in moa
Look the movie here , there is 3 network shown on right bottom of corner, probably 2 for virtual machine 1 real.

***Suggestion:
Messenger 4.7 can be on livexp too, 4.7 is supported by microsoft for a long time as MS gave messenger 4.7 with xp cd.
i asked here http://www.boot-land.net/forums/?showtopic=5421 but no answer yet.
anybody have a messeger 4.7 plugin for bartpe?

***Suggestion:
netmeeting , just for fun, nothing serious, i have emotinal feelings about netmeeting, it is still nice on lan, also nice for drawing pictures together over lan.

***X64 Related

***IssueX64 "3 - hivesFactory.Script" ( Peter's script ) - Have no effect on usage - post #717 and post #719

***IssueX64 !WBVerify.Script ( Peter's script)
Read post 1055
lineshould be sth like:

***IssueX64 Minor - shortcut creation ( Peter )
only this dont work with showing icons (put in ImgBurn.script + "Do not refresh shortcuts on ISO boot" enabled + autolocalisation enabled for tr)
Run,%BuildModelScript%,Add-Shortcut,"DE","#$pprogramfiles#$p\%ProgramFolder%\%ProgramEXE%","ImgBurn6_DONTWORK"
here is a test script: http://lancelot.winbuilder.net/5F/ImgBurn_TEST.rar

***Info_X64: Gather files
Script developers, Avoid using "gather files" as script option, when hostOS is x64 (or vista) gathering files may result in gathering wrong files. (like gathering a .sys file may cause trouble)
If you have to use "gather files" as an option:
--Put a check routine to check hostos before gathering files (Example: Acronis-DiskDirector10.script)
--Gather files to a folder under %GlobalTemplates%\xxx....xxxx\ so user can gather files with a hostosxp32 computer and copy files to his/her hostos.

***Info_X64: ProgramFiles - programfiles
Script developers notes:
(Old issue report is moved to post #3 as main reason and solution found by fxscrpt (Thanks a lot) at post 647.)
For compatibility, dont use ProgramFiles in script, use programfiles,
Also dont use CommonProgramFiles in script, use commonprogramfiles
Example:
Not Compatible with x64hostos, only works right with x86hostos
RegWrite,"HKLM",0x2,"WB-Software\Classes\http\shell\open\command",,"#$q#$pProgramFiles#$p\CD-Opera\Opera.exe#$q#$s#$q%1#$q"
Compatible with x64hostos and x86hostos:
RegWrite,"HKLM",0x2,"WB-Software\Classes\http\shell\open\command",,"#$q#$pprogramfiles#$p\CD-Opera\Opera.exe#$q#$s#$q%1#$q"
in contrast
Message,"#$pProgramFiles#$p",Information
shows %ProgramFiles% on x64
and
IniWrite,"%TargetDir%\%WorkDir%\CD-Opera\profile\Opera6.ini","User Prefs","Toolbar Configuration","%ProgramFiles%\CD-Opera\profile\toolbar\%ToolbarStyle_ScrollBox%.ini"
writes %ProgramFiles% to ini
probably this commands will be writing ProgramFiles(x86) in future which will be the right change with an unwanted result by hostosx64 user.
so better to use %programfiles% in scripts

***Info_X64:
this helps a lot
%ProcessorType% ('386', '486', '586', '2200', '8664')
'2200' is the Intel 64 bit, '8664' that one of AMD
%Wow64% (True, False)
True when the 32 bit WinBuilder app runs on a 64 bit host OS
%Wow64Dir%
Points tho the system directory when a 32 bit app is brocessed by 64 bit OS
(thanks fxscrpt)
---Here is a min list:
The Variables
%Wow64%
%Wow64Dir%
%Programs64%
The commands
System,REGREDIRECT
System,FILEREDIRECT
ps: death link new variables are introduced by peter,

***Info to remember

***Info
new cdimage parameters sometimes gives this: http://img60.imageshack.us/img60/2129/snap2nu0.png , nothing to worry, all files are in its place, just took picture and share here to document as command windows closes fastly.

***Info-Issues about OleSupport
ps: This issue is well known by masters, as this feature works mostly nice, it is kept (and i agree that) as an optional feature.
1) look post 344
devmgr.dll is not registered in PE (SP2 not visible, because pre-registered, SP3 not registered)
AND
devmgr.dll is unregistered on my host pc. (my computer > manage > system > no device manager)
(run regsvr32 devmgr.dll on host to repair)
2) 'Stray registry entry' http://www.boot-land.net/forums/index.php?...ost&p=45737
getting the following registry entry created on my local host machine when building LiveXP: 'HKCU\WB-Temp\System\CurrentControlSet\Control\Windows\ShellErrorMode'.
3) for me with 2k3x64 , i have an experimental IE6 script, which works after registring dll, but dont work with oleout feature (all same order)
**
a) one should remember the already known issue about olesupport.script that is well explained by medevil at post 299
and an Explanation post 16 of Peter from 'Stray registry entry' topic

***Info FBWF
Using fbwf enable, dera and i have different results. With fbwf enabled with 128mb, for a single file: dera can copy up to ~80mb, i can copy up to ~134mb
for more info: post 398,post 399,post 403,post 409,post 410
Also
fxscrpt
introduce a /minint trick and with previous posts (post 416) subject continues from post 491 (with dera's 80m limit) post 493 494 495 496 197 and at post 498 fxsrpt put a new script than continues 499 500 501 504 506

***Info Winbuilder variables
* Survey_wb_vars_20090108.pdf (Thanks to Maine Coon post 15xxx
* Galapo suggestion: project variables, defining for cross-project portability of scripts

***Why Exit dont work
Simple: you forgot a unhive in a script
Basic: WinBuilder after the Exit continues until all hives are closed.
Advice: Use exit after you unhive and dont forget unhive on other scripts
Example: http://www.boot-land.net/forums/index.php?showtopic=7907

Winbuilder.exe bugies i noticed


**winbuilder 075b5K
when code writing forgotten Begin
cause interface not working anymore (by adding spaces)
also adds spaces to sections too
i like adding spaces between begin-end
maybe to prevent use to be mistaken (fixing takes time)
-a warning saying (Begin section not closed)
-only begin-end inside the specific section, not outside


**IssueX64 Winbuilder.exe
clicking pictures on gui
Fixed with using cmd BUT
--Here is a test on x64hostos
Click on picture on gui of a script
you will see mspaint.exe opening the picture
check from taskmanager, you will see "mspaint.exe * 32"
which means C:\Windows\SysWOW64\mspaint.exe opened the picture,
not C:\Windows\System32\mspaint.exe
Should be fixed more properly with using System,FILEREDIRECT,OFF - cmd - System,FILEREDIRECT,ON in case in future someone uses x64 viewer.

You should not be surprised. I'm ALWAYS interested in issues improving WinBuilder.
But sometimes I need a

And if you (usually you do so) write something like 'just an idea' or 'not so important': Due to the amount of 'important' things I have to do here, I very fast will forget your post.

In the future: Do not go 'back' and if you think that something is important, tell us!
And, if like in the above sample, your post is decreased in my mind to 'nothing', increase it to 'important' again by a new post!
I'm not Mister God and can fail!

Peter

Original post from here: