Topic: Help me understand why this (DIY) plugin doesn't work  (Read 614 times)

Re: Help me understand why this (DIY) plugin doesn't work
« Reply #20 on: December 10, 2019, 02:22:42 PM »

flexy123

  • Jr. Chef
  • **
  • Date Registered: Dec 2019
  • Posts: 16
I spent several days on this with Win10XPE, no dice. I think I tried everything.

Then I used Win10PESE, and it's *working* the first time I built with everything in it.

Same exact ISO, where I enabled .NET3 on source, .NET 4, DirectX 11, 12, nothing special.

Saying there must be something fundamentally different with Win10XPE. Whether this is an issue with XPE, or with the program I don't know.
Just to let you know.

« Last Edit: December 10, 2019, 02:24:26 PM by flexy123 »

Re: Help me understand why this (DIY) plugin doesn't work
« Reply #21 on: December 10, 2019, 02:58:12 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Was your testing on x86 or x64 ???
I believe it was OK on x86 .....

Test OCTv4 on x86 Basic Build w/ Directx & Full NetFx2-4 & VC++8.9 Runtime (although already default requirement in script)
I believe this should test with positive results...

Then swap to x64 Build and see if away of these files are Required (via Additions)
« Last Edit: December 10, 2019, 05:16:14 PM by James, Reason: attachment removed »

Re: Help me understand why this (DIY) plugin doesn't work
« Reply #22 on: December 10, 2019, 03:35:58 PM »

flexy123

  • Jr. Chef
  • **
  • Date Registered: Dec 2019
  • Posts: 16
Yeah I know. I am always building x64 only. So both images were x64.

I am *guessing* that some component(s) could be missing on XPE, but I wouldn't know which one without doing even more crazy debugging. (Processmon etc.)
(I had built the older where it didn't work with anything I could think of, DirectX,  even directx runtime, all .NETs (verfified with the tool), SysWoW64, SxS etc.)

Also, for getting it to run on PESE I didn't need to copy additional files, I simply 7-zipped the program folder, no need for any custom files in Windows. (After all, that should all be there already)
« Last Edit: December 10, 2019, 03:43:57 PM by flexy123 »

Re: Help me understand why this (DIY) plugin doesn't work
« Reply #23 on: December 10, 2019, 03:45:38 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
the issue would appear to be missing SysWoW64 files on x64 Build...
Yes the base files are different between the 2 projects..
DirectX and DOTNET are more likely up to date on XPE...
edited post above with Host Syswow file list
« Last Edit: December 10, 2019, 03:48:08 PM by James »

Re: Help me understand why this (DIY) plugin doesn't work
« Reply #24 on: December 10, 2019, 04:28:30 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
I did a compare on Host vs PE wow64 files

unmark this line in script
Code: [Select]
//If,%Architecture%,Equal,x64,ExtractSectionFiles,%ScriptFile%,AddFiles6432

then replace the following
Code: [Select]
[AddFiles]
\Windows\apppatch\sysmain.sdb
\Windows\assembly

[AddFiles6432]
\Windows\SysWOW64\l_intl.nls
\Windows\SysWOW64\rasman.dll
\Windows\SysWOW64\security.dll

See if that helps
Success.......
« Last Edit: December 10, 2019, 04:52:29 PM by James »

Re: Help me understand why this (DIY) plugin doesn't work
« Reply #25 on: December 10, 2019, 05:09:40 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Also, I would like to thank you for taking the time to test, I know it involved a lot of time, effort and persistence
In the long run it sometimes reaches the desired result...

OCCT v4.5.1.99 - XPE Plugin
« Last Edit: December 10, 2019, 05:52:04 PM by James »

 

Powered by EzPortal