8 replies to this topic

[patsch]

---Service Note-----
Topic Closed,

Relevant lines in script are okey and confirmed working fine by both admins of the project with post 2 and post 4.

patsch turned topic to his personal affair. We have community section for that.

Lancelot
---Service Note-----

the code in the script is

[Process-CoExWOW64]

If,Not,ExistFile,%target_win%\SysWOW64\#1,CopyOrExpand,%SourceDir%\i386\W#1,%target_win%\SysWOW64\#1

imo should be

[Process-CoExWOW64]

If,Not,ExistFile,%target_win%\SysWOW64\#1,CopyOrExpand,%SourceDir%\i386\#1,%target_win%\SysWOW64\#1

[Galapo]

But if you have a look at, say, a line such as the following

CoEXWOW64,avifile.dll

without the prefixed w you'll get an error because avifile.dl_ doesn't exist in the source but instead you'll find wavifile.dl_.

Is your x64 source different to this?

Regards,
Galapo.

[patsch]

yes, my source is different to this ... I find avifile.dl_
I'll try to get another source ... but I thought that the source I use is untouched ...

[Lancelot]

@patsch

There is no such bug with the script.
LiveXP section is to support LiveXP Project. Use LiveXP to build.

[patsch]

ahh, thanks a lot Lancelot ... your answer is as good as always ... but
I did use LiveXP
I did use XP64bit as source ... so thanks again for your great comment. As in the Win7PE SE section: you can greatly motivate others in testing and reporting. I think LiveXP is now dead for me because I do not want to have such comments again.
Thanks a lot

[Lancelot]

Thanks a lot.
It is the first good news of today

[patsch]

Do you think your post is funny?

Just for your info ... I was searching for a 64Bit PE that works with my test tools for graphic cards. Because of the problems I had with directX and the non-function on some hardware machines with win7pe se I wanted to try livexp 64bit cause of the integrated directx script.
I opened this thread because the script did not work, nothing less nothing more.

I don't know why you had a go at me the second time ... did I attack you in this post? Did I flame on the project? Or something else?
I put a question mark at the end of the thread title because I really don't know if that was a bug or not. The only thing I can say now is that my source is likely different from the original winxp64 (look at the answer to Galapo's post) ... but I thought this was an original one

I now know that you do not like me ... ok, but then please do not answer on none of my posts. I can live with that.
But with your behaviour you disqualify yourself, your work on this project and the winbuilder comm.
There are other people who read your posts and if one reads how you react on questions or reports without being attacked it doesn't cast a positive light on you.
For me that is not the way one should react in a community and this is not a way to motivate others to work in this community.

[MedEvil]

I now know that you do not like me

That's not true. Lancelot hates everone!

I don't know why you had a go at me the second time ... did I attack you in this post? Did I flame on the project? Or something else?

See that's the problem right there. Didn't Lancelot ask loudly enough to get attacked and be flamed the first time?

[Lancelot]

@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