Please do NOT waste your time reading this topic
If you have a livexp related problem/issue
1) 'Post Reply' to current topic
2) open a new topic at LiveXP section
Post 1 have not updated for a long while, there maybe misinformations IF you read, Read with care
Welcome to the 1st main post,
When things here solved or added etc., it is deleted in 1st post, so dont surprise if it gets shorter
When new things are found and documented it is added to 1st post, so dont surprise if it gets longer
As you already can create a new topic, You can also post any issue if you want to this topic.
(also issues are collected by me to this topic when noticed)
***I cant find time to check post #1, some of the things on post #1 maybe fixed in time, still this is a nice topic/archive to catch/clean/remember bugs and development notes about LiveXP.
If "Master Issues" now empty, we are all happy
****Issue: Vista (i guess mostly x64)
"Driver Signature Enforcement" stops mounting utilities (ex: vdk.exe) prevent working. We need a creation of .img/.vmdk files with a way like wimpack without mounting.
Solution: Vista64 Users, disable "Driver Signature Enforcement", there is plenty of methods on net you can find with a quick google-fu
****Issue: fbwf upper limit (full) issue
when user uses all available space provided by fbwf, LiveXP lock down.
This is important for automatic AV updates after PE boots. A warning made here
*Probable Future solution: a monitoring tool that monitors fbwf and stops writing anymore file at a limit (say free space 3mb) (maybe another added feature for setresolution )
*Solution for now: WARNING, do not use all space provided by fbwf
Windows DEP is not tolerant of WinBuilder and vdk. Switch off DEP and LiveXP builds OK. niche99 post26 probably warning for Vista Users
ps: xp-->no problem, 2k3-->set settings to xp settings, Vista-->switch off dep
Future hope of Solution:
I hope one day we will have a DEP checker
****Issue: msi.script - Something missing - reported post 1097
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
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
Change the Explorer.Script's Verify item as you think how it is needed!
I'll copy the result into nativeEx_barebone.
**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)
having fat option back (reason post 1241 )
**TODO: for create iso and bootsdi script
(System,SAVELOG, not available with wb076, first with wb077b1)If,%pCheckBox5%,EQUAL,True,Begin StrFormat,DATE,%myDate%,"yyyymmddhhnn" System,SAVELOG,%target_win%\logfile%myDate%.html End If, ... ,ShellExecute,Open,%Tools%\mkisofs.exe ...++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)
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)
I have a first experimental LODR-pack for dotnet3 working.
Translating this to the standards we discussed here is way beyond my skills.
Anyway - if anybody is interested in translating this to LiveXP I can try to explain.
The procedure for grabbing the required files is a nightmare.
Once created you need a wim about 170 Mb and about 30 Mb of free space in NTFS-formatted X:
**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
**TODO: Script project
my wimL idea with optiononal LOD (first written in sanbarrow's topic)
It is nice to read nice things from you Peter,
Some more things about 'Midway' to clarify,
With 'Midway' i mean: this is not absolutely sanborrow's method, this is a method that will suit Nuno and Galapo's (and mine) concerns tu use LOD (+wimL)
And i highly believe, many things i wrote can be done automatically by api without changing a script a lot like FastStoneCapture.
With my idea only adding 2 (or 3) options to the begining of [process], and rest can be done by api
For wimL: 1 interface button and 1 line to the beginin process section for wimL -->will be enough for most scripts like FastStoneCapture--->rest can be done by api
For wimL+LOD: 1 interface button and [LODextra] section for creating .cmd file and related shortcuts for loading on demand
Maybe somebody who understands what i mean can post with better english, if nobody understands, than lets drink beer .
Anyway, , i will be glad to be the first tester :) for the result of work you will do with sanbarrow. Good luckGalapo, Thank you for help by post 64
I cant use wimpack.exe on builds for now, but it is better to put half of my idea (the other half will be load on demand) (all idea is at post 23 and post 26) in a simple script
can you check this:
this is NOT a ready script, look two // MISSING - STAGE in script file
i hope it is more understandable now? what do you think ?I need to figure out to pack with wim by using winbuilder, i love this idea but i will finish later ......
Here's basic syntax for wimpack.exe:
wimpack.exe targetdir folder_in_targetdir_to_pack cmd_file system_exclude_file_list
Eg: wimpack.exe c:\target program c:\target\cmd.cmd none
Note: in targetdir a folder 'i386' must exist, to which the outputted WIM will be generated. cmd_file is necessary in this case only to avoid program error.
+++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 thistitle Start LiveXP_RAM.iso find --set-root --ignore-floppies /LiveXP_RAM.iso map /LiveXP_RAM.iso (hd32) map --hook chainloader (hd32) bootIt will be better to have also thistitle Start LiveXP_RAM_ISO.iso find --set-root --ignore-floppies /LiveXP_RAM.iso map /LiveXP_RAM.iso (hd32) map --hook chainloader (hd32) boot
**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
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
So have made a try with my Sigmatel once more:
using DrvImp.exe I have success only in that case if the extracted files of the driverpackage located in the right folder,
in my case it is '%ProgramFiles%\IDT\WDM'
if the files located in any different folder: DrvImp failed - copy the .ini files into system32 doesn't help.
DriverForge can successfully install the driver from any location - seems it is no matter where the files are located,
(the '%ProgramFiles%\IDT\WDM' is correctly created during the installation proces)
also have success not using DrvImp.exe or Driver Forge,
but simply updating the driver of an Unknown device via Device Manager
(Properties > Driver > Update Driver...)
pointing to the .inf
in this case also no matter where the files are located
(the '%ProgramFiles%\IDT\WDM' is correctly created during the installation proces)
-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
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:
-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
Mini info about 'symbolic link', 'hard link' , 'Directory Junction' from howtogeek
Java Runtime Environment
Wouldn't it better to have sharing->permission option for folders?
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.
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...?showtopic=5421 but no answer yet.
anybody have a messeger 4.7 plugin for bartpe?
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.
------End of post issues-----------------
(for some reasons, i put them in the end of post #1)
****Issue: 4 - !WBVerify.Script ( Peter's script )
If a user forgets to show source and starts building with winbuilder, wb asks for source and user shows the source
wbverify dont understand this and gives this error
with 2nd run, this error dont happen anymore
****Issue: 4 - BuildModel.Script ( Peter's script )
defined post 329
target is X:\ in both cases
****Issue: 4 - BuildModel.Script ( Peter's script )
New SR option with build model not working (post 333)
****Issue: !WBVerify.Script ( Peter's script )
Verify Should Check UAC on Vista machines to be sure UAC is enabled for winbuilder.exe
Solution Temporary: During tests Vista directly asked for UAC permission for winbuilder.exe which i press YES so no problem occured creating iso, i advice all users to give UAC permission
Here is a note in bugtracker
Here are some links on net:
****Issue: BootSDI - Wimpack - !WBVerify.Script ( Peter's script )
Verify Should Check "Driver Signature Enforcement" on Vista64 with a trial/test (test/trial because some other utilities may disable "Driver Signature Enforcement" by faking Vista64 that DSE is working )
Solution Temporary: I am sure Vista64 users can google-fu and find ways on internet to disable DSE
Here are some info:
*Press F8 on Windows boot load, you get Vista Advanced Boot Options, select “Disable Driver Signature Enforcement” to bypass driver signing check on vista
u3-usb support--sth missing: http://www.boot-land...?showtopic=6495
I hope we can have tests with a usb device which one of our frequent user have
****Issue: Vista Format
behavior with vista format tool (vista 32bit) that causes wimpack stage fail (fixed with change on script) but still i dont know how to calculate when ntfs is choosen.
Look: post56 - post70 - post72 - post74
Solution Temp: Wimpack script now formats FAT32 as default so no problem for a new user. If someone who uses vistahostos and ntfs, than for now he should increase freespace in vmdk script till he get enough freespace.
++Galapo Post 972 to make fix on code
***Issue: Font support
I use english source, but i need turkish font support fully
By dera's advice (post 246) i created a script for myself (i use xpsp2eng as source, turkish keyboard) by taking regs from a xpsp2x86 eng OS which is configured to use TR. Here it is (ONLY WHEN ENGLISH SOURCE USED to have TURKISH FONTS enabled): http://lancelot.winb...Eng-Font_TR.rar
Maybe an auto_clssupport script, and besides a manual one, Masters decide for more permenant solution
++we have hungary and cyrillic support scripts, better to unite all in one
***Issue: RestoreBase.Script SaveBase.Script ( Peter's script )
A bug report from saydin77
i never use SaveBase.Script (or restore) , but looking inside the script i can confirm saydin77's findings.
here they are:
"use current build" works properly
"use predefined standard build" cause errors
in [do-list] section this fixes needed regedit -> regedit-api , taskman -> taskman-api
there are path changes for qEmuNIC_RTL8139, UniversalVideoDriver,VirtualBoxNIC_AMD_PCNET ...
2 variables dont work properly %PE_Programs% + (saydin77 dont remember the 2nd one)
and when restorebase used, the things that should be in "program files" are in basedir. (or restorebase.script directory)
Thanks to galapo, now there is "Create backup archive of Live XP" option, use this instead of RestoreBase.Script and SaveBase.Script.
***Issue: (as galapo wrote "it would require a re-write and change of logic by the imdisk driver" here no recent expectation for solution , SetPageFile script will mostly suit demand for pagefile which will be nice to use essentially with pendisk)
how to make a page file with imdisk, so pagefile can created in ramdisk or bootsdi. (look Galapo's posts)
how to make a page file for livexp for the utilities that needs a pagefile --> look mini solution
maybe minimum 6mb, max(large number) of a pagefile under ramdrive (B:\) can be nice,
look link for the issue
also i tried SetPageFile1008.cab but couldnt suceed.
ps: you can try this script to see if pagefile works correctly. http://www.boot-land...?showtopic=5493
For info about pagefile subject look:
post 102 Galapo
post 186 Galapo
SetPageFile script , works nice with realhd, but dont like to work with imdisk as galapo described in posts.
+ thunn wrote a script PePageFile.Script for pagefile, but it doesnt work with livexp 'cause of reason galapo described.
+ mounting images fail when images are in ramdisk, probably 'cause of reason galapo described.
+ Oleg gave info "The problem is that the ImDisk drive is not created early enough in the boot process to use the normal settings for pagefile." , also Oleg informed at swapadd topic, at post12 by Galapo and post13 by dog, it still fails to create pagefile on ramdisk with LiveXP.
***Issue (Minor) hostnic script ( Peter's script )
hostnic script look post 218 (follow link), post 219, simply there should be something that should stop hostnic to install when there is no fbwf or bootsdi. Also there should be a warning in gui of hostnic. (like driver import pe script)
------End of post issues----------END----
I find this in livexp registry, it was not there before (i checked a long time ago before)
because in HIVESFT.INF this line exists:
and HOJOPE does not 'convert' %ProgramFiles% to %programfiles%.
***IssueX64 !WBVerify.Script ( Peter's script)
Read post 1055
lineIf,%cnt%,NotEqual,0,ShellExecute,Open,"%VerLog%",""should be sth like:System,FILEREDIRECT,OFF If,%cnt%,NotEqual,0,ShellExecuteex,"Hide","cmd.exe","/C %VerLog%" System,FILEREDIRECT,ON
***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)
here is a test script: http://lancelot.winb...mgBurn_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
Not Compatible with x64hostos, only works right with x86hostos
Compatible with x64hostos and x86hostos:
shows %ProgramFiles% on x64
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
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
Points tho the system directory when a 32 bit app is brocessed by 64 bit OS
---Here is a min list:
ps: death link new variables are introduced by peter,
**PeterPSC comment about xp64 from hereLancelot comment as an answer for Peter's comment: I am a happy x64 user. Maybe i am happy because i am a fool, but still i am happy.
Suggestion to all x64 users:
- Offer your PC at ebay.
I'm sure you'll get a good price, because there are enough fools thinking that they need it.
- Buy a good old x32 at ebay.
I'm sure you'll get it for good price, because there are enough fools thinking that they do not need it any more.
I would like to help and take your issue into the debugger.
But I only have x86-32. And just to buy 64 for 'playground' is too expensive for me.
Maybe I can give some help, if you 'eccessevely' explain the environment (no links please! )
An after a while here
After a long time, I realized that I did not understand the real sence of your question:
In case of Wow64:
<shortcut request> -> BuildModel -> Shortcut : OK
<shortcut request> -> API -> BuildModel -> Shortcut : NOK
I today ordered a 64 bit PC.
Maybe that helps (not the order itself, but using the PC after delivery)
***Info to remember
new cdimage parameters sometimes gives this: http://img60.imagesh...29/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)
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...?...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
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
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
***Why i get this error
"This archive was built with a different version of ZLBArchive (v-2094635132) Extract File, %ScriptFile%, %AFolder%, %Archive%, %Target%"
Simple: redownload the file
Reason: There should be something like
[EncodedFile-Files-xxxxx.7z] lines=75 0=N3q8ryccAAMIsu ... ... 75=ai7EwzeVf4L ...No other lines, no missing line between 0 and 75. If there is something else error occurs.
Reference: info from psc on this topic
Winbuilder.exe bugies i noticed
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
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,
Should be fixed more properly with using System,FILEREDIRECT,OFF - cmd - System,FILEREDIRECT,ON in case in future someone uses x64 viewer.
**Winbuilder.exe boot-inf support bugies-missing
i got bored about this subject, idea is making inf compatible to both winbuilder and pebuilder. But sadly i cant trust Peter saying one day "upppps, i forget nodelete function of ; lines with .inf files" which is very essential for .inf files, people familiar with .inf files will understand my feelings. Instead i only make simple .inf files with no need of ; lines for that purpose (no problem with using // in some sections of .inf files).
-- winbuilder.exe MUST NOT delete ; lines of .inf files (probably solved now)
-- winbuilder.exe MUST NOT delete empty lines of .inf files
-- some shortcut issues reported before
-- there should be an option for shortcut creation (maybe yes maybe no, if no i need to have ability to delete folder if not exists)
-- gui dont work as it suppose to be ( post 40 )
-- i still insist to have winbuilder=0 at [pebuilder] section to disable winbuilder.exe to read .inf file which will make life easier. Reason is, i know convert complex .inf files to .script and i make 2 packages to distrubute.
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!
Original post from here:
ps: Following post #3 and post #5 is to look or to remember solved issues.
(seperate posts (#3 and #5) due to forum quote rule: "You have posted more than the allowed number of quoted blocks of text" )