Hello dear guest!

Boot Land is a community driven pc software site established since 2006 and focused on recovery/backup boot disks, research of Microsoft Windows 2000/XP/2003/Vista/7 install/deployment/lease/antivirus/antispam tools, customizing Microsoft Windows PE administration systems and even learning how to recover computer data from disaster situations!

How about joining our boot disk community? So do it. Life's short!

  - You get free access to our newsletter with all the interesting buzz about boot disks
  - We share publicity revenue with everyone who wishes to participate at the forums
  - Publicity is never, never, never displayed to members (along with many other cool things)
http://boot-land.net/register


184 Pages V   1 2 3 > » 

Pinned: [Package] PEFactory
Lancelot
Posted on: Yesterday, 06:01 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


@paraglider

QUOTE (paraglider @ Jun 16 2010, 02:27 PM) *
I don't see it. Only use of targetwow64 in commonapi is in Arch_Check:


the result of arch check triggers the behaviour of require_file

giving example:
before there were any multiarchitecture projects, following was sufficient for a 32bit application script

CODE
[Process]
unpack,,%setupFile%,True
require_file,msvbvm60.dll


but what will happen on x64 build (none wow64) with these codes,
64bit version of msvbvm60.dll will be extracted with also 32bit application.
1) 32bit application will not work because without wow64 it cannot
2) even if there is wow64, 32bit version of msvbvm60.dll does not exists since copied one by script is 64bit.

to solve 1st problem, it is obvious a variable needed to determine target pe behaviour to x86 applications, and psc also admits that fact today by reinventing a variable that is already used on all projects. (=> you logically can not agree with psc) (besides none of psc project have feature to support wow64, if package was for other projects, than follow other projects common variable, if package for nativeex only, than does not need ===> nooo, better to implement a self made redundant variable silently inside other projects if they get the fish, this is the way he likes)

I asked this to Max_Real Qnx since at that time Leopard was the only project that supports multiarchitecture (well livexp was also building multiarch that times, but not public, according to gentleman rules I asked Max Real QNX), and he invent a new variable %x864% with a method of determining this variable which we use even today. It was you who said %x864% is confusing, hence variable name changed to %TargetWOW64% which is more meaningful. It seems you forgot old topics why this variable (and following api) needed where you take part. Well they are old topics because since things made there is NO issue, only 1 man making annoyance.

Max model is simple,
at 1st steps of building, after finding sourcearch set TargetWOW64 equal to sourcearch PERMANENTLY
Set,%TargetWOW64%,%sourcearch%,Permanent
on x86 builds, value stable x86, hence for x86 projects value can be easly added to script project as a stable value.
on none x86 builds, if there is another script that adds wow64 ability to the target build, than this script will change %TargetWOW64% value x86 PERMANENTLY
hence following build is aware the condition.

First problem solved,
with this solution following works half
CODE
[Process]
If,%TargetWOW64%,Equal,x86,Begin
unpack,,%setupFile%,True
require_file,msvbvm60.dll
End

above still gets msvbvm60.dll x64 version from source.

Since we have a variable now, there might be following solution by inventing require_filewow64 api

CODE
[Process]
If,%TargetWOW64%,Equal,x86,Begin
unpack,,%setupFile%,True
IF,%sourcearch%,Equal,x86,require_file,msvbvm60.dll
IF,Not,%sourcearch%,Equal,x86,require_filewow64,msvbvm60.dll
End


well, above does not look nice and simple.

Instead api call arch idea found and developed by Galapo which is much much much superior than above.

as a result to make a 32bit application script that supports multiarchitecture projects following change

CODE
[Process]
unpack,,%setupFile%,True
require_file,msvbvm60.dll

===>
CODE
[Process]
arch,x86
unpack,,%setupFile%,True
require_file,msvbvm60.dll


fits. I hope you know can see the direct relation between arch and %targetwow64%
One should be an idiot to object such a good solution. Truely it was that idiot who told me to practice a solution for the sitation by telling me he would follow if okey. Well it is working okey but after sometime this idiot decide to sabotage all projects by either wb coding or misinformed objections, usually lieing, and practicing games to insert his variables to other projects (ex: this topic package) . Since these actions are supported by also Nuno, Long while ago I decide no need to object anymore around. But after my absance this idiot intentionally writing WRONG and LIEING information around with naming me for a loooong while forced me to write this post. At least this topic proves that this idiot now accept (after all objections in past) there is a need of a new variable in his project, but instead of using %TargetWOW64% which is used by ALL projects, reinventing another one just to be cooparative (check a cooparative topic around that demonstrates how cooparative (sarcasm) and childish (hi JFX, I remember you) behaviour this idiot have. (well idiot is from above post of psc, not my personal choice, I prefer better descriptive words but decide to follow the one he prefers calling himself)

anyway,
I contact to all admins,
Administrators of multi-architecture projects agreed to the solution using %TargetWOW64% by understanding why needed, only 1 not agreed saying his project not need that saying it is redundant which shows he could not either a- understand b- did not like some other find a fundemantal variable name than him. (practically psc also right, nobody use that projects for x64 builds, and win7 parasite (not project) part naturally does not support x64, hence no problem for him that time)
Administrators of single architecture projects add %TargetWOW64% variable setting to x86 to support multiarchitecture scripts.

ps: I was the only admin of win7rescue project that times, and made adjustments to win7rescue, someone should remember times of annoyance when people write they need a method to write app script to fit all projects. One should be idiot to take maintance responsibility of a project and keep it with its so far found missings and bugs reported to its topic.

This opened gates to developers making multiarchitecture scripts.

You can remember that above solutions created without existance of a wow64 script demanded by me having a farsight thinking, but we did not wait so long, a hero come from Germany called JFX who made wow64 scripts for LiveXP and later pe2/3 world, and scripts with arch lines worked with pex64wow64 builds nicely :>:>.

Till than, a set of improvments made on arch since we have a practice on pex64wow64 builds by the help of JFX script. Differences of arch section on capi's are due to capi versions (revisions). When project admins or end users update their capi (I do not mean capiex, instead of capiex nativeexapi should be more proper but lie is a habit hard to leave), they will have required improvments.

I hope not to see further LIEING comments about what I've done so far, but it is only a fake hope, I well know the beheviour of liers around. In the past I worked hard to solve issues of apps scripts to share between projects (which i guess i was the only one), starting work with JonF hence made a perfect syncronisation with VistaPE-Capi to share scripts and when Joshua around with Win7Rescue. Later with new multiarchitecture projects, I also worked hard on developing above perfect solution for the new generation multiarchitecture scripts with Galapo and Max and ctmag. (psc ignored that times saying he does not need that). With PaPeuser helping on testing on win7pese x64 builds also made required changes on a set of apps scripts to easly share between projects. I am happy to see scripts working nicely and so far made adjustments fits all conditions too. It is a good story of success with team work.

and reminding, what i wrote above is not about current topic's package.
This package, besides lieing goal, demonstrate how idiot brain work (for the ones who carelfully reads) on dictating other projects some permanent variables and incompatible methods to insert his scripts to other projects.
It is usual topic games by usual topic gamer regulars, changing subject to something else (like targetwow64 etc) instead of talking about topic (package), and to do this replying with misleading and lieing posts to point Lancelot, LiveXP or anyother in future.
ex: since galapo comment on saying %targetwow64% is redundant, check how topic goes, a good demonstration.
Because of misinforming topic that have goal to increase excitment, I get some communication from some users that does not check what is inside asking me how to use.
After checking i well explained them this is not what they expect, it is only fooling others with exciting title.
Shortly:
what package does can be simply made by: on vistape-capi, cache the build just before OtherOS, and make other builds with this caching continuing with changing scripts after OtherOS.
(well this is what i do easly more than a year on livexp , thanks to olegpov for pointing)
with using bad workaround, some further improvments maybe done by replaing registry on pe2/3 builds.

Main improvments with pe2/3 should be made to shift settings from mainconfiguration to somewhere near end (create iso) IF admins of pe2/3 projects interested in such a cache solution, which i believe would be nice. There are logical reasons for making these settings at begining with initial design of nightman. Better pe2/3 project admins comment on such needs on these changes. (!!)

Above package not needed at all if wb could process faster than slower. It simply caches build at some point, and do processing later. This is also what i do personally on livexp for my testings since olegpov pointed the issue a year ago, but practically not needed much. But since wb is slower and pe2/3 projects bigger with their files and registry, need of a workaround arise (like caching, or using ready reg files, or using smaller script adjustments, a set of scripting techniques etc. ) by end users since they can not fix wb. It is sad (well truely comic) to see wb development instead of fixing their builder, trying to workaround like normal end users.

As usual Well done (->sarcasm)


Additionally:
there were previous posts about another incompatibilty again lieing accusing livexp. Truely livexp took nightman model for adding grub4dos bootloader, hence supporting grub4dos scripts around. We did not put an OtherOS folder to project to demonstrate, we only followed footsteps of nightman to get a compatible solution to all pe2/3 projects , instead of reinventing and dictating them. Since than livexp is the only pe1 project that supports grub4dos scripts. If something compatible to pe2/3 on this manner, it is also compatible to livexp unless someone forces conditions to make something incompatibleÁ


Further, I may get some personal posts here which would as usual only serve to distracts facts written on this post and some others, by lieing, misinforming, misleading info to misinform (like previous post, facts are covered by pretending his usage of inserting a redundant variable by setting permanent, truely %targetwow64% used directly on build scripts (not apps) and this can not be covered by capi, a redundant line to capi only added to fit 1 project admin unlogical objection ) or by personal comments which are being done so far. (=>post games) . Have fun on reading them.


@psc
STOP lieing using my name and STOP using my name with lieing to distract a subject.
I guarentee you, Wait sometime, be sure there MAY be some other project admins or users which you will be able to fool, lie, push out etc. like before me. For a loooong time I do not join anymore to wb developement topics or your shity project topics.
Pretend to be like a mature man.
  Forum: NativeEx · Post Preview: #102525 · Replies: 40 · Views: 1,389

File-system redirection
Lancelot
Posted on: Jun 13 2010, 10:52 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi target_practice,

To me this is the best thing ever happened after firadisk and winvblock cheerleader.gif cheerleader.gif Thanks a lot. worship.gif

QUOTE (target_practice @ Jun 13 2010, 01:00 AM) *
I'd like to know whether this is worth pursuing or not.
Sure it is thumbup.gif And be sure after stable release your script will be in livexp distribution when you flag stable cheers.gif (I guess Galapo would agree too)

works nicely on cdfs and with fbwf thumbup.gif with using b: ntfs.

My initial tests was giving confusing confused1.gif results to me (xpsp2enux86), and caused some wrong reports and a set of unneeded things (ex: net start wink.gif), after a long tracking w00t.gif of tests at last i found clap.gif

Iniside fbwf script i use for tests, for some historical reasons (check post 5 and further), I was changing pagedpoolsize to -1 (default is 0) to have available fbwf >128 at hand (personally i never need bigger than 128....)

RegHiveLoad,WB_setup,%target_sys%\setupreg.hiv
RegWrite,HKLM,0x4,"WB_setup\ControlSet001\Control\Session Manager\Memory Management",PagedPoolSize,-1
RegHiveUnLoad,WB_setup

I found setting PagedPoolSize to -1 (0xffffffff) is currently poisoness for vjunc, using vjunc.exe results with error screen hence junction not works.
this may (or may not) have relation to wimboot too (my limited time ended here), there is an entry in wimboot script that sets PagedPoolSize -1 if value greater than 128.

I hope above info helps, I am very excited thinking how far your development can go further.

Thanks again cheers.gif
  Forum: Project forge · Post Preview: #102310 · Replies: 20 · Views: 1,202

CloneDisk
Lancelot
Posted on: Jun 12 2010, 09:39 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi erwan.l,

I am one of a silent reader of current topic, trying to learn things following informations on your development way of clonedisk....

converting vhd image from WindowsXPMode_zh-cn.exe (.vhd extracted out from .exe) to .img results with a very biig .img file during operation, in the end shrinks to 3.00GB.
i could not open this .img file with winimage (8.0.8000 , probably old now) or with imdisk (==>I am sure i am missing sth , maybe imageoffset etc. truely i have not start self training on these stuff much and not much time these days)

my initial trial for convert operation was on a disk with 20gb free space, ended with clonedisk "writefile error:112", at this point there were was no option but only to click ok and ok and ok....., so taskkilled..... maybe for such condition having an abort option with deletion of unfinished extraction can be a fine thingy or what ever you decide.... (+there are no abort option after conversion started)
edit: + if one uses clonezilla systemdrive with some freespace but not enough, it *may not be desirable to fill all space for our bad os windows wink.gif which may* start responding sloww.

further, during operation, since it took long, clonedisk inside gui disappeared (title remains, I mean ingredient (=tabs, file-tools selections)), with disappeared i mean turn to white/gray. http://img441.imageshack.us/img441/3600/20100612142244.png . I know from my experiences of some other tools this is not important and i wait until operations finishes, but may cause misunderstanding for some others.

This is what i can do to support with my limited knowledge for now, Thanks a lot for all cheers.gif

edit:
  Forum: Project forge · Post Preview: #102202 · Replies: 124 · Views: 16,811

Sardu + Livexp bootsdi.IM_
Lancelot
Posted on: Jun 12 2010, 07:53 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi again dsolmon,

sardu naturally can not cover all options of livexp build, this is not a sardu fault , nobodies fault, for other options than create iso, you should make some manual arrangements.

Defination:
your build is: cab compressed bootsdiimg with wimpack, using 2k3 setupldr loader (not patched), rest using default options
.\i386\BootSdi.im_
.\WIMs\WIMs.vmdk

your goal is: making multiboot cd including above livexp build

Further:
you tried sardu, but sardu provides option for create iso, not above condition. I guess sardu option is for livexp.iso and you renamed livexp_ram.iso to livexp.iso to make sardu work. If so nice try, but as far as i read, sardu not designed for that.

More:
If you were making a bootsdiimg build without wimpack, adding LiveXP_Ram.iso directly to the media (ufd/cd etc.) with menu.lst of "title LiveXP_RAM.iso - direct and/or mem" variant should be working.

But, Since you made bootsdiimg build with wimpack, this will not work,

through working solutions, follow this one which i belive would be shortest/easiest:
1) Extract LiveXP_RAM.iso\WIMs\WIMs.vmdk and delete WIMs folder in LiveXP_RAM.iso, in the end inside LiveXP_RAM.iso you should not have WIMs folder
2) put LiveXP_RAM.iso and \WIMs\WIMs.vmdk to your multibootcd
multibootcd\LiveXP_RAM.iso
multibootcd\WIMs\WIMs.vmdk
3) use title "LiveXP_RAM.iso - direct" variant that boots LiveXP_RAM.iso in cd


Also:
there is an option on wimpack which says
"Place VMDK container outside ISO in %ISODir% (output to be placed at the root of another drive, eg USB stick)"
which does same things above (1-2-3) at build time.

Advice:
it will be easier to test using ufd by
copying LiveXP_Ram.iso that contains only bootsdi.im_
and copying \WIMs\WIMs.vmdk
to ufd, and make your menu.lst of ufd to boot LiveXP_Ram.iso.


Above is one of the methods that is a safe and easier than others i know. I hope it helps. (and if not i hope some other good people around would help you further)


btw, you really gambled nicely but house wins loleverybody.gif

additional: I do not use ultraiso, but check maanu's adviced setting to avoid some ultraiso thingies which i read around, post 7 maanu



@davidecosta

Hi davidecosta, you can not make settings with sardu to automate these procedure(s), They are very highly flexible, all (or most) possible options provided by project are optional to fit end users requests. That is one of the reason livexp users love livexp but not good for sardu design.

As far as i read , sardu design is okey, you made adjustments for LiveXP.iso which is the iso file sardu expects. (this is what we call create iso build, which is default option)

It seems dsolmon, giving a shot, gambled with sardu by changing LiveXP_Ram.iso to LiveXP.iso...(guess rest), since sardu not designed for that condition house wins wink.gif

An idea to avoid future gamblers in sardu/livexp casino, as a precaution, you can put a check to see if the iso file pointed to sardu is a ram boot image or not by checking exitance of following files.
CD.iso\I386\SYSTEM32\cmd.exe
CD.iso\AMD64\SYSTEM32\cmd.exe
If one of them exists, than it is create iso, and sardu continue its operations, if not I am sure you put a nice warning screen
"Gambling is not good smile.gif , house (=sardu) always wins"

Well, on the other hand making own house always is a good idea too, still house always wins thumbup.gif


cheers.gif

edit: above cmd.exe precaution method may not work with some build options livexp have, but since they are rarely used it is still a good precaution cheers.gif
  Forum: Sardu · Post Preview: #102199 · Replies: 7 · Views: 349

Lancelot
Posted on: Apr 22 2010, 09:01 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


as written on relevant topic,
you provided wrong info, insisted on it, and misleading us to wrong direction, causing time lost.
After Nuno moved topic to LiveXP section, Galapo also asked topic to be moved to winbuilder beta section, but instead I decide to close giving info at post 1 for all users, and informed Galapo.

There is no personal actions on my decisions. I do not write agressive personal posts, annoying posts, changing a project manually providing wrong infos to their admins causing lost of time or post games on any topic. But some others sadly do giving foolish names to others on different topics, accusing how bad project livexp is being complex, advertising his/her projects on livexp section !...... and so on.

But so far, LiveXP users are happy with LiveXP. We get less and less issue reports through years showing our perspective of evolution and moderation on project and livexp section is right.

I am not sorry for commenting bravely on winbuilder development or users behaving badly. I never used admin powers to crush or split users topics into pieces or respond with unrelevant answers. If not doing these shows I act personal, well done.
  Forum: Community forum · Post Preview: #98655 · Replies: 33 · Views: 1,820

Lancelot
Posted on: Apr 22 2010, 07:33 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


@jaclaz,

Even if explained reason at post #6 happens again, next time i will not thumbup.gif cheers.gif
  Forum: Community forum · Post Preview: #98645 · Replies: 33 · Views: 1,820

Lancelot
Posted on: Apr 22 2010, 07:10 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


QUOTE (patsch @ Apr 22 2010, 08:58 PM) *
but this is a surprise because this is a source from the computer center of my university (and they say they have it from MSDNAA) as a support member told me by mail
yep, I read similar things (university-msdnaa-told me) before.

I checked all my sources
2k3 x64 SP2 English_Standart
2k3 x64 SP2 English
2k3 x64 SP2 Spanish
2k3 x64 SP2 German
2k3 x64 SP2 French
2k3 x64 SP2 Chinese Simplified
2k3 x64 SP2 Chinese Traditional
2k3 x64 SP2 Korean
2k3 x64 SP2 Italian
2k3 x64 SP2 Portuguese Brazilian
2k3 x64 SP2 Russian
2k3 x64 SP2 Japanese
XP x64 SP2 English
XP x64 SP0 English

same file same place , i386\wavifile.dl_

however, even we do not support or test multilanguage x64 sources for now (since not testing, a warning will be added, As far as i remember there were other differences between english and none-english sources but currently LiveXPx64 is at evolving stage), I will try to find more XP x64 language sources to check.
  Forum: Community forum · Post Preview: #98642 · Replies: 33 · Views: 1,820

Lancelot
Posted on: Apr 22 2010, 06:52 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


@jaclaz
From my perspective: topics is not warez etc. but seems overreacting of patsch due to personal relations but not LiveXP. Hence I pointed patsch to community forum.

@patsch
QUOTE (patsch @ Apr 22 2010, 08:41 PM) *
in your Service Note ...
Again sorry for that, now fixed.

QUOTE (patsch @ Apr 22 2010, 08:41 PM) *
not mine as I posted ...
There are too many modified sources around. On LiveXP maintaince we lost lots of valuable time figuring out source is not valid billy source. It will be no surprise yours is one of them, hence both Galapo's and my comments (post2-4 of relevant topic) about this subject is right. We can not change project for unvalid sources. But we react a bit more flexible than other PE1 project for such sources.
  Forum: Community forum · Post Preview: #98640 · Replies: 33 · Views: 1,820

Lancelot
Posted on: Apr 22 2010, 06:37 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


QUOTE (patsch @ Apr 22 2010, 08:20 PM) *
a.) please write my name correctly
accept my apology for that. If you can point where written wrong I would love to fix.

about subject:
QUOTE (patsch @ Apr 22 2010, 08:20 PM) *
german source
german source also contains \i386\WAVIFILE.DL_ file at source. However for now LiveXPx64 is only tested with 2k3/xp-x64sp2enu sources, to protect end users from wrongs builds I will take precaution.

For the rest (shortly): you (or any other) are welcomed to support, as far as not changing events to personal affairs. You seem to be too eager for that. Take your advices for yourself.

edit: fix
  Forum: Community forum · Post Preview: #98634 · Replies: 33 · Views: 1,820

[Solved - sort of] WimPack Problems
Lancelot
Posted on: Apr 22 2010, 05:47 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi niche99,

About wimpack issue:
Good to hear things working nice there. However there is really something** unidentified yet that happens time to time. Since you initiate this topic I again tried to chase this event. So far I can say it is not related to path name or lenght (unless you use a 4096 lenght path rolleyes.gif ) , still making some tests to reproduce thumbup.gif

above log warnings/errors come from winbuilder debug log:

On winbuilder-->tools-->options ==> there is debug log checkbox which you seem to enable manually.
If you disable this checkbox these warnings/errors will not appear.
They are not real warnings or errors. cheers.gif
  Forum: LiveXP · Post Preview: #98631 · Replies: 11 · Views: 785

Lancelot
Posted on: Apr 22 2010, 05:36 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


@patsch

initially you post report of xpe_directx_x64.script to win7pese topic,
and since you insisted to the reply of Galapo,
and since you did NOT provide any info saying you are using LiveXP to build (or log, or source info, nothing), I naturally thought you are testing script with win7pe reporting here, as usual after testing and checking with valid x64 sources.

Sadly you replied with a personal post providing only 1 useful info, you are using LiveXP.

I am not joking, I am very happy if unfriendly or postgaming people do not come by here and write annoying things around (and yes, I do not like them). You can spend some time to see how we deal with the issue reports by checking some topics here.

Bye.

edit: topic closed
  Forum: LiveXP · Post Preview: #98629 · Replies: 8 · Views: 600

Lancelot
Posted on: Apr 22 2010, 01:12 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Thanks a lot.
It is the first good news of today thumbup.gif
  Forum: LiveXP · Post Preview: #98610 · Replies: 8 · Views: 600

Lancelot
Posted on: Apr 22 2010, 12:47 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


@patsch

There is no such bug with the script.
LiveXP section is to support LiveXP Project. Use LiveXP to build.
  Forum: LiveXP · Post Preview: #98604 · Replies: 8 · Views: 600

KAPE WinPE Builder
Lancelot
Posted on: Apr 21 2010, 10:47 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi jjjjoseph,

First of all thanks for sharing smile.gif.

kape alpha do not support hostosx64 for now, hence give this
http://lancelot.winbuilder.net/5F/20100422010319.png
2 methods to fix:
kape x64 wink.gif
kape x86 having getting access to restricted folders and registry on hostosx64

so I installed waik to a virtual machine xp32bit to test kape smart.gif

Bad things:
not for people who like to have full power on building process
new package integration not possible within kape (not easly expandable)

Good things:
nicely and fastly makes the iso file thumbup.gif
not tested but it is good to provide an easy to use driver integration thumbup.gif
good design to ask user verification when changes made thumbup.gif
Easy to understand and use menus (%95) thumbup.gif (%5 is only minor thingies, no need to mention)
After %5 we can say Kape is ready for even newbies which I feel not much time will pass thumbup.gif (I may start to suggest to friends after this %5)

I guess "Good things" shows the main goal of Kape, hence not providing "Bad things" is understandable. And since I now have a version to test, I can now understand why you do not want distribution freely, and for such a builder I agree this is not required.

As a result I would like to say you guys mostly reach your goals. It is a nice builder for an easy/fast/usable pe2/3x for rescue operations.

cheers.gif
  Forum: FireSage applications · Post Preview: #98572 · Replies: 26 · Views: 3,990

ShutdownPE
Lancelot
Posted on: Apr 21 2010, 01:12 AM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


QUOTE (homes32 @ Apr 21 2010, 03:08 AM) *
did you use the eject checkbox?
absolutely no.
  Forum: Development · Post Preview: #98456 · Replies: 62 · Views: 4,959

[Solved - sort of] WimPack Problems
Lancelot
Posted on: Apr 21 2010, 12:47 AM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi niche99,

boot-land attachement malfunction these days, as a result I can not get your log at post #1.
I tested your script selection arrangement by using loooong paths with small numbered of selected scripts....

Here is a mini test package,
http://lancelot.winbuilder.net/5F/201004210328.7z
extract to the failed place you previously reported,
put required files of wimpack to ...\Workbench\Common\Wimpack\
and as usual big blue rolleyes.gif

If failure, please provide log file using www.2shared.com thumbup.gif
  Forum: LiveXP · Post Preview: #98451 · Replies: 11 · Views: 785

WinXP Live boot over network HELP Please !!
Lancelot
Posted on: Apr 20 2010, 06:28 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi www,

well, I feel there are too many custom changes on your build which is hard to understand what is going on.

get a copy here (updated 2 days ago)
http://winbuilder.net/download.php?view.35
make you build, see how things work.

to fix krokodox script (Krokodox_util.script), open script with notepad and change [Process-Files] section with following

CODE
[Process-Files]
Echo,"Expanding files from source..."
require_file,chkdsk.exe
require_file,xcopy.exe
require_file,tftp.exe


and use
LiveXP-->Drivers-->5 Ramdisk==>Win2k3_Ramdisk script by providing ramdisk.sys , setupldr.bin files. (2k3 sp1)

cheers.gif
  Forum: Tftpd32 · Post Preview: #98423 · Replies: 6 · Views: 1,151

I have not USB icon in my computer
Lancelot
Posted on: Apr 20 2010, 06:08 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi Jaclaz,

Do we need to explict the obvious !!!! . To me subject changed out of topic to hot-plug feature of LiveXP which works nicely. Anyway, as i wrote before the left suspicions from post 1 gone with 2nd post of pamela67120 (post 9) which also pointed by Galapo. End of issue wink.gif.

and nope, I do not induce you ......, I clearly know you will never test. I thought it would be better to give you some verbal written informations time to time so you can comment a bit more properly on LiveXP related things with the increasing knowledge, that is all. thumbup.gif
  Forum: LiveXP · Post Preview: #98419 · Replies: 30 · Views: 1,354

I have not USB icon in my computer
Lancelot
Posted on: Apr 20 2010, 11:23 AM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


QUOTE (Wonko the Sane @ Apr 20 2010, 12:20 PM) *
That means that the stick is seen as "fixed" instead of "removable".
which was already known from post 1 , 2nd picture.
I had some suspicions for the reason (driver or ....) with lack of info at post 1, besides advicing mounstorpe was accurate for solution.
As Galapo indicated 2nd post of pamela67120 decrease suspects to 1.

since you do not know, download or test LiveXP, here more info to you:
dummy filter script not selected as default distribution,
there is Clear, Bolded info on script's interface where we expect end users to read when they decide to change a default settings of distribution. There clearly advices usage of MountStorPE.

cheers.gif
  Forum: LiveXP · Post Preview: #98407 · Replies: 30 · Views: 1,354

KAPE WinPE Builder
Lancelot
Posted on: Apr 20 2010, 02:09 AM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


QUOTE (jjjjoseph @ Apr 20 2010, 03:49 AM) *
We chose to limit distribution of our apps from our domain simply for the sake of being able to track and measure the interest level of each product.
It is really limiting (to me) to anyone making a ready legal distributable pack build without being able to provide the builder itsself...... Well I hope you can find a midway solution which fullfils also your goals.
QUOTE (jjjjoseph @ Apr 20 2010, 03:49 AM) *
we place no limitations on the use of our freeware apps, and have no intention to change freeware apps to commercial... ever!
Good to hear that.
QUOTE (jjjjoseph @ Apr 20 2010, 03:49 AM) *
Wait, everything we make is verrrrrry good! wink.gif
which I truely hope.
QUOTE (jjjjoseph @ Apr 20 2010, 03:49 AM) *
Actually, I want to make sure I clarify that our current suite of apps were created for in-house use, as the need arose, and we are simply sharing our work with the WinPE world rather than letting it sit on the shelf collecting dust.
I approve that.
QUOTE (jjjjoseph @ Apr 20 2010, 03:49 AM) *
Our goal is to provide a service which this community finds valuable, but we could easily place them back on the shelf if the interest level isn't there.
Do not worry about that. My personal philophy for such things, "If something is good, really good, people will find it on net as long as you provide, even if you use an uncommon language" wink.gif. (but nicer to read english rolleyes.gif )
QUOTE (jjjjoseph @ Apr 20 2010, 03:49 AM) *
This explains the reason we ask for a little feedback, the apps are already in use by us, but we don't want to invest/waste time unnecessarily if the technology isn't going to help anyone.
Well, at least it would help me and you can be sure my interest on this is very real and high. Sadly there is not much things to compare. As an end user and tester (hence supporter) I had some bad experiences which I do not want to live ever again. I hope you understand my concerns & suspicions.
QUOTE (jjjjoseph @ Apr 20 2010, 03:49 AM) *
As mentioned earlier today, we are working to clean-up the code a little and expect to provide something for review in a few days. Thanks again for the feedback.
This will help more to figure out what is the main design and ease the support. It is very hard to talk about something that not exists and I feel I already provide good info on previous post under this conditions.

My Best Luck cheers.gif
  Forum: FireSage applications · Post Preview: #98394 · Replies: 26 · Views: 3,990

ShutdownPE
Lancelot
Posted on: Apr 20 2010, 12:54 AM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi Homes32,

today for another case, I was having real hardware tests hence also tested shutdownpe (tested both v8 and v7 of script with same results)

Shutdown was slow probably due to the error, and in the end there comes a screen with:
(sorry not picture, I write on a paper with pencil wink.gif )

Title: Windows - Drive Not Ready
Text: The drive is not ready for use ; its door may be open. Please check drive and make sure that a disk is inserted and that the drive door is closed.

I have 2 suspects in mind:
1) my floppy drive is enabled on bios, but I do not have a real floppy hardware, hence on LiveXP I have an unaccessable A:\
(ps: this was an accidantel bios setting, but maybe helped to find something)
(edit2: check here )
2) my raid0 disk(s).
3) ......

edit: no usb device connected during tests.

cheers.gif
  Forum: Development · Post Preview: #98388 · Replies: 62 · Views: 4,959

I have not USB icon in my computer
Lancelot
Posted on: Apr 20 2010, 12:27 AM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


Hi Galapo,

Besides It is obvious it will not work on tests, I just tested to post accurate information:
no need suspect, pamela67120 will fail with above refered other project by using refered USB_Support.Script containing .reg file having conditions represented.

Honestly, I see no true benefit of this .reg file for overall (general) usage. To me, it is only an annoying .reg file at boot time which "sometimes" may increase hot-plug working possibility and still needs mounstorpe (or similar) utility to be perfect for end user... I really do not think we need that.

As you indicated, 'Removable Devices Combo' works on most cases with hot-plug and mounstorpe there to fix other situations which NO hot-plug can fix.

But If you say boot time .reg needed, than you are the boss.
  Forum: LiveXP · Post Preview: #98387 · Replies: 30 · Views: 1,354

I have not USB icon in my computer
Lancelot
Posted on: Apr 19 2010, 11:28 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


@Galapo

nope, it is another thing and very clear at post 1 of pamela67120 , and more clear in pamela67120's later posts. Sadly somebody is busy with advertising his project ranting2.gif than trying to figure out what is going on.


@pamela67120

ignore my previous post about restarting explorer.
with your conditions,
after adding driver letter,
* To access drive letter with explorer, you should restart "explorer shell" (tested)
OR
* Instead of restarting explorer shell, probably using another file management utility will help too (ex: a43)

However, as written on my post 3, why not use mounstorpe instead of making manual , unconfortable interactions.

LiveXP development put MounstorPE of kare (CD-RW) as default to the project since 2008 in order to help users avoiding conditions like yours.
with great help of olegpov and kare's support, MountstorPE starts up as default with LiveXP since I guess 2009-03 hence perfectly and automatically avoiding such situations.

As a result we do not get reports like yours for a loong while. wink.gif.

I advice you to use mounstorPE like written in my initial post (post 3), it will automatically do the things for you thumbup.gif
  Forum: LiveXP · Post Preview: #98379 · Replies: 30 · Views: 1,354

I have not USB icon in my computer
Lancelot
Posted on: Apr 19 2010, 10:25 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


@pamela67120

after manually adding drive letter, close all explorer windowses, and start explorer again wink.gif.
  Forum: LiveXP · Post Preview: #98372 · Replies: 30 · Views: 1,354

I have not USB icon in my computer
Lancelot
Posted on: Apr 19 2010, 10:22 PM


Frequent Member
****

Group: .script developer
Posts: 734
Joined: 8-May 08
From: Turkiye/Izmir
Member No.: 15,072


@ jaclaz,
QUOTE (Lancelot @ Apr 19 2010, 10:03 PM) *
Meanwhile, as usual, I will retest when I find time. smart.gif

I just retested (without mounstorpe) and confirm ufd plugging in/out with conditions you write working fine with LiveXP.
As I wrote before, pamela67120 condition is different which was not mentioned on his writings. Either adding manually like you write or using mounstorpe will be helpfull to pamela67120. (like written in my initial post (post #3) of current topic). cheers.gif
  Forum: LiveXP · Post Preview: #98369 · Replies: 30 · Views: 1,354

184 Pages V   1 2 3 > » 

New Posts  New Replies
No New Posts  No New Replies
Hot topic  Hot Topic (New)
No new  Hot Topic (No New)
Poll  Poll (New)
No new votes  Poll (No New)
Closed  Locked Topic
Moved  Moved Topic