Win10XPE Project General Discussions

Hi

 

Code: [Select]

If,ExistFile,%MainPlugin%,AddVariables,%MainPlugin%,Variables

appears to be working in both builders, thanks

Thank You -
 
That Helps Me Out With A Better Way Of Doing AutoUpdate XPEPlugins
Especially with XPEPlugins using %ProgramVer%

Revised XPEPlugin(s) - Program File Version & Update Via Interface
Beyond Compare-4
Disk Genius
CPU-Z *
GPU-Z
HWinfo *
HW Monitor

* Denotes > /Projects/MyPlugins/

Thanks for keeping real

(Genius_XPE.Script) DirCopy - Failed to copy directory [%BaseDir%\Temp\Disk Genius_x64\Disk Genius_x64\dos] to: [%BaseDir%\ISO\Programs\Disk Genius_x64]: Unknown error

After Getting Error Message:
Verify Exists Directory > "\Win10XPE\Temp\Disk Genius_x64\Disk Genius_x64\dos"
Verify Exists Directory > "\Win10XPE\ISO\Programs\Disk Genius_x64"

Here is what exists after that error message:

\Temp\Disk Genius_x64\DGEngSetup.exe - Nothing else in this folder and no "dos" folder.
\ISO\Program\Disk Genius_x64 - Directory exists but is empty.

This is probably an old version of DG script, I just downloaded the newest one and it works.  Explanation below.

15 characters is the max name length

Yes and the computer name cannot contain the following characters \ / : * ? " < > |
I added a Section to take only the first 15 chars and replace the special characters
With a Warning in the Log if the input Computer Name is changed
Thanks for repporting 

(Attachment Link) to be copied into \Projects\Win10XPE\Features folder

Thanks!

Hi mbstech

re Genius_XPE.Script

This app is built into the project now, not a standalone plugin.

are you sure?

anyway, just tested DiskGenius Ver 510653 with latest XPE and get no build errors
using link --> Disk Genius

APT you are correct.  Sorry about that, I got a bit confused apparently.  When looking at the plugin list on the forum, I accidentally looked a "HD Tune" and seen it had the * at the end, which denotes it is included in the project.  For some reason I had HD Tune on the mind when researching Disk Genius issue.  I grabbed the newest files and it is working.  Sorry for wasting your time on this confusion.  Was a rough week last week.

Has anyone else seen this error when trying to launch Macrorit Disk Scanner program in PE?  I have it set to run with RAM instead of USB.



I have noticed that if I browse to here:  XPE\Temp\Macrorit Disk Sanner_x64\macrorit disk scanner_x64\DM.st

I can launch that with no issues and this D drive error doesn't happen.

@James
In plugin Beyondcompare-4 section [Launch_Program] doesn't work because %HostOSArch% is empty, it has no value, neither x86 nor x64.

Code: [Select]

Set,%Tapp%,%GTemp%\%ProgramFolder%\%HostOSArch%
//OpenDir,%Tapp%
Start,,%ProgramEXE%,,%Tapp% ?????

(deleted)

In plugin Beyondcompare-4 section [Launch_Program] doesn't work because %HostOSArch% is empty, it has no value, neither x86 nor x64.

Hi Oscar,

It is by design, you must build once to get Launch buttons with multiarch xpeplugins work. 

I see. Thank you.

I was aware of that issue, and it was by design, but it also has unintended consequences (although first report)
So, I have proposed a move of that process to ChrisR..

but it also has unintended consequences (although first report)

It should be expected consequences...

As being the inventor of "Launch" button on all plugins since only x86 times :

Not first report, It was reported 9 or more years ago before the current forum ...
 Because of some idiots that always sabotage projects,
  and some forum amigos at those times, which simply cause wasted time,
   It took 3 years to solve that with step by step development

Technically, %SysType% (from Nightman times) and %OSArch% (after JFX or ChrisR) was variables of hostarch.
 Later I develop %HostOSArch% for the Launch button and other things.
  (not implemented to Win10XPE the way I designed, It was added like %SysType% or %OSArch%)
   No failure report around since 7 years or more, and now again. 

   As I wrote before these are Expected results and there will be more.... 

     Just another short note to history, that is all.

Thanks for the History Lesson...
History also shows XPE Processes being followed or duplicated...

So to Quote Myself for XPE History

I was aware of that issue, and it was by design, but it also has unintended consequences (although first report)
So, I have proposed a move of that process to ChrisR..

History also shows XPE Processes being followed or duplicated...

History also shows James follow and duplicate 100 or more plugins, delete others names with an excuse of Fabricated Incompatibility.
  James like follow Win10PESESE other SE and Gena processs.  but with failures, and as written before there will be more. 

So to Quote Myself for XPE History

very funny indeed. Knowing you for years I already know you like to hear yourself a lot.


Anyway, keeping short, what you all wrote after my Reply #731 is about other topics "Fabricated Incompatibility Win10XPE Discussion"
http://theoven.org/index.php?topic=2697.msg31993#new

Launch buttons James duplicated have expected failure and written as a historical post, that is all.

I love this conversation.

I think the conversation is disrespectfully and used in a manner to discredit Author. 

XPE has been out almost a year - and we recently received the first report of a bug regarding Launch Button..
It was never considered a bug because you need to make a First Run to populate project and feature variables...
A fix has been proposed to the Author in regards to that Launch Button bug report...
That will fix the Launch Button bug - but it still would not populate the project and features variables...

That is how Feedback and troubleshooting 101 is used..
Verify the complaint...
Suggest a fix...
the rest in Authors Hands..

So the Fix for this non critical Launch Button issue has been addressed..